Processes for Engineering a System EIA-632acqnotes.com/Attachments/Processes for Engineering a System EIA - 632.pdf© 2004 Kasse Initiatives, LLC version NDIA CMMI Conf v1.3 SE Tutorial

SE Tutorial Processes for Engr Sys - 1version NDIA CMMI Conf v1.3© 2004 Kasse Initiatives, LLC

Processes forProcesses forEngineering aEngineering a

SystemSystemEIAEIA -- 632632


Fundamental ProcessesFundamental Processesfor Engineering a Systemfor Engineering a System

Processes forEngineeringA System

Acquisition and Supply•Supply Process•Acquisition Process

Technical Management•Planning Process•Assessment Process•Control Process

System Design•Requirements Definition Process•Solution Definition Process

Product Realization•Implementation Process•Transition to Use Process

Technical Evaluation•Systems Analysis Process•Requirements Validation Process•System Verification Process•End Products Validation Process


T e c h n i c a l M a n a g e m e n tP l a n n in gP r o c e s s

A s s e s s m e n tP r o c e s s

C o n t r o lP r o c e s s

T e c h n i c a l E v a l u a t i o nS y s t e m sA n a l y s i sP r o c e s s

R e q u i r e m e n t sV a l id a t io n

P r o c e s s

S y s t e mV e r i f i c a t i o n

P r o c e s s

E n d P r o d u c t sV a l i d a t i o n

P r o c e s s

A c q u i s i t i o n& S u p p l y

S u p p l yP r o c e s s

A c q u is i t io nP r o c e s s

P r o d u c tR e a l i z a t i o n

I m p l e m e n t a t io nP r o c e s s

T r a n s i t io n t o U s eP r o c e s s

S y s t e mD e s i g n

R e q u i r e m e n t sD e f i n i t i o n P r o c e s s

S o lu t io n D e f i n i t io nP r o c e s s

P l a n s ,D i r e c t i v e s

& S t a t u s

O u t c o m e s&

F e e d b a c k

P r o d u c t s

Acq

uisi

tion

Req

uest

Syst

em

Prod

ucts

Relationship of ProcessesRelationship of Processesfor Engineering a Systemfor Engineering a System


Relationship of ProcessesRelationship of Processesfor Engineering a Systemfor Engineering a System -- 22

�The appropriate processes are appliedrecursively and iteratively to:�Define the system products of the system hierarchy

from the top down�Implement and transition the system products from

the bottom up to the user or customer�The requirements that are assigned to the

proposed engineering processes are, inpractice, implemented concurrently and arehighly iterative


AcquisitionAcquisitionandand

SupplySupply


Acquisition and SupplyAcquisition and SupplyProcessProcess

Supply Process

AcquisitionProcess

Supplier

Developer

Acquirer uses

Serves in the role of

Serves in the role of

uses

Acq

uisi

tion

Req

uire

me n

ts

Agr

e em

ent


Acquisition and SupplyAcquisition and Supply

�The Acquisition and Supply Processes areused by a developer to arrive at an agreementwith another party to accomplish specific workand to deliver required products

�The parties can be inside the developer’s ownenterprise (another project, functionalorganization, or project team) or can be in adifferent enterprise


Acquisition andAcquisition andSupplySupply -- 22

�The agreement within an enterprise can takethe form or a work directive, work package,work authorization, or project memorandum ofagreement

�Agreements between enterprises can take theform of:�A formal contract for the delivery of a product�A memorandum of agreement that establishes the

working relationship between two or moreenterprises on a common project



�The agreement should include informationsuch as:�Work to be performed�Concept of operations�Requirements to be satisfied�Product and data to be delivered�Information regarding cost, schedule, planning,

delivery information, product structure, packagingand handling instructions, or installation instructions

�Appropriate technical plans



�Applicable financial structure, management, andauthority provisions

�Exit criteria for relevant life-cycle phases�Identification of applicable engineering life-cycle

phases�Required technical reviews


TechnicalTechnicalManagementManagement


Technical ManagementTechnical ManagementProcessProcess

