INSE6400 – Introduction2

8/17/2019 INSE6400 – Introduction2

1/29

Introduction 2


2/29

Reasons for systems projects◦ Improved service

◦ Better performance

◦ More information

◦ Stronger controls◦ Reduced cost


3/29

Internal Factors◦ Strategic plan

◦ Top managers

◦ User requests

◦ Information technologydepartment

◦ Existing systems

External Factors◦ Technology

◦ Supplier

◦ Customers

◦ Technology

◦ Competitors

◦ The economy

◦ Government


4/29

1-Use an interdisciplinary systems thinking approach toconsider the complete problem in every systems decision inevery stage of the system life cycle.◦ What is the system under consideration?

◦ What is the system boundary?

◦

What is the actual problem we are trying to solve?◦ Who are the decision makers and stakeholders?

◦ What are the influencing factors and constraints of the systemenvironment?

◦ How will we know when we have adequately defined the problem?

◦ What value can the system provide to decision makers and stakeholders

including clients, system owners, system users, and consumers ofproducts and services?

◦ How much time do we have to solve the problem?


5/29

2: Convert customer needs to system functions, requirements,and performance measures.◦ Who are the stakeholders (clients, system owners, system users, and

consumers of product and services) holding a vested interest in thesystem?

◦ What is our methodology for implementing the systems engineeringprocess to define system functions and requirements?

◦

How do we involve decision makers and stakeholders in our systemsengineering process?◦ What are the functions the system needs to perform to create value for

stakeholders?◦ What are the design objectives for each function?◦ How will we measure the ability of a design solution to meet the design

objectives?◦ What are the requirements for each function?◦ How will we allocate system functions to system elements?◦ How, when, and why do system elements interact?◦ What are the design, operational, and maintenance constraints?◦ How will we verify that elements meet their requirements and interfaces?


6/29

3: Lead the requirements analysis, design synthesis, andsystem validation to achieve successful system realization.◦ How will we know when we have adequately solved the problem?◦ How do we ensure that the design will meet the requirements?◦ How do we resolve conflicting requirements, interfaces or design

issues?◦

How can we allocate system performance to system elements?◦ How can we identify and validate component and system

interfaces?◦ Can we trade off one performance measure versus another

measure?◦ How will we verify that system performance has been achieved?◦ How do we identify, assess, and manage risk during the system

life cycle?◦ How do we trade off system performance with life cycle cost to

ensure affordability?


7/297

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.


8/29

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

8


9/29


10/2910


11/2911


12/29

Functional View

Input: addition of material, energy, or information to a system

Process: Altering material, energy, or information

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

12

Input OutputProcess


13/29

13


14/29

14


15/29

15


16/29

Choose an Engineered System◦ Identify the inputs, outputs, and process for this

system

◦ What are the building blocks you think is used in

this project

16


17/29

Step 1: Understand the problem oropportunity

Step 2: Define the project scope andconstraint

Step 3: Perform fact-finding Step 4: Evaluate feasibility Step 5: Estimate project development time

and cost Step 6: Present results and recommendation

to management


18/29

Analyze the problem encountered Define the need for the new system

Identify information systems involved

Initiate the project


19/29

Project scope: boundaries or extent of theproject.

A constraint: a requirement or condition thatthe system must satisfy or the outcome thatthe system must achieve.


20/29

Conduct interview Review documentation

Observe operation

Conduct a user survey


21/29

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


22/29

Operational Feasibility Technical Feasibility

Economic Feasibility

Schedule Feasibility


23/29

Operational Feasibility means that aproposed system will be used effectivelyafter it has been developed.◦ Does management or do users support the

projects? 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.


24/29

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 technicalexpertise?◦ Will the hardware and software environment be

reliable?◦ Will the system be able to handle future

transaction volume and company growth?


25/29

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 orpostponing the project


26/29

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?


27/29

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.


28/29

Estimate the project time and develop thetime schedule

Estimate the project cost based on TCO


29/29

Introduction Systems request summary

Findings

Recommendation Time and cost estimates

Expected benefits

Appendix

Documents

INSE6400 – Introduction2