2 SYSTEM REQUIREMENTS ANALYSIS

1 Section III:2 SYSTEM REQUIREMENTS Analysis31 NYS Project Management Guidebook2 SYSTEM REQUIREMENTS ANALYSIS PurposeThe purpose of SYSTEM REQUIREMENTS Analysisis to obtain athorough and detailed understanding of the business need asdefined in Project Origination and captured in the BusinessCase, and to break it down into discrete REQUIREMENTS , whichare then clearly defined, reviewed and agreed upon with theCustomer Decision-Makers. During SYSTEM RequirementsAnalysis, the framework for the application is developed, pro-viding the foundation for all future design and REQUIREMENTS ANALYSIS can be a challenging phase,because all of the major Customers and their interests arebrought into the process of determining REQUIREMENTS .

2 Thequality of the final product is highly dependent on the effective-ness of the REQUIREMENTS identification process. Since therequirements form the basis for all future work on the project,from design and development to testing and documentation, itis of the utmost importance that the Project Team create acomplete and accurate representation of all REQUIREMENTS thatthe SYSTEM must accommodate. Accurately identified require-ments result from effective communication and collaborationamong all members of the Project Team, and provide the bestchance of creating a SYSTEM that fully satisfies the needs of primary goal of this phase is to create a detailed FunctionalSpecification defining the full set of SYSTEM capabilities to beimplemented, along with accompanying data and process mod-els illustrating the information to be managed and the process-es to be supported by the new SYSTEM .

3 The Functional Speci-fication will evolve throughout this phase of the SDLC asdetailed business REQUIREMENTS are captured, and as support-ing process and data models are created, ensuring that theeventual solution provides the Customers with the functionali-ty they need to meet their stated business of ProcessesThis phase consists of the following processes: Prepare for SYSTEM REQUIREMENTS ANALYSIS , where stepsare taken to ensure that the project environment andProject Team members are adequately prepared to bothcapture and analyze the SYSTEM REQUIREMENTS ; Determine Business REQUIREMENTS ,where in-scope andout-of-scope business REQUIREMENTS are identified, businessrules are defined and documented, and interfaces to andfrom the new application are discussed; Define Process Model,where a pictorial top-down representation of the major business processes that interact with the SYSTEM is diagrammed and decomposedinto manageable functions and sub-functions until no further breakdown is feasible.

4 Define Logical Data Model,where data that supports the processes and business rules is logically modeled,identifying entities and their relationships to other entities,and defining attributes with their business definitions; Reconcile Business REQUIREMENTS With Models,wherethe Project Team ensures that the Process and LogicalData Models accommodate all REQUIREMENTS and businessrules; Produce Functional Specification, where interfaces,processes and data are merged to describe systematicallyhow the Consumer will use the application, and how datawill be retrieved, processed and following chart illustrates all of the processes and deliver-ables of this phase in the context of the SYSTEM III:2 SYSTEM REQUIREMENTS AnalysisNYS Project Management GuidebookSection III.

5 2 SYSTEM REQUIREMENTS Analysis33 NYS Project Management GuidebookFigure 2-1 SYSTEM InitiationPrepare for SYSTEM InitiationValidateProposed SolutionDevelopSystem ScheduleValidatedSolutionSystem RequirementsAnalysis ScheduleHigh-Level SystemDevelopment Schedule Validated BusinessRequirements and ModelsFunctional SpecificationIterative and ConcurrentSystem REQUIREMENTS AnalysisPrepare for SYSTEM RequirementsAnalysisDetermine Business RequirementsDefine Process ModelDefine Logical Data ModelReconcile Business Requirementswith ModelsProduce Functional SpecificationPrepare for SYSTEM DesignDefine Technical ArchitectureDefine SYSTEM StandardsCreate Physical DatabasePrototype SYSTEM Components Produce Technical SpecificationsSystem DesignLogical Data ModelProcess ModelBusinessRequirements34 Section III:2 SYSTEM REQUIREMENTS AnalysisNYS Project Management GuidebookList of RolesThe following roles are involved in carrying out the processesof this phase.

