Price: $3,999.00

Length: 4 Days
Print Friendly, PDF & Email

Model Based Requirements Engineering, MBRE Training

Model-Based Systems Engineering (MBSE) is a methodology that uses visual models to depict the elements and architecture of a system, as well as the relationships between those elements. This as opposed to the older approach of using stacks of documents.

In the same way, Model-Based Requirements Engineering (MBRE) rely on drawings to communicate more precise and concise requirements. This is the direct result of trying to use a natural language such as English, which is verbose and loaded with built-in ambiguities.

Consequently, specifying system requirements (SysReqs) is a critical activity in complex systems development. The SysReqs and emerging architecture are constructed through gradual and iterative transition from the problem domain and operational stakeholder requirements to the conceptual solution domain.

Not only are model-based requirements more consistent and visual than textual ones, they are amenable to checking, simulation, and verification.
One rather substantial challenge for systems engineers (SEs) using an MBRE approach is that stakeholders are often unwilling to work in drawings rather than the standard textual documents.
Additionally, there is a need to map visual models to textual specifications and to cover the problem domain and the conceptual solution domain in a single model.

Model Based Requirements Engineering Course Specifics

Model Based Requirements Engineering training introduces you to model-based requirements engineering and management by providing various perspectives that shaped the fundamentals and principals of this technique. Such perspectives consider each requirement one by one in regards to its definition, but then also give meaning to each requirement by positioning it into the proper “context.”

The requirement being put into a context is known as a “use case.” It is put based on either the stakeholders or levels of hierarchy in a system. Then, every use case must be evaluated and validated by a series of scenarios and official mathematical and logic-based verifications that deliver the precision necessary for safety-critical and mission-critical systems.

Model Based Requirements Engineering Training

Model-based requirements engineering training also discusses the important question of modeling notations for requirements modeling and it includes the use and application of UML, SysML, text and tabular formats.

Model-based requirements engineering training also covers all the key factors of Model-Based requirements engineering including concepts, modeling, structures and hands-on exercises.

Tonex Training Feature

Model-based requirements engineering training is a combination of interactive lectures and practical exercises. The hands-on training part of the class includes labs, individual/group activities and hands-on workshops. Participants are encouraged to bring in their own sample project from their organization to work on, or they can practice with the real-life case studies provided by the Tonex instructor.

Added Value of the Training

  • Enhanced systems engineering by the use of MBSE
  • How to accomplish more effective communication, improved understanding, and how to reduce complication by modeling
  • How to present the advantages of MBSE and their relevant significance to stakeholders within the business
  • How to apply MBSE into a business
  • Greater self-assurance for you, your teams, your business and your clients

Learn About:

  • The need for requirements
  • Requirements engineering and requirements management
  • Requirements modeling
  • Context-based modeling
  • A framework for requirements modeling
  • Modeling requirements in UML
  • Requirement model traceability
  • Non-functional software requirements
  • Briefly on requirements in SysML
  • Briefly on formal methods
  • The need for an efficient technique to requirements modeling
  • The main visions that build a model-based method, including the meta-model and what contains each view
  • How to model individual requirements and use cases
  • How to arrange and manage requirements, including traceability and automation


  • System engineers
  • Requirements engineers
  • System managers
  • Software engineers and managers
  • Quality personnel

Training objectives

Upon the completion of model-based requirements engineering training, the attendees are able to:

  • Understand and describe the principles and concepts of requirements engineering and management
  • Apply a systematic method to modeling requirements in a model-based systems engineering (MBSE) environment
  • Make a decision as to which level of rigour and relevant techniques is suitable for them
  • Explain the concept of MBSE, and how it compares to traditional systems engineering
  • Discuss the advantages of MBSE
  • Apply MBSE in their industry
  • Understand how SysML supports MBSE
  • Offer various ways their organization can apply a systems modeling tool to construct systems models
  • Apply MBSE methods to specify and design systems
  • Transition an organization to MBSE
  • Determine and explain the use of SysML™ diagrams
  • Apply a formal approach to create a system model in a modeling tool
  • Use an activity diagram to model system behavior
  • Use a state diagram to model system behavior
  • Use a sequence diagram to model system behavior
  • Use a requirements diagram to model requirements
  • Use a use case diagram to model requirements
  • Use block diagrams to model structure
  • Assign behavior to framework in a model
  • Identify parametric and restraints and describe their application

Course Outline


  • Requirements engineering definition
  • Fundamentals of communication theory
  • Characteristics of a requirements engineer
  • Requirement types
  • Importance and categorization of quality requirements

System and Context Boundaries

  • System context
  • Defining system and context boundaries
    • Defining the system boundary
    • Defining the context boundary
  • Documenting the system context

Eliciting Requirements

  • Requirements sources
    • Stakeholders and their roles
    • Managing stakeholders in the project
  • Requirements classification based on the Kano model
  • Elicitation techniques
    • Types of elicitation methods
    • Survey techniques
    • Creativity techniques
    • Document-based techniques
    • Observation techniques
  • Support techniques

