MISSOURI UNIVERSITY OF SCIENCE AND TECHNOLOGY Rolla, Missouri, U.S.A.

MISSOURI UNIVERSITY OF SCIENCE AND TECHNOLOGY Rolla, Missouri, U.S.A.
SysEng 368 Systems Engineering and Analysis I “Agile Systems Engineering: Experiential and Active Learning” Lecture 1: Introduction to the Course Steven Corns, PhD MISSOURI UNIVERSITY OF SCIENCE AND TECHNOLOGY Rolla, Missouri, U.S.A.

Distribution List E-mail me your preferred e-mail address
Please provide by Aug 24th You can also forward Missouri S&T Please start all s with “SE368”

Text Systems Engineering and Analysis, B.S. Blanchard and W. J. Fabrycky, 5th edition, Prentice-Hall, 2010.

Other Texts Systems Engineering Guidebook: A Process for Developing Systems and Products (Martin) Systems Engineering: An Approach to Information-Based Design (Hazelrigg) Fundamentals of Systems Engineering (Khisty and Mohammadi) Systems Engineering Principles and Practice (Kossiakoff and Sweet) Introduction to Systems Engineering (Sage and Armstrong) NASA Systems Engineering Handbook

Class Outline Introduction to Systems
Systems Engineering and the System Design Process Systems Engineering Management Design for Operational Feasibility Systems Analysis and Design Evaluation See Syllabus—Posted on Blackboard

Objectives Exposure to the Systems Engineering Process
Survey view across many disciplines Application of Systems Engineering to a team project

Grading A—90 and above B—80-89 C—70-79
D—60-69 (Undergraduate Students) F—Less than 70 (Graduate Students) or Less than 60 (Undergraduate Students)

Grading Homework (5% each) 20% Project Reviews Conceptual Design 5%
Preliminary Design % Detail Design/ Final Presentation* 10% Final Project % Professionalism/Teamwork* 10% * Student assessments are significant portion of the grade

Homework Four homework assignments throughout the semester (each is 5% of overall grade) Homework assignments are part of the group projects. Will not be accepted late

Expectations Homeworks will be turned in on time (unless specific situations are previously arranged.) End of semester peer reviews will be submitted on time—if not-submitted or submitted late a reduction in Class Participation grade will be assessed Final Team Presentation evaluations will be submitted on time—late or non-submittals will have Class Participation grade reduced

Lecture Notes Charts for each module posted to Blackboard by ~noon of the day of class Posted under course “content” in Lecture Material folder Syllabus also posted under course “content”

Control System for Wireless, Immersive Simulation Vest
The Project? Control System for Wireless, Immersive Simulation Vest More on deliverables later

Systems Engineering Definitions (International Council of Systems Engineers)
Systems Engineering: An interdisciplinary approach and means to enable the realization of successful systems. Systems Engineering considers both the business and the technical needs of all stakeholders with the goal of providing a quality product that meets the user needs. System Architecture: The aggregation of decomposed system functions into interacting system elements whose requirements include those associated with the aggregated system functions and their interfaces requirements/definition.

Value of Systems Engineering*
Cost and Schedule Performance as a Function of Systems Engineering Effort *Source: INCOSE Systems Engineering Center of Excellence SECOE INCOSE 2003; & Honour, E. “Understanding Value of Systems Engineering”, INCOSE Conference, June 20-24, 2004

Evolution of Systems Engineering
Prior to World War II, architects and civil engineers were, in effect, the Systems Engineers of their time and operated without any theory and science of Systems Engineering or any defined and continuously applied processes or practices.

Examples of prior to World War II system artifacts
Coliseums, Rome Rumeli Fortress, Istanbul Saint Peter's Basilica Golden Gate Bridge

After World War II, Systems Engineering began to evolve as a branch of engineering as the services and prime contractors sought tools and techniques that would help them excel at: system performance and mission success project management: technical performance, delivery schedule, and cost control PERT- the Program Evaluations and Review Technique used by the U.S. Navy during Polaris A1 development was one of the first tools.

