Challenges of Requirements Modelling in the Product Development Process

Transcription

1 Challenges of Requirements Modelling in the Product Development Process - Integrated Requirements Modelling DI Michael Maletz michael.maletz@virtuellesfahrzeug.at ProSTEP ivip Symposium 2006 Köln, April 25 th 26 th Dr. Ralf-Stefan Lossack ralf.lossack@magnasteyr.com Dan Brisson dbrisson@mecanicasolutions.com April 25 th 2006 Michael Maletz by ViF 2006 K plus Kompetenzzentrenprogramm, eine Förderinitiative des Bundesministeriums für Verkehr, Innovation und Technologie (BMVIT) Gefördert mit Mitteln des FFG, des Landes Steiermark und der Stadt Graz und der steirischen Wirtschaftsförderung (SFG) 1

2 Outline Introduction Challenges in Product Development Motivation & Complexity of Requirements Modelling Current Best Practice in RM & Call for Action Solution Approaches / Concepts Requirements Compliant Product Development Integrated Requirements Modelling Traceability Concept Requirements Modelling Example Verification of Concept on the Example of a Vehicle Door Limitations of Current Practice - Tools Outlook & Summary 2

3 Introduction Motivation & Complexity Challenges in Product Development Current Best Practice in Requirements Modelling & Call for Action 3

4 Importance of Requirements Modelling Customers explanation Project Leaders Understanding Understanding of As Designed Described by Consultant Documented Delivered Billed Supported Real need of Customer 4

5 Importance of Requirements Modelling Requirements are statements which describe properties and characteristics a product and/or a process has to fulfill. Requirements modelling is the process of eliciting analyzing managing tracing verifying requirements and their evolution through the whole product life cycle. 5

6 Challenges in Product Development CAE OEM R1 R1 CAD Concept R2 R2 R3 R3 CAD Tier 1 R1.1 R2.1 R3.1 R4 R5 R6 Production Planning Manufacturing Manufacturing Supplier Supplier R4.1 R5.1 R6.1 R7 R8 R9 Engineering Engineering Supplier Supplier Tier 2 Global distributed development Collaborative teamwork Changing and evolving requirements Keep track of dependencies Management of requirements / product evolution 6

7 Requirements Modelling Today & Tomorrow Today s RM Problems Solutions for Tomorrow Complexity - products are becoming more and more complex Lack of Formalization due to product complexity and no unique req. understanding Priority - higher at different stages of the development process Acceptance - of company culture and historically grown domains Boundaries - poor integration of customer, supply chain & company internally Integration into: ~ development processes ~ support processes ~ manufacturing process planning Support in: ~ early phases for customer / supplier cooperation Consistency tracing over the whole life cycle and beyond company borders Realization of computer supported RM in PDM/PLM Systems 7

8 Complexity of RM in the Product Development Process OEM Tier 0.5 Tier 1 Tier 2 April 25 th 2006 Michael Maletz by ViF 2006 Based on VDA 4.3 8

9 Current Best Practice for RM Tools Two main types of Tools for RM: a) Modelling and validation tools for system development b) Requirements management tools Main functions of existing RM tools are: Office integration (import / export to MS-Word etc.) Handling of attributes for requirements Linking and traceability options between requirements Baselining and rollback Different views on requirements Web based multi client capability Some approaches to integrate requirements in PDM Systems 9

10 State of the Art in Product Development / RM RM Tool 1 (e.g. DOORS) RM Tool x (e.g. Requisite Pro) Consistent Requirements Data (e.g. RIF*) Call for action: integration of SOTA RM to product development process in a consistent manner. Product Development Process PLM 1 Consistent PLM Data (i.e. PLM Services) PLM x * Requirements Interchange Format 10

11 Solution Approaches / Concepts Requirements Compliant with Product Development Integrated Requirements Modelling Traceability Concept (Horizontal & Vertical) 11

12 Requirements Compliant Product Development Product Development processes Support processes Manufacturing processes Escalations Requirements Costs Project Changes Releases Requirements Requirements Requirements Requirements Elicitation Analysis Management Verification Voice of Customer Interpret needs Specification Documents Explicit Req. Evolving Req. Communicating Req. Trace Req. Agreeing Req. 12

