project is properly organized, with an appropriate life cycle; development team members have defined tasks and responsibilities;

documentation plans are implemented; documentation contains what it should contain; documentation and coding standards are followed; standards, practices and conventions are adhered to; metric data is collected and used to improve products and processes; reviews and audits take place and are properly conducted; tests are specified and rigorously carried out; problems are recorded and tracked; projects use appropriate tools, techniques and methods; software is stored in controlled libraries; software is stored safely and securely; software from external suppliers meets applicable standards; proper records are kept of all activities; staff are properly trained; risks to the project are minimised.

a b c d e f g h i j k l m n o

No.

Risk

1 The developers get pressure

2 Increase the cost

Description As well as affect their spirit, the work of develops team will certainly increase, this will request more developers to complete the project. If the developers have pressure then it will affect their spirit and reduce the quality of their work. When the time decrease, it requires Tracer must enhance more developers or the work of developers increase, Tracer must pay more money for developers.

Not enough time to complete The project may be not completed on time because dont have enough developers to product develop project within 8 months. The spirit of developers is very important of development team, the time decrease Reduce the quality of TRAIN makes the work of developers increase 4 certainly, so the code of TRAIN web portal web portal project project may have more errors and reduce the quality of this project. The quality of TRAIN web portal project is reduced will make a doubt of GoForlt to The prestige of Tracer may be Tracer, decrease the prestige of Tracer and 5 decreased GoForlt Ltd does not want to cooperate with Tracer any more. The time is reduced so the process of The process of project may be project may be changed and affect to 6 changed project. 3 No. Risk Description As well as the working time is increased, the pressure on developers will be rised, and The pressure being pushed on effect their mental, may be reducing the developers efficient in work. And this will resulted in the request for more human resources to complete the development plan. With the project time-scale shortened, it requires TRACER team must encourage their The rise in cost staffs by giving bonus or extra money to them, and this will affect the overall project cost. Because of the changing in user The system can not be requirement, if the TRACER is lacks of complete within the timemanaging the time and software quality, in scale some case, the project may be not complete in 8 months time.

The Quality Drop

5 6 7

Engagement between developers Matter of security Loss of control

New developers are not qualified

Failure in organization

10

Changing the process of project development

The working time of TRACER developers is fully stacked, and their mental is very important for this work. There is another the risk that the Quality of the TRAIN System will be drop. Confliction between developers of different companies. Outsourcing to 3rd company can cause a loss in data. TRACER party depends on sub-contractors and can get delaying on delivery the final product. Developers need to be trained before they can get into our current activities. TRACER need to hire trainer or hiring high level developers It is hard to organize differents developes and staffs from different place or country of companies. Changing the current process by making more parrallel tasks can make TRACER staff to be confused and take time to get familiar with, they might also reduce their Productivity

Factor

People

Cost

Time

Quality

Quality

Process

Effect on Factor

Productivity

Cost

Time

Quality

Productivity Organization Organization

Cost

Organization

Productivity & Time

Risk Score

Description

1 2 3 4 5
Risk Score

Negligible Tiny effect Noticeable Serious effect Failure of project

Description

0-20% 20-40% 40-60% 60-80% 80-100%

Improbable Remote Occasional Probable Frequent

No.

1 2 3 4 5

Risk

Probability

Impact

The developers get pressure Increase the cost Not enough time to complete product Reduce the quality of TRAIN web portal project The process of project may be changed

36.00% 68.00% 1.00% 55.00% 25.00%

3 4 2 4 3

No. 1 2 3 4 5 6 7 8 9 10

Risk The pressure being pushed on developers The rise in cost The system can not be complete within the timescale The Quality Drop Engagement between developers Matter of security Loss of control New developers are not qualified Failure in organization Changing the process of project development

Probability Impact 46.00% 68.00% 1.00% 2.00% 10.00% 8.00% 7.00% 15.00% 1.00% 25.00% 3 3 5 5 2 3 3 2 5 4

No

Description

1 2 3 4 5 6 7 8 9 10 11 12

The project is well organized, with a suitable life cycle. Development team members have defined tasks and responsibilities; The group of developers has identified activities and responsibilities. The guideline planning is applied. Tracking the coding and document to ensure it follow the standard. Evaluation and audits takes place and properly carried out. Testing is executed and detailed carefully. Track and record all the problems that occurred. The system software should be kept securely. All the activities should be documented and recorded. All the staff should have the right skill and be well trained. Minimize risks of the project.

