Model with its definition, by drawing a line connecting them. assess risks at each step: do most critical action first build an initial small requirement spec, code it, then "evolve" spec and code as needed build initial requirement specs for several releases, then design code each in sequence standard phases (requirements, design, code, test) in order write some code, debug it, repeat (i.e. ad-hoc) or organization who wants a product to be developed is known as the: (b) User (c) Contractor (d) Initiator (e) Client form of testing COTS software is ____ testing. (b) Integration (c) Alpha (d) Module (e) Beta maintenance phase, the produce must be tested against previous test cases. This is known as _______ testing. (b) Integration (c) Regression (d) Module (e) Beta property of the rapid prototype is not important? speed with which it can be developed speed with which it can be modified ability to determine the client's real needs insights that the design team can gain from it internal structure example of the risk involved in software development is personnel may resign before the product is complete. manufacturer of critical components (e.g. the hardware associated with a real-time system) may changes may render the product obsolete may market a fully functional lower-cost equivalent package of these above are risks involved in software development. way of looking at the spiral software life-cycle model is as waterfall model with each proceeded by (b) Freezing (c) Synchronization (d) Testing (e) Risk analysis degree of interaction between two modules (or two classes) is known as