13 Integrated Requirements Modelling Integrate requirements modelling in product development process by linking of requirements functions - components linking to core and support processes as basis for traceability Design Simulation Validation Core Processes Requirement Function Component Support Processes Requirements Releases Changes 13

14 Horizontal Impact Traceability Concept Horizontal tracing used to carry out impact analysis understand how requirements are satisfied understand impact of changing requirements possible effects of component tests / failures satisfaction links to identify related requirements, functions and components Requirement Function Component satisfies satisfies 14

15 Transfer of requirements traceability to the V-ModelV Development undertaken in different levels Vertical Traceability Concept in the Example of the V-ModelV Requirements & functions play an important role at each level Statement Statement of of need need (VoC) (VoC) Customer Requirements System Reqs & Functions validation verification Operational Operational use use System Test Product Acceptance Sub-System Reqs & Functions verification Sub-System Test Component Reqs & Functions Component Test 15

16 RM in Support Processes Computer supported requirements management as basis for decision in e.g. change and release processes in all development phases (e.g. at milestones, quality gates etc.) Req. Eliciting Req. Analysis Core Development Processes Support Processes Req. Verification Process Product Reqs Change Process Requirements Management Release Process Reqs 16

17 Requirements Modelling Example Verification of Concept in DOORS on the Example of a Vehicle Door Limitations of Current Best Practice Tools 17

18 Initial Situation Example for RM on a vehicle door 1) OEM: assignment of module development (e.g. door) requirements specification documents 2) Supplier & OEM: - exchange documents & negotiate Reqs. Reqs. 3) Development requirements fulfillment Use Case Scenario: Requirements: vehicle must fulfill FMVSS 214 *, easy assembly must be guaranteed, etc. Functions of components: the side protection system offers resistance for side impact, the frame joint positions the door in the frame, Dependencies: the frame joint also affects the requirement for the door assembly * Crash test standard for side impacts 18

19 Complexity of Dependency - Functions & Components The door consists of: Components Parts Functions DOORS Screenshot: Complexity and relation between components & functions Function Component 19

20 Verification of Traceability Concept Question: What happens if the frame joint changes? What functions are affected? What requirements are related to the frame joint? Requirement Function Component 20

21 Results / Limitations with Today s RM Tools Today s tools offer the ability to: Locate dependencies Trace changes Analyze impacts Etc. Limitations: Mostly stand alone solutions Poor support for product life cycle Not very well suited for modelling of product requirements Poor integration of development processes Little to no integration to PDM/PLM Systems 21

22 Outlook, Conclusion & Summary 22

23 Ongoing R&D: RM as Backbone in the PLM Context Standards etc. Specification Documents Changes etc. Release Components Product Structure Collisions etc. Access checks Document Management Workflow Management BoM DMU Functions etc. etc. Requirements Management Requirements Modelling Product Lifecycle Management Requirements Modelling Program Management Configuration Management Manufacturing Process Planning Resource Management Costs Team Reporting etc. Variants etc. Powertrain BiW etc. Robots Jigs etc. 23

24 Ongoing R&D Collaboration State of the Art: Research Results Emerging Standards Use-Case Scenarios Project (OpenMPM) State of the Art: Requirements Use-Cases Industrial Best-Practices State of the Art Software Tools for Engineering Collaboration April 25 th 2006 Michael Maletz by ViF

25 Lifecycle of Ongoing R&D Collaboration (OpenMPM) Docs. Workf. BoM DMU Req. Progr. Config. Manuf. Res. April 25 th 2006 Michael Maletz by ViF

26 Conclusion Deeper integration of requirements modelling in the product development process in order to improve product quality, development time and reduction of costs Computer supported approach in which requirements modelling builds the basis in product modelling Incorporate requirements modelling in manufacturing & production planning processes Include different disciplines (marketing, engineering, after sales, etc.) & supply chain 26

27 Summary Highlighted the complexity & challenges of requirements modelling in the product development process Summarized the current best practices in requirements modelling Discussed solution approaches for integrated requirements modelling Overview of future activities to implement requirements modelling into the PLM context 27

28 Thank you! Questions? Discussion? This work was promoted with funds of the Kplus Competence Center Program, the Land Steiermark, the Steirischen Wirtschaftsförderungsgesellschaft mbh and the city of Graz, Austria. 28