35
Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Embed Size (px)

Citation preview

Page 1: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Systems Development

Prepared byJohn Nicholas, Ph.D.

Loyola University Chicago

Project Management for Business, Engineering, and Technology

Page 2: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Systems

• Definition: A system is an organized or complex whole; an assemblage of parts interacting in a coordinated way.– Parts are affected by being in the system– Assemblage of parts does something– The assembly is of particular interest

• Holistic approach; parts of the body can not exist outside of the body

Page 3: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Classification

• Static structures– maps, floor plans, organizational charts

• Simple Dynamic– clockworks– predetermined motions– machines, solar system

• Control or Cybernetic– self-regulating– maintain equilibrium– servo-mechanisms

Page 4: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Classification

• Open – self-maintaining– self-reproductive– celluar forms, life

• Genetic - Societal– distinctive stages of life– plants

• Animal– mobility

Page 5: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Classification

• Human– self-consiousness– goal formulation– speech and symbolism

• Social– values, roles, history, culture, art forms, . . .

• Transcendental– unknowables which currently escape us

Page 6: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Taxonomy of Systems

Types ofSystems

Ref: John P/ van Gigch, Applied General Systems Theory, 2nd ed., Harper and Row, 1978.

PhysicsChemistryEarth science

BiologyBotanyZoology

AnthropologyPolitical Sci.PsychologySociology

BehavioralScienceEconomicsManagement

PhilosophyMetaphysicsTheology

FrameworksClockworksThermostats

Cells PlantsAnimals

HumansSocial Systems & Organizations

AllSystems

Physical Sci. Life Sci.Life Sci. Behavioral Sci.Behavioral Sci. Social Sci.Social Sci. TranscendentalsTranscendentals

Fields

Nonliving

With orwithoutfeedback

Living Systems

Open Systems

Level 1,2,3 Level 4,5,6 Level 7 Level 8 Level 9

Page 7: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Principles

• Element– smallest part of a system

• Subsystem– system which is part of a larger system

Page 8: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Elements & Systems

SeniorManagement

System - Company

Personnel Marketing Production Finance

Production Manager

Scheduling Manufacturing Inventory

Functional subsystem

Production subsystem

Page 9: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Principles

• Attributes– used to monitor system behavior and performance

• Environment– affects system performance, but outside of

decision makers control

• Boundary– separates a system from its environment

• Irrelevant Environment– has no influence on the system

Page 10: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Relevant / Irrelevant

Questions: 1. Is it relevant to system? 2. Can I control it?

Control It ?Relevant ?

Yes No

Yes

No

System

Environment

Irrelevant Env.

Irrelevant Env.

Page 11: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Principles

• Objectives– method of analyzing a system, have a clear

concise statement of objectives

• Structure– elements & subsystems linked by

relationships

• Constraints/Conflicts– limitations imposed from within or from

environment

Page 12: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Principles

• Open/Closed– closed systems are self-contained, ignore the

environment– open systems interact & adapt with environment – to manage an open system you must view it

within the context of the environment

• Natural/Man-made– man-made systems are designed and operated

by man

Page 13: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Organizations as Systems

Outputsgoodsservicesinformationwasteeconomic development

Inputsenergyinformationmateialpeople finances . .

Competition

Organization

PoliticalTechnology

SocialogicalEducational

Cultural

Environmental Subsystems

Page 14: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

External Environments

Mega-Environment

Technological

Element

Econo

mic

Elem

ent

Legal-Political Element

Sociocultural

Element

Inte

rnat

iona

l

E

lem

ent Task

Culture ofOrganization

Customers & Clients

Competitors

SuppliersLabor

Government Agencies

Page 15: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

System Concepts and Principles

Inputs, Process, Outputs• Human-made systems achieve objectives by converting

inputs into outputs through a defined process. • Outputs: end-result of a system and the purpose for which

the system exists. • Inputs: the raw materials, resources, or prior steps

necessary for the system to operate, produce outputs, and meet objectives. – Feedback: Input that originates from the system itself.

• Process: means by which the system transforms inputs into outputs. – One goal of system design is to create a process that

produces the desired outputs and meets system objectives effectively, and minimizes consumption of inputs and production of wasteful outputs.

Page 16: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Input-process-output relationship

Inputs OutputsProcess

Feedback

Page 17: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Deming System

Production, assembly, inspection

Suppliers

A

B

C

Tests of processesmachines, methods, costs

Distribution

Consumer Research

Design and redesign

Page 18: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Deming System

Productivity Increases

Provide jobsand more jobs

ImproveQuality

Stay in Business

CaptureMarket

Cost decrease dueto less rework, fewerdelays

Page 19: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Review

• Describe the following and explain how they fit into systems thinking: elements, subsystems, environment, boundary, open systems, structure, and constraints.

