1. Software Process Guidelines VIETTEL Corporation

2. CONTENTS I.Standard folder structure II.Review Process III.Data Repository IV.Naming Convention 2

3. 1.Adopting Agile Software Development approach 2.Iterative development, where requirements and solutions evolve through collaboration between self-organizing cross-functional teams. 3.Begin with a simple implementation of a subset of the full functionality and iteratively developing it (allows for late added requirement) till the full feature is implemented. I. Software Development Life Cycle 3

4. 4.Test cases are developed in parallel to requirement gathering and code implementation, following a V- model. 5.Bug fix should be done in the same iteration where it was discovered. 6.Quick adaptability to changes. I. Software Development Life Cycle 4

5. I. Software Development Life Cycle 5 Iteration N Iteration 1

6. II. Review Process 6 1.Review or inspection process is required for process documents (eg. SRS, SAD, etc) and code changes. 2.Provides a mean to capture and feedback errors (eg. missing requirements, incorrect code change) to author before base-lining the change. 3.Keeps a formal record and allows traceability.

7. II. Review Process 7 (1) Complete changes and schedule review meeting (2) Conduct review meeting and record action items (3) Baseline document/code (1) Checklist + check in document or code branches to repository + fill up peer review form - assign recorder/auditor - invite inspectors related to the changes or helpful with the review - specify document/code location and version + send out peer review form together with meeting invite (2) Checklist + author will go through the document or code changes in the meeting + action items have to be recorded into peer review form by assigned recorder Pass? Yes No (3) Checklist + update action items accordingly + auditor shall inspect the updated document or code changes to ensure that the action items are processed correctly + Manager or Lead will approve the change for baselining + All changes made shall be version-controlled and archived appropriately

8. III. Data Repository 8 1.Contains all project related and software team information. 2.Data needs to be organized in structural manner. Refer to “Repository_structure.xls” for the details.

9. IV. Naming Convention 9 1.Process documents (eg. SRS, SAD, etc) _.doc E.g. SRS-000001_LED_Indicator.doc 2.Test matrix Test_Matrix_ E.g. Test_Matrix_STP-000001.xls 3.Peer Review form for document changes Doc_Review_.xls E.g. Doc_Review_SAD-000001.xls

10. IV. Naming Convention 10 4.Peer Review form for code changes Code_Review_.xls E.g. Code_Review_DTS000001.xls

11. 11 Thank You…