Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis
description
Transcript of Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis
![Page 1: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/1.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 1
System Requirements Analysis:The first step to value-based system development
Joris VanderschrickVerhaert - Embedded Systems [email protected]
![Page 2: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/2.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 2
![Page 3: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/3.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 3
What is a system requirement?
1. A need: a process or improvement, thatstakeholders want to realize through a system.
2. A demand to a system: the behavior(= functionality) or quality (= performance) thata system must have to fulfil the need of the stakeholders.
Uit: Handboek Requirements
![Page 4: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/4.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 4
The bridge function of requirements
Requirements
Stakeholders-) Business-) Customer-) Users…
Development Team
• Requirements: What the system must be able to do…
• Stakeholders: …to optimally be able to support us
• Development team: …and we have to implement them
![Page 5: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/5.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 5
For who are requirements important?
Requirements
StakeholdersCustomer Service Provider
USERS DevelopmentTeam
Testers/Validation
![Page 6: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/6.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 6
Users: The system must create Added Value
Utility
Desirability
Usability
Alowability
Feasibility
Add
ed V
alue
The ‘requirements’ must enable the developedsystem concept to create Added Value for the end-user
• What is the Added value of your product/system?
![Page 7: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/7.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 7
What is the importance of requirements
![Page 8: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/8.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 8
If you cannot manage to define the requirements at the start of a project, than itdoes not matter anymore how good you execute the following actions.
Importance of adequately defining the requirements
Phase Relative Correction costs
Requirements 1‐2
Technical Concept 5
Realisation 10
Unit Test 20
Acceptance Tst 50
Maintenance 50
Davis (1993)
![Page 9: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/9.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 9
Conclusion: Leffingwell & Widrig (2003): Of the total budget for (software) development tasks, 25 to 40% will be spent on the correction of errors in the requirements.
Importance of ‘good’ requirements
![Page 10: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/10.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 10
Criteria for well-defined requirements
Completeness:
Consistency:
No missing requirements: All the requirements, that the system must fulfil, must be defined
No conflicting requirements: Requirements can conflict when stakeholdershave different opinions about the specific demands for the systems
![Page 11: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/11.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 11
Criteria for well-defined requirements
Unambiguity:
Validity:
• Only 1 interpretation possible of the requirements. • Not 100% possible Written in natural language
Requirements are only valid if they contribute to the added value for the stakeholders
“Around 45% of the developed functionality for a system is never used!”
“Don’t waste time with the overkill functionality.“
The Standish Group, 2003
![Page 12: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/12.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 12
Requirements Analysis issues
The first step in the system engineering process: REQUIREMENTS ANALYSIS
![Page 13: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/13.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 13
System Requirements Analysis
In the traditional waterfall model of system development, the first phase of requirements analysis is also the most important one.
Goal:
• Understanding the customer's business context and constraints• Functions the product must perform• The performance levels it must adhere to• The external systems it must be compatible with
![Page 14: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/14.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 14
The System Engineering Process
![Page 15: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/15.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 15
Origin Process Inputs
Analyze all aspects of the entire system life cycle including all equipments touch points with consumers, installers, service & maintenance staff
1. Customer Needs/Objectives/Demands
• Goals• Measures of Effectiveness• Environments• Constraints
2. Other:
• Technology Base• Output Requirements from Prior Development
Effort• Requirements Applied Through Specifications and Standards
Attract
Choose
UseSupport
Retain
Customer Needs ObjectivesDemands
![Page 16: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/16.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 16
Key System Requirements
• Operational :
Where will the system be used?How long will the system be in use by the user?
• Environmental:
How are the various system components to be used? Utility!What environments will the system be expected to operate in an effective manner?
• Goal: How will the system accomplish its mission objective? Added Value!
• Performance:
What are the critical system parameters to accomplish the goal?How effective or efficient must the system be in performing its goal?
![Page 17: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/17.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 17
Break-down requirements
• Items to be Developed: These are the primary requirements that will create the added value of the system. The biggest development efforts are initiated to fulfil these requirements.
• Specifications: Secundary development Items: These are the quantified requirements that do not need much development effort. They can immediately be fulfilled by existing components or sub-systems. Usually purchasing parts.
![Page 18: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/18.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 18
Holistic approach
• Define the Functional & Performance requirements
• Define Design constraints• Define the Interface requirements
![Page 19: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/19.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 19
Define functional and performance requirements
Functional requirements: What the system must do…Performance requirements: How well the system must perform…Break-down of the ITD
![Page 20: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/20.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 20
Constraints & Interfaces
Define design constraints:
Limit Design flexibilityEnvironmental conditions & limitsStandards
Interface requirements:
Define the functional and physical interfaces to external or higher-level and interacting systems.
![Page 21: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/21.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 21
FunctionalRequirements
Performance Requirements
CustomerRequirements
Security System for the Traffic Light Controller
FunctionalRequirements
Performance Requirements
CustomerRequirements
Interface System between traffic lights& Central for coördination
Traffic LightController IPC
Remote SecuritySystem
Central forcoordination
Interface Requirements
Interface Requirements
![Page 22: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/22.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 22
Break-down requirements
Security System for the Traffic Controller (Traffic Lights)
Functional Requirements:
• Polling the Traffic Controller for Error• Analysis of the Error Messages• Routing the Error Messages to a Remote Central Security System
Performance Requirements:
• Polling speed (@1Hz)• Data transfer speed Error report available at remote system within 20 seconds• Redundant
Interface SystemFunctional Requirements:
• Receiving commands of the central system for the coordination of the Traffic Lights• Translating the specific command towards the protocol of the Traffic Controller
Performance Requirements:
• Reaction time between command & traffic lights change: <3 seconds
![Page 23: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/23.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 23
Design constraints
• Easy serviceability & maintainability• Minor Assembly efforts• Re-use known company plaforms: Cirrus Logic ARM• Easy accessiblity• IP-67• No internal Airflow• System temperature up to 70°C.• Migration options for future communication upgrades• EN-50129 Safety related electronic systems for signaling
![Page 24: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/24.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 24
Interface requirements
Routing the Error Messages to a Remote Central Security SystemReceiving commands of the central system for the coordination of the Traffic Lights
• Functional: IPC communication network to the Security & Interface system• Physical layer: Long-range wireless network or installed cable infrastructure
Polling the Traffic Controller for Error
• Functional: IPC communication network to the Traffic Controller• Physical layer: Short-range wireless network
![Page 25: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/25.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 25
Functional Analysis & Allocation
• Clearly define the Global Framework and the different sub modules• Define successively lower-level functions• Allocate Performance and other limiting requirements • Defining/Refine functional architectures at ever-increasing levels of detail• Refine the Internal/External Functional Interfaces
![Page 26: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/26.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 26
Functional Analysis Tool: FAST diagram
![Page 27: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/27.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 27
Result: Functional Architecture
A Simple Rule:
Look to see if all the functions are verbs. If there is a function identified as a noun, then there is a problemwith the understanding of the functions.
![Page 28: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/28.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 28
Refine Interface architecture
![Page 29: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/29.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 29
Convert system architectures from Functional to Physical
Synthesis
• Physical decomposition defines the physical elements needed to execute the function.
• Define preferred physical solutions for the Primary and Secondary Development Items
• Define Internal and External Physical Interfaces
• Define Alternative System Concepts (Morphological map)
![Page 30: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/30.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 30
Morphological mapAlternative Design ConceptsAlternative concepts can be defined via a Morphological map that provides a structure overview of the different Items to Be Developed (ITD’s) and the different options to develop them.
to a correct Risk Profile
![Page 31: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/31.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 31
Example: Mobile Phone
![Page 32: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/32.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 32
It is challenging to fix the concept, that will create the most Added Value in respect to a correct Risk profile. This is a very important task when defining the best System concept
![Page 33: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/33.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 33
System Analysis and Verification
• Diverge: create a spectrum of requirements, sub-modules, functions, solutions,…Avoid fixation to 1 or 2 solutions Other options will become variations
• Verfication: Verify with the requirements, constraints, main goal, Added Value
• Converge: Trade-Off the different solutions and select
![Page 34: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/34.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 34
System Specifications
• Add the Secundary Development Items• Clearly defined specifications and baselines• System Architecture• Concept Design• Decision Database
![Page 35: Verhaert Innovation Day 2011 – Joris Vanderschrick (VERHAERT) - System Requirements Analysis](https://reader038.fdocuments.net/reader038/viewer/2022103109/544f5312af7959157d8b88f1/html5/thumbnails/35.jpg)
CONFIDENTIAL
INNOVATIONDAY 2011 Slide 35
Hogenakkerhoekstraat 219150 Kruibeke (B)
tel +32 (0)3 250 19 00fax +32 (0)3 254 10 08
More at www.verhaert.com
helps companies and governmentsto innovate. We design productsand systems for organizationslooking for new ways to providevalue for their customers.We are a leading integratedproduct innovation center; creatingtechnology platforms, developingnew products and business inparallel, hence facilitating new-growth strategies for our clients.