Announcements/ Reminders

FB group (IE 155 A.Y. 2012-2013) Form 5 and class card Index card/ picture 1/4 sheet (at least one per mtg) Case study #1 on Monday, December 10

Previously

System Life-Cycle [Engineering]

M.A.Ramirez | December 04, 2012

Objectives
Define system life cycle Identify the phases of a system life cycle and activities associated Identify principles and approaches in designing for the system life cycle Identify problems in a system life cycle Enumerate some system process models

Introduction
Last meeting .
Industrial engineers design industrial systems Few I.E.s really engage in overall system design

Introduction
Industrial engineers are systems engineers Classical engineers has focused mainly on product performance as the main objective rather on development of the overall system of which the product is a part Accordingly, engineers must turn its focus on lifecycle engineering

The System Life Cycle

Fundamental to application of systems design/ engineering is understanding the system life-cycle process illustrated for the product in the figure below

The System Life Cycle

The significance of focusing on the system life cycle is that decisions made early in the Acquisition Phase are informed of the proposed and intended activities in the Utilization Phase (e.g. Maintenance and Operation, etc.) A life cycle focus can save money in the long term
Sixty percent of the errors in system development originate in the systems requirements analysis

The System Life Cycle

Classification is generic Both the acquisition and utilization process may involve both the customer and the producer Detailed presentation of the elaborate technological activities and interactions that must be integrated over the system lifecycle process is shown in your handout :)

The System Life Cycle

Progression is iterative from left to right, and not serial Life cycle functions described and illustrated are generic It is essential that this process be implemented completely, not only in the acquisition of new systems but also in reengineering of existing systems

The System Life Cycle

A. IDENTIFYING THE NEED/ CONCEPTUAL DESIGN
producing a clearly-defined set of user requirements at the system level clearly defining the functional requirements of the system establishes a Functional Baseline (the whats and whys of the system)

The System Life Cycle

B. PRELIMINARY DESIGN
Aim: convert the Functional Baseline into a preliminary definition of the system configuration or architecture (the hows of the system) The stage where functional design is translated into physical design Result: Allocated Baseline -- indicates that the functional requirements have been grouped together logically and allocated to subsystem level requirements which combine to form the overall system design

The System Life Cycle

C. DETAIL DESIGN and DEVELOPMENT
Development of the individual subsystems and components in the system Prototyping, testing and evaluation Product Baseline

The System Life Cycle

D. PRODUCTION and/or CONSTRUCTION
system components will be produced in accordance with the detailed design specifications Configuration audits

The System Life Cycle

E. PRODUCT USE, PHASEOUT, & DISPOSAL
Operational use and system support Disassembly and disposal of elements or components of the system without causing environmental degradation

The System Life Cycle

Systems engineering activities may continue to support any modification activity that maybe required rectify performance shortfalls meet changing operational requirements or external environment enhance current performance or reliability maintain ongoing support to the system

Designing for the Life Cycle

Get sheet!
What is the meaning of designing within the system life-cycle context compared to the old school definition of design?

Designing for the Life Cycle

Life-cycle focused design is simultaneously responsive to customer needs and to life-cycle outcomes Design should not only transform a need into a definitive product and system configuration It should ensure the designs compatibility with related physical and functional requirements

Designing for the Life Cycle

System life cycle goes beyond the product life cycle It embraces the life cycle of the manufacturing process as well as the life cycle of the product support and service capability

Designing for the Life Cycle

3 concurrent life cycles progressing in parallel

Designing for the Life Cycle

Need for the product comes into focus first During conceptual design of the product, consideration should simultaneously be given to its production This gives rise to a parallel life cycle for bringing a manufacturing capability into being

Designing for the Life Cycle

3 concurrent life cycles progressing in parallel

Designing for the Life Cycle

Third life cycle is of great importance too, but often neglected until product and production design is completed Needed to service the product during use and to support the mfg capability during its cycle

Designing for the Life Cycle

Communication and coordination is needed to develop the product, the manufacturing process, and the support capability Not easy to achieve Progress in this area is facilitated by new technologies that make more timely acquisition and use of design information possible

Designing for the Life Cycle

Systems Engineering Process Models

Waterfall Process Model

Waterfall Process Model

Introduced by Royce in 1970 Initially used for software development Each phase is carried out to completion in sequence until the product is delivered

Vee Process Model

Vee Process Model

Developed by Forsberg and Mooz the Vee describes and models the technical aspect of the project cycle Starts with user needs (upper left) Ends with user-validated systems (upper right)

Spiral Process Model

Spiral Process Model

Developed by Boehm in 1986 Introduces a risk-driven approach for the development of products and systems Iterative and proceeds through the several phases

System Life Cycle Problems

What the requirement stated.

What the designer specified

What the programmers implemented

What the user wanted

System Life Cycle Problems

It leads to misunderstandings between users and developers about what is to be delivered The information used in one subsystem is frequently needed by other subsystems Systems grow and change

System Life Cycle Problems

The SDLC needs an integration stage that identifies all inter-relationships Every system is part of a larger system and can be broken into smaller subsystem The numerous components of a system must communicate with each other

System Life Cycle Problems

The most specialized systems are the least adaptable Slow, inflexible, people-intensive system that is complex and unresponsive to organizational needs

Next Meeting

Quality function deployment; and/or Functional Analysis

- END

Thank you!