lecture 1 introduction s

8/17/2019 Lecture 1 Introduction S

1/41

Introduction

Fereshteh Mafakheri

[email protected]


2/41

A system is◦ A collection of different elements that work

together to produce a greater results than eachelement could obtain

Example of a system is a company which ismade of these elements◦ People◦ Hardware◦ Software◦ Documents◦ Policies◦ Departments

2


3/41

Functional View

Input: addition of material, energy, or information to a systemProcess: Altering material, energy, or information

Output: movement of matter, energy, or information out of asystem

3

Input OutputProcess


4/41

Systems Engineering isThe application of science, math, andbusiness to meet customer's needsthrough the entire system lifecycle

Definition of SystemsEngineering(NASA SE Handbook )◦ Systems Engineering is a robust

approach to the design, creation, andoperation of systems .

4


5/41

The function of systems engineering is toguide the engineering of complex systems .Guide to lead, manage, or direct, usuallybased on the superior experience in pursuinga given courseEngineering design, construction andoperation of efficient and economicalstructures, equipment, and systemsSystems a set of interrelated componentsworking together toward some commonobjectiveComplex diverse elements with intricaterelationships with one another

5


6/41

Systems Engineering◦ An interdisciplinary approach and means to enable

the realization of successful systems.◦ It focuses on holistically and concurrently

understandingstakeholder needs;exploring opportunities;documenting requirements; and

synthesizing, verifying, validating, andevolving solutions while considering the completeproblem, from system concept exploration throughsystem disposal.

6


7/41

An organized and systematic way of design.Considers all the factors involved in the designIntegrates all the disciplines and specialty groups into a teameffortEnsures the business and customer needs of all stakeholdersand ensures a system that meets the user needs

7


8/41

Requires investment of time and effort togain experience & an extensive broadening ofthe engineering base as well as learningcommunication and management skills

Educational experience in a traditionalengineering discipline is necessary

There are few tools & quantitativerelationships to help make decisions


9/419


10/4110


11/4111


12/4112


13/41

Math & Physical Sciences◦ Qualitative modeling◦ Quantitative modeling◦ Physical modeling◦ Theory of Constraints◦

Physical LawsManagement Sciences◦ Economics◦ Organizational Design◦ Business Decision Analysis◦

Operations ResearchSocial Sciences◦ Multi-disciplinary Teamwork◦ Organizational Behavior◦ Leadership


14/41

Body of Knowledge◦ Problem definition

System boundariesObjectives hierarchyConcept of operationsOriginating requirements

◦ Concurrent engineeringSystem life cycle phasesIntegration/Qualification

◦ ArchitecturesFunctional/LogicalPhysical/OperationalInterface

◦ TradesConcept-levelRisk managementKey performanceparameters

14


15/41

15


16/41

16


17/41

17


18/41

18


19/41


20/41

20

Any engineer acts as a systems engineer whenresponsible for the design and implementationof a total system.The difference with “traditional engineering” liesprimarily in the greater emphasis on defininggoals, the creative generation of alternativedesigns, the evaluation of alternative designs,and the coordination and control of the diversetasks that are necessary to create a complex

system.The role of Systems Engineer is one of the

n ger that utilizes a structured valuedelivery process


21/41

21


22/41

22

The major steps in the completion of a typical systemsengineering project are the following: (1) problem statement; (2)identification of objectives; (3) generation of alternatives; (4)analysis of these alternatives; (5) selection of one of them; (6)creation of the system, and, finally, (7) operation.

Some examples of Systems Engineering Process activities are:

Defining needs, operational concept, and requirements Functional analysis, decomposition, and allocation System modeling, systems analysis, and tradeoff studies Requirements allocation, traceability, and control Prototyping, Integration, and Verification

System Engineering Product and Process control Configuration and Data Management Risk Management approaches Engineering technical reviews and their purposes


23/41


24/41

24


25/41

Reasons for systems projects◦ Improved service◦ Better performance◦ More information◦ Stronger controls◦ Reduced cost


26/41

Internal Factors◦ Strategic plan◦ Top managers◦ User requests◦ Information technology

department◦ Existing systems

External Factors◦ Technology◦ Supplier◦ Customers◦ Technology◦ Competitors◦ The economy◦ Government


27/41

Operational FeasibilityTechnical FeasibilityEconomic Feasibility

Schedule Feasibility


28/41

Operational Feasibility means that aproposed system will be used effectivelyafter it has been developed.

◦ Does management or do users support theprojects? Do users see the need for change?

◦ Will the system result in a work force reduction?◦ Will the system require training for users?◦ Will customers experience adverse effect in

anyway, either temporarily or permanently.


29/41

The technical resources needed to develop,purchase, install, or operate the system.

◦ Does the company have the necessary hardware,

software, and network resources?◦ Does the company have the needed technical

expertise?◦ Will the hardware and software environment be

reliable?◦ Will the system be able to handle future

transaction volume and company growth?


30/41

Economic Feasibility means that the projectedbenefits of the proposed system outweigh theestimated costs usually considered the total cost ofownership (TCO).

◦

People, including IT staff and users◦ Hardware and equipment◦ Software◦ Formal and informal training◦ Licenses and fees◦ Consulting expenses◦ Facility costs◦ The estimated cost of not developing the system or

postponing the project


31/41

Schedule Feasibility means that a project canbe implemented in an acceptable time.

◦ Can the company or the IT team control the factor

that effect schedule feasibility?◦ What condition must be satisfied during thedevelopment of the system?

◦ Will an accelerated schedule pose any risk?◦ Will the project manager be appointed?


32/41

Identify and weed out the systems requestthat are not feasible.Even if the request is feasible, it might not benecessary.Feasibility analysis is an ongoing task thatmust be performed throughout the systemsdevelopment process.


33/41

Step 1: Understand the problem or opportunity

Step 2: Define the project scope and constraint

Step 3: Perform fact-finding

Step 4: Evaluate feasibility

Step 5: Estimate project development time and costStep 6: Present results and recommendation tomanagement


34/41

Analyze the problem encounteredDefine the need for the new systemIdentify information systems involvedInitiate the project


35/41

Project scope: boundaries or extent of theproject.A constraint: a requirement or condition thatthe system must satisfy or the outcome thatthe system must achieve.


36/41

Conduct interviewReview documentationObserve operationConduct a user survey


37/41

Evaluate the project’s operational, technical,economic, and schedule feasibility.


38/41

Estimate the project time and develop thetime scheduleEstimate the project cost based on TCO


39/41

IntroductionSystems request summaryFindingsRecommendationTime and cost estimatesExpected benefits


40/41

Introduction to complex systems


41/41

Systems Engineering: Principles and Practice,2nd edition, 2011. A. Kossiakoff et al., Wiley.

Chapter 1 & 2