Chaos Model

• The whole project must be defined, implemented, and integrated.
• Systems must be defined, implemented, and integrated.
• Modules must be defined, implemented, and integrated.
• Functions must be defined, implemented, and integrated.
• Lines of code are defined, implemented and integrated.

• The chaos model may help explain why software is so unpredictable.
• It explains why high-level concepts like architecture cannot be treated independently of low-level lines of code.
• It provides a hook for explaining what do next, in terms of the chaos strategy.

References

• Roger Pressman (1997) Software Engineering: A Practitioner's Approach 4th edition, pages 29-30, McGraw Hill.
• Raccoon (1995) The Chaos Model and the Chaos Life Cycle, in ACM Software Engineering Notes, Volume 20, Number 1, Pages 55 to 66, January 1995, ACM Press.
• Johnson Sarlie (1996) Brody's Software theories

<< Previous Word Browser Next >>
domingo faustino sarmiento d'ni treaty of oliwa 1604 in science charles of guise lajos kossuth alfred windischgrtz radley metzger albion woodbury small british north america act 1867 kenny anthony	henrietta anne stuart arthur grgei 2003 4 heineken cup stphane lupasco metoclopramide k line pete yorn g line webert sicot ambrosiana jerome guy sebastian	cui jian enfield, massachusetts hartnett croatoan island list of football clubs in japan american impressionism john henry twachtman chaos strategy large cardinal warwickshire telluric current	defector live in texas net book agreement carbohydrate metabolism index register ramsey, cambridgeshire alois kayser nec corporation michael dobbs g5 root locus