6 Detailed descriptions of these roles can be foundin the Introductions to Sections I and III. Project Manager Project Sponsor Facilitator Business Analyst Database Administrator Data/Process Modeler Technical Lead/Architect Software Quality Assurance (SQA) Analyst Technical Services (HW/SW, LAN/WAN, TelCom) Information Security Officer (ISO) Technical Support (Help Desk, Documentation, Trainers) Customer Decision-Maker Customer Representative Consumer Performing Organization StakeholdersList of DeliverablesThe following table lists all SYSTEM REQUIREMENTS Analysisprocesses, some techniques available for use in executingthese processes, and process outcomes and III.

7 2 SYSTEM REQUIREMENTS Analysis35 NYS Project Management GuidebookFigure 2-2 ProcessesTechniquesProcess Deliverables (Outcomes)Prepare for SYSTEM Team Skills AssessmentEstablished Team andRequirements Site Walk-throughs Environment for ANALYSIS Technology Needs AssessmentRequirements AnalysisTool Needs AssessmentDetermine Business InterviewsBusiness RequirementsRequirementsJAD SessionsBrainstormingStoryboardingCritic al Success Factor InterviewingContext DiagrammingUse Case DiagrammingPrototypingWalk-throughsPoten tial Problem AnalysisExpressing Logic: Pseudo Code, Structured English, Object Oriented LogicDefine Process Work Flow DiagrammingProcess ModelModelFlow Chart DiagrammingProcess ModelingCustomer Event DiagrammingUse Case DiagrammingDecision TreesPrototypingDefine Logical DataEntity Relationship Diagramming Logical Data ModelModelData Normalization/De-NormalizationReconcile BusinessCRUD MatricesAnalysis AssessmentRequirements Gap AnalysisValidated BusinessWith ModelsRequirements and ModelsProduce FunctionalProcess Association and Grouping Functional SpecificationSpecificationLogical OrganizationWork Flow Clustering Expressing Logic.

8 Pseudo Code, Structured English, ObjectOriented Logic36 Section III:2 SYSTEM REQUIREMENTS AnalysisNYS Project Management FOR SYSTEM REQUIREMENTS ANALYSIS PurposeThe purpose of Prepare for SYSTEM REQUIREMENTS Analysisis to position the Project Team and their working environmentto ensure successful completion of SYSTEM RequirementsAnalysis. This is the point at which the Project Team preparesto capture the detailed functional, technical, operational, andtransitional REQUIREMENTS of the preparing for this phase, the Project Manager must focus onthe Project Team and the environment in which the team each new project phase comes the need for new skills,experience, and, potentially, new Project Team members.

9 Theteam needed during this phase must possess analytical skillsthat allow them to continually peel the onion , driving to con-tinuously deeper levels of REQUIREMENTS definition. Experiencein effective interviewing, facilitation, variousmodeling techniques, REQUIREMENTS gathering,and gap ANALYSIS will be extremely reviewing the Validated Solution all teammembers must share a clear and commonunderstanding of the scope of this phase ofthe project, the Project Schedule, the deliver-ables to be produced, and their individualresponsibilities relating to the creation ofthese of the size of the developmenteffort being undertaken.

10 SYSTEM Require-ments ANALYSIS may place the greatest demand upon Customersin terms of resources and the extent of their required partici-pation. During the preparation for this phase, the ProjectManager should continue to manage the Customer s expecta-tions surrounding this participation. Less involvement typicallyleads to a less acceptable finished product. In addition, manyRoles Project Manager Project Sponsor Business Analyst Facilitator Data/Process Modeler Technical Lead/Architect Customer Decision-Maker Customer RepresentativeSection III:2 SYSTEM REQUIREMENTS Analysis37 NYS Project Management Guidebookindividuals earmarked to participate in the REQUIREMENTS gath-ering sessions may not have been privy to earlier project scope-setting sessions.