Explore BrainMass

Explore BrainMass

    Requirement management, cotext & process model, event model

    This content was COPIED from BrainMass.com - View the original, and get the already-completed solution here!

    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?

    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.

    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".

    6. 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.

    © BrainMass Inc. brainmass.com October 9, 2019, 6:27 pm ad1c9bdddf


    Solution Preview

    STEP 1
    Requirement management
    -Learning - creating the list.
    -Triage - trimming the list
    -Documentation - specification

    Learning relates to creating the list of requirements in the organizational setting. It should be recognized that all requirements have characteristics that give excellent information to the company. Generating the list also helps in understanding the boundaries, ascertaining the stakeholders, recognizing their objectives, testing feasibility and assessing risks. Generating the list also helps in assessing the appropriate use of language, communications and understanding.
    Triage brings in the factors of development priority, issues of validation, negotiation, conflict resolution and prioritization of different requirement. There is no mechanical means of doing triage. It is not that requirements of every project are pruned. No, in fact there may be several projects of which all the listed requirements are kept in place. Instead some projects based on the objectives of the organization may be deferred. The triage process is crucial for adjusting the project with the allocated budget.
    Documentation: There should be completeness in the known requirement specifications. The requirements should not be conflicting and there should be regularity in the requirements. The description of the requirements should be so specific that there is no scope for multiple interpretations. In other words there should be no equivocation in documentation. The documentation should facilitate the tracing of the source of requirement. Even if details are not provided by the requirement is adequately externally identifiable, it should be documented. In every document in spite of the additional information, the actual requirement should be clearly identifiable.

    Need for requirement management:

    Requirements management is needed to understand the objectives of the business unit and its customers and how these are transformed into functions and constraints related to the specifications of products, the systems management and services provided. Requirement managements seeks the reasons for the requirements, analyzing requirements, validating them with the ...