How to Write Requirements - How to MBSE PT.1

HowtoWriteRequirements
Presented by: Steven H. Dam, Ph.D., ESEP – Part One of the “How to MBSE” webinar series.

AskUsYourQuestions
• Ask us your questions using
the panel on the right
• This presentation is being
recorded and will be made
available to you.
• Contact us after the webinar
through
• support@Innoslate.com
• Call 571.485.7800
• LinkedIn Innoslate User Group
• Twitter
2
Proprietary of SPEC Innovations® February 17, 2022, Dr. Steven Dam

MeetYourHost
• President and Founder of SPEC
Innovations
• Participated in the development of C4ISR
and the DoDAF
• Expert Systems Engineering Professionals
Certificate
• steven.dam@specinnovations.com
• @stevenhdam
3

“HowtoMBSE”WebinarSeries:
WhereDoesRequirementsManagementFitintotheSystemLifecycle?
4
Documentation
Requirements
Analysis
Functional
Analysis
Verification
Validation
Risk Analysis
Operations
Analysis

AProvenRequirementsAnalysisProcess
Source
Documents
External Interface
Database
User Needs
Decompose Statements
Critical Issue?
Statement
Verifiable?
Determine Options and Perform
Trade Studies
See System Analysis and
Control for details
Resolve Issues with Customer
YES
NO
Coordinate Changes to Make
Statement Verifiable
NO
Review Statements and Risks
with Customer
Update Knowledgebase
YES
Identify Risks and Plan Mitigation
Updated
Requirements
Traceability Matrix
Preliminary Test
Requirements
Standards Selected
Change
Requests
SE
Knowledgebase
Trace Requirements to
Actions/Assets/Measures
5

WhatYouWillLearn
• Gathering your requirements
• Baselining and change management
• Using AI to manage quality in your requirements
• Checking for risk in your requirements
• Adding relationships (traced, verified, and satisfied)
• Creating reports and matrices
• Creating verification requirements
6

BaseliningRequirements
• “Once your requirements have been defined based on the
baselined scope, they must be agreed to by all key stakeholders
and formally baselined and controlled. Baselining your
requirements before design puts your requirements under
configuration control and the resulting configuration control
process. ”
• - Why Do We Need to Baseline Our Requirements
7

BaselineYour
Requirements
8
Baselining your requirements allows for proper
configuration control.
Create baseline reports to send to
stakeholders.
Tips in Innoslate:
Baselined documents will have vertical blue
bars.
If the vertical bar is blue in the live document,
it signifies that the document has not changed
from the last baseline.
Seek stakeholder and team approvals using the
comments panel on the left or through the
workflow tool.

TwoMethods
For Requirements Analysis
• Heuristic Analysis
• Functional Analysis
9

Performing heuristics analysis for requirements.
10
HeuristicAnalysis

Differencebetweenstatementsandrequirements
Statements Requirements
A statement specifies text referenced by the
knowledgebase and usually contained in an Artifact.
Descriptions that support the system.
• Reports
• White Papers
• Planning Documents
Example:
Elvis is King!
Our goal is to be the first on Mars.
A requirement identifies a capability,
characteristic, or quality factor of a system to
have value and utility to the user.
Example:
The pump shall weigh no more than 1.2 kg.
• Shall: requirement that is contractually
binding, meaning it must be implemented,
and its implementation verified
• Will: Statements of Fact (Constraint, but not
subject to verification)
• Should: Desirable but not Necessary
11

CharacteristicsofGoodRequirements
 Clear: Unambiguous and not confusing
 Complete: Express a whole idea
 Correct: Describes the user’s true intent and is legally possible
 Consistent: Not in conflict with other requirements
 Design: Does not impose a specific solution on design; says “what”, Independent not “how”
 Feasible: Able to be implemented with existing technology, and within cost and schedule
 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
12
Reduces Communication Errors

HeuristicsforDevelopingRequirements
Artificial Intelligence NLP Tools Can Assist Here
• DON’T use ambiguous language
• DON’T use bullet lists; use numbered lists instead
• DON’T use jargon or acronyms
• DON’T use language that provides an escape clause
• Ex: “The user shall be able to access the Internet as
often as is practicable”
• DON’T write long, rambling sentences
• DON’T put two requirements in one sentence
• Ex: “The system shall … and …”
• DON’T use vague terms
• Ex: “user-friendly”
• DON’T include suggestions or possibilities
• Ex: “may”, “should”, “ought”
• DON’T include wishful thinking
• Ex: “The system shall be 100% reliable”
13

ChecktheQualityofYourRequirementsAutomatically
14
Innoslate checks for
6 of the 8 quality
criteria using
AI/NLP technology.

UseIntelligenceViewto
AnalyzeforOtherHeuristics
15
• Intelligence View provides 68
heuristics for better overall
modeling using NLP
• These include 6 global
heuristics and 9 specifically
for requirements
• Heuristics can be set by users
to “Error”, “Warning”, and
“Ignore”
• Provides means to fix
problems as well

DocumentManagement
EnablesAnalysisofAllYour
RequirementsDocuments
16
• Innoslate enables you to
manage all your
documentation, not just
requirements documents
• Innoslate’s cross projects
feature enables sets of
documents to be created
and specific requirements
used
16

