SYSTEMS ENGINEERING Flashcards

1
Q

Successful organizations, large and small, need to think both

A

operationally and strategically

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

Operational thinking relates to ___________________ operations

A

“business as usual”

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

Strategic thinking relates more to (lti, o, d)

A

longer term imperatives,
opportunities, and direction.

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

Gaps in organizational capability may be a problem because

A

Gaps prevent achieving strategic objectives
Gaps prevent exploiting opportunities
Gaps open potential threats

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

Examples of organizations and their capability gaps
(ICGM)

A
  1. Individuals with personal capability gaps
  2. Commercial businesses with business-related gaps
  3. Government organization with a gap in government services
  4. Military organization with a gap relating to military capability shortfalls
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Conceptual Design Steps
(D-Dst-Dsy-Csl-Csd)

A

C1. Define business needs and requirements/BNR

C2. Define stakeholder needs and requirements/SNR

C3. Define system requirements.

C4. Conduct system-level synthesis.

C5. Conduct System Design Review (SDR)

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

C1. Define business needs and requirements (IESEF)

A

Identify stakeholders
Elicit needs
Scope system
Extract requirements
Finalize requirements

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

T or F: Stakeholders involved in the early stages of conceptual design are generally limited to those who have a right to affect the system

A

True

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

Stakeholders may include: MEMLUC

A

Management
Engineering/technical
Maintenance
Logistics
Users
Clients

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

Types of Constraints (BPED)

A

○ Business constraints
○ Project constraints
○ External constraints
○ Design Constraints

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

In eliciting business needs, (Dmgo-Ds-Dvc-Dlc)

A

Define mission, goals, objectives (MGO)
Develop scenario on system usage
Develop validation criteria
Define lifecycle concepts

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

It is important for business stakeholders to explain expectations on how the system will be (OADSD)

A

Operated
Acquired
Deployed
Supported
Disposed

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

When finalizing on business requirements

A

Update and record the Business Needs and Requirements (BNR)

○ Preliminary Lifecycle Concept Document (PLCD)
○ Business Requirements Specifications (BRS)

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

C2. Define stakeholder needs and requirements. (DDF)

A

▪ Define stakeholder needs
▪ Define stakeholder requirements
▪ Finalize stakeholder needs and requirements

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

C3. Define system requirements. (Erf-Praa-Dsy-Csr)

A

▪ Establish a requirements framework
▪ Perform requirements analysis and allocation
▪ Draft the System Requirements Specification (SyRS)
▪ Conduct System Requirements Review (SRR)

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

What question is asked to Determine functional/non-functional requirements

A

What does the system need to be able to
do?

16
Q

What question is asked to Define performance requirements?

A

○ What other characteristics are required

○ What other systems are involved

17
Q

What question is asked to Define verification requirements?

A

○ Have we built the system right?
○ Have we built the right system?

18
Q

C4. Conduct system-level synthesis. (DPCP)

A

▪ Draft System Requirements Specification
▪ Potential solutions are proposed against the SyRS
▪ Compliance level, options, and other information considered
▪ Preferred solution selected

19
Q

C5. Conduct System Design Review/SDR (RRTP)

A

▪ Review the proposed solution.

▪ Review the refined SyRS,

▪ the traceability back to the Stakeholder requirements Specification (StRS), and

▪ the planning that has been put in place to execute and manage the technical program

20
Q

Preliminary Design

A

Define the system elements

Perform requirement analysis and allocate requirements to the elements

21
Q

What are the sub-system options in preliminary design?

A

▫ Off-the-shelf (OTS)
▫ Modified off-the-shelf (MOTS)
▫ Developmental

22
Q

Advantages of OTS

A

Known function
Known performance
Availability
Known costs

23
Q

Disadvantages of OTS (TO)

A

Technical documentation
Obsolescence

24
Q

Advantages of MOTS

A

Known function
Known performance
Availability
Known costs

25
Q

Disadvantages of MOTS (WSEDTC)

A

Warranty
Support agreements
Effort
Detailed design data
Time
Cost

26
Q

Advantage of Developmental option

A

Theoretically offers a perfect match to requirements

27
Q

Disadvantages of Developmental option (LTTC)

A

Lifecycle Issues
Through-life support
Time
Cost

28
Q

Steps in Preliminary Design

A

▪ Iterate to make optimal use of any design space in sub-system design

▪ Finalize the preliminary design

▪ Conduct a design review establishing the subsystem level design requirements

29
Q

In detailed design, there will probably be elements of our solution that need to go
through detailed design activities:

A

▫ Developmental elements of the design
▫ OTS items that need to be modified
▫ Elements of the design that need to be integrated together
▫ Development of the fabrication process and materials

30
Q

The aim of detailed design is to:

A

finalize design so that the
solution is ready for construction and production

31
Q

When we think about what needs to be achieved during detailed design

A

▫ Design the items so that meet their relevant specification

▫ Ensure items can integrate to next higher level of assembly