Documenting Requirements

  • Document design
  • Types of documentation
    • The three views of requirements
    • Requirements documentation using natural language
    • Requirements documentation using conceptual models
    • Hybrid requirements documents
  • Document framework
  • Standardized document structures
  • Customized standard contents
    • Introduction
    • General view
    • Requirements
    • Appendices
  • Using requirements documents
  • Quality standards for requirements documents
    • Unambiguity and consistency
    • Clear structure
    • Modifiability and extendibility
    • Completeness
    • Traceability
  • Quality standard for requirements
  • Documenting requirements in natural language
  • Impacts of natural language
    • Nominalization
    • Nouns without reference Index
    • Universal measurements
    • Incompletely specified conditions
    • Incompletely specified process verbs
  • Requirement construction using templates
    • Identify the legal obligation
    • The requirement core
    • Recognize the activity of a system
    • Enter objects
    • Identify logical and temporal conditions

Model-Based Requirements Documentation

  • The term model
    • Properties of models
    • Modeling languages
    • Requirements models
    • Advantages of requirements models
    • Combined use of models and natural language
  • Goal models
    • Goal documentation using and/or trees
    • Example of and/or trees
  • Use Cases
    • UML Use Case diagrams
    • Modeling elements of UML Use Case diagrams
    • Example of UML Use Case diagrams
  • Use Case requirements
  • Three perspectives on the requirements
  • Requirements modeling in the data perspective
    • Entity-relationship diagrams
    • Modeling elements of entity-relationship diagrams
    • Example of an entity-relationship diagram
    • UML class diagrams
    • Modeling elements of class diagrams
    • Example of a UML class diagram
  • Requirements modeling in the functional perspective
    • Data flow diagrams
    • Modeling elements of data flow diagrams
    • Example of a data flow diagram
    • Models of the functional perspective and control flow
    • UML activity diagrams
    • Sequence modeling using UML activity diagrams
    • Control flow of main and alternative scenarios
  • Requirements modeling in the behavioral perspective
    • Statecharts
    • UML state diagrams

Modeling with SysML

  • SysML in Support of model-based requirements engineering
  • Modeling functionality with Use Cases
  • Modeling requirements and their relationships
  • Modeling structure with blocks (Block Definition Diagrams)
  • Modeling structure with blocks (Internal Block Diagrams)
  • Modeling flow-based behavior with activities
  • Modeling event-based behavior with state machines
  • Modeling message-based behavior with interactions
  • Modeling constraints with parametric
  • Modeling cross-cutting relationships with allocations

Requirements Validation and Negotiation

  • Fundamentals of requirements validation
  • Fundamentals of requirements negotiation
  • Quality aspects of requirements
    • Quality aspect “content”
    • Quality aspect “documentation”
    • Quality aspect “agreement”
  • Principles of requirements validation
    • Engaging the proper stakeholders
    • Specifying the determination and the correction of errors
    • Validation from various perspectives
    • Sufficient variation of documentation type
    • Building of development artifacts
    • Double validation
  • Requirements validation methods
    • Commenting
    • Inspection
    • Walk-through
    • Perspective-based reading
    • Validation through prototypes
    • Using checklists for validation
  • Requirements negotiation
    • Conflict identification
    • Conflict analysis
    • Conflict resolution
    • Documentation of the conflict resolution

Requirements Management

  • Assigning attributes to requirements
    • Attributes for natural language requirements and models
    • Attribute scheme
    • Attribute types of requirements
  • Visions on requirements
    • Selective views on the requirements foundation
    • Condensed views on the requirements
  • Prioritizing requirements
    • Method for requirements prioritization
    • Techniques for requirements prioritization
    • Ranking and top-ten technique
    • Single-criterion classification
    • Kano classification
    • Prioritization matrix according to Wiegers
  • Traceability of requirements
    • Advantages of traceable requirements
    • Purpose-driven definition of traceability
    • Classification of traceability relations
  • Representation of requirements traceability
    • Text-based references and hyperlinks
    • Trace matrices
    • Trace graphs
  • Versioning of requirements
    • Requirements versions
    • Requirements configurations
    • Requirements baselines
  • Management of requirements changes
    • Requirements changes
    • The change control board
    • The change request
    • Classification of incoming change requests
    • Basic method for corrective and adaptive changes

Hands-On Activities

  • Labs
  • Individual/group activities
  • Hands-on workshops

Tonex Hands-On Workshop Sample

  • Defining the project
  • Defining the goals and objectives
  • Identifying the requirements
  • Fully understanding the system and its components
  • Defining the Use Cases
  • Modeling the requirements
  • Verifying and validating the requirements
  • Presenting the results to the class


Model Based Requirements Engineering, MBRE Training

Request More Information

Please enter contact information followed by your questions, comments and/or request(s):
  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.

Request More Information

  • Please complete the following form and a Tonex Training Specialist will contact you as soon as is possible.

    * Indicates required fields

  • This field is for validation purposes and should be left unchanged.