ControlProcess

AssessmentProcess

PlanningProcess

Plans &Directives

Plans &Directives

OutcomesStatus

Request forRe-planning

Plans, Directives, Status

Acquisition, Documents, Agreement,Outcomes, and Feedback


TechnicalTechnicalManagementManagement

�The Technical Management Processes are tobe used to plan, assess, and control thetechnical work efforts required to satisfy theestablished agreement.


Planning ProcessPlanning Process

�This process is used to support enterprise andproject decision making and to prepare allnecessary plans that support and complementproject plans to:�Arrive at a decision to supply services according to

an external solicitation�Determine whether to proceed with an internal

enterprise for a new product or a productimprovement

�Guide the work efforts that will meet therequirements of an established agreement


Planning ProcessPlanning Process -- 22

�Replan applicable processes for engineering asystem. Replanning is normally initiated:


Planning ProcessPlanning Process -- 33

�Technical Plans�The developer shall create technical plans to ensure

an integrated and cost effective technical effort inaccordance with the defined schedule andorganization. The subordinate plans include:� Risk Management Plan� Technical Review Plan� Verification Plans� Validation Plans� Quality Plan� Configuration Management Plan� Measurement Plan


Assessment ProcessAssessment Process

�The Assessment Process is used to:�Determine progress of the technical effort against

both plans and requirements�Review progress during technical reviews�Support control of the engineering of a system

�The product and process metrics selected forassessing progress should provide informationfor:�Risk aversion�Meaningful financial and non-financial performance�Support of project management


Control ProcessControl Process

�The Control Process is used to:�Manage the conduct and outcomes of the

Acquisition and Supply Processes, System DesignProcesses, Planning and Assessment Processes,Product Realization Processes, and TechnicalEvaluation Processes

�Monitor variations from the plan and anomaliesrelative to the requirements

�Distribute required and requested information�Ensure necessary communications


Control ProcessControl Process -- 22

�Outcomes Management�The developer shall manage the outcomes of

technical effort through mechanisms like:� Configuration Management� Interface Management� Risk Management� Data Management� Managing Information Databases� Managing and tracking Stakeholder requirements


System DesignSystem Design


System DesignSystem DesignProcessProcess

RequirementsDefinitionProcesses

SolutionDefinitionProcess

Specifications, Drawings, Models

Acquirer and Other Stakeholder Requirements

Validated SystemTechnical Requirements

RequirementsConflicts & Issues

ProductCharacteristics


System DesignSystem DesignProcessProcess -- 22

�The System Design Processes are used toconvert agreed-upon requirements of the buyerinto a set of realizable products that satisfybuyer and other stakeholder requirements

�Two processes are linked together�Requirements Definition�Solution Definition


RequirementsRequirementsDefinition ProcessDefinition Process

�Inputs to the Requirements Definition Processare of three types:�Requirements from the agreement, other

documents, and individuals or groups that have astake in the outcome of the engineering orreengineering of the system

�Requirements in the form of outcomes from otherprocesses such as technical plans, and decisionsfrom technical reviews

�Requested or approved changes in therequirements


Solution DefinitionSolution DefinitionProcessProcess

�The Solution Definition Process is used togenerate an acceptable design solution andsatisfy:�The system technical requirements resulting from

completing the Requirements Definition Process�The derived technical requirements


Solution DefinitionSolution DefinitionProcessProcess -- 22

�Logical Solution Representations�The developer shall define one or more validated

sets of logical solution representations that conformwith the technical requirements of the system

�Tasks to consider include:� select and implement one or more appropriate

approaches for providing an abstract definition ofthe solution to the system technical requirements

� perform necessary tradeoff analyses� identify and define interfaces� assign performance requirements and constraints

