Question 1. Requirements
a) Describe the 3 major steps/stages of requirement management. Be sure to discuss what the stage is and does.
-Learning - creating the list.
-Triage - trimming the list
-Documentation - specification
b) Why is requirement management needed and important?
c) There are commercial requirements management tools, like Telelogic DOORS/ERS. What types of functions do these tools provide and why do we need such things?
Question 2. Context Model/Process Model
a) What is the purpose and value of the context model?
b) David A. Ruble calls the context, event and information models the "big three". He is, by default, also including the process model in this comment because the context model is a Level 0 DFD. What is most important is the recognition that this set of models (context/process, event, information) completely defines this part of the business through three interdependent views. Describe how these models inter-relate and connect.
Question 3. Event/Architectural Model:
a)What is the purpose/value of the Event Model and the Architectural Model?
b) The architectural model and event model collide when we investigate topics such as peak vs. average loading. Explain what this is and how our architecture might differ if we have to design for peak loads instead of average loads. Be sure to include a short discussion of what happens during a "peak" time period if we have chosen to design for "average".
Question 4. Performance/Reliability/Availability
a) Why would we want to perform reliability and/or performance modeling? After all, it's not that accurate. What is the value of these methods?
b) Two primary performance modeling techniques are simulation modeling and analytical modeling. Explain what these are being sure to include a discussion of the pros & cons of each method.
c) In our brief classroom discussion on reliability, we touched on the categories of: backup/restore, disaster recovery, and reliability/availability modeling. In a page or so, discuss one of these areas - what it is and its value in designing/building a system.