Project Update

Version Update

1. 1) Why Need Version Update

   Version Update is important to keep track of every version of the system updates/changes. Knowing the what, who, and when of changes will help by comparing the performance of particular versions, working out when bugs are introduced (or fixed), and so on. Any problems that arose from a change can then be followed up by an examination of who make the change and the reasons they give for making the change.

    

   In our PhIS project, a new version update can be tracked using Software Release Note starting with Release version 1.0

    

   2) Types of Version Update

   In PhIS system we control version update based on three (3) categories as below:

    

   i. Bug / Defect log

2. List of issues reported by the user using connect manage system that has been resolved and verified by QC team. This version will be released to the user as soon as possible.

    

   ii. Change Request

3. List of requests raised by the user using connect manage and supported after JKN, Project Team and Change Request Committee review. This version update shall be released to the facility phase by phase based on the importance and urgency.

    

   iii. Technology Update

4. Technology update shall be introduced in response to the global market demand for the more advanced and user-friendly system. Examples of technology update are updated framework, compatible browser, system integration component and so on.

    

Any changes made will be updated in the new version. Details of the changes in the new version will be informed in the Release Notes equipped with Quick Guide. Users will learn to perform new processes or activities through the Quick Guide. Please click here to find out the latest version and Quick Guide.

In addition, users also have been provided with the user manual as a guide for using the system. The PhIS User Manual can help users carry out any activity in PhIS. Please click here for PhIS User Manual