"Page:1 Stakeholder Needs and Requirements DefinitionStakeholder Needs and RequirementsDefinition Process Department of Engineering Management & SystemsEngineering (EMSE) Dr. Gina Guillaume-JosephPage:2 Stakeholder Needs and Requirements DefinitionThese slides were developed to present and amplify the content ofINCOSE’s Handbooks and as such incorporate text and graphics from thehandbooks.These items retain INCOSE’s copyrights statement: © 2015 INCOSE. All RightsReserved. May not be copied,scanned, or duplicated, in wholeor in part, except for use aspermitted in a license obtainedfrom INCOSE for classroom use.Page:3 Stakeholder Needs and Requirements DefinitionAgenda ? Context ? Purpose ? Key Activities ? OutcomesPage:4 Stakeholder Needs and Requirements DefinitionContext Not consideringBusiness orDisposal the business /UnexpectedMission Analysis environment emergence Stakeholder NeedsOperation Maintenance & Reqts Definition Insufficient System ReqtsValidation Analysis Definition Poorcommunication Not enough Architecture UnexpectedTransition Definition alternatives emergence DesignGetting here Verification Definition too quickly – orstarting here UnexpectedIntegration System Analysis emergence SE Process Producibility Implementation Challenges issuesPage:5 Stakeholder Needs and Requirements DefinitionRequirements: The Big Picture ISO 15288:2015 Processes Business or Mission Analysis Concept of Need Operations Stakeholder Needs & Reqts Definition Derived Allocated ArchitectureRequirements Architecture System ReqtsDefinition Mission Definition Requirements System System DesignStakeholders’ Requirements Definition Requirements Component Components Requirements Configuration Item Configuration Items Requirements Integration and Qualification Systems Adapted from The Engineering Design of Systems, Buede, 2009Page:6 Stakeholder Needs and Requirements DefinitionTransforming Needs into Requirements Source: SEH v4 p. 48Page:7 Stakeholder Needs and Requirements DefinitionStakeholder Needs and Requirements DefinitionProcess ? Purpose – Define the stakeholder requirements for a system thatcan provide the capabilities needed by users and otherstakeholders in a defined environment • Identify the stakeholders • Elicit their needs for a new or changedcapability • Analyze and transform these intostakeholder requirements • For the operation and effects of thesolution • For its interaction with the operationalenvironment Raytheon • For its interaction with the enablingNext Generation Destroyer environment Source: SEH v4 p. 52Page:8 Stakeholder Needs and Requirements DefinitionThe Ipotace of Captuig SouceRequirements ? Stakeholder Needs and Requirements are the foundation of the project ? Source requirements will be greatly refined and decomposed but all childrenand the system segments that implement them must be unambiguouslytraceable back to the source requirements ? Use a database approach to preserve all the linkages, issues, and decisions ? As a minimum, the foundation must include the following: - Mission requirements - Project requirements - Customer specified constraints - Interface, environmental, and quality requirements - Unclear issues discovered in the requirements analysis processes - An audit trail of the resolution of the issues raised - Verification / Validation methods required by the customer - Traceability to source documentation Source: SEHv3.2.2 p. 66Page:9 Stakeholder Needs and Requirements DefinitionCapturing Source Requirements 1. Empower a systems analysis team with the authority and mission to carryout the activity 2. Assign experienced Systems Engineer(s) to lead the team 3. Assign experienced team members from relevant engineering, test,manufacturing, and operations (including logistics) disciplines to beavailable to the team 4. Establish the formal decision mechanism (e.g., a design decision database)and any supporting tools; select and obtain necessary SE tools for theactivity 5. Complete the relevant training of team members in the use of toolsselected for the activity 6. Define the formats of the output deliverables from this activity (to permitthe definition of any database schema tailoring that may be needed) Source: SEHv3.2.2 p. 66Page:10 Stakeholder Needs and Requirements DefinitionStakeholder Needs and Requirements DefinitionProcess Source: SEH v4 p. 53Page:11 Stakeholder Needs and Requirements DefinitionKey Activities 1. Prepare for stakeholder needs and requirementsdefinition 2. Define stakeholder needs 3. Develop the Operations Concept and other lifecycleconcepts 4. Transform stakeholder needs into stakeholderrequirements 5. Analyze stakeholder requirements 6. Manage the stakeholder needs and requirementsdefinition process Source: SEH v4 p. 49Page:12 Stakeholder Needs and Requirements DefinitionPrepare for Stakeholder Needs and Requirements1 Definition ? Determine who the stakeholders or classes ofstakeholders are - Business or Mission Analysis? major stakeholders - Now ? business operations level ? Determine the need for and requirements of anyenabling systems, products, or services Source: SEH v4 p. 52Page:13 Stakeholder Needs and Requirements Definition1 Stakeholders – Who Are They? ? Any entity (individual or organization)with a legitimate interest in the system Users Customers ? Typically: - Users Support - Operators - Ogaizatio deisio-akes Decision Makers - Parties to the agreement Regulatory Bodies - Regulatory bodies - Developing agencies - Support organizations Testers System Engineers - Soiet-at-lage - Future generations? Source: SEH v4p. 52Page:14 Stakeholder Needs and Requirements Definition1 Identify Users and Stakeholders Source: SEHv3.2.2p. 61Page:15 Stakeholder Needs and Requirements Definition1 Stakeholder Roles Evolving in the Lifecycle Source: Space Mission Analysis and Design (SMAD) by Wertz and LarsonPage:16 Stakeholder Needs and Requirements DefinitionKey Activities Cotd 1. Prepare for stakeholder needs and requirementsdefinition 2. Define stakeholder needs 3. Develop the Operations Concept and other lifecycleconcepts 4. Transform stakeholder needs into stakeholderrequirements 5. Analyze stakeholder requirements 6. Manage the stakeholder needs and requirementsdefinition process Source: SEH v4 p. 49Page:17 Stakeholder Needs and Requirements Definition2 Defining Stakeholder Needs ? This will involve the integration of disparate views, which maynot necessarily be harmonious - Ofte aoplishedoi ttee atio - Try to create a common paradigm for examining and prioritizinginformation – goal modeling might help ? Eah of the use’s ies of the eeded sstes aetaslated to a cootop-level syste desciptio that isunderstood by all participants ? All decision making activities (e.g. scope) must recorded forfuture examination Source: SEH v4 p. 55Page:18 Stakeholder Needs and Requirements Definition2 Needs Elicitation ? Why is needs elicitation necessary? - Gain knowledge relevant to the problem A joint learning- Udestad the use’s atual eeds exercise » The user may not fully understand these » The user may not be able to state these in a meaningful way What is meant by“ease of use?” Bridge Ratings, LLCPage:19 Stakeholder Needs and Requirements Definition2 What Do We Want to Learn? ? ….fo ou customers? ? ….fo ou users? - Understanding of the problem in - Understanding of the problem insolution-independent terms solution-independent terms» Domain-specific terminology - The user groups that will beaffected by the system - Problems or limitations with thecurrent system - Overall program goals » Shortfall identification - Specific program objectives - Domain knowledge - Motivations » Functions, interfaces,- Concerns performance issues, physical- Expectations characteristics, operational issues,RMA, operability requirements - Constraints - Needs versus wants - Priorities-- performance, cost,» New ideas schedule, riskPage:20 Stakeholder Needs and Requirements Definition2 Needs and Requirements Elicitation ? Needs and RequirementsPrimary Elicitation Methods elicitation--The process ofacquiring all relevant knowledge? Interviewing needed to produce a-Formal or informal requirements model of a? Scenario-based problem domain -Develop scenarios with customers andusers to describe interaction with system ? Must occur before system? Form Analysis requirements can be derived-Review existing documentation related toand allocated the problem domain ? Must understand ? Reverse engineering and SRD re-use -Examine an existing system or existing SRD - Nature of desired solution ? Joint Application Design (JAD) - Required features ? Quality Function Deployment (QFD) - System boundaries ? Elicitation process may require a combination of methods"