Difference between revisions of "Requirements Management"

From
Jump to: navigation, search
m
m
Line 121: Line 121:
 
|}
 
|}
 
|}<!-- B -->
 
|}<!-- B -->
 +
 +
= Requirements Management Tools =
 +
{|<!-- T -->
 +
| valign="top" |
 +
{| class="wikitable" style="width: 550px;"
 +
||
 +
<youtube>ze6HtPCJ6cM</youtube>
 +
<b>Using Innoslate for Model Based Systems Engineering (MBSE)
 +
</b><br>SPEC Innovations  Dr. Steve Dam will walk you through the process of using Innoslate’s modeling and simulation capabilities while applying a MBSE methodology. At its core, Innoslate is a full model-based systems engineering tool. Within Innoslate, system models are formalized and capable of simulation to derive cost, schedule, and performance data. Your webinar will cover: Functional modeling Functional modeling is at the heart of how Innoslate derives new requirements and ensures logical accuracy. Physical modeling  We can describe synthesizing the physical model in Innoslate with eight different diagrams, including the Asset Diagram, Layer Diagram, Block Definition Diagram, and Internal Block Diagram.  Executing a model Innoslate includes a ‘Discrete Event Simulator’ to verify functional diagram’s logic, calculate cost, compute time, and quantify performance. Relating Requirements to Diagrams Requirements traceability ensures that the lifecycle and origin of a requirement is fully tracked. Innoslate includes relationship matrices to represent traceability relationships between entities in tabular view. Requirements Generation After modeling the system, often an engineer will derive textual requirements from the models by hand. Innoslate includes an automatic facility that generates requirements documents in a standard format (as outlined in “The Engineering Design of Systems: Models and Methods“).
 +
|}
 +
|<!-- M -->
 +
| valign="top" |
 +
{| class="wikitable" style="width: 550px;"
 +
||
 +
<youtube>ID2</youtube>
 +
<b>HH2
 +
</b><br>BB2
 +
|}
 +
|}<!-- B -->
 +
{|<!-- T -->
 +
| valign="top" |
 +
{| class="wikitable" style="width: 550px;"
 +
||
 +
<youtube>ID3</youtube>
 +
<b>HH3
 +
</b><br>BB3
 +
|}
 +
|<!-- M -->
 +
| valign="top" |
 +
{| class="wikitable" style="width: 550px;"
 +
||
 +
<youtube>ID4</youtube>
 +
<b>HH4
 +
</b><br>BB4
 +
|}
 +
|}<!-- B -->
 +
 +
  
 
= The Expert =
 
= The Expert =

Revision as of 09:59, 16 September 2020

Youtube search... ...Google search


Being semi-structured, requirements led themselves to Natural Language Processing (NLP) nicely.


Analyzing the Entire Program: Applying Natural Language Processing to Software Engineering
A powerful, but limited, way to view software is as source code alone. Mathematical techniques, such as abstract interpretation and model checking, can indicate whether the program satisfies a formal specification. But, where does the formal specification come from? A program consists of much more than a sequence of instructions. Developers make use of test cases, documentation, variable names, program structure, the version control repository, and more. I argue that it is time to take the blinders off of software analysis tools: tools should use all these artifacts to deduce more powerful and useful information about the program. Researchers are beginning to make progress towards this vision. In this talk, I will discuss four initial results that find bugs and generate code, by making use of variable names, error messages, procedure documentation, and user questions.

Lecture - Requirements, Models, and Properties: Their Relationship and Validation
Lecture by Mats Heimdahl, Ph.D. of University of Minnesota. Getting the system requirements right in a development project is crucial for success. One highly promising approach to rigorous requirements capture and definition is modeling of the requirements in formal notations. In such Model-Based Requirements Engineering, an initial set of natural language requirements forms the basis for an initial behavioral model of the intended system behavior and an initial formalization of the natural language requirements into formal requirements properties. Recent breakthroughs in formal verification now allow formal verification techniques to be used to analyze the set of requirements properties as well as the behavioral models. For example, the set of requirements properties can be checked for consistency and the behavioral model can be verified against the formalized requirements properties. The results from this analysis can then be used in an iterative requirements validation process where the analysis results serve as a basis for the modification, refinement, and extension of the set of requirements and/or the behavioral models to bring them in conformance with the truly desired (or notional) system requirements.

Analysis of Software Requirements with Natural Language Processing
Prof. Lionel Briand University of Luxembourg, Luxembourg Huawei Workshop on Applications of Artificial Intelligence to Software Engineering December 15th 2017