Page 20: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Review

• Describe the differences between open and closed systems. How do organizations best behave as systems?

Page 21: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Review

• What is the relevance of systems thinking to project management?

Page 22: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Systems Approach Methodology

The systems approach is a methodology for solving problems and managing systems that accounts for

1. The objectives and the performance criteria of the system.

2. The environment and constraints of the system.3. The resources of the system.4. The elements of the system, their functions,

attributes, and performance measures.5. The interaction among the elements. 6. The management of the system.

The methodology commonly employs models

Page 23: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

System Models

• A model is a simplified representation of the world; it abstracts the essential features of the system under study.

• A physical model is a scaled-down abstraction of the real system. It includes some aspects of the system and excludes others.– Example: model airplane.

• A conceptual model depicts the elements, structure, and flows in a system in terms of a schematic diagram or mathematical formulation. – Example: population dynamics schematic (next)

Page 24: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Births

Conceptual model of population dynamics

Terminal age group

Deaths

aging

Migration

Initial agegroup

Intermediate age group

aging

Page 25: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

System Life Cycle

• System life cycle is the pattern of change or evolution that similar kinds of systems follow.

• The basic life cycle of all organisms is the pattern of conception, birth, growth, maturity, senescence, and death.

• The basic life cycle of human-designed systems is the series of logical, structured steps called the systems development cycle. – The cycle has the phases of conception, definition, design,

development, fabrication, testing, installation or launch, production, operation and maintenance, and enhancement, replacement, or termination.

– The prescribed stages or phases for large-scale development projects is called systems engineering.

Page 26: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Systems Engineering

• The science of designing complex systems in their totality to insure that the components and subsystems making up the system are designed, fitted together, checked, and operated in the most efficient way.

• The conception, design, and development of complex systems where the components themselves must be designed, developed, and integrated together.

• A way to bring a whole system into being and to account for its whole life cycle—including operation and phase-out—during its early conception and design.

Page 27: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Dimensions of Systems Engineering

1

2

3

Page 28: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Dimensions of Systems Engineering (Cont’d)

1. SE is a multifunctional, interdisciplinary, concurrent effort.

– Systems engineers work with the system’s stakeholders to determine their needs and what the system must do to fulfill them.

– The needs become the basis for defining the system requirements, which specify what the system will do.

Page 29: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

2. It addresses the system’s structure and elements—its functional and physical design.

– System elements and subsystems are designed to perform the functions necessary to satisfy stakeholder objectives and requirements.

– The design effort focuses on how the system will meet the requirements.

Dimensions of Systems Engineering (Cont’d)

Page 30: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

3. It takes into account the way the system will be produced, operated, maintained, and finally disposed of—the entire system life cycle.

– This helps insure that the system will be economical to develop, build, operate, and maintain, and friendly to users and the environment.

Dimensions of Systems Engineering (Cont’d)

Page 31: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Systems Engineering Process

Forsberg and Mooz’s V-model (adopted from K. Forsberg and H. Mooz in Software Requirements Engineering, 2nd ed., ed. R. Taylor, M. Dorfman, and A. Davis (Los Alamitos, Calif.: IEEE Computer Society Press, 1997): 44-77).

Page 32: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Systems Engineering Process (cont’d)

Creating a system concept that will satisfy requirements involves a series of steps to define the subsystems and elements of the system. The process is an iterative cycle of

1) top-down analysis of details (decomposing the system into smaller parts)

2) bottom-up synthesis (building up and integrating the parts into successively larger parts)

3) evaluation (checking to see that results meet requirements)

Page 33: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

• The downstroke of the V represents subdividing functions of the system into subfunctions and requirements.

– At each level the process of working with customers to define requirements repeats, except the “customer” becomes the function at the next higher level and the question becomes, What must the functions at this level do to meet the requirements of the next higher level function?

Systems Engineering Process (cont’d)

Page 34: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Systems Engineering Process (cont’d)

• The upstroke of the V represents– assessing “design alternatives” to satisfy requirements– implementing design decisions—converting designs

into physical parts– integrating the parts– verifying that the integrated parts meet the

requirements. • The alternatives involve procuring available parts or

designing and building new ones.• Parts are checked individually and then assembled into

modules and again tested. – If tests reveal that parts or modules do not meet

requirements, the process returns to the downstroke of the V to determine why.

– the analysis-synthesis-evaluation cycle repeats.

Page 35: Systems Development Prepared by John Nicholas, Ph.D. Loyola University Chicago Project Management for Business, Engineering, and Technology

Review

• How does systems engineering differ from systems analysis?

• What is the emphasis in systems management? How does it differ from just “management”?

• How do systems analysis, systems engineering, and life cycles fit into systems management?