No. 1 2 3 4 5 6 7 8 No. 1 2 3 4 No. 1 2 3 4 5 No. 1 2 3 4 5 6

Deliverable Stage Customer / User Requirement Specification Software Requirement Specification Software Architechtural Design Software Detailed Design Software Production Transfer Operations Maintenance Plan

Software Project Management Plan Software Configuration Management Plan Software Verification and Validation Plan Software Quality Assurance Plan
Process Model Standards

Entry standards Input standards Tasks standards Output standards Exit standards

The System Size The number of Sub-System The System Type The Usage Pattern MTBF MTTR

Delivery items

1 Design

2 Source code

3 Deployment documents Deliverables

1 Design

2 Software Source Code 3 Software Design Document 1 2 3 4 5 6 7 8 9 10 11 12 Customer Requirement Software Requirement Software Architechural Design Software Detailed Design Software Production Plan Software Source Code

13 14 15 16

Quality assurance activities Create some templates that are up to date with new technologies that appropriate with typical website like TRAIN Define coding convention or following international coding convention of Java; choose a appropriate framework for project and assist all members follow the framework Structure of documents should follow the company standards or international standards; legibly and easy to use

Create the design template standards of TRAIN System. The user input to the software project is the user requirement documentation. They have to be identified first, and SQA staff should not allow a software development to begin unless it has been produced. SQA staff have to check that user have specified all the constraints that they want on the URS. The URS also have to define all the output interfaces in the Interface Requirement Documents. In TRACER, every project must create a Software Project Management (SPM) plan. This plan will declare the aim of TRAIN System, it include the statements of deliverables, required functionality, performance, maintenance, quality The aim should be arranged. SQA staff will examine all the objectives and check that plans are appropriate with them. Define the coding guideline follow the internation coding convention of programming languages (e.g C#, Java). Synchonize the framework guideline across the developers in TRACER Company. Structure of

TASK Project Management Project Monitoring Prepare Control plan Customer / User Requirement Specification Collect information and requirement from GoForIt Analyze GoForIt Requirement Review GoForIt Requirement and Purpose Software Requirements Specification (SRS) Translate from User Requirement to Software Requirement Software Architectural Design (SAD) Design the database for TRAIN System Design the interface for TRAIN System Finalize a Archtectural Design Software Detailed Design (SDD) & Software Production Planning a Detail Detailed design Coding Testing Formal review Implementation TRAIN System Demo TRAIN System Review 1 TRAIN System Final Release Transfer Operational & Maintenance Phase

9 10 11

WEEK 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

TASK Project Management Project Monitoring Prepare Control plan Customer / User Requirement Specification Collect information and requirement from GoForIt Analyze GoForIt Requirement Review GoForIt Requirement and Purpose Software Requirements Specification (SRS) Translate from User Requirement to Software Requirement Software Architectural Design (SAD) Design the database for TRAIN System Design the interface for TRAIN System Finalize a Archtectural Design Software Detailed Design (SDD) & Software Production Planning a Detail Detailed design Coding Testing Formal review Implementation TRAIN System Demo TRAIN System Review 1 TRAIN System Final Release Transfer Operational & Maintenance Phase

WEEK 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

TASK Project Management Project Monitoring Prepare Control plan Customer / User Requirement Specification Collect information and requirement from GoForIt Analyze GoForIt Requirement Review GoForIt Requirement and Purpose Software Requirements Specification (SRS) Translate from User Requirement to Software Requirement Software Architectural Design (SAD) Design the database for TRAIN System Design the interface for TRAIN System Finalize a Archtectural Design Software Detailed Design (SDD) & Software Production Planning a Detail Detailed design Coding Testing Formal review Implementation TRAIN System Demo TRAIN System Review 1 TRAIN System Final Release Transfer Operational & Maintenance Phase

WEEK 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36

WEEK TASK Project Management SYSTEM ANALYSIS List the requirement List the functions Behavior and Technology Research Methodologies and functionality Research SYSTEM DESIGN Database Design Graphic User Interface Design Main Class CODING Test Driven Development Cycle Produce Class Produce Function Produce Graphic User Interface TESTING Produce Test Plan and Unit Test IMPLEMENTATION Release Beta Version Review Release Final Version
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15

16 17 18 19 20 21 22