5301

The SE Process:

-Establishes a common process framework for describing the life cycle of man-made systems
�Defines a set of processes and associated terminology for the full life cycle, including
conception, development, production, utilization, support, and retirement

The system engineer never has to be concerned with functions such as contracts and finance because that is the project managers roll

false

both ConOps and OpsCon are NOT considered systems thinking because they are strictly focused on the use of a system and not the overall system development

False

When stakeholders are in conflict it is only important to satisfy the one with a greater ability to impact the results of the system

False

TPM's must currently be satisfied to pass decision gate criteria and progress to the next lifecycle phase

False

It is considered best practiceto start incorporating design characteristics in thesystem architecture to expedite schedule

False

Due to the need for replicating the same SE process, tailoring is typically not permitted within an organization

False

Requirements can be represented as a hierarchy and broken down from the top to lower levels.
List the type of requirements in the hierarchy. The lowest level requirement has been provided.

-Stakeholder requirement
- System requirement
-Performance Requirement
- System Element Requirement

Identify what type of stakeholder each of the descriptions below represent
- Should be monitored by the project manager in case their status changes but which require almost no attention at that point in time

apathetic

Identify what type of stakeholder each of the descriptions below represent
- Need to be satisfied by the outcome of the project but who may not require regular attention during the project itself

Latent

Identify what type of stakeholder each of the descriptions below represent
-Will support the project and its aims and should be given regular updates to keep them included and motivated

defenders

Identify what type of stakeholder each of the descriptions below represent
- The stakeholder with the largest capacity to support the project within the business but also have the largest capacity to derail it if not carefully handled

promoter

During systems requirements definition you are not only defining requirements but also how those requirements will be

verified and validated

Overengineering something above and beyond requirements is defined as

Gold plating

Which SE model best supports an approach for continuing progress when requirements are unclear or yet to be fully developed

Incremental and iterative

What defines the evolution of a system, product, service, project or human made entity from conception through retirement

Lifecycle

System engineering and the technical process reduce what?

Risk

Drawing and diagrams are examples of design

Enablers

Which of the following would be considered a stakeholder of SMU

UNT board of directors

Which of the following are needed in defining your requirements

They need to be necessary, traceable, unambiguous, singular, cost effective, achievable and verifiable

Sequential Methods

In a sequence without feedback
�The plan progresses from left to right as a function of time
�Adheres to specified process
�Requirements>Design>Finished Product
Benefits of Sequential methods:
�Predictability
�Stability
�Repeatability
�High assurance

Waterfall Model

The most popular model. In this cycle, each phase must be completely finished before the next begins

Incremental and Iterative Methods

Allows a project to provide an initial capability, followed by successive deliveries,until the desired System of Interest is achieved

SE Lifecycle

Concept, development, production, utilization/support, retirement

Stakeholder

A person with an interest or concern
�Customer (Acquirer)
�Organization (Supplier)
�End-User
�Development team
Different stakeholders will have different needs

Kano Model

Basic Needs: Some needs make us unhappy if they are
not met, but don't make us happy if they are met.
-Tires included with a car
Performance Needs: Some needs make us steadily happier the more they are met.
�Horsepower, fuel economy,
Delighters: Some need

Requirements Derived from Needs

Requirements are formal structured statements that can be verified and validated
-Written in the form of "The who shall what"
-The cake shall be 10 ft

Goals

The word should can be used instead of shall to indicate a goal which must be addressed, but is not formally verified
�The cake should taste good

ConOps and OpsCon

Operational Concept (OpsCon)
-describes what the
system will do (not how) and why (rationale)
Concept of Operations (ConOps)
-addresses the leadership's
intended way of operating the
organization, use of one or more systems to advance the organization's g

Technical Measurements

MOE
- Measure of Effectiveness -
The metrics by which an acquirer will measure
satisfaction with products produced by the technical effort.
MOP
- Measure of Performance -
An engineering performance measure that
provides design requirements that are necess

Stakeholder Types

Low interest and low power -
apathetic stakeholders
- those who should be monitored by
the project manager in case their interest or power changes but which require almost no
attention at that point in time
�Low interest and high power -
latent stakeholde

Architecture Definition

Purpose
-Generate system architecture alternatives. Select alternatives that address stakeholder concerns and meet system requirements. Express in a set of consistent views

Function

- An activity or purpose
�This is why we have systems

Design Definition

HOW ARE WE GOING TO GET FROM ARCHITECTURE TO IMPLEMENTATION
Characteristics - shapes/ measurement/materials
Enablers - drawings, diagrams, metrics