1 System Engineers Toolbox 1 Compliance Automation, Inc. INCOSE: NM Enchantment Chapter By Cheryl Hill August 12, 2009.

Slides:



Advertisements
Similar presentations
You have been given a mission and a code. Use the code to complete the mission and you will save the world from obliteration…
Advertisements

RAC One Node – The “Always On” Single Instance Database
FIS Enterprise Solutions EPK/EPM Implementation
Requirements Engineering Processes – 2
PROJECT MANAGEMENT BASICS
Software Requirements
© Copyright 2006 FPT Software 1 © FPT SOFTWARE – TRAINING MATERIAL – Internal use 04e-BM/NS/HDCV/FSOFT v2/3 How to work in Fsoft project Authors: KienNT.
Requirements Engineering Process
Chapter 8 Software Prototyping.
Chapter 1 The Study of Body Function Image PowerPoint
Copyright © 2011, Elsevier Inc. All rights reserved. Chapter 5 Author: Julia Richards and R. Scott Hawley.
1 Copyright © 2010, Elsevier Inc. All rights Reserved Fig 2.1 Chapter 2.
M. Elowitz 4/11/07 1 REQUIREMENTS FOR PROJECT SUCCESS A Paper by Ralph Young in Crosstalk December, 2006
ASYCUDA Overview … a summary of the objectives of ASYCUDA implementation projects and features of the software for the Customs computer system.
RECORD KEEPING Cooperative Development of Operational
for Cabin Safety Inspectors
Business Transaction Management Software for Application Coordination 1 Business Processes and Coordination.
Objectives To introduce software project management and to describe its distinctive characteristics To discuss project planning and the planning process.
SIP/2012/ASBU/Nairobi-WP/19
Jeopardy Q 1 Q 6 Q 11 Q 16 Q 21 Q 2 Q 7 Q 12 Q 17 Q 22 Q 3 Q 8 Q 13
Jeopardy Q 1 Q 6 Q 11 Q 16 Q 21 Q 2 Q 7 Q 12 Q 17 Q 22 Q 3 Q 8 Q 13
Title Subtitle.
0 - 0.
DIVIDING INTEGERS 1. IF THE SIGNS ARE THE SAME THE ANSWER IS POSITIVE 2. IF THE SIGNS ARE DIFFERENT THE ANSWER IS NEGATIVE.
Addition Facts
Year 6 mental test 5 second questions
Introduction to Relational Database Systems 1 Lecture 4.
Making the System Operational
ZMQS ZMQS
IAEA Training in Emergency Preparedness and Response Module L-051 General Concepts of Exercises to Test Preparedness Lecture.
Electric Bus Management System
EMS Checklist (ISO model)
1 Dr. Ashraf El-Farghly SECC. 2 Level 3 focus on the organization - Best practices are gathered across the organization. - Processes are tailored depending.
TRAIL BRIDGE INSPECTION 101
Testing Workflow Purpose
Abstract To provide efficient and effective access to enterprise information that meets stakeholder needs and supports mission success, NASA is implementing.
ABC Technology Project
Enterprise Performance Life Cycle (EPLC) Stage Gate Reviews
Checking & Corrective Action
Software Change Impact Analysis
Software Requirements
Quality Manual for Interoperability Testing Morten Bruun-Rasmussen Presented by Milan Zoric, ETSI.
Squares and Square Root WALK. Solve each problem REVIEW:
1 Functional Strategy – IS & IT Geoff Leese November 2006, revised July 2007, September 2008, August 2009.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 28 Slide 1 Process Improvement 1.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 4 Slide 1 Software processes 2.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 27 Slide 1 Quality Management.
Lecture 5: Requirements Engineering
Chapter 5 Test Review Sections 5-1 through 5-4.
SIMOCODE-DP Software.
GG Consulting, LLC I-SUITE. Source: TEA SHARS Frequently asked questions 2.
1 First EMRAS II Technical Meeting IAEA Headquarters, Vienna, 19–23 January 2009.
Addition 1’s to 20.
25 seconds left…...
©Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapters 1,3 Slide 1 Software Engineering Software Engineering.
© Paradigm Publishing Inc Chapter 10 Information Systems.
Week 1.
We will resume in: 25 Minutes.
©Brooks/Cole, 2001 Chapter 12 Derived Types-- Enumerated, Structure and Union.
© Prentice Hall CHAPTER 15 Managing the IS Function.
1 Unit 1 Kinematics Chapter 1 Day
PSSA Preparation.
Chapter 11: Systems Development and Procurement Copyright © 2013 Pearson Education, Inc. publishing as Prentice Hall Chapter
How Cells Obtain Energy from Food
McGraw-Hill©The McGraw-Hill Companies, Inc., 2001 Chapter 16 Integrated Services Digital Network (ISDN)
S D Compliance Automation, Inc 1 Larry Fellows Compliance Automation, Inc. When Any Road Won’t Do… Project Scope Points the Way.
1 Requirements Best Practices. Webinar Host Presenter: Cheryl Hill, PMP Requirements Experts
Methods for Effective Requirements Development
10 Steps to Better Requirements
Presentation transcript:

1 System Engineers Toolbox 1 Compliance Automation, Inc. INCOSE: NM Enchantment Chapter By Cheryl Hill August 12, 2009

2 Objectives 2 To provide three tools to help you: Elicit requirements Get all the requirements Communicate better with customers and developers Reduce rework due to requirement defects

3 33 SCOPE Requirement Check List Rationale

4 Toolkit 1: Scope Scope is an iterative process Drivers and Constraints Operational Concepts Interfaces Schedule Need Authority and Responsibility Assumptions Risk Scope is an iterative process Goals and objectives Business Case or Mission Budget

5 Why Scope? Effect Of Requirements Definition Investment On Program Costs Why are you running so fast when you dont know where you are going? German proverb

6 NEED NASA – vehicle to replace shuttle NASA – make human access to space safer and cheaper

7 NEED IS –derived from a problem assessment –why we are doing something –a way to ensure we stay on track IS NOT –the product –subject to change MUST BE –in writing –available to all

8 Goals and Objectives Goals –define specific things to accomplish to meet the need Objectives –define how we will know when we get there Transport crew to and from space station Twice as safe as shuttle

9 Stakeholders Engineering Software Logistics Operations Testing Manufacturing Maintenance System Engineering Customer Reliability Developers Security Training Safety Quality Procurement

10 External Interfaces database command status command & data Your System Test Physical Power

11 Operational Concepts Maintenance Development Test and Verification Transportation Deployment Installation Integration Transition Manufacturing Training Logistics Upgrades Operations Storage Disposal Life-cycle

12 Toolkit 2: Requirement Checklist Requirement wording Ambiguities Implementation Operations

13 Good Requirements Needed Verifiable Attainable –Technically –Cost –Schedule Customer-Centered Products, p. 119 Mandatory Characteristics

14 Characteristics of Good Requirements Improving Communications One Thought Concise Simple Stated Positively Grammatically Correct Can only be understood one way Customer-Centered Products, p. 119

15 What a requirement must state Who What Connect WHO is responsible –The system –The software –The structure WHAT shall be done –operate at a power level of … –acquire data from … –withstand loads up to …

16 Use The Correct Terms Requirements are binding - Shall Facts or Declaration of Purpose - Will Goals are non-mandatory provisions - Should Dont use must

17 Avoid Ambiguous Terms etc. Maximize Sufficient User-friendly Robust High speed Including, but not limited to Minimize Adequate Easy Ultra-low power TBD Customer-Centered Products, p Indefinite pronouns - this - these - it - and/or - be able to/be capable of Accommodate Support

18 How: The aircraft shall have three engines (DC-3 initial requirements). What: The aircraft shall meet the operation requirements with a single engine out. The magic of why Implementation Versus Requirements How: The System shall include flight performance instrumentation. What: The System shall measure its flight performance. What do you want to verify?

19 Operations Statements Requirement The operator shall have the capability to change the given thread selection. Rewrite The system shall allow a change of thread selection during operations. The system shall provide a user interface for thread selection changes.

20 Toolkit 3: Rationale What How Why

21 Rationale – defines Why a requirement is needed What assumptions were made What design effort drove the requirement Information to help understand the requirement Source of any numbers

22 What NOT to Put in Rationale A rewrite of the requirement Hidden requirements Copy of another requirements rationale Everything you know on the topic

23 Rationale Benefits Key to understanding Reduce interpretation problems Facilitate maintenance and upgrades Preserve corporate knowledge

24 Example Requirement: The truck shall have a height of no more than 14 feet. Rationale: Ninety-nine percent of all U.S. interstate highway overpasses have a 14- foot or greater clearance. (Assumption: The truck will be used primarily on U.S. interstate highways for long-haul, intercity freight in the U.S.)

25 SCOPE Requirement Check List Rationale Your Tool Box