Lessons learned during this time period led to innovations in all phases of high technology development, namely: Sample changes introduced: parts traceability, materials and process control, change control, engineering, improved product accountability, and procurement, formal interface control. manufacturing, testing, and quality control.

Now Systems Engineering combines many disciplines with a strong foundation in basic engineering, such as: Network Centric Information and Communication System of Systems Affordability Human System Interface System Safety Operations Analysis Survivability Vulnerability Etc.

More Basic Definitions
References: INCOSE and CMMI Systems Engineer: An engineer trained and experienced in the field of Systems Engineering. Systems Engineering Processes: A logical, systematic set of processes selectively used to accomplish Systems Engineering tasks. System Architect: System architects postulate and develop models of the system, making judgments about allocation of requirements to system components. System Architecture: The arrangement of elements and subsystems and the allocation of functions to them to meet system requirements.

Recently Developed System Artifacts
Boeing 787 F/A -18 Mars Rover F/A-18F ScanEagle B1-B C-17

Importance of Systems Engineering (1 of 3)
Systems are complex and innovative System architecture is arbitrary Interfaces are very significant and initially unknown Technical and process domain expertise are important Systems engineering and the systems engineer must be involved throughout the life of the system; from development through production, deployment, training, support, operation and disposal

System Engineering is non-linear journey from cradle to grave, a non-analytic top down design process Solution concepts not unique Optimization not possible; balance is sought Societal factors important, and sometimes difficult to predict Need to iterate between form and function, experimentally

“Redesign is a part of Design” Bottom-Up Integration and Test Process Massive amounts of data, and the need for configuration management, especially given Evolutionary Acquisition Systems Architecting and Engineering are an art utilizing science

Systems Engineering Process
Functional Analysis/Allocation Decompose to lower-level functions Allocate performance and other limiting requirements to all functional levels Define/refine functional levels Define/refine functional interfaces (internal/external) Define/refine/integrate functional architecture Synthesis Transform architectures (functional to physical) Define alternative system concepts, configuration items and system elements Define/refine physical interfaces (internal/external) Select preferred product and process solutions Verification Loop Design loop Requirements loop Requirements Analysis Analyze missions and environments Identify functional requirements Define/refine performance and design constraint requirements System Analysis and Control (balance) Control loop Process output Phase dependent Decision support data System architecture Specifications and baselines Process input Customer needs/ objectives/ requirements Missions Measures of effectiveness (MOEs) Environments Constraints Technology base Outputs from prior phase Program decision requirements Requirements applied through specifications and standards Trade-off studies Effectiveness analyses Risk management Configuration management Interface management Data management Performance based progress measurement IMP/IMS TPM Technical reviews

System Definition System - a combination of elements forming a complex whole. System’s Function (Purposeful Action) - A system is a set of interrelated components working together toward some common objective or purpose.

System Elements Components – operating parts of the system consisting of input, process, and output. Attributes – properties of the components, which characterize the system. Relationships – links between components and attributes.

System Components The properties and behavior of each component (or subset) of the system: Has an effect on the properties and behavior of the system as a whole. Depends on the properties and behavior of at least one other component in the set. Components can’t be divided into independent subsets.

System Components Structural Components - static
Operating Components - perform the processing Flow Components - material, energy or information being altered

System Definition Systems and Subsystems Environment Inputs/Outputs
Systems, segments, elements, subsystems Environment Inputs/Outputs Throughput – what is being transformed! Defined System Boundaries

Examples Fire Department University Highway System Computer System
Other? Subsystems or …? Environment? Inputs? Outputs? Throughput?

System Classification
Natural vs. Human - Made Systems Physical vs. Conceptual Systems Static vs. Dynamic Systems Closed vs. Open Systems Consider Examples – Do they have more than one applicable classification?

