Professional Documents
Culture Documents
CSEP Flashcards V 4 8
CSEP Flashcards V 4 8
What is an activity?
What is an enabling system?
What is an organization?
What is a process?
What is a project?
What is a stage?
What is a system?
What is a system-of-interest?
What is a system-of-systems?
What is Tailoring?
What is Life-Cycle-Cost-Analysis?
Acronym List 1
Acronym List 2
Acronym List 3
Acronym List 4
Acronym List 5
Acronym List 6
What is Resilience?
What is Prototyping?
A. Perform Implementation
C. Prepare for Implementation
D. Manage results of Implementation
A. Perform Integration
C. Manage results of Integration
E. Prepare for Integration
A. Perform Validation
C. Prepare for Validation
E. Manage results of Validation
B. Respond to a tender
C. Establish and maintain an agreement
E. Execute the agreement
F. Prepare for the supply
H. Deliver and support the product or service
What are the inputs for the Business or Mission analysis Process? (Choose 6)
A. Source documents
B. Stakeholder requirements traceability
D. OpsCon
E. Project constraints
F. Life cycle constraints
H. Organizational strategic plan
What are the outputs of the Business or Mission analysis Process? (Choose 11)
A. Business or mission analysis strategy
B. Alternative solutions classes
C. Major stakeholder identification
E. Preliminary life cycle concepts
F. Preliminary validation criteria
G. Business requirements traceability
J. Preliminary MOE data
K. Preliminary MOE needs
L. Problem or opportunity statement
N. Business requirements
P. Business or mission analysis record
What are the inputs for the Stakeholder Needs and Requirements Process? (Choose 12)
A. Source documents
D. System requirement traceability
E. Stakeholder Needs
G. Preliminary life cycle concepts
I. Problem or opportunity statement
J. Preliminary MOE needs
K. Preliminary MOE data
M. Life cycle constraints
N. Business requirements traceability
O. Major stakeholder identification
P. Preliminary validation criteria
R. Alternative solutions classes
V. Project constraints
W. Business requirements
What are the outputs of the Stakeholder Needs and Requirements Process? (Choose 10)
A. Stakeholder needs and requirements definition strategy
C. Stakeholder requirements traceability
F. Initial RVTM
G. System function identification
I. Life cycle concepts
J. Stakeholder requirements
L. Validation criteria
M. Stakeholder needs and requirements definition record
N. MOE needs
R. MOE data
What are the outputs of the Project assesment and control Process? (Choose X)
A. Project assessment and control strategy
C. Project performance measures data
F. Project performance measures needs
G. Project lessons learned
H. Project status report
J. Project control request
L. Project change request
O. Project assessment and control record
What are the inputs for the Decision management Process? (Choose 1)
A. Decision situation
What are the inputs for the Risk management Process? (Choose 1)
A. Candidate risks and opportunities
What are the outputs of the Risk management Process? (Choose 3)
A. Risk management strategy
B. Risk report
C. Risk record
What are the inputs for the Configuration management Process? (Choose 2)
A. Candidate configuration items
D. Project change requests
What are the inputs for the Information management Process? (Choose 2)
A. Candidate information items
C. Project change requests
What are the inputs for the Life cycle model management Process? (Choose 4)
A. Organization strategic plan
B. QM corrective actions
D. Organization tailoring strategy
E. Quality management evaluation report
What are the outputs of the Life cycle model management Process? (Choose X)
A. Life cycle model management plan
E. Life cycle models
F. Organization policies, procedures, and assets
H. Organizational process performance measures needs
J. Organizational process performance measures data
K. Lyfe cycle model management report
L. Lyfe cycle model management record
What are the inputs for the Infrastructure management Process? (Choose 3)
A. Organization strategic plan
B. Organization infrastructure needs
F. Project infrastructure needs
What are the outputs of the Infrastructure management Process? (Choose 5)
A. Infrastructure management plan
E. Infrastrcture management record
F. Organization infrastructure
G. Project infrastructure
I. Infrastructure management report
What are the inputs for the Portfolio management Process? (Choose 4)
A. Organization strategic plan
B. Supply strategy
D. Project status report
E. Organization portfolio direction and constraints
What are the inputs for the Portfolio Human resource management Process? (Choose X)
A. Organization strategic plan
D. Project portfolio
F. Project human resources needs
What are the outputs of the Human resource management Process? (Choose X)
A. Human resource management plan
B. Human resource management report
E. Human resource management record
G. Qualified personnel
What are the inputs for the Quality management Process? (Choose X)
A. Organization strategic plan
C. Customer satisfaction inputs
D. Quality assurance report
E. Quality assurance plan
G. Quality assurance evaluation report
What are the inputs for the Knowledge management Process? (Choose 4)
A. Organization strategic plan
B. Organization lessons learned
C. Records
E. Project lessons learned
D. Project
C. ISO/IEC 15288
A. Tailoring guidelines of chapter 10 should be used to remove any conflicts with existing policies
A. ISO/IEC 15288
B. Agreement Processes
D. Technical Management Processes
D. Utilization
B. Systems Engineering
A. System of systems
A. Concept
B. >10%
The role of the systems engineer encompasses the entire life cycle for the
system‐of‐interest. Systems engineers orchestrate the development of a
solution from requirements determination through operations and system
retirement by assuring that domain experts are properly involved, that all
advantageous opportunities are pursued, and that all significant risks are
identified and mitigated. The systems engineer works closely with the project
manager in tailoring the generic life cycle, including key decision gates, to meet
the needs of their specific project.
Conway’s law suggests that ”organizations which design systems … are
constrained to produce designs which are copies of the communication
structures of those organizations.” Systems thinking and systems engineering
help organizations avoid the pitfall of Conway’s law by ensuring that system
designs are appropriate to the problem being addressed.
In short, to better understand, evaluate, control, learn, communicate, improve, predict, and
certify the work performed. For a given organizational level, the processes vary
with the project’s goals and available resources. At a high level, the company’s
business strategy determines the business approach, with the main goals of
time to market, minimum cost, or higher quality and customer satisfaction
setting the priorities. Similarly, the company’s size; the number, knowledge,
and experience of people44 (both engineers and support personnel); and
hardware resources determine how to achieve those goals. The application
domain and the corresponding system requirements, together with other
constraints, form another important factor in defining and applying processes.
B. assuring that domain experts are properly involved
D. all advantageous opportunities are pursued
E. all significant risks are identified and mitigated
A. terminate project
D. go to a preceding stage
E. continue this stage
A. Detailed planning
B. Development activities
C. IV&V activities
A. Concept
A. predictability
C. stability
D. repeatability
B. Retirement
C. Production
D. Utilization
A. Product
B. Funding
E. Business Case
B. Predictability
C. High assurance
E. Stability
A. Velocity
D. Adaptability
A. Acquisition Concept
D. Operational Concept
F. Retirement Concept
B. Concept of Support
C. Stakeholder requirements
A. Measures of the system’s ability to fulfill its objectives as defined by the requirements
B. Its ability to operate within resource constraints like time, budget, available knowledge and
skills
D. Cost of implementing and operating the system over its entire life cycle
F. It implements the functional architecture
A. WBS
B. Project budget
C. Project schedule
D. Procedures
E. Reports
F. Configuration baselines
G. Information repository
H. Measurement repository
I. QM corrective actions
J. Quality assurance evaluation report
K. Validated requirements
B. Project Plan
D. Configuration Baselines
C. Configuration Items
D. Change Requests
• A Configuration Management Plan (CMP) is tailored to satisfy the individual project procedures for
configuration management.
• The primary output of the Configuration Management Process is the maintenance of the
configuration baseline for the system and system elements wherein items are placed under formal
control as part of the decision‐making process.
• Establish a CCB with representation from all stakeholders and engineering disciplines
participating on the project.
• Begin the Configuration Management Process in the infancy stages of the system and continue
through until disposal of the system.
• Configuration management documentation is maintained throughout the life of the system.
A. Project Assessment and Control Process
B. CMP . Configuration Management Plan
C. QMP . Quality Management Plan
E. RMP . Risk Management Plan
A. Technical
C. Cost
Supportability analysis is an iterative analytical process by which the logistics support requirements
for a system are identified and evaluated.
The foundation for program success is rooted in requirements development. Human performance
requirements are derived from and bounded by other performance requirements within the system.
Front‐end analyses are extremely important in generating system requirements, which incorporate
HSI‐related requirements. Effective front‐end analyses start with a thorough understanding of the
mission of the new system and the actual work to be performed, successes or problems with any
predecessor systems, and the knowledge, skills, abilities, and training associated with the people
who are likely to interact with the proposed system technology.
A. Activity Diagram
B. Sequence Diagram
B. Investigate the consequences of implementation
D. Frame the problem context.
B. Activity Diagrams
C. Sequence Diagrams
B. Concept of operation
D. System constraints
D. FMEDA
E. FTA
D. Project Manager
C. Heuristic
E. Participative
C. Producibility Analysis
A. Identify and document the characteristics of system elements such that they are unique and
accessible in some form
B. Establish controls to allow changes in those characteristics
D. Record, track, and report status pertaining to change requests or problems with a product
C. New technology has extended the capability of the system
D. Costs of development, utilization, and/or support have been reduced
E. Reliability and availability of the system has been improved
A. SEMP
B. Concurrent Development
A. Requirements Validation
B. Replaceable as an entity
C. Unique specification
D. Formal control of form, fit and function
F. Defined functionality
A. Traced from source document statements
A. Delphi Technique
C. Interviews
D. Focus groups
A. Composite
a) Start with source operational requirements, deduce set of statements describing the higher level,
mission oriented system objectives and record them
b) Review the system objectives with end users and operational personnel and record the conflicts
d) For each model, generate a context diagram to represent the model boundary
D. Inspection
B. Constraints
C. Functional Requirements
D. Concept of Operations
A. Context Diagrams
B. Data Dictionaries
D. Data flow diagrams
A. Logical groupings
C. State transitions
A. Its place in a network characterizing its interrelationships with the other functions at its level
B. Its inputs and outputs, both internal and external
D. The set of functional requirements that have been allocated to it and which define what it does
A. Behavior diagrams
B. Context diagrams
D. Data dictionaries
A. Functional flow block diagrams that meet all of the functional requirements of the system
C. Requirements analysis
A. Identify from the SOW all design constraints placed on the program
B. Identify the groups defining constraints and incorporate them into Systems Engineering effort
D. Analyze the appropriate standards and lessons learned to derive requirements to be placed on
the h/w and s/w configuration item design
C. Functional
A. Analysis tools
C. Requirements traceability tools
D. Modeling tools
A. Measures of risk
C. Accommodation of interfaces
E. Measures of quality factors
C. Analysis of alternatives
E. System Architecture Synthesis
A. Procedures
B. Interfaces
C. People
A. System Requirements
C. Technology (available and emerging) and technology constraints
B. Synectics
D. Surveys
E. Inventory of existing concepts
A. Schedule span
B. Risk estimates for each alternative
E. Evidence that each alternative is consistent with the business case for the system
D. Systems Engineering
B. Brainstorming
D. Morphological analysis (MA)
E. Literature research
B. Requirements
C. Programmatic considerations such as available resources, acceptable risk, and political
considerations
E. Operating concept
A. Parkinson Technique
C. Analogy
E. Price-to-Win
A. Top-Down
C. Bottom-Up
D. Algorithmic (parametric)
B. Requirements analysis
C. Architectural Design
E. Test and verification
A. Mental
B. Formal
C. Informal
A. Sensitivity
D. 90%
C. Price-to-win
D. Design-to-cost
A. Parkinson technique
A. Top-down
D. Parametric
C. Analogy
D. System
D. Representation and simulations
A. Requirements analysis
B. Architecture design
C. Design and development
B. Architecture design
C. Select the appropriate type(s) of model, design the model, validate the model, obtain needed
input data and operate the model
A. Acoustic
B. Prototype
D. Wind tunnel
(Choose 2)
B. Structural test models
C. N2 charts
B. Small scale models
C. Comparison with test cases in the form of independent models of proven validity
B. Formal
C. Informal
D. Mental
A. Reliability
B. Testability
D. Maintainability
A. operational context
C. technology
D. interfaces between/among system elements
A. system owner
B. operators
D. support personnel
A. suitability
C. reliability
D. maintainability
A. lighting
C. vibration, noise, and temperature control
E. availability of medical care, food and/or drink services
A. life support
B. body armor
E. ejection equipment
C. Initiate HSI Early
D. Identify Issues and Plan Analysis
E. Make HSI a Factor in Source Selection for Contracted Development Efforts
B. HSI Assessment
D. Human-machine
A. System owners
B. Operators
A. Peer Reviews
B. Trade Studies
A. IPDT Analyses
B. Trade studies
A. Cost of mishaps
B. Handling hazardous materials
D. Disposal costs
A. Manpower
C. Personnel
D. Training
C. Requirements
D. OpsCon
B. System Build
C. System Integration with External Systems
B. N2 Charts
C. Functional Block Diagrams
D. Interface Working Groups (IFWGs)
A. Physical
C. Functional
D. Logical
A. Interface statements/drawings
a. People were using systems engineering when they built the pyramids.
b. Systems engineering developed from operations research and decision analysis after World War
II.
c. Systems engineering began to evolve as a branch of engineering during the late 1950s.
a. Subsystem
b. Program Activity
a. Concept Exploration
b. Program Definition and Risk Reduction
c. Engineering and Manufacturing Development
c. Risk management
b. System Design
a. Based on a standard
b. Includes Statement of deficiencies
a. Technical
b. Cost
c. Schedule
a. Expert interviews
c. Estimating relationships
d. Life Cycle Cost Analysis
b. Product development teams can make significant productivity improvements over hierarchical
management structures.
c. Scenario
a. ICDs
c. An examination of a defined function to identify all the sub functions necessary to the
accomplishment of the function
a. System synthesis
d. Function
b. Define more detailed functions derived from higher-level functions in a step-by-step fashion
c. When the risk reduction for continuation becomes smaller than the cost in time and money of the
effort to further decompose
c. Trade Studies
e. Risk Report
b. You should perform a sensitivity analysis to test the robustness of the final selection
d. Use formal techniques if the criteria are numerous, difficult, or controversial
b. A top-down approach, starting with a set of system architecture options is created, each
providing a framework into which element options may be inserted
a. Reliability/ Availability
a. Verification
d. System build
a. Involves customers and users
b. Is often performed by a third party
c. May be performed in the operational environment or a simulated operational environment
b. House of Quality
a. Requirements
c. What
e. Features
c. Decision database
d. All of the above
b. SEMS
c. N2 charts
c. 9.6 minutes
c. Use combination of oral and written communications and simplify the organizational processes
B. The expected project results should be based on clearly defined and measurable criteria.
1. SEMP
2. WBS
A. The risk management process shall avoid cost- and schedule risks.
B. Because it determines the critical path of the technical activities of the project.
C. Because verification activities in the SEMS have especially high attention.
D. The SEMS and the task dependencies defined in it are helpful to justify requests for personnel
and ressources
Lower costs
Higher probability of mission success
A decision tree is useful in trade studies where there are clear, important and distinct events that
stand between the alternatives and the eventual consequences.
A. Test
B. Analysis
B. There is not enough time to fix errors the verification will detect.
Results of verification are to be read in verification documentation and finally in the RVTM.
C. The core of system safety engineering is to identify and eliminate or control safety risk potential
within the development, operation or maintenance phase.
B. With different analyses it shall be reasoned, whether it is more cost effective to Influence the
design of the system or to plan for spare parts and maintenance during operation of the system
C. Relationship ear
The Technical Processes are used to define the requirements for a system, to transform the
requirements into an effective product, to permit consistent reproduction of the product where
necessary, to use the product to provide the required services, to sustain the provision of those
services and to dispose of the product when it is retired from service.
Copying with change versus Copying with complexity
Setting a direction versus Planning and budgeting
Aligning people versus Organizing and stuffing
Motivating people versus Controlling and and problem solving
The purpose is to define the stakeholder requirements for a System that can provide the
cabability needed by users and other stakeholders in a defined environment
The purpose is to transform the stakeholder, user oriented view of desired capabilities
into a technical view of a solution that meets the operational needs of the user.
The purpose is to provide sufficient detailed data and information about the system and ist
elements to enable the implementation consistent with architectural entities as definied in models
and views of the system architecture
The purpose is to provide a rigorous basis of data and information for technical understanding to
aid decision-making across the life cycle
The purpose of the Implementation process is to realize a specific system element
The purpose of the Integration process is to synthesize a set of system elements into a realized
system that satisfies system requirements, architecture, and design
The purpose of the Verification process is to provide objective evidence that a system or system
element fulfils ist specified requirements and characteristics
The purpose is to establish a capability for a system to provide services specified by stakeholder
requirements in the operational environment
The purpose is to provide objective evidence that the system, when in use, fulfills ist business or
mission objectives and stakeholder requirements, achieving ist intended use in ist intended
operational environment
The purpose is to use the system to deliver ist services
The purpose is to end the existence of a system element or system for a specific intended use,
appropriately or retired elements, and to properly attend to identied critical disposal needs
The purpose is to identify, analyze, treat and monitor the risks continually
The purpose is to generate, obtain, confirm, transform, retain, retrieve, disseminate and dispose of
information, to designated stakeholders
Information management plans, executes, and controls the provision of information to designated
stakeholders that is unambiguous, complete , verifable, consistent, modifiable, traceable and
presentable. Information includes technical, project, organizational, agreement and user information
The purpose is to collect, analyze, and report objective data and information to support effective
management and demonstrate the quality of the products, services, and processes
The purpose is to help ensure the effective application of the organization's Quality Management
process to the project
The purpose is to obtain a product or service in accordance with the acquirer's requirements
The purpose is to provide an acquirer with a product or service that meets agreed requirements
The purpose is to define , maintain, and assure availability of policies, life cycle processes, life
cycle models, and procedures for use by the organization with respect to the scope of
[ISO/IEC/IEEE 152888
The purpose is to provide the infrastucture and services to projects to support organization and
project objectives throughout the life cycle
The purpose is to initiate and sustain necessary, sufficient and suitable projects in order to meet the
strategic objectives of the organization
The purpose is to provide the organisation with necessary human resources and to maintain their
competencies, consistent with busniess needs
The purpose is to assure that products, services and implementations of the quality management
process meet organizational and project quality objectives and achieve customer satisfaction
The purpose is to create the capability and assets that enable the organization to exploit
opportunities to re-apply existing knowledge
A: Automotive Systems
B: Biomedical and Healthcare Systems
D: Defense and Aerospace Systems
E: Infrastucture Systems
G: Space Systems
H: Transportation Systems
Resilience is the ability to prepare and plan for, absorb or mitigate, recover from, or more
successfully adapt to actual or potential adverse events
B: Threats
C: Objectives and Priorities
E: Type and Purpose of SOI
F: Solution proposals
1. Models and simulation confirm the need for the systems and the anticipated system behaviours
before proceeding with the development of an actual system
2. Models and simulation present a clear, coherent design to those who will develop, test, deploy,
and evolve the system, thereby maximizing productivity and miniminzing error.
Informal models
Physical mockups
Formal models
Abstract models
Physical simulation
Computer-based simulation
Hardware simulation
Model-Based Systems Engineering
A: mproved communication
C: Improve product quality
D: Enhance knowledge
MBSE enhances the ability to capture, analyze, share, and manage the information associated with
the specification of a product.
It is an approach to SE that focuses on the functional architecutre of the system. A function is a
characteristic task, action, or activity that must be performed to achieve a desire outcome.
The purpose is to create a functional architecture for which system products and processes can be
designed and to provide the foundation for defining the systems architecure trhough the allocation
of functions and subfunctions to hardware/software, database, facilities and operations
N2-Diagramms are a systematic approach to analyze interfaces. These apply to system interfaces,
equipment interfaces, or software interfaces. N2-Diagrams can also be used at later stages of the
development process to analyze and document physical interfaces between systems
DSM is a straightforward and flexible modeling technique that can be used for designing,
developing, and managing complex systems. DSM offers network modeling tools that represent the
elements of a system and their interactions, thereby highlighting the system's architecture or
designed structure
Integrated product and process development recognizes the need to consider all elements of the
product life cycle, from conception through disposal, starting at the beginning of the life cycle.
Important items to consider include quality, cost, schedule, user requirements, manufacturing, and
support. IPD also implies the continious integration of the entire product team, including
engineering, manufacturing, verification, and support, throughout the product life cycle.
Lean SE is the application of Lean Thinking to SE and related aspects of organization and
project management. SE is focused on the discipline that enables flawless
development of complex technical systems. Lean Thinking is a holistic paradigm
that focuses on delivering maximum value to the customer and minimizing
wasteful practices.
Lean Thinking: "Lean thinking is the dynamic, knowledge‐driven, and
customer‐focused process through which all people in a defined enterprise
continuously eliminate waste with the goal of creating value."
Lean Systems Engineering: The application of lean principles, practices and
tools to SE to enhance the delivery of value to the system's stakeholders.
"Value is a measure of worth (e.g., benefit divided by cost) of a specific
product or service by a customer, and potentially other stakeholders and is a
function of (1) the product's usefulness in satisfying a customer need, (2) the
relative importance of the need being satisfied, (3) the availability of the
product relative to when it is needed, and (4) the cost of ownership to the
customer."
Waste: "The work element that adds no value to the product or service in
the eyes of the customer. Waste only adds cost and time."
1. Over-Processing
2. Waiting
3. Unnecessary movement
4. Over-Production
5. Transportation
6. Inventory
7. Defects
8. Waste of human potential
Over‐Processing – Processing more than necessary to produce the
desired output. Consider how projects "over do it" and expend more
time and energy than needed:
• Too many hands on the “stuff” (material or information)
• Unnecessary serial production
• Excessive/ custom formatting or reformatting
• Excessive refinement, beyond what is needed for Value.
Waiting – Waiting for material or information, or information or
material waiting to be processed. Consider "things" that projects
might be waiting for to complete a task:
• Late delivery of material or information
• Delivery too early – leading to eventual rework.
Unnecessary Movement – Moving people (or people moving) to access
or process material or information. Consider any unnecessary motion
in the conduct of the task:
• Lack of direct access – time spent finding what you need
• Manual intervention.
Over‐Production – Creating too much material or information.
Consider how more "stuff" (i.e., material or information) is created
than needed:
• Creating unnecessary data and information
• Information over‐dissemination; pushing data.
Transportation – Moving material or information. Consider how
projects move "stuff" from place to place:
• Unnecessary hand‐offs between people
• Shipping “stuff” (pushing) when not needed
• Incompatible communication – lost transportation through
communication failures.
Inventory – Maintaining more material or information than is needed.
Consider how projects stockpile information or materials:
• Too much “stuff” built‐up
• Complicated retrieval of needed “stuff”
• Outdated, obsolete information.
Defects – Errors or mistakes causing the effort to be redone to correct
the problem. Consider how projects go back and do it again:
• Lack of adequate review, verification, or validation
• Wrong or poor information.
Under the Value Principle, subenablers promote a robust process of establishing the value of the
end‐product or system to the customer with crystal clarity early in the program. The process should
be customer‐focused, involving the customer frequently and aligning employees accordingly.
The subenablers under the Value Stream Principle emphasize wastepreventing measures, solid
preparation of the personnel and processes for subsequent efficient workflow and healthy
relationships between stakeholders (e.g., customer, contractor, suppliers, and employees); detailed
program planning; frontloading; and use of leading indicators and quality measures. Systems
engineers should prepare for and plan all end‐to‐end linked actions and processes necessary to
realize streamlined value, after eliminating waste.
he Flow Principle lists subenablers that promote the uninterrupted flow of robust quality work and
first‐time right products and processes; steady competence instead of hero behavior in crises;
excellent communication and coordination; concurrency; frequent clarification of the requirements;
and making program progress visible to all.
The subenablers listed under the Pull Principle are a powerful guard against the waste of rework
and overproduction. They promote pulling tasks and outputs based on customer need (including
rejecting others as waste) and better coordination between the pairs of employees handling any
transaction before their work begins so that the result can be first‐time right.
The Perfection Principle promotes excellence in the SE and organization processes; the use of the
wealth of lessons learned from previous programs in the current program; the development of
perfect collaboration policy across people and processes; and driving out waste through
standardization and continuous improvement. A category of these subenablers calls for a more
important role of systems engineers, with responsibility, accountability and authority for the overall
technical success of the program.
The Respect‐for‐People Principle contains subenablers that
promote the enterprise culture of trust, openness, honesty, respect,
empowerment, cooperation, teamwork, synergy, and good
communication and coordination, and enable people for excellence.
IID distinguishes itself from conventional
approaches through velocity and adaptability.
Leverages an agile architecture for SE, enabling reconfiguration of goals, requirements, plans, and
assets, predictably.
Leverages an architecture for agile SE, enabling changes to the product during development and
fabrication, predictably.
Leverages an empowered intimately involved "product owner", enabling broad-level systems
thinking to inform real-time decision making as requirements understanding evolve.
Leverages human productivity factors that affect engineering, fabrication, and customer satisfaction
in an unpredictable and uncertain environment.
- Leverages an agile architecture for SE (product) enabling reconfiguration of goals requirements,
plans, and assets, predictably.
- Leverages an architecture for agile SE (product), enabling chanfes to the product (system) during
development and fabrication, predictably.
- Leverages an empowered intimately involved "product owner", enabling borad-level systems
thinking to inform real-time decision making as requirements understanding evolve.
- Leverages human productivity factors that affect engineering, fabrication, and customer
satisfaction in an unpredictable and uncertain environment.
- Time to respond
- Cost to respond
- Predictability of response capability
- Scope of response capability
Modules, passive infrastructure, and active infrastructure.
Modules are self-contained enapsulated units complete with well-defined interfaces that conform to
the plug-and-play passive infrastructure.
The passive infrastructure provides drag-and-drop connectivity between modules. Ist value is in
isolating the encapsulated modules so that unexpected side effects are minimized and new
operational functionality is rapid.
Active infrastructure designates specific responsibilities that sustain agile operational capability.
Services are activities that cause a transformation of the state of an entity by mutually agreed terms
between the service provider and the customer.
SE methologies are adapted to include a disciplined, systematic, and service-orientated, customer-
centric approach among different stakeholders and resources for near-real-time value cocreation
and service delivery.
Service SE brings a customer focus to promote service excellence and to faciliate service
innovation through the use of emerging technologies to propose creation of new service systems
and value cocreation.
Enterprise SE is an emerging discipline that focuses on frameworks, tools, and problem solving
approaches for dealing with the inherent complexities of the enterprise. Furthermore, enterprises
SE addresses more than jus solvin prolems; it also deals with the exploitation of opportunities for
better ways to achieve the enterprise goals.
The objective of performing VE is to improve the economical value of a project, product, or process
by reviewing its elements to accomplish the following:
- Achieve the essential functions and requirements
- Lower total LCC
- Attain the required performance, safety, reliability, quality, etc.
- Meet schedule objectives
Value is defined as a fari return or the equivalent in goods, services, or money for something
exchanged. Value = function/cost
Phase 0: Preparation/planning
Phase 1: Information gathering
Phase 2: Functional analysis
Phase 3: Creativity
Phase 4: Evaluation
Phase 5: Development
Phase 6: Presentation/implementation
- Thinking strategically and looking at the long-term implications of decisions and actions to set
vision and course
- Seeing the "big picture"
- Casting or capturing the vision for the organization and communicating it
- Defining the journey from the "as is" of today to the "to be" of tomorrow
- Turning ambiguous problem statements into clear, precise solution challenges for the team
- Working with the stakeholders (including customers), representing their points of view to the team
and the team's point of view to them
- Maximizing customer value by ensuring a direct tie of all engineering effort to the customer
business or mission needs
- Estaablishing an environment for harmonious teams while working to leverage the potential
benefits of diversity
- Challenging conventional wisdom at all levels
- Managing conflicts and facilitating heatlhy conflict around ideas and alternatives
- Facilitating decision making
- Demanding and enabling excellence
Category 1 Category 2
Chapter 1 Ver. 4
Chapter 1 Ver. 4
Chapter 1 Ver. 4
Chapter 1 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 7 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 6 Ver. 4
Chapter 6 Ver. 4
Chapter 6 Ver. 4
Chapter 6 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 1 Ver. 4
Chapter 1 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Ver. 4
Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8
Chapter 10 Ver. 4
Chapter 10 Ver. 4
Chapter 10 Ver. 4
Chapter 10 Ver. 4
Chapter 10 Ver. 4
Chapter 10 Ver. 4
Chapter 10 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 9 Ver. 4
Ver. 4
Chapter 9 Ver. 4
Ver. 4
Ver. 4
Ver. 4
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Pre-Test
Chapter 5 Ver. 4
Chapter 2 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 4 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 5 Ver. 4
Chapter 6 Ver. 4
Chapter 6 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 7 Ver. 4
Chapter 8 Ver. 4
Chapter 10 Ver. 4
Chapter 10 Ver. 4
Chapter 10 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 9 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4
Chapter 8 Ver. 4