Cross-cutting SE Flashcards

1
Q

What’s diff. between traditional document based SE and MBSE?

A

Traditional

  • Information generated about the system that is contained in documents and other artifacts
  • Often difficult to maintain and synchronize, and difficult to assess in terms of its quality (correctness, completeness, and consistency)

MBSE

  • The system model is a primary artifact of the SE process.
  • Significant improvements in system definition information;
  • Enhance productivity through reuse of system artifacts; and
  • Improve communications among the system development team.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

What’s the least I need to know about object oriented SE?

A

Objectives:
–Capture information throughout the life cycle sufficient to specify, analyze, design, verify, and validate systems
–Integrate MBSE methods with object-oriented software, hardware, and other engineering methods
–Support system-level reuse and design evolution

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

What is Lean SE?

A

Lean SE (LSE) is the area of synergy between Lean Thinking and SE

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

What is the 8th waste discussed in lean SE?

A

Waste of human potential

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

What are the 3 critical elements of the agile architectural framework?

A

–a roster of drag-and-drop encapsulated modules,
–a passive infrastructure of minimal but sufficient rules and standards that enable and constrain plug-and-play operation, and
–an active infrastructure that designates specific responsibilities that sustain agile operational capability

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

What is an IPDT?

A

An IPDT is a process-oriented, integrated set of cross-functional teams
–charged with the responsibility and authority to define, develop, produce, and support a product or process (and/or service).
–given the appropriate resources
–staffed with the skills necessary to complete their assigned processes

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

What are the 3 levels of IPDTs?

A
  • External Interface & System Level - SEIT
  • Upper Level System Elements - Product Integration Teams
  • Lower Level System Elements - Product Development Teams (PITs)
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

What are the various types of models in the general model taxonomy (not the SysML one)?

A

Physical mock-ups — represents an actual system,

Abstract models – can have many different expressions to represent a system, entity, phenomena, or process, which vary in degrees of formalism.

Formal models
–Geometric model represents the geometric or spatial relationships of the system or entity.
–Quantitative models represent quantitative relationships (e.g., mathematical equations) about the system or entity that yield numerical results.
–Logical models, also referred to as conceptual models, represent logical relationships about the system such as a whole—part relationship, an interconnection relationship between parts, or a precedence relationship between activities, to name a few. Often depicted in graphs (nodes and arcs) or tables.

Informal models — One can represent a system using a simple drawing tool or with words.

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

What are the various types of US defense simulations?

A
  • Live simulation
    • refers to live operators operating real systems
  • Virtual simulation
    • refers to live operators operating simulated systems
  • Constructive simulation
    • refers to simulated operators operating with simulated systems
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

What are the various model types in SysML?

A
  • Package
  • Behavior
    • Use Case
    • State Machine
    • Sequence
    • Activity
  • Requirement
  • Parametric
  • Structure
    • Block Definition
    • Internal Block
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

What is FBSE?

A

An approach to SE that focuses on the functional architecture of the system.
A function:

  • Characteristic task, action, or activity that must be performed to achieve a desired outcome.
  • May be accomplished by one or more system elements comprising equipment (hardware), software, firmware, facilities, personnel, and procedural data.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

What is a function?

A
  • Characteristic task, action, or activity that must be performed to achieve a desired outcome.
  • May be accomplished by one or more system elements comprising equipment (hardware), software, firmware, facilities, personnel, and procedural data.
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

What is the FBSE Objective(s)?

A

–Create a functional architecture for which system products and processes can be designed
–Provide the foundation for defining the system architecture through the allocation of functions and subfunctions to hardware/software, databases, facilities, and operations (e.g., personnel).

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

What are key outputs of FBSE?

A
  1. Input- Process - Output (IPO) diagrams
  2. Behavior diagrams
  3. Control flow diagrams
  4. Data flow diagrams (DFDs)
  5. Entity relationship (ER) diagrams
  6. Functional flow block diagrams (FFBDs)
  7. Integrated definition for functional modeling (IDEF) diagrams
  8. Data dictionaries
  9. Models
  10. Simulation results
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

What’s the overall process for creating the functional architecture?

A
  1. The functional architecture begins at the top level as a set of functions that are defined in the applicable requirements document or specification, each with functional, performance, and limiting requirements allocated to it
  2. the next lower level of the functional architecture is developed and evaluated to determine whether further decomposition is required.
  3. If it is, then the process is iterated through a series of levels until a functional architecture is complete.
    1. ​​​Decompose the function into subfunctions
    2. Decompose requirements & allocate to subfunctions
    3. Evaluate alternative decompositions & select 1
    4. ID all internal and external interfaces
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

What are benefits of models/simulations?

A

–Confirms the need for the systems and the anticipated system behaviors before proceeding with the development of an actual system,
–Presents a clear, coherent design to those who will develop, test, deploy, and evolve the system, thereby maximizing productivity and minimizing error.
–Helps avoid higher project cost and schedule overruns later in a project by detecting limitations and incompatibilities early in a project
–Value increases with the size, be it physical or complexity, of the system or System of Systems (SoS) under development.