Systems Science and Cybernetics
Domain that touches virtually all traditional disciplines Includes Computational Intelligence (neural networks, fuzzy systems, and evolutionary computation), dynamic systems, chaos and adaptive systems Adapted from Principia Cybernetica Web

System Science Cybernetics - the study of control in complex systems, e.g., nervous system. - Focus on feedback mechanisms General Systems Theory - a systematic framework for describing relationships. Systemology - the science of systems or their formation, e.g., operations research

System Definition- System of Systems
If a System’s Function is a purposeful Act. What is a System of Systems? SOS connects seemingly different parts with the whole to achieve large-scale objectives (Based on Purdue University College of Engineering web-site) Examples Air Traffic Management ECO-Systems Stock Market War (*Network Centric Warfare) So is there both SE and SOSE?

Technology & Technical Systems
The Machine Age & The Industrial Revolution How do we understand the world around us Reductionism Disassemble to independent and indivisible parts Explaining the behavior of the parts Aggregation of these explanations to explain the whole Essentially the whole = sum of the parts Mechanism All things are explainable by cause and effect Understanding excluded environment Ultimately the world is perceived as a self-contained mechanism Machines replaced people and people’s tasks were modeled after the operation of a machine

Transition to the Systems Age
New approaches to understanding the world around us All things are parts of a larger whole—focus on the whole, not the parts Things are explained from the perspective of their role in the larger whole (system) Objective is to overcome the predisposition to perfect the details, but ignore the whole (sub-optimize?) Applied to organizations through the perspective of “Systems Thinking” Focuses on systems that are goal seeking or purposeful

The Concepts of Systems Engineering as Practiced by the Wright Brothers
Denis Bluede, 12th annual INCOSE symposium

Systems Engineering Concepts Used
System Boundary Included pilot as part of the system Defined Requirements Necessary horsepower Propeller Thrust Functional Analysis Understood the functions of the airplane – used to drive the design process Functions of subsystems (propulsion)

Systems Engineering Concepts Used
Prototypes and Testing Built successively more complex gliders before building the airplane Employed sophisticated testing at each level Trade-off Decision Control of the airplane versus stability Test System Created wind tunnel to address specific needs Careful selection of test site Etc.

“It is fascinating that such extensive use of systems engineering concepts could be found in one system prior to the use of the phrase “systems engineering” ten to twenty years later.”

Technology & Technical Systems
Technology & Society Society Culture Technology The course of history is linked to the progress of technology The transition from past to present to future is neither easy nor painless Technical Systems All types of human made artifacts The hierarchical nature of systems Systems have become more complex and cross traditional boundaries

Engineering in the Systems Age
System Complexity and Scope Human “intervention” has created a more complex world Pieces of the system must be integrated and function together Systems must be integrated to function together Technological Growth and Change Attempt to satisfy a currently unmet need Look beyond technical and economic feasibility Social factors/Political objectives/Ecological constraints

Systems Thinking Applied to Business
“The systems thinking approach emphasizes connectedness and how connections change over time. In contrast to traditional analysis, which call for isolating each piece of a system and studying it individually, systems thinking focuses on studying how one aspect of a system [enterprise] interacts with the other components.” Business at Illinois Perspectives, University of Illinois College of Business, Spring 2005

So—What is Systems Engineering?
Systems engineering is the overarching process that a program team applies to transition from a stated capability need to an operationally effective and suitable system. Systems engineering encompasses the application of systems engineering processes across the acquisition life cycle (adapted to each and every phase) and is intended to be the integrating mechanism for balanced solutions addressing capability needs, design considerations and constraints, as well as limitations imposed by technology, budget, and schedule. From the Defense Acquisition Guide Book

System Engineering – Common Themes
Top-Down Approach Life Cycle Perspective System Requirements Emphasis Interdisciplinary/Integrated Team Approach

