Software Life Cycle Processes

ISO 12207

ISO/IEC 12207, as reported in [Singh95] and [MooreJRada96]

ISO 12207 provides a language and an architecture for producing and acquiring software. BUT it does not prescribe a sequence, method, or structure for developing software. It is essentially a template where details need to be placed into it. The organisation below is to help understanding not as a plan of action for all projects.

Disclaimer. Something may have been lost in translation.

1. participant::Sets, of people and organizations taking part in the project.
2. party::shorthand=participant.

3. LIFE_CYCLE_PROCESSES::=following
   Net
   1. acquirer::party.
   2. supplier::party.
      
   3. |-PRIMARY(acquirer, supplier).
      
   4. |-SUPPORT.
      
   5. |-ORGANIZATIONAL.
   6. Tailoring::=special normative process to fit this standard to particular project.

   
   (End of Net)
   
   
4. PRIMARY::=following
   Net
   1. acquirer::party=given.
   2. supplier::party=given.
   3. developer::party.
   4. operator::party.
   5. maintainer::party.

   6. done_by::@(activities_and_tasks, party).

   7. Acquisition::activities_and_tasks.
      
   8. |-Acquisition done_by acquirer.
   9. Supply::activities_and_tasks.
      
   10. |-Supply done_by supplier.
       
   11. |-Supply includes { Development, Operation, Maintenance}.
   12. Development::activities_and_tasks.
       
   13. |-Development done_by developer.
   14. Operation::activities_and_tasks.
       
   15. |-Operation done_by operator.
   16. Maintenance::activities_and_tasks.
       
   17. |-Maintenance done_by maintainer.

   
   (End of Net)
   
   
5. SUPPORT::=following
   Net
   1. Documentation::=records information produced by other processes.
   2. Configuration_managment::=identifies baseline items, controls modification and release, records and reports status, controls storage handling and delivery.
   3. Quality_Assurance::=assures independent and objective compliance and adherence to requirements. objective and so autonomous from production.
   4. Verification::=checks products against previously established requirements.
   5. Validation::=checks fanil product fulfills specific intended use.
   6. Verification_and_Validation::=combined Verification with Validation.
   7. Joint_Review::=review technical status ad progress, Joint_Review done_by reviewing and reviewed.
   8. Audit::=assess compliance of products and tasks vs requirments and plans, Audit done_by auditor.
   9. Problem_Resolution::=closed loop process for resolving problems and nonconformances, taking corrective acctions, reversing trends.

   
   (End of Net)
   
   
6. ORGANIZATIONAL::=following
   Net
   1. Management::activities_and_tasks=generic form applied to other primary and support tasks.
   2. Infrastructure::=establish and maintain an infrastructure.
   3. Improvement::=assess, measure, control, and improve whole process.
   4. Training::=aquire or develop personel resources and skills.

   
   (End of Net)
   
   

   Possible Relation between ISO 12207 and IEEE SESC Standards

   ISO 1207	IEEE SESC Standards
   Primary
   Acquisition	1062 Sofware Acquisition
   Supply	-
   Development	803 SRS, 1016 SDS, 1008 Unit Testing, 829 test documentation
   Operations	-
   Maintenance	1219 Sw Maintenance
   Support
   Documentation	-
   CM	828 Sw CM Plans
   QA	730 SQA Plans, 1298 SQ Mant system & Requirements
   Verification,Validation	1012 Sw V&V
   Joint Review, Audit	1028 Sw Reviews & Audits
   Problem Resolution	1044 classification of Sw Anomalies
   Organisational
   Managment	1058 Sw Project Mant Plans
   Infrastructure	1209 Eval & selction of CASE, 1348 CASE Toll adoption
   Improvement	-
   Training

. . . . . . . . . ( end of section Software Life Cycle Processes) <<Contents | End>>