17
Q

What are objectives of M&S?

A

–Obtain information about the system before significant resources are committed
–Support decision making by generating affordable and timely data for the analyst or reviewer, not available from existing sources

18
Q

What are purposes of modelling?

A
  • Characterizing an existing system
  • Mission and system concept formulation and evaluation
  • System architecture design and requirements flow-down
  • Support for systems integration and verification
  • Support for training
  • Knowledge capture and system design evolution
  • Represent the essential characteristics
  • Can be used within most system life cycle processes
19
Q

What are the three main types of simulations (not the specific names used in DoD)?

A
  • Physical
  • Computer-based
  • Hardware and/or human-in-the-loop simulations
20
Q

What’s the diff. among abstract syntax, concrete syntax, and semantics?

A
  • Abstract syntax - defines model constructs and rules for constructing the model
  • Concrete syntax - specifies graphic / text symbols used to represent model constructs
  • Semantics - define the meaning of the constructs and define concepts employed
21
Q

In SysML, what does a parametric diagram represent?

A

A parametric diagram (par) represents constraints on system property values as necessary to support detailed engineering analysis. These constraints may include performance, reliability, and mass properties, among others.

22
Q

In SysML, what’s diff. between block definition diagram and internal block diagram?

A

The bdd is more focused on the system hierarchy and classification of system elements. The ibd is more focused on internal interfaces (ports, connectors),

23
Q

How is model quality typically assessed?

A

–Adherence of the model to modeling guidelines
–The degree to which the model addresses its intended purpose.

24
Q

What are the two common types of prototyping?

A
  1. Rapid - Quickly assembled and quick to get user performance data and evaluate alternate concepts
  2. Traditional - May be partial or full, but is a high-fidelity representation that can be used for learning, risk reduction, and identifying changes needed to reduce costs or improve performance.

Neither of these should be retained after serving their intended purpose (i.e. don’t update the prototype and put it into production).

25
Q

What are common interface analysis tools/methods?

A
  • Design structure matrix
  • N2 diagram
  • Functional Flow Block Diagrams (FFBDs) & Data Flow Diagrams (DFDs)
  • Internal block diagram (SysML ibd)
26
Q

What are benefits of MBSE?

A

–Improved communications among the development stakeholders
–Increased ability to manage system complexity by enabling a system model to be viewed from multiple perspectives and to analyze the impact of changes
–Improved product quality by providing an unambiguous and precise model of the system that can be evaluated for consistency, correctness, and completeness
–Enhanced knowledge capture and reuse of the information by capturing information in more standardized ways and leveraging built-in abstraction mechanisms inherent in model-driven approaches. This in turn can result in reduced cycle time and lower maintenance costs to modify the design
–Improved ability to teach and learn SE fundamentals by providing a clear and unambiguous representation of the concepts

27
Q

What are two MBSE methods in the Handbook?

A

FBSE and OOSEM

28
Q

What are the key OOSEM hi-level activities?

A
  • Analyze stakeholder needs
  • Analyze system requirements
  • Define logical architecture
  • Synthesize candidate physical architectures
  • Optimize and evaluate alternatives
  • Maintain requirements traceability
  • Verify/validate system
29
Q

How does OOSEM relate to SE overall?

A
  • Basically an version of what’s in the V
  • Integrates object-oriented concepts with model-based and traditional SE methods
  • OOSEM incorporates foundational SE practices, object-oriented concepts, and other unique techniques to deal with system complexity.
  • Applies fundamental tenets of SE, including the use of multidisciplinary teams and disciplined management processes such as planning, risk management, configuration management, and measurement.
30
Q

What does agile SE leverage?

A
  • An agile architecture for SE (process), enabling reconfiguration of goals, requirements, plans, and assets, predictably.
  • An architecture for agile SE (product), enabling changes to the product (system) during development and fabrication, predictably.
  • An empowered intimately involved “product owner” (chief systems engineer, customer, or equivalent responsible authority on product vision), enabling broad-level systems thinking to inform real-time decision making as requirements understanding evolve.
  • Human productivity factors that affect engineering, fabrication, and customer satisfaction in an unpredictable and uncertain environment.
31
Q

What are the key metrics for agility?

A
  • Time to respond
  • Cost to respond
  • Predictability of response cape
  • Scope of response cape
32
Q

What are agile architecture reusability principles?

A
  • Encapsulated modules
  • Facilitated interfacing
  • Facilitated reuse
33
Q

What are agile architecture reconfigurability principles?

A

Peer-peer interaction

Distributed control and information

Deferred commitment

Self-Organization

34
Q

What are agile architecture scalability principles?

A

Evolving standards

Redundancy and diversity

Elastic capacity