Revision as of 08:41, 16 September 2004 edit 62.139.133.170 (talk) →Processes and meta-processes ← Previous edit		Revision as of 21:57, 16 September 2004 edit undo 202.2.56.50 (talk) →Processes and meta-processes Next edit →
Line 8: A growing body of [[software development]] [[organisation]]s implement process methodologies. Many of them are in the [[defence industry]], which in the U.S. requires a '[[Rating]]' based on '[[Process model]]s' to obtain [[contract]]s. The [[Capability Maturity Model]] (CMM) grades organizations on how well they create software ~~accrording~~according to how they define and execute their processes. [[ISO 9000]] describes standards for formally organizing processes with documentation. [[ISO 15504]], also known as Software Process Improvement Capability dEtermination (SPICE), The software process life cycle is also gaining wide usage. This standard is aimed at setting out a clear model for process comparison. SPICE is used much like CMM and CMMI. It models processes to manage, control, guide and monitor software development. This model is then used to measure what a development organization or project team actually does during software development. This information is analyzed to identify weaknesses and drive improvement. It also identifies strengths that can be continued or integrated into common practice for that organization or team.

Software development process: Difference between revisions