© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 1

Systems EngineeringPresented at

Stevens–New Jersey Community College Strategic Partnership27th September, 2005

Dr. Rashmi JainAssociate Professor

Systems Engineering and Engineering Management

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 2

Engineering Challenges

Engineering Challenges that Demand an Academic Response» Compressed delivery schedules/time-to-market» Increasing emphasis on recapitalization of existing systems

and assets» Increasing use of Reusable Parts, Common Platforms, and

Commercial Off the Shelf (COTS) system elements» Extremely high cost of errors, failures, and rework» Increasing emphasis on capabilities that require extended

architectures and implementation of “System of Systems” concepts and interoperability

» Increasing emphasis on multiple partner and contractor teams

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 3

Challenges:Compressed Time-to-Market

Knowledge ofEnvironment

Stakeholders buy-in

Trad

e of

fs

ConvergingDesign

Decisions

Requirements Concept Architect Design

Cost of ChangeScope of

Change Time to ChangeRobustness

of Change

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 4

0 50 100Years

Results from survey of organizations conducted in March 2003 on Recapitalization of Legacy assets.

Challenges:Recapitalization of Existing Assets

11%

29%

24%

36%

We are considering our options

We are still accessing ourlegacy systems the same waywe always haveWe are using middlewareproducts to leverage the valueof our legacy appsWe have ported most of ourlegacy apps to another platform

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 5

Only one third of 300,000 projects were developed from scratch.Two thirds of the projects were developed using reusable parts and COTS.

0% 5% 10% 15% 20% 25% 30% 35%

Developed from scratch using traditional languages andmethods

Purchased application & modified

Developed from scratch using an object model

Developed some components & purchased others

Purchased application & modified extensively

Purchased components & assembled the application

Purchased application & performed no modifications

CHAOS: A Recipe for Success, The Standish Group International, Inc, 1999

Challenges:Reusable Parts, Common Platforms, and COTS

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 6

Challenges:High Cost of Errors/Failures/Rework

What do defect rates really mean? Is there any significance to them? To demonstrate the real impact of defects, let's consider the following:

Would you consider it acceptable for the following processes to be 99.9% reliable? Each 0.1% defect rate would result in an additional:

1 hour per month of contaminated drinking water. 16,000 letters lost every day by the US Postal Service. 2 accidents per month at O'Hare International Airport. 20,000 erroneous drug prescriptions each year. 50 babies dropped on the delivery room floor each hour. 22,000 checks drawn from the wrong account per hour.

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 7

Challenges:High Cost of Errors/Failures/Rework

Longer a defect remains undetected - More expensive it becomes to correct.The savings potential from early defect detection is huge.

About 60 percent of all defects usually exist by design time (Gilb, 1988).

Normal module development$500 to $1000 per function point

Error-prone module development» $2000 to $4000 per function

point

* Source: Steve McConnell, “Software Quality at Top Speed”, 1996

(McConnell, 1996)

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 8

System 3

Company BCompany A

Exchange Site Company C

System 1

System 3

System 1

System 2

Translate

Route

Rules

System 2

System 1

System 1System 2

EAI EAI

EAI

Challenges:Extended Architectures/SoS Capabilities

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 9

Evolution of Enterprise SolutionsIncreasing Role of middlewareIncreasing Role of Systems Integrators

Step 1

System Context

Step 2

Architecture &Design

Step 3

Implementation

Traditional Sequential Approach Proposed COTS Simultaneous Approach

Marketplace

Programmatics/Risk

Stakeholder Needs/Business Processes

Architecture/Design

Simultaneous Definitionand Tradeoffs

Key to building solutions – simultaneously define and make tradeoffs among the above shown ‘spheres of influence’.

Challenges:Evolution towards Systems Integration Model

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 10

Challenges:Multiple Contractor and Partner Teams - Airbus

International co-operation and partnerships with major companies all over the world and a network of:» 1500 suppliers in 30

countries.» 46,000 employees in

China, France, Germany, Japan, North America, Spain, and UK,

» Spare parts centers in Toulouse, Miami and Beijing and 120 field service officers around the world.

AIRBUS FRANCEAIRBUS DEUTSCHLANDAIRBUS UNITED KINGDOMBelairbusAIRBUS ESPANARolls Royce or Engine Alliance engines

Cabin Interior (AIRBUS DEUTSCHLAND) not shown

Airbus A380 industrial work share

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 11

Please note: Product model-technology mix changes from product to product.

Ergonomics

Technical Writing

Graphic Design

Packaging Eng.

Electrical Eng.Computer Eng.

Sales Eng.