Course Coverage (Concept of Operations) CONOPS
This is the first course in a sequence of two courses that covers the whole systems life cycle, from system inception to artifact production and disposal. In the first course the students produce the system architecture and detailed design based on customer needs and high level system attributes using engineering principles and agile systems engineering principles, processes and tools.

Course Coverage (Concept of Operations) CONOPS
In the second course students manufacture and validate to the customer a physical artifact based on their architecture and detail design from the previous course using engineering principles and agile systems engineering principles, processes and tools.

Course Objective (Statement of Need)
The objective of the course is to teach systems engineering principles, processes and tools to engineers or engineering seniors based on domain specific real life engineering need provided by DoD and validate that this is achieved based on the final product and verify that the agile systems engineering fundamental knowledge is learned through accepted and agreed rubrics ( Design Project document).

Success Criteria (Key performance attributes for DoD)
Effective prototype artifact development Degree of willingness of the DoD representative to further develop the artifact Degree of “disruptive engineering thinking “ in design Degree of willingness to support research for further development of the artifact.

Recorded WebEx Project Group Meetings
Weekly project meeting on WebEx for 1-2 hours Systems Engineering PhD Students as Project Group Managers Project Team Systems Engineering PhD Students as DoD Mentor Facilitator, as needed Industrial Mentors from The Boeing Company, as needed Engineering subject matter experts for domain specific areas, as needed Agile systems engineering subject matter experts, as needed

Proposed Project Topic to DoD
The project will culminate in the development of a vest capable to supply force-feedback through the use of mechanical components capable of subtle simulation of real battlefield scenarios. These scenarios will simulate getting shot, getting hit, and minor restriction. The choosing of the proper components and capabilities will be determined by a guided trade study. The main development will be the use of wireless communication capabilities to activate the vest components in a timely and reliable manner. Hence, students will focus on the wireless transmission of activation to which embedded sensors in the vest will react by activating the mechanical components within it. Thus, transmission, reception control systems, and interfaces will comprise of the majority of the student development. The use of cheap wireless motes will supply the wireless network.

Highlights of Proposed Design
RT – 19 Vest Haptic Vest Wireless Communication Element Interface Interface Controller Actuator Simulation Environment (Virtual, mixed or real) Power Virtual or mixed reality – short range radio Real territorial training – long range radio Commands to actuator: Position, Density, Sequence, and Time Solder Info.: ID, Position, State

Current Artifacts Infantry Immersion Trainer Videos

Proposed DoD Scenario A unit has recently assumed authority over an area in Helmand Province, Afghanistan. The unit has been tasked with conducting patrolling operations of a town emanating from a Company Base nearby. This town was not patrolled frequently by the preceding unit, so the unit will be entering the town with a limited knowledge base. The unit has been tasked with planning for the introduction of a government center in the town, to include an Afghan Nation Police (ANP) station. The first Marine patrol will allow the Marines to become accustomed to what is normal in the village, introduce village personalities, and allow them to pursue some intelligence requirements related to enemy activity in the area. These findings and relationships will set the stage for follow on events. Relationship building is a key component of this unit’s work; it is critical that unit members be familiar with the cultural and societal norms of this province, have adequate language skills, and have an accurate representation of the physical, temporal, and cultural terrain.

Proposed DoD Scenario The mission is to provide security for the government center, so that police recruiting can occur. The unit will relieve another unit, which has been conducting security around the government building. A third unit will be in view, conducting vehicle control on a key route into the village. One unit will conduct security for the building and ensure no ‘applicants’ pose a threat to the recruiting operation and will witness an attack on the vehicle control point that will result in casualties. Later, a suicide bomber will attempt to enter the secure area to detonate his device. The squad will be presented with a complex attack in the form of an gunfire from various locations to follow up on the suicide bomber threat.

