Requirements Management and Analysis with Innoslate

Presented by: Michael Campbell

Interact with Us

LinkedIn Group:Innoslate Users

@innoslate

Presenter: Michael Campbell

Senior Mission Analyst

michael.campbell@specinnovations.com

6 year veteran of the World’s Greatest Navy. Operational experience to include Damage Control, Maintenance Material Management, Enlisted Surface Warfare Specialist. Two 6 Month Deployments with full work ups.

B.S. Biology/Chemistry

Attending Georgia Institute of Technology for Professional Masters of Applied Systems Engineering Degree – Fall 2016

Agenda

• The makings of a good requirement• Importing Requirements into Innoslate• Requirements Analysis• Creating Relationships of Requirements• Executing Traceability • What next?• Summary• Questions?

Considerations• Keep sentences and paragraphs short. Use the active voice. Use proper grammar,

spelling, and punctuation. Use terms consistently and define them in a glossary or data dictionary.

• Avoid long narrative paragraphs that contain multiple requirements. A helpful granularity guideline is to write individually testable requirements.

• Watch out for multiple requirements that have been aggregated into a single statement. Conjunctions like “and / or” should never be used in a requirement and should be split into separate requirements.

• Write requirements at a consistent level of detail. Organization of requirements at different levels allows for easier understanding of functionality as well as satisfying, verifying and tracing the requirement through the process.

• Avoid ambiguity and duplicate requirements that can be lopped into multiple areas of a requirements deck.

• There are plenty of things to consider when performing Requirements Analysis and Management, using Innoslate will certainly make the job a bit easier.

Importing Requirements

• Import Analyzer• Correct Format• Multiple imports• Requirements View

Requirements Analysis

• Using Innoslate to Analyze Requirements• Requirements View• Rationale• Quality Score - Criteria• Improving Quality Score

Creating Relationships

• Multiple ways • Multiple views• Identification of Satisfied, Traced, and Verified

Traceability

• Entity View Tracing• Spider Diagram• Requirements Traceability Matrix• Requirements Traceability and Verification Matrix

What’s Next?

• After requirements, what can you do?• Modeling• Simulation• Test Plans• Verification• Production• Operations Support• Program Management

Summary

• Requirements Management and Analysis is the initial step after the concept phase. There are different types of requirements that can be applied to any project and Innoslate is able to identify these type of requirements in multiple ways.

• Writing good requirements is important for the success of the product in the lifecycle. • Analyzing requirements to be individual statements resolve ambiguity and duplication

which creates more work for verification and testing purposes. • There is more to requirements than just writing them and analyzing them. Program

Management and Systems Engineering methods can be applied after RM&A for more detailed look into the product and its success. The more data you have the more refined your test process can be.

• There are many tools that apply multiple add ons for extra costs to do what Innoslate can do in one tool for a fraction of the cost. These tools are complex and tend to be difficult to use.

• Cloud or Enterprise versions are available with the same capabilities.

Questions?