Requirements specification: A structured document that sets out the services the system is expected to provide Should be precise so that it can act as a contract between the system procurer and software developer and thus needs to be understandable by procurers and developers
Too complex for complete analysis Separation into non-interacting subsystems distorts the results The most important properties are emergent Too organized for statistics Too much underlying structure that distorts the statistics Organized Complexity\(Weinberg) Copyright Nancy Leveson, Sept 1999
opyright Nancy Leveson, Sept. 1999 Stage 1: Forming Team members begin to discover what behaviors are acceptable Usually highly unstructured environment Attempt to identify tasks, how to accomplish them Decisions on what information is needed Hesitant participation