ISO 29110 Lecture

Lecture.md

ISO 29910 Lecture

This lecture note is taken from Workgroup Software Development Process course...

PDCA Cycle

• Plan, do, check, act.

1. Defined (กนชจ)
2. Documented (ลลอษ)
3. Consistently Used (ชยสค)
4. Continuously Imporoved (ปปตน)

Process Model vs Process Implementation

• Process Model - What are the key characteristics?
  • CMMI, ISO 29910, ...
• Process Implementation - How to implement? Activities?
  • TSP, Scrum, RUP, ...

ISO 29110-5

Consists of

• Project Managementation (PM) Process
• Software Implementation (SI) Process

PM Process

To establish and carry out in a systematic way the tasks of the software implementation project, which allows complying with the project’s objectives in the expected quality, time and costs.

Objectives

1. Project plan is developed and validated with the customer.
   • The tasks and resources are sized and estimated.
2. Progress is monitored against the plan and recorded.
3. Change Requests are addressed.
   • Requirement changes are evaluated for cost, schedule, and technical impact.
4. Review meetings with the Work Team and Customer are held.
   • Agreements are registered and tracked.
5. Risks are identified.
6. Version Control Strategy is developed.
   • Items of software are identified, defined, baselined.
   • Modifications and releases are controlled and made available to customer.
7. Software Quality Assuarance is performed.

Input

Input Product	Source
Statement of Work	Customer
Software Configuration	Software Implementation
Change Request	Customer Software Implementation

Output

Output Product	Destination
Project Plan	Software Implementation
Acceptance Record	Organizational Management
Project Repository	Software Implementation
Meeting Record	Customer
Software Configuration	Customer

Internal Products

• Change Request
• Correction Register
• Meeting Record
• Verification Reults
• Progress Status Record
• Project Repository Backup

PM Roles

Role Name	Abbr
Customer	CUS
Project Manager	PM
Technical Leader	TL
Working Team	WT

Project Planning

• Reviewed Statement of Work.
  • Tasks needed to satisfy requirements.
• Lift cycle.
• Quality assurance strategy
• Work team, customer roles and responsibilities.
• Resources and training needs.
• Estimates of effort, cost, and schedule.
• Identified project risks.
• Version control and baseline strategy.
• Project repository.

Software Implementation Process

The purpose of the Software Implementation process is the systematic performance of the analysis, design, construction, integration and tests activities for new or modified software products according to the specific requirements.

Objectives

1. Tasks are performed through the accomplishment of the current Project Plan.
2. Software requirements are defined and analyzed for correctness and testability.

• Approved by the Customer.
• Baselined.
• Communicated.

3. Software architectural and detailed design is developed and baselined.

• It describes the software components and internal and external interfaces.
• Consistency and traceability to requirements are established.

4. Software components defined by the design are produced.

• Unit tests are defined.
• Tracibility are established.

5. Software is produced by performing integration of software components.

• Verified by test cases and test procedures.
  • Results are recorded in test report.
  • Defects are corrected.
• Consistency and traceability established.

6. Software configuration (includes user, operation, and maintenance documentations).

• Integrated.
• Baselined.
• Stored at project repository.
• Needs for changes are detected.
  • Change requests initiated.

7. Verification and validation are performed.

• Defects identified and corrected.
• Records are stored.