Challenge Problem In summary, model the scenario to the greatest breadth and depth possible Develop a M&S/training environment which broadly models as much of the scenario as is possible while developing specific kinematic, social-cultural, or other devices/tools necessary to provide specific detailed feedback about discrete aspects of the scenario, e.g., interaction with intelligent avatars, feedback from firing weapon, feedback from taking incoming fire, provide an immersive village environment and control over friendly forces dispersed across the environment, a realistic vehicle checkpoint scenario with control of friendly forces and avatars, visualizations which represent human fields of view, realistic locomotions. Scoring metric will accommodate both scenario breadth and realism as well as detailed interactions/models (e.g., blue force control, specific haptic feedback, avatar interaction, training objectives accomplished, etc.)

Challenge Problem Specifically develop tactical level immersive training capabilities for: Intuitive decision making skills Cultural and situational fluency Culture general skills Training skills will integrate: Appropriate and clearly defined learning objectives Geo-located knowledgebase of situational, human, and cultural terrain elements Avatars operating at the appropriate level of fidelity for specified learning objectives Measures of Effectiveness and Performance Demonstrate ability to assess and measure learning of non-kinetic/cultural skills and evaluate new capabilities using advanced immersive techniques Define sampling and testing methodology and address how learning extends to behavioral changes in the field?

Next Steps? Determine a system scope that is achievable within a semester Discuss need statement and reach customer agreement. Determine scenarios that can represent approximately percent of the desired system behavior Generate systems requirements based on engineering models and customer input. Start developing system architecture

Systems Engineering Challenge
To bring products and systems into being that meet customer expectations – performance cost timeliness availability Circle “expectations”

Systems Engineering Process
Functional Analysis/Allocation Decompose to lower-level functions Allocate performance and other limiting requirements to all functional levels Define/refine functional levels Define/refine functional interfaces (internal/external) Define/refine/integrate functional architecture Synthesis Transform architectures (functional to physical) Define alternative system concepts, configuration items and system elements Define/refine physical interfaces (internal/external) Select preferred product and process solutions Verification Loop Design loop Requirements loop Requirements Analysis Analyze missions and environments Identify functional requirements Define/refine performance and design constraint requirements System Analysis and Control (balance) Control loop Process output Phase dependent Decision support data System architecture Specifications and baselines Process input Customer needs/ objectives/ requirements Missions Measures of effectiveness (MOEs) Environments Constraints Technology base Outputs from prior phase Program decision requirements Requirements applied through specifications and standards Trade-off studies Effectiveness analyses Risk management Configuration management Interface management Data management Performance based progress measurement IMP/IMS TPM Technical reviews

Statement of Need Succinct statement of the customer’s need, including any initial significant boundaries/constraints. E.G., An unmanned vehicle to conduct underwater geologic exploration to identify possible sites for oil exploration. Vehicle will be deployed from the Petro Explorer vessel. Vehicle to be available by XXX, and vehicle cost including development to be approximately $YYYM.

Engineering For Product
Engineering For Product Competitiveness in a Global Market The System Comes Before the Components 1) Improving methods for defining product and system requirements, including determination of performance, effectiveness, and essential system characteristics. 2) Addressing the total system with all of its elements from a life – cycle perspective. Form follows function. 5 processes Defining TPM’s “Technical Performance Meas.” Define life cycle (concept to disposal)

Engineering For Product Competitiveness
3) Considering the overall system hierarchy and interactions between various levels in the hierarchy. Look both horizontally and vertically. 4) Organizing and integrating the necessary engineering and related disciplines into the main systems engineering effort in a timely concurrent manner. 3 Various views of “hierarchy” Physical view Functional view – inputs and outputs Logical view – algorithms Timing view 4) Ims --- schedule and resource mgt.

Engineering For Product Competitiveness
5) Establishing a disciplined approach with appropriate review, evaluation, and feedback provisions to insure orderly and efficient progress from the initial identification of need through phase out and disposal. Disciplined !!!!! Stay out of the firefighting syndrome

