requirements analysis and management using innoslate
TRANSCRIPT
Requirements Analysis and Management using InnoslateTHE WEBINAR WILL BEGIN SHORTLY
Interact with UsLinkedIn Group:Innoslate Users
@innoslate
Presenter Profiles
Ph.D. in Physics, U. of South Carolina
B.S. in Physics, George Mason University
INCOSE certified Expert Systems Engineering Professional (ESEP)
President, SPEC Innovations
Our Agenda Where Do Requirements Come From?
What Makes a “Good” Requirement?
What’s the Difference Between Requirements Management and Requirements Analysis?
How Does Innoslate Make Me a Better Requirements Analyst and Manager?
Live Demonstration
Q&A
1
2
3
4
5
6
Where Do Requirements Come From? Customers: “I want an iPhone that is bullet-proof … literally!” Policy Documents: “You can find that in DoDI 4540.05, Change 2,
Enclosure 2, paragraph 2, (1), (b), 2.” Laws: “That’s in US Code Title 50, Chapter 41, Subchapter I, Section 2401,
paragraph 2 (b).” Analysis: “Here are the functional requirements we derived from user
stories.” Architectures: “I have a lot of drawings … OV-1s, SV-3s, etc. What can you
do with these?” Models: “Here is my Requirements Diagram … it has everything you
need!”
So how do I know any of these are any good?
What Makes a Good Requirement?
Original Customer Requirement “shall have 3 engines”
Why? Rationale “So it can land with an engine failure”
New Requirement “shall be able to land with one engine failure”
"Douglas DC-3, SE-CFP" by TowpilotWikipedia
Here we do not specify the design with the requirement!
What Makes a Good Requirement?
The pot shall have 2 handles.
The watering can’s spigot shall be above the fill hole.
The pot’s handles shall be placed in a line on either side of the pot opening.
The watering can’s spigot shall face away from the handle.
Here we add clarity to the requirement!
What Makes a Good Requirement?
Relationships From the originating document To model elements To V&V methods
Coverage Verifies that what your building
matches the requirement Prevents over-engineering
Context Makes learning a system easier Traceability is critical to
having a good requirement
What Makes a Good Requirement?
Requirements need to meet certain established criteria for quality: Clear: unambiguous and not confusing Complete: express a whole idea Consistent: not in conflict with other requirements Design: does not impose a specific solution on design; says “what”, Independent not
“how” Traceable: uniquely identified, and able to be tracked to predecessor and successor
lifecycle items/objects Verifiable: provable (within realistic cost and schedule) that the system meets the
requirement Feasible: implement with existing or projected technology and within cost and schedule Correct: describes the user’s true intent and is legally possible
Green indicates automatic quality checker You may want to add others, this is a good start
What’s the Difference Between Requirements Management and Requirements Analysis?
“Requirements Management is the identification, derivation, allocation, and control in a consistent, traceable, correlatable, verifiable manner of the system functions, attributes, interfaces, and verification methods that a system must meet including customer, derived (internal), and specialty engineering needs.”
[Stevens and Martin, 1995]
”Requirements Analysis: Systems Engineering (SE) technical process that results in the decomposition of end-user needs (usually identified in operational terms at the system level during implementation of the Stakeholder Requirements Definition process).”
[Glossary of Defense Acquisition Acronyms and Terms]
Examples of RM vs. RA RM: Baselining Establishes a common
base between stakeholders
Control & manage scope & requirements creep
Track requirements changes through the design process
Create baselines for milestone goals
RA: Quality and Risk Checking Does the requirement
meet the quality criteria? How can I change it to
meet the criteria? What is the rationale for
this requirement? Does this requirement
pose a risk or create an issue?Are you doing both of these now? … Does your tool support both?
How Does Innoslate Make Me a Better Requirements Analyst and Manager?
Key (not all!) Innoslate Features that Support RM and RA Requirements View Baselining Branching and Forking History Quality Checker Import Analyzer Schema Editor Intelligence Relationships to other Classes Auto-Generation of Requirements from Models Support for Functional Analysis and Solution Synthesis
Is the real job just to “manage” requirements? … Isn’t it really to support the design and acquisition process throughout the lifecycle?
Live Demonstration
Questions and Answers:
ENTER YOUR QUESTION IN THE GOTOWEBINAR CONTROL PANEL