Unit 2.1 Flashcards

(50 cards)

1
Q

in a physical sense, what term is “system” synonymous with?

A

product

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

since system is synonymous with the term “product” in a physical sense, what can we say about the project?

A

project is delivering a system or is delivering a product

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

TRUE OR FALSE.

Systems are much more than just the aggregation of hardware or software products, as they also include:

the organization, personnel, collective training systems, facilities, data support, and operating procedures, and organization policies.

A

true

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

what does the system delivers aside from a product?

A

an operational capability

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

what is created through the proper and effective interaction of people, process, and technology?

A

capability system

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

a system’s composition of elements can be into 2 types of hierarchy

A

logical (functional) and physical

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

a system’s mission is broken down into a hierarchical structure of its major function

A

logical (functional) hierarchy

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

a simple 4-layer (common) such as system > subsystem > assemblies > components, representation of a system

A

physical hierarchy

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

this pertains to the number of phases and activities each of which builds results from preceding phase

A

system engineering life cycle

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

what are the 4 parts of the system engineering life cycle

A

pre-acquisition phase
acquisition phase
utilization phase
retirement phase

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

this phase is where an idea for a system is being generated as a result of business planning. hence, business needs are confirmed

A

pre-acquisition phase

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

this phase is focused on bringing the system into being wherein the system is defined in term of business, stakeholders, and system requirements

A

acquisition phase

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

this phase is the operation part where modifications and upgrades are happening

A

utilization phase

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

this phase could be a mark of another life cycle for the replacement system if and only if the system is:
- the business has no further need for the system
- no longer meet the functions required by the organization
- no longer cost-effective to keep in service

A

retirement phase

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

what are the 4 parts under the acquisition phase?

A

conceptual design
preliminary design
detailed design and development
construction and/or production

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

what is the formal transition form the business world to the project world where it establish a proper definition of the business requirement?

A

conceptual design

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

what are the key elements to establish a Functional Baseline (FBL) in the Conceptual Design?

A

BNR = Business Needs and Reqs
SNR = Stakeholder Needs and Reqs
SyRS = System Requirements and Specifications

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

this is where the Conceptual ends where it confirms the BNR, SNR, and SyRS and provide a formal record of design decisions and design acceptance

A

System Design Review (SDR)

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

what converts the logical architecture of initial FBL to a description of a physical subsystems that will meet the system requirements?

A

Preliminary design

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

what is the result of the preliminary design?

A

Allocated Baseline (ABL)

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

in the ABL, what is the sublevel physical groupings of the functions in the FBL which are grouped logically?

A

Configuration Items (CI)

22
Q

in what review does the preliminary design ends?

A

Preliminary Design Review (PDR)

23
Q

this uses engineering disciplines to develop the individual subsystems, assemblies, and components in the system

A

Detailed Design and Development

24
Q

Detailed Design and Development results in?

A

Product baseline (PBL)

25
what is the review at the end of the Detailed Design and Development activity?
Critical Design Review (CDR)
26
what is the final design review which results in the official acceptance of the design and the subsequent commencement of the construction/production. PBL CDR?
Critical Design Review (CDR)
27
this activity is where components are produced in accordance with the PBL specifications, and the system is ultimately constructed
Construction and/or Production
28
Construction and/or Production. activity ends with
Formal Qualification Review (FQR)
29
what parties involved defines the system's requirements, expectations, and constraints based on their needs.
customer or end-user
30
what parties involved provides input during the requirement gathering phase, participates in reviews, and gives feedback during testing and validation phases
customer or end-user
31
what parties involved oversees the entire project, ensuring that timelines, budgets, and resources are managed effectively
project manager
32
what parties involved coordinates between all parties, manages risks, and ensures the project meets its objectives.
project manager
33
what parties involved lead the design, integration, and management of complex systems throughout their life cycle
systems engineers
34
what parties involved engage in requirements analysis, system design, integration, verification, validation, and deployment
systems engineers
35
what parties involved ensures the system meets the defined requirements and is free of defects. where they conduct testing at various stages, including unit testing, integration testing, system testing, and acceptance testing
test and quality assurance team
35
what parties involved design and build the system components and work on detailed design, coding, prototyping, and creating technical documentation.
Design and Development Team
36
what parties involved integrates various subsystems and components into the final system and ensures compatibility between subsystems and performs integration testing.
integration team
37
what parties involved manages the system once it is deployed, including monitoring, maintenance, and updates and engages in deployment, provides support, and ensures system availability and performance
operations and maintenance team
38
what parties involved provide hardware, software, or other system components by supplying necessary materials or tools and may also provide technical support and warranties.
suppliers and vendors
38
what parties involved ensure that the system complies with relevant laws, regulations, and standards. they review and approve system designs, and conduct audits or inspections.
regulatory bodies
38
A linear and sequential approach where each phase (e.g., requirements, design, implementation, testing, deployment) is completed before the next one begins
waterfall model
39
what parties involved may provide input during requirements gathering and feedback during testing and validation
stakeholders
40
what parties involved manages the decommissioning of the system and are responsible for data migration, archiving, and disposal of system components in compliance with regulation
end-of-life team
40
what parties involved include individuals or organizations affected by the system but not directly involved in its development
stakeholders
41
an extension of the Waterfall model) where development stages are paired with corresponding testing stages. The left side of the "V" represents decomposition of requirements, and the right side represents integration and validation.
v model
42
is often used in industries where safety, reliability, and regulatory compliance are paramount.
v model
43
well-suited for projects where requirements are expected to evolve over time, and where feedback and refinement are critical to achieving the desired outcomes
iterative model
44
It emphasizes developing the system in small, manageable portions (iterations), allowing for continuous improvement and adaptation based on stakeholder feedback
iterative model
45
- emphasizes iterative development, - strong focus on risk management and flexibility. - well-suited for projects that are complex, high-risk, and where requirements are expected to evolve or be refined over time
spiral model
46
The process is divided into four phases: planning, risk analysis, engineering, and evaluation, which are repeated in ______
spirals