System Engineering – Definitions
1) The application of scientific and engineering efforts to: a) transform an operational need into a description of system performance parameters and a system configuration through the use of an iterative process of definition, synthesis, analysis, design, test, and evaluation;

System Engineering - Definitions
b) integrate related technical parameters and ensure compatibility of all physical, functional, and program interfaces in a manner that optimizes the total system definition and design; c) integrate reliability, maintainability, safety, survivability, human engineering, and other such factors into the total engineering effort to meet cost, schedule, supportability, and technical performance objectives. Understand (determine and define the weighted relationships) At some level the all is relative to cost Including safety, schedule, reliability

2) An interdisciplinary approach encompassing the entire technical effort to evolve and verify an integrated and life-cycle balanced set of system, people, product, and process solutions that satisfy customer needs. Systems engineering encompasses:

a) the technical efforts related to the development, manufacturing, verification, deployment, operations, support, disposal of, and user training for system products and processes; b) the definition and management of the system configuration; c) the translation of the system definition into work breakdown structures; d) development of information for management decision making.

3) An interdisciplinary collaborative approach to derive, evolve, and verify a life-cycle balanced system solution, which satisfies customer expectations and meets public acceptability.

Key Words/Themes Top-down Lifecycle Interdisciplinary
Definition of System Requirements Top down -- bottoms up

System Lifecycle Process
Definition of Need Conceptual Design Preliminary Design Detail Design and Development Production/Acquisition Utilization and Support Phaseout and Disposal See Figures 2.1 through 2.4

System Lifecycle User’s Perspective
N E D Conceptual Detail Production Design Design ACQUISITION PHASE Product Use, Phase Out, Disposal UTILIZATION PHASE

Conceptual Design Finalized Need Statement (Agreed to with Customer)
Feasibility Analysis (alternative concepts) -Technical (Can it do the job) -Cost (Is it affordable) -Schedule (Will it be available when desired) -Risk (Is the risk acceptable) High Level Requirements Analysis - Operational Requirements - Maintenance and Support - Technical Performance Measures - Functional Analysis and Allocation - Analysis, Synthesis and Evaluation Relate SON to MER

Preliminary Design System Functional Analysis
Preliminary Synthesis and Allocation of Design Criteria System Optimization System Synthesis and Definition (More later)

Detail Design System/Product Design Prototype Development
System Prototype Test and Evaluation (More later) PRD…….CDR……..

Production & Product Use
System Assessment and Evaluation Modifications - Corrective Action - Product Improvement Utilization and Support - Assessment, Analysis and Evaluation - Modifications

Phase Out And Disposal Considerations Throughout the Life-Cycle
Design for Disposability Green Engineering

Other Process Models Waterfall Model (Risk not well addressed)
Spiral Model (Intended to accommodate risk and technology evolution) V Model (Portrays verification throughout the life-cycle) Note: Most models must be tailored! See Figure 2.5

System Design Evaluation/Feedback

A Combined Perspective
From V Diagram and the Systems Engineering Engine By William Schoening, Dec 2005

System Design Criteria
Requirements Analysis Operational Requirements Feasibility Analysis Maintenance and Support Concept Measures of Effectiveness (Technical Performance Parameters, Technical Performance Measures) System Level

System Design Evaluation
Identification of Design-Dependent Parameters (DDP) Analysis and Trade-off Studies Synthesis and Evaluation System Level

System Design Criteria
Requirements Analysis Functional Analysis and Allocation Measures of Effectiveness (Technical Performance Parameters, Technical Performance Measures) Subsystem Level

System Design Evaluation
Identification of DDP Analysis and Trade-off Studies Synthesis and Evaluation Subsystem Level

Evaluation of Multiple Criteria
System Attributes Measures of Effectiveness/Technical Performance Measures Design Dependent Parameters

Multiple Criteria System Attributes - arise from/in need statement
Measures of Effectiveness - must be specified in terms of some level of importance, as determined by the customer and the criticality of the functions to be performed (units of measure) Design Dependent Parameters(DDP) - tradeoffs must be made

Generating Alternatives
First-Order Consideration SYSTEM VALUE ECONOMIC FACTORS TECHNICAL FACTORS Second-Order Considerations REVENUES LIFECYCLE COST SYSTEM EFFECTIVENESS (Adapted From: Blanchard and Fabrycky, “System Engineering and Analysis, Prentice Hall, 2005)

Product Realization A K C B C U S T O M E R D E F L G J I H 1 2 5 T O
1 A P L I E D R S C H 2 5 T O P D W N Need, Functions, and Requirements A K C B 9 4 3 T E C H N O L G I S C U S T O M E R Design Synthesis Design Team D D E C I S O N E F L B O T M U P 8 6 Estimation & Prediction G Design Evaluation J I H 7 Databases & System Studies Existing Subsystems & Components (Adapted From: Blanchard and Fabrycky, “System Engineering and Analysis, Prentice Hall, 2005)

Implementing Systems Engineering
Applications Domains for Systems Engineering Management of Systems Engineering Potential Benefits See Section 2.6 (More on Management Later)

Conceptual System Design
Problem Definition & Need Identification Advance System Planning System Feasibility Analysis System Requirement Analysis Measures of Effectiveness/Technical Performance Measures (TPM) Functional Analysis and Allocation Synthesis, Analysis, Evaluation & Trade Studies System Specification Conceptual Design Review

System Design Problem Definition & Need Identification Applied
Advanced System Planning System Feasibility Analysis Applied Research System Requirement Analysis Operational Requirements Maintenance and Support Requirements Technical Performance Measures (TPM) Functional Analysis and Allocation (System Level) Analysis Synthesis, Evaluation & Trade Studies SEMP Technology Development and Application System Specification Conceptual Design Review Preliminary Systems Design (Adapted From: Blanchard and Fabrycky, “System Engineering and Analysis, Prentice Hall, 2005)

Problem Definition and Need Identification
Focus: Key Customer Needs and Functionality Define Key System Attributes! Includes Initial System Capabilities/Limitations/Constraints Probably the most difficult step! Must involve customer! Don’t Design It Now and Fix It Later!

Advanced System Planning
Determine Overall Program Requirements Program Management Plan Overall Organization Cost and Schedule Management Supplier Management Systems Engineering Management Plan (SEMP) Technical Execution Systems Engineering Implementation

Advanced System Planning
Definition of system operational requirements Development of the system maintenance and support concept Identification and prioritization of technical performance measures Completion of a top-level functional analysis Preparation of a system specification Identification of program milestones Entry and Exit criteria for each milestone Integrated Master Plan/Integrated Master Schedule High Level Only (For Now)

System Feasibility Analysis
Identify possible system-level design approaches Evaluate most likely approaches based on - Performance - Effectiveness - Maintenance and Sustaining Support Economic Criteria Schedule Risk Recommend a preferred course of action consistent with resource constraints. Need Technology

Missouri University of Science & Technology
Program Completed Missouri University of Science & Technology © 2003 Curators of University of Missouri

MISSOURI UNIVERSITY OF SCIENCE AND TECHNOLOGY Rolla, Missouri, U.S.A.

Similar presentations

Presentation on theme: "MISSOURI UNIVERSITY OF SCIENCE AND TECHNOLOGY Rolla, Missouri, U.S.A."— Presentation transcript:

Similar presentations

About project

Feedback

Log in

Auth with social network:

MISSOURI UNIVERSITY OF SCIENCE AND TECHNOLOGY Rolla, Missouri, U.S.A.

Similar presentations

Presentation on theme: "MISSOURI UNIVERSITY OF SCIENCE AND TECHNOLOGY Rolla, Missouri, U.S.A."— Presentation transcript:

Similar presentations

About project

Feedback