Applying Machine Learning Techniques to the Flexible Assessment of Requirements Quality
In the world of systems engineering, the importance of having high quality requirements is well known and that is why there are standards and guidelines that establish the characteristics that the requirements must have for considering them of good quality. To obtain quality measurements of the requirements it is common to use quantitative quality metrics based on established standards. However, the risk is to build assessment methods and tools that are both arbitrary and rigid in the parameterization and combination of metrics. This webinar is focused on the presentation of a flexible method to assess and improve the quality of requirements that can be easily adapted to different contexts, projects, organizations and quality standards, with a high degree of automation. In the method proposed, the domain experts contribute with an initial set of requirements that they have classified according to their quality, and their quality metrics are extracted. Then machine learning techniques are used to emulate the implicit expert’s quality function. A procedure to suggest least-effort improvements in bad requirements is also provided. The method is easily tailorable to different contexts, different styles to write requirements, and different demands in quality. The whole process of inferring and applying the quality rules adapted to each organization is highly automated.

AI for Requirements Management
IBM is bringing the power of Watson AI to the engineering life cycle with Requirements Quality Assistant. Get started today! Learn more about IBM's Engineering Requirements Management solutions http://ibm.co/2UxZGJN

ExtractorAI Presentation
IMP Consulting - Artificial Intelligence comes to Compliance--and it can save you time, money and lower your risk.

Quick Bytes with CTO Sky Matthews: Thoughts on AI and requirements management
Learn more about AI and requirements management with IBM: https://ibm.co/2Xcbjrp IBM Watson IoT CTO Sky Matthews talks about how AI is playing a significant role in the systems that we build and also will play a big role in how we build these systems. How can engineers, developers and coders utilize and learn from the massive amounts of data that is generated from the design of things, and ultimately do it better?

Why does DoD struggle in using Machine Learning to automate decision making?
Software Engineering Institute | Carnegie Mellon University Watch Elli Kanal discuss

The Full Stack: AI for Requirements Management
Watch the experts tackle engineering complexity in real-time in this AI for Requirements Management episode of the Full Stack, from IBM Watson IoT. IBM's Engineering Requirements Management tools now feature the option to embed Watson AI to improve quality and minimize risk during the writing of requirements.

The Full Stack: Requirements Management
Watch the experts tackle engineering complexity in real-time in this Requirements Management episode of the Full Stack, from IBM Watson IoT. IBM Engineering tools can provide valuable insights for systems engineers in the area of requirements management and automation

Requirements Management Tools

Using Innoslate for Model Based Systems Engineering (MBSE)
SPEC Innovations Dr. Steve Dam will walk you through the process of using Innoslate’s modeling and simulation capabilities while applying a MBSE methodology. At its core, Innoslate is a full model-based systems engineering tool. Within Innoslate, system models are formalized and capable of simulation to derive cost, schedule, and performance data. Your webinar will cover: Functional modeling Functional modeling is at the heart of how Innoslate derives new requirements and ensures logical accuracy. Physical modeling We can describe synthesizing the physical model in Innoslate with eight different diagrams, including the Asset Diagram, Layer Diagram, Block Definition Diagram, and Internal Block Diagram. Executing a model Innoslate includes a ‘Discrete Event Simulator’ to verify functional diagram’s logic, calculate cost, compute time, and quantify performance. Relating Requirements to Diagrams Requirements traceability ensures that the lifecycle and origin of a requirement is fully tracked. Innoslate includes relationship matrices to represent traceability relationships between entities in tabular view. Requirements Generation After modeling the system, often an engineer will derive textual requirements from the models by hand. Innoslate includes an automatic facility that generates requirements documents in a standard format (as outlined in “The Engineering Design of Systems: Models and Methods“).

HH2
BB2

HH3
BB3

HH4
BB4


The Expert

The Expert (Short Comedy Sketch)
Starring: Orion Lee, James Marlowe, Abdiel LeRoy, Ewa Wojcik, Tatjana Sendzimir. Written & Directed by Lauris Beinerts Based on a short story "The Meeting" by Alexey Berezin Produced by Connor Snedecor & Lauris Beinerts Director of Photography: Matthew Riley Sound Recordist: Simon Oldham Production Designer: Karina Beinerte 1st Assistant Director: James Hanline Make-up Artist: Emily Russell Editor: Connor Snedecor Sound Designer: James Bryant Colourist: Janis Stals Animator: Benjamin Charles

Retrieved from "https://primo.ai/index.php?title=Requirements_Management&oldid=16855"