to elements of the logical solution representation(subfunctions, objects, data structures


Product RealizationProduct Realization


Product RealizationProduct RealizationProcessProcess

ImplementationProcess

TransitionTo UseProcess

Agreement SatisfactionOther Stakeholder Satisfaction

Specified RequirementsSupplier or Buyer-Provided Products

Verified Integrated Products


Product RealizationProduct RealizationProcessProcess -- 22

�The Product Realization Processes are usedto:�Convert the specified requirements and other design

solution characterizations into either a verified endproduct or a set of end products in accordance withthe agreement and other stakeholder requirements

�Deliver these to designated operating, customer orstorage sites

�Install these at designated operating sites or intodesignated platforms

�Provide interface service support


ImplementationImplementationProcessProcess

�The Implementation Process deals withtransforming the characterized design solutioninto an integrated end product that conforms toits specified requirements


ImplementationImplementationProcessProcess -- 22

�Implementation�Tasks to consider include:

� receive the subsystem products that make up thesystem’s end products

� validate the subsystem products received� assemble the validated subsystem or physically

integrate the product components� verify each test article against its requirements� ensure the product will be ready and available to

perform the intended functions required by thesystem’s end products

� validate the verified end products


Transition to UseTransition to UseProcessProcess

�The Transition to Use Process results inproducts delivered to the appropriatedestination, in the required condition for use bythe buyer, and for the appropriate training ofinstallers, operators, and maintainers


TechnicalTechnicalEvaluationEvaluation


Technical EvaluationTechnical EvaluationProcessProcess

SystemVerification

Process

End ProductsValidationProcess

SystemsAnalysisProcess

ProductCharacteristics

Verification Results

Analytical Models & Assessments, Validated RequirementsVerified System Products, Validated End Products

Analysis Requests, Requirements,Implemented Products

RequirementsValidationProcess

Validation Results

RequirementsConflicts & Issues


Technical EvaluationTechnical Evaluation

�The Technical Evaluation Processes areintended to be invoked by one of the otherprocesses for engineering a system�Systems Analysis�Requirements Validation�System Validation�End Products Validation


Systems AnalysisSystems AnalysisProcessProcess

�The Systems Analysis Process is used to:�Provide a rigorous basis for technical decision

making, resolution of requirements conflicts, andassessment of alternative physical solutions

�Determine progress in satisfying technical andderived technical requirements

�Support risk management�Ensure that decisions are made only after

evaluating the cost, schedule, performance, and riskeffects on the engineering or reengineering of thesystem


Systems AnalysisSystems AnalysisProcessProcess -- 22

�Evaluate the effectiveness of each design solution�Define, calculate, and report the cost, schedule,

performance, and risk effects of each functional,performance, and design alternative

�Applicable quality factors such as maintainability,reliability, safety and security must not be degraded


RequirementsRequirementsValidation ProcessValidation Process

�Requirements are validated when it is certainthat the set of requirements describes the inputrequirements and objectives such that theresulting system products can satisfy therequirements and objectives

�Validation ensure the product or productcomponent will work in the intended use oroperational environment


System VerificationSystem VerificationProcessProcess

�The System Verification Process is used toascertain that:�The system design solution generated by

implementing the requirements is consistent with itssource requirements

�End products at each level of the system structureimplementation, from the bottom up, meet theirspecified requirements

�Enabling product development or procurement foreach associated process is properly progressing

�Required enabling products will be ready andavailable when needed to perform


System VerificationSystem VerificationProcessProcess -- 22

�Enabling Product Readiness�The developer shall determine readiness of

enabling products for development, production test,deployment, installation, training, support /maintenance, and retirement or disposal


End ProductsEnd ProductsValidation ProcessValidation Process

�The End Products Validation Process is usedto demonstrate that the products to bedelivered, or that have been delivered, satisfythe validated buyer requirements that wereinput to the system design processes and thatare applicable to the resulting end products


SummarySummary

�A system is one or more end products and setsof enabling products that allow end products,over their lifecycle of use, to meet stakeholderneeds and expectations

�Products are an integrated composite ofhierarchical elements so integrated as to meetthe defined stakeholder requirements

�The engineering of a system and its relatedproducts is accomplished by applying a set ofprocesses to each element of the systemhierarchy by a multi-disciplinary team of peoplewho have the requisite knowledge and skills