Preview

Software Engineering

Powerful Essays
Open Document
Open Document
3574 Words
Grammar
Grammar
Plagiarism
Plagiarism
Writing
Writing
Score
Score
Software Engineering
PHASE 4: REQUIREMENTS ANALYSIS PHASE
The Requirements Analysis Phase begins when the previous phase objectives have been achieved. Documentation related to user requirements from the Concept Development Phase and the Planning Phase shall be used as the basis for further user needs analysis and the development of detailed requirements. Multiple-release projects require only one iteration of the Requirements Analysis Phase, which should involve requirements definition for all planned releases. 1.0

OBJECTIVE/GOALS

Objectives Successful completion of the Requirements Analysis Phase should comprise: • Definition of approved requirements • Creation of the System Requirements Document and Requirements Traceability Matrix • Development of planned test activities • Approval to progress to the Design Phase Goals The purpose of the Requirements Analysis Phase is to transform the needs and high-level requirements specified in earlier phases into unambiguous (measurable and testable), traceable, complete, consistent, and stakeholder-approved requirements. 2.0

DELIVERABLES AND APPROVALS

SDLC deliverables help State agencies successfully plan, execute, and control IT projects by providing a framework to ensure that all aspects of the project are properly and consistently defined, planned, and communicated. The SDLC templates provide a clear structure of required content along with boilerplate language agencies may utilize and customize. State agencies may use formats other than the templates, as long as the deliverables include all required content. . The development and distribution of SDLC deliverables: • Ensure common understanding among Planning Team members and stakeholders, • Serve as a reminder of specified plans as projects become increasingly complex, • Provide agency senior management and other State officials insight into project risks and ongoing performance, • Encourage the execution of repeatable and consistent processes, • Facilitate the implementation

You May Also Find These Documents Helpful

  • Satisfactory Essays

    Prepare a 2-3 page plan for gathering requirements. Build on the systems development selected in Week Two. Begin gathering the requirements for the project. State any assumptions you make. State the difficulties of gathering the requirements.…

    • 409 Words
    • 2 Pages
    Satisfactory Essays
  • Satisfactory Essays

    EXAM 5 AIS

    • 1909 Words
    • 18 Pages

    Which development phase has the purpose of developing specifications for the new or revised system?…

    • 1909 Words
    • 18 Pages
    Satisfactory Essays
  • Satisfactory Essays

    Requirements Definition: This step defines project goals into specific functions and operations of the intended application. It also analyzes end-user information needs.…

    • 595 Words
    • 3 Pages
    Satisfactory Essays
  • Powerful Essays

    The purpose of requirement management is to establish a common understanding of the technical and non-technical requirements that will be addressed by the…

    • 1483 Words
    • 6 Pages
    Powerful Essays
  • Powerful Essays

    Software Engineering

    • 2867 Words
    • 12 Pages

    Any coherent and reasonable project must have some requirements that define what that project is supposed to do. The requirements are the basic steps in implementing a project. A requirement is an objective that must be met. There are several types of requirements such as price, performance and reliability objectives. Requirements are instructions describing what functions the project is supposed to provide, what characteristics the project is supposed to have, and what goals the project is supposed to meet. The shortage of requirements causes many problems in starting and implementing a project. This law states that this shortage of requirements is the main source in the failure of the project.…

    • 2867 Words
    • 12 Pages
    Powerful Essays
  • Powerful Essays

    The Functional Specification of Requirements is the end product of the Functional Analysis. It is the document that formalizes the client’s needs.…

    • 14927 Words
    • 60 Pages
    Powerful Essays
  • Powerful Essays

    In this stage also the System analyst will be involved he will use the feasibility report and carry out a requirement analysis .It encompasses those tasks that go into determining the needs or conditions to meet for a new or altered product, taking account of the possibly conflicting requirements of the various people involved, such as users. It is sometimes referred to loosely by names such as requirements gathering,…

    • 1181 Words
    • 5 Pages
    Powerful Essays
  • Powerful Essays

    The next chapter, the Overall Description section, of this document gives an overview of the functionality of the product. It describes the informal requirements and is used to establish a context for the technical requirements specification. Requirements and Specification section, of this document is written primarily for the developers and describes in technical terms the details of the functionality of the product. Both sections of the document describe the same software product in its entirety, but are intended for different audiences and thus use different language.…

    • 850 Words
    • 4 Pages
    Powerful Essays
  • Good Essays

    Project

    • 548 Words
    • 3 Pages

    To accomplish this project we will use questionnaires and interviews to get the functional and non-functional requirements for this project. Functional requirements deal with what the system should do or provide for users while A Non-Functional Requirement is usually some form of constraint or restriction that must be considered when designing the solution. When the functional and non-functional requirements gotten from the company this will form a legal document between the company and the contractor which will be signed by both parties…

    • 548 Words
    • 3 Pages
    Good Essays
  • Powerful Essays

    Prject Management

    • 3231 Words
    • 13 Pages

    SDLC deliverables help State agencies successfully plan, execute, and control IT projects by providing a framework to ensure that all aspects of the project are properly and consistently defined, planned, and communicated. The SDLC templates provide a clear structure of required content along with boilerplate language agencies may utilize and customize. State agencies may use formats other than the templates, as long as the deliverables include all required content. The development and distribution of SDLC deliverables: • Ensure common understanding among Systems Team members and stakeholders, • Serve as a reminder of specified plans as projects become increasingly complex, • Provide agency senior management and other State officials insight into project risks and ongoing performance, • Encourage the execution of repeatable and consistent processes, • Facilitate the implementation of project management and agency IT best practices, and • Result in a comprehensive record of project performance useful for many purposes…

    • 3231 Words
    • 13 Pages
    Powerful Essays
  • Satisfactory Essays

    Software Engineering

    • 449 Words
    • 3 Pages

    Project management involves various tasks in terms of planning and execution, below we focus on these two approaches: Scrum and Plan-based approaches based on the effectiveness of each approach for planning the allocation of people to projects, estimating the cost of projects, maintaining team cohesion, and managing changes in project team membership.…

    • 449 Words
    • 3 Pages
    Satisfactory Essays
  • Powerful Essays

    In phase 1, the systems analyst or the end-user is concerned with three (3) tasks) –…

    • 2116 Words
    • 14 Pages
    Powerful Essays
  • Good Essays

    Business requirements are the critical activities of an enterprise that must be performed to meet the organizational objective(s). The BRD should remain solution independent. In the context of the project scoping for hardware procurement and installation, this is about identifying and documenting the business requirements of customers, employees, and vendors early in the development cycle to guide the design of the future state. Business requirements are captured by analyzing the current business activities and processes of the as-is state (current process) and defining a target state (to-be process) that will deliver the planned business outcomes that contribute to the organizational objectives.…

    • 1039 Words
    • 4 Pages
    Good Essays
  • Good Essays

    The main aim of the analysis phase is to perform statistics and requirements gathering. Based on the analysis of the project and due to the influence of the results of the planning phase, the requirements for the project are decided and gathered.…

    • 644 Words
    • 3 Pages
    Good Essays
  • Good Essays

    In this phase the overall business study of the desired system is done. The business requirements are specified at a high level and the information requirements out of the system are identified. Once this is done, the basic architectural framework of the desired system is prepared.…

    • 833 Words
    • 4 Pages
    Good Essays