Model Based System Engineering Flashcards

1
Q

What is Model-Based Systems Engineering (MBSE)?

A

MBSE is a systems engineering methodology that uses modeling to support

  • system requirements,
  • design,
  • analysis,
  • verification and validation

from the conceptual design throughout the lifecycle of development.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What is the main goal of MBSE?

A
  • Improve the quality of the products being developed, …
  • increase productivity
  • provide better documentation through a model-centric approach, rather than a traditional document-based approach
  • reduce risks
  • improve communication among system development team
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Why would MBSE reduce risks?

A
  • Improved accuracy and consistency: Consistent definition and alignment of all elements -> better understanding of complexities -> less misunderstanding of system requirements and specifications
  • Enhanced traceability of requirements -> easier verification that all reqs have been met & that changes are systematically assessed for impact -> preserves scope creep, prevents overlooking of critical aspects
  • Early problem detection: Through simulation
  • Integrated validation & verification: Model is checked continuously against specified requirements -> ensures that system conforms to intended design and functions
  • Better decision making: Visualization helps stakeholders understand complexity and making informed decisions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

How does MBSE differ from traditional systems engineering?

A
  • traditional systems engineering: relies heavily on document-based communication
  • MBSE: utilizes formalized models as the primary means of information exchange between engineers and stakeholders
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Which types of requirements will remain in textual language despite the trend towards model-centric development?

A

Initial requirements and some non-functional requirements.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

What most common modeling language used in MBSE?

A

SysML (Systems Modeling Language) is the most widely used language in MBSE

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

What are the key processes involved in MBSE?

A
  • requirements engineering
  • system architecture and design development,
  • verification and validation
  • operations and maintenance modeling.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What role do models play in requirements engineering in MBSE?

A
  • help capture, analyze, trace, and manage system requirements
  • Models facilitate understanding and communication of requirements across stakeholders
  • Models help ensure that all system specifications and constraints are met
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

How does MBSE approach system architecture and design?

A

MBSE uses models to:

  • Create and refine the system’s architecture and design, including:
    • Structural aspects: Defining system components and their relationships.
    • Behavioral aspects: Modeling how the system and its components behave and interact.
  • Address key areas such as:
    • The interaction of system components.
    • The components’ performance and their required functions.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What does verification and validation mean?

How does MBSE support these activities ?

A
  • verification: ensure that models and system conform to its specified requirements: „You built the system right“
  • validation: ensures that system, as modeled, meets the intended use and user needs under operational conditions: „You built the right system“
  • MBSE supports the activities through simulation, test case generations from models and ongoing assessments
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What are some challenges in implementing MBSE?

A
  • cultural and organizational resistance,
  • training and expertise requirements,
  • tool integration and interoperability,
  • model quality management,
  • costs of implementation and resource allocation
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What are the main purposes of models in MBSE?

A
  • facilitate communication,
  • support decision-making,
  • aid in system verification and validation,
  • and act as up-to-date documentation of system information.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What are key characteristics of models?

A
  • Abstract Representation:
    • do not replicate every detail of the system
    • focus on essential characteristics relevant to
      • understanding,
      • designing,
      • analyzing
      • verifying
        the system.
  • Purpose-Driven:
    • Different models may be developed for different aspects of the system:
      • requirements
      • architecture
      • behavior
      • verification.
    • Each model is tailored to serve
      • specific purposes or
      • to address specific concerns of stakeholders.
  • Hierarchical Structure:
    • Models often contain various levels of abstraction,
    • allowing engineers to drill down from general system characteristics to specific details.
    • hierarchical structuring helps manage complexity.
  • Dynamic and Iterative Development:
    • Models are not static;
    • evolve as the system design progresses
    • refined and expanded in iterative cycles of the engineering process.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

What are components of MBSE models?

A

Models in MBSE typically consist of several interconnected elements:

  • Structural Elements:
    • Represent the physical or logical components of the system, such as subsystems, modules, interfaces, and connections.
  • Behavioral Elements:
    • Define how the system behaves in response to various inputs or events. (This includes the logic, operations, and sequences that occur within the system.)
  • Requirement Elements:
    • Capture and relate system requirements directly within the model, facilitating traceability and validation.
  • Parametric Elements:
    • Include constraints and relationships that define the operational parameters of the system, which can be used for performance analysis and optimization.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What is Model Driven Architecture (MDA)?

A

Model Driven Architecture (MDA) is an initiative to:

  • Create a cohesive set of model-driven technology specifications using Unified Modeling Language (UML) and specific profiles.
  • Focus on separating the specification of system operations from the details of how the system uses its platform.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are the three primary goals of MDA?

How are they achieved?

A

The primary goals of MDA are:

  • Portability
  • Interoperability
  • Reusability

goals are achieved through

  • architectural separation of concerns (the system’s core functionality is kept independent from the platform specifics)
17
Q

How does Model-Driven Architecture (MDA) achieve platform independence?

A
  • Separating the specification of the system’s operation from the details of the platform it uses.
  • This separation allows the system’s functionality to be defined independently of the underlying platform.
18
Q

What does the MDA process for system specification involve?

A

The MDA process involves:

a. Specifying the system independently of the platform:

  • Focuses on defining what the system should do (its functionality) without considering how it will be implemented on a specific platform.

b. Specifying platforms:

  • Identifies the characteristics and capabilities of the potential platforms where the system might be deployed.

c. Choosing a platform for the system:

  • Selects the most suitable platform based on the system’s needs and the available platform options.

d. Transforming the system specification into one for a specific platform:

  • Adjusts the system’s general design to fit the specific features and limitations of the chosen platform, ensuring it operates effectively on that platform.
19
Q

What is a software component?

A

A software component is a unit

  • designed for reuse
  • clearly defined interfaces
  • strictly specified dependencies.
  • independently deployable
  • can be composed by third parties without knowledge of its internal workings (encapsulated, black box).
20
Q

What are the criteria that define a software component?

A
  • multiple-use/reusable,
  • non-context-specific,
  • composability,
  • encapsulation,
  • independent deployment and versioning.
21
Q

How have testing methodologies changed with the shift to model-based software development?

A
  • Traditional approaches: testing procedures like unit, integration, and system tests were manually written
  • Model-based development:
    • focus on Validating and Verifying the models themselves. If the models are verified and validated against the software requirements and the code generator is reliable, model Verification and Validation (V&V) can replace traditional manual unit and integration testing.