PCB DesignSoftware

Engineering

MarketingMechanical Eng.

Industrial Design

Manufacturing Eng.

Mechanical Eng.

Aesthetics

Reliability

The “whole” product requires the integrated contribution of numerous technical and non-technical disciplines throughout

the life cycle of the product, albeit to different degrees at different times.

A Product Scope

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 12

RIEE – The “Total Design” Spine

Create and implement a framework within the design spine which will enable students to practice total design. Total design is the systematic activity necessary from the identification of the market/user need, to the selling of the successful product to satisfy that need –an activity that encompasses product, process, people and organization. Focus on product/system development process» how design is practiced in a ‘context’» subscribe to a common methodology» systems thinking» higher thinking skills in young adults

Market

Specification

Conceptual design

Preliminary design

Detail design

Manufacture

Sell

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 13

Total Design – Educational Objectives

1. The graduates will be able to interact with customers and stakeholders, understand their needs and translate them into systems requirements.

2. The graduates will be innovative and creative in formulating andevaluating different concepts of design.

3. The graduates will be thoroughly aware of, and sensitive to environmental, social, ethical and economic impacts of the systems they will design throughout their lifecycles.

4. The graduates will have the technical competencies and the breadth of knowledge needed to design, build and manage complex systems.

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 14

Total Design

Operational ModelOperational Model Detail DesignDetail DesignFunctional DeficiencyOperational Deficiency

Technology FusionTechnology Breakthrough

Behavior AnalysisAccidental Discovery

Production/ManufacturingMaintenance

Retirement/Obsolescence

Production/ManufacturingMaintenance

Retirement/Obsolescence

© Dr. Rashmi Jain

Systems Engineering

Systems engineering is a process that transforms an operational need or market opportunity into a system description to support detail design, its development,

production, maintenance, retirement and obsolescence

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 15

Systems Engineering vs. Total Design

Systems Engineering» The design, production and

maintenance of trustworthy systems within cost and time constraints – A.P. Sage

» Systems Engineering is a robust approach to the design, creation ad operation of systems – NASA

Total Design» Total design is the

systematic activity necessary from the identification of a market/user need, to the selling of the successful product/process/service to satisfy that need – an activity that encompasses product, process, people and organization – S. Pugh

Product

People

Organization

Process

Product

Realization

Market/User

Need

Production

Mainten

ance

Retirement

Desig

n Total Design

Systems Engineering

© Dr. Rashmi Jain

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 16

Systems Engineering Process – Total Design

Need / Market Opportunity

Concept Generation,

Evaluation and Selection

Operational Scenarios

System Functionalities

Physical Realization

System ModelDetail DesignDevelop / Build

Stakeholder Identification

Requirements Gathering and

Analysis

Testing and Integration

Itera

tive

Itera

tive

Con

curr

ent

Con

curr

ent

Ope

ratio

nsO

pera

tions

Mai

nten

ance

Mai

nten

ance

Ret

irem

ent/O

bsol

esce

Ret

irem

ent/O

bsol

esce

Total Design

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 17

PreferredDesign Concept

PreferredSystem Architecture

and Configuration

FunctionalNeed

Need/OpportunityIdentification

Detail Design& Development

PreliminarySystem Design

ConceptualSystem Design

17

Simplified view of systems engineering process involving Total Design

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 18

Systems Engineering and Integration

Systems

Engineering And

Integration

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 19

Systems Engineering and Integration:Business Process and Operational Assessment

Support Customers/Stakeholders in Identification of Business & Operational Shortfalls

Elicit, Gather, & Confirm Business and Mission Intent and Requirements

Translate Shortfalls (Business and Mission Requirements) into Solution/System RequirementsGenerate, assess, and evaluate system concepts and technologiesIdentify and Manage System Operational, and Functional BaselinesIdentify what is Achievable within the Cost and Schedule Envelope

Systems

Engineering And

Integration

© 2005 Stevens Institute of Technology, Dr. Rashmi Jain, rjain1@stevens.edu 20

Systems Engineering and Integration:System/Solution/Test Architecture Development

Identify Preferred Implementation Approach

Implementation Approach Trade-Offs vis-à-vis Business/Mission Requirements

Develop System, Solution and Test Architectures

Adhere to Open Architecture Guidelines to Ensure Scalability, Modularity, and Future Upgrades and Enhancements

Adhere to Consistent Solution Testing, Validation and Verification Approach

Determine and Manage Impact to Currently Fielded Solutions

Plan and Manage Systems Integration Issues

Manage and optimize interfaces

Systems

Engineering And

Integration