We think you have liked this presentation. If you wish to download it, please recommend it to your friends in any social system. Share buttons are a little bit lower. Thank you!
Presentation is loading. Please wait.
Published byGraham Whelpley
Modified over 2 years ago
EuSEC Tool Vendors Challenge Adie Ditchburn Jon Chard 19 Sep 2006
© Telelogic AB 2 Approach Discuss Method of Deriving Requirements –Structure –Role of Modelling Relationship of Models to requirements Demonstrate DOORS Structure –Database Level –Module Level Demonstrate Modelling using TAU –Use Case to System Level Activity Models –Logical System Structure Models Discuss Information Traceability Demonstrate Traceability in DOORS –Traceability Reports
© Telelogic AB 3 System Requirements Agree Requirements Qualification Strategy Analyze & Model Stakeholder Requirements Acceptance Strategy Agree Requirements System Models Analysis Results Derive Requirements & Qualification Strategy Deriving System Requirements
© Telelogic AB 4 Understanding your requirements Dont just list requirements, use structure to understand them Organise similar requirements into sections within documents Use structure to discover: –Context (overall situation in which the requirement occurs) Allows you to see the whole picture – Duplications (same requirement stated twice) Causes work to be performed twice Can lead to conflicting requirements Doubles your maintenance cost – Omissions (missing requirements) Unstated requirements become missing functionality Could cause shortcomings in non-functional areas such as performance, reliability, ease of use - that can not be re- engineered back into the system once developed
© Telelogic AB 5 Functional modeling Functional modeling Functional modeling Models Bridge Layers of Requirements Requirements layer Modeling layer Requirements layer Modeling layer Requirements layer Modeling layer Requirements layer e.g Goal / Usage modeling e.g. Functional modeling Sponsor Requirements Design Specification System Requirements Statement of need e.g. Performance modeling Concept: Requirements and Modeling
© Telelogic AB 6 Tool Vendor Challenge CCC Layers of Requirements and Models Challenge Statement Concept: Requirements and Modeling Stakeholder Requirements System Requirements Sub-System Requirements Constructed in DOORS Functional modeling Functional modeling Functional modeling Use Case modeling Activity modeling Functional modeling Constructed in TAU Implementation
© Telelogic AB 7 DOORS and TAU Demonstrations Demonstration of Requirements Structure in DOORS Demonstration of SysML Modelling in TAU Over to you Jon
© Telelogic AB 8 Requirements visualization and satisfaction through modelling in Tau with traceability to DOORS
© Telelogic AB 9 System black-box use cases in Tau SysML
© Telelogic AB 10 Example system block structure in Tau SysML
© Telelogic AB 11 Example configuration block internal structure diagram
© Telelogic AB 12 State machine description of subsystem block behaviour
© Telelogic AB 13 Information Traceability INFORMATION TRACEABILITY: Understanding how high-level objectives are transformed into low-level goals. e.g. in business terms: Understanding how business vision interpreted as business objectives implemented as business processes e.g. in systems engineering: Understanding how user requirements satisfied by system requirements implemented as design artifacts implemented as components
© Telelogic AB 14 Benefits of Information Traceability Greater confidence that objectives are being met. Ability to manage change through ability to access change impact. Greater accountability of subordinate organisations/suppliers. Ability to track progress / status particularly in the formative stages of project. Ability to deliver value through cost/benefit analysis.
© Telelogic AB 15 DOORS Demonstration Demonstration of Production of Traceability Reports Once again Jon
© Telelogic AB 16 Use of DOORS traceability analysis tools to show requirements satisfaction through SysML model.
Kathy Reed June 4, 2013 IIBA Austin CBAP Study Guide for the Business Analyst Body of Knowledge (BABOK) Version 2.0.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 7 Slide 1 Chapter 7 System Models.
© Telelogic AB 1 Managing Change From Customer Request to Implementation Jean-Louis Vignaud & Dominic Tavassoli.
Lecture 8: Testing, Verification and Validation Dr Valentina Plekhanova University of Sunderland, UK.
Overcoming Customer Constraints on Requirements Documents Presented by: Robert Smole Presented by: Robert Smole November 5, 2008 Sub-Optimization of Systems.
Leverage MarkITS for agile solutions delivery that balances strategic thinking with tactical execution for “Business & Technology Convergence” MarkITS.
© Telelogic AB Modeling DoDAF Compliant Architectures Operational Systems Technical.
© Telelogic AB  Sandia is a multiprogram laboratory operated by Sandia Corporation, a Lockheed Martin Company for the United States Department of Energys.
Chapter 14 Contemporary approaches to measuring and managing performance 14-1 Copyright 2009 McGraw-Hill Australia Pty Ltd PowerPoint Slides t/a Management.
How to commence the IT Modernization Process? 1 Tony Lester August 2011.
1 Computer Systems & Architecture Lesson 3 5. Designing the Architecture.
© 2005 by Prentice Hall Chapter 13 Finalizing Design Specifications Modern Systems Analysis and Design Fourth Edition Jeffrey A. Hoffer Joey F. George.
Software Engineering Lecture 8 Systems Analysis: Concept and Principles 1.
Telelogic Lifecycle Solutions Connecting People, Process, and Tools Greg Gorman Vice President, Product Management Modeling and Test Products.
© Gerald Kotonya and Ian Sommerville 2010 Requirements Validation.
Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides prepared by Gunter Mussbacher with material from: Sommerville & Kotonya 1998, Lethbridge.
Nick Coblentz OWASP CLASP Overview.
Software Process Modeling with UML and SPEM Chris Armstrong Armstrong Process Group
COMET Approach for UML Overview Chapter 6 Designing Concurrent, Distributed, and Real-Time Applications with UML Hassan Gomaa (2001)
1 Notes content copyright © 2004 Ian Sommerville. NU-specific content copyright © 2004 M. E. Kabay. All rights reserved. System Models IS301 – Software.
Nica Valentin–Danut SEM 2012 Service system fundamentals: Work system, value chain, and life cycle.
1 Test documentation and Test case design Iana Mourza QA Lead/Release Lead VMware, Inc
2010 UBO/UBU Conference Title: Information Managements (IMs) Requirements Management and Delivery Framework: Developing the Blueprints for IT Systems Session:
The Masterclass Strategy ◦ What is it? ◦ Influencing ◦ AHP strategy standard Clinical Governance ◦ Elements of CG ◦ Risk management ◦ Evaluation and.
Systems Analysis and Design 8 th Edition Chapter 7 Development Strategies.
PHARMA QUALITY EUROPE / / Quality Information Technology Pharmaceuticals PQE A Road Map to COTS CSV, HPLC 1 A Road Map to.
©Ian Sommerville 2000 Software Engineering, 6th edition. Chapter 26Slide 1 Chapter 26 Legacy Systems.
Chapter - 5 Understanding Requirements Unit II. Introduction Definition : “The broad spectrum of tasks and techniques that lead to an understanding of.
© 2016 SlidePlayer.com Inc. All rights reserved.