TheSchemaEditorProvides
theMeanstoCapture
DifferentTypesInformation
17
• The 'Schema Editor' enables
users to extend their project's
current database schema to
better meet their needs
• Use cases include creating new
classes (or subclasses), adding
additional properties or
relations on existing classes,
creating new labels, and much
more
• We recommend care be used in
modifying the schema to avoid
duplication and confusion

UseLabelsforSortingandFiltering
18
• A label is an identifying short word or phrase used to classify
similar entities into categories, much like a folder system is used to group
together like projects
• Differing from project folders, however, more than one label can be applied to
each entity, allowing the user to categorize, and subsequently filter, similar
entities as they see fit
• Customize and edit labels in Schema Editor
• https://help.innoslate.com/users-guide/schema-editor/customizing-
labels/

CreateReports
19
• Reports can be generated from
Documents View for a specific
document
• Can also create saved queries in
Database View to show tabular
output
• Use the settings to
select columns and related
classes
• Save query for yourself or the
entire project (if owner)
Proprietary of SPEC Innovations® February 17, 2022, Dr.

20
FunctionalAnalysis

UseFunctionalandRisk
AnalysistoDeriveGood
Requirements
21
• Provides a means to model
processes, from which you
can derive good
requirements
• You can also execute this
process to identify timing,
resource, and other potential
issues
• Use risk diagrams to capture
and track risks to the process
and resulting requirements

DerivePerformance
RequirementsUsing
Simulation
22
• Innoslate and Sopatra
provide discrete event and
Monte Carlo simulation
• Sopatra adds special features
to determine if the process
executes within the available
operational time window
(AOTW)

ProcessModelingcanincludetestprocesses
23
•Create Test Cases to generate action diagram
•Link test process to test plan
23

UseTestCenterDevelopTest
CasestoEnsureRequirements
areVerifiable
24
Use Expected Results during planning
Use Actual Results and status during V&V

UseTraceabilitySpiderDiagram
toLinkBetweenRequirements,
Actions,Assets,andTestCases
• Shows how a single entity (database
object) is related to the rest of the
system
• Drag and drop new entities and create
relationships right from the diagram
• Sidebar enabled

UseTraceabilityMatricesto
EnsureRequirements
Traceability
• Traces between requirements
and any other class of
information can be made by
clicking an “X” in the box
• The Traceability Assist &
Suspect Assist features use NLP
algorithms to identify appropriate
and inappropriate connections
Proprietary of SPEC Innovations® February 17, 2022, Dr. Steven Dam 26

WhatAboutHumanErrors?
• We discussed writing good requirements for medical device errors, but what about human errors
• Sopatra takes a human factors engineering approach to develop and analyze procedures that work
• NLP technology used to determine See & Hear cues and determine Long Term Memory needs
27
Create a free account at Sopatra.innoslate.com.

CreatingVerification
Requirements
28

CreatingVerification
Requirements
29
• Innoslate provides for the
development of verification
requirements
• Labels provide the means to
identify verification method(s)
• Analysis
• Demonstration
• Inspection
• Modeling & Simulation
• Test

GenerateaVCRM
30
• The verification method labels
are used to generate this report
• Output is an MS Excel
spreadsheet
• Red bars show requirements
that have no verification method
selected

AnAlternativeApproach
31
• Add a new subclass of
Statement:
• Verification Requirement
• Use the following attributes:
• Verification Method
• Acceptance Criteria
• Evidence
• Rationale
• Add relationships
• verifies
• traced to

BeaRequirementsHero
When We Write Good Requirements; There’s No News Story
• Remember what we do matters
• High-quality requirements save projects, products,
systems, and lives
• Develop high-quality requirements by using Innoslate’s
Quality Checker and Intelligence View
• Reduce medical staff errors by using Sopatra
32

Questions and
Answers
Use the panel on the right to ask your questions
33

Next Webinar
“How to Develop and Simulate
Models (with no coding
experience!)”
March 24, 2022, 11:00 am ET
Go To Webinar
34

MoreResources
SPEC Innovations offers training, books, videos, documentation, trials, and more
Training: specinnovations.com/training
Books: “Real MBSE” textbook and lab manual available on
Amazon
Videos: Visit the SPEC Innovations Youtube channel
LinkedIn: Innoslate and Systems Engineers User Group
Documentation: help.Innoslate.com
Trial: cloud.Innoslate.com
35

SPEC Innovations offers training, books, videos, documentation, trials, and more
Thank you!
Visit cloud.innoslate.com for a trial.
SPEC Innovations
@Innoslate
Innoslate User Group
Innoslate.com/blog
571.485.7800
innoslate.com
36

How to Write Requirements - How to MBSE PT.1

Recommended

Recommended

More Related Content

Similar to How to Write Requirements - How to MBSE PT.1

Similar to How to Write Requirements - How to MBSE PT.1 (20)

More from Elizabeth Steiner

More from Elizabeth Steiner (20)

Recently uploaded

Recently uploaded (20)

How to Write Requirements - How to MBSE PT.1

Editor's Notes