25
SYSTEM DEVELOPMENT METHODS 노노노 , 노노노 , 노노노 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Embed Size (px)

Citation preview

Page 1: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

SYSTEM DEVELOPMENT METHODS

노형종 , 문정곤 , 허승구

Class Term Project2005 Spring

POSTECH

IE 381 Management Information Systems

Page 2: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Contents

1/21

Systems Development Life Cycle (SDLC)

Rapid Application Development (RAD)

Prototyping

Page 3: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Definition The overall process of developing information systems through a

multi step process from investigation of initial requirements through analysis, design, implementation and maintenance.

<Russell Kay, Computer World>

Types of SDLC Waterfall, Fountain, Spiral

Outputs from one step inputs to next Often referred to as the “waterfall” model

(the oldest one - early 1970s)

Systems Development Life Cycle

2/21

Page 4: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Waterfall Development Method

Systems AnalysisSystems Designs

3/21

Page 5: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Phase 1: Investigation Initialization

Management planning, Users’ needs & opportunities

Formal definition Objective, motivation, scope, boundaries, constraints, strategy Verifying a problem or deficiency really exists, or to pass judgment on the new

requirement.

Feasibilities studies Technical Feasibility is the availability of computing hardware and software to

do a particular job. In many cases the managers’ concerns were well founded because the technology did not exist.

Economic Feasibility is the ability of a system to pay for itself in monetary terms. Management does not want to spend a dollar unless it receives more than a dollar in return. Ex) The cost-benefit Analysis, Break-even Analysis, Payback Analysis, NPV.

Operational Feasibility relates to the ability of the people working within a system to do their jobs in a prescribed manner. Ex) Ability of Users and Participants & Attitudes of Users and Participants

Organizational Feasibility. How well a proposed e-commerce system firs the company’s plans for developing Web-based sales, marketing, and financial system.

4/21

Page 6: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Analysis What a system should do to meet the needs of users.

Determine requirementsStudy current systemStructure requirements and eliminate redundancies

Requirement AnalysisFunctional requirementsPerformance requirements

Generate alternative designs Compare alternatives Recommend best alternative

Phase 2: Analysis

5/21

Page 7: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Design How the system will accomplish this objective.

User interface DesignScreen, Form, Report, and Dialog

Design

Data DesignData Element structure Design

Process DesignProgram and Procedure Design

Phase 3: Design

6/21

Page 8: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Evaluating Hardware, Software, and Services Companies may use a scoring system of evaluation when

there are several competing proposals for a hardware or software acquisition.

Software Development or Modification Documentation

Major mechanism of communication during development process

Data Conversion Correcting incorrect data, filtering our unwanted data,

consolidating data form several data warehouses. Testing

Testing & Debugging the Software Training

Phase 4: Implementation

7/21

Page 9: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Phase 4: Implementation

Conversion

Parallel Strategy

Plunge Strategy

Phased Strategy

Pilot Strategy

Run old & new systems for awhile to check validity. Safe.

Install in one part of organization at a time. Learn and adapt

In large system change one function at a time (e.g., order entry)

Start using entire system. Can be dangerous if errors exist.

8/21

Page 10: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Modification Modifying established system due to changes

in the system for potential problems or necessary change.

Correcting errors

Feedback

Phase 5: Maintenance

<Martin, “Managing Information Technology” p.395>

9/21

Page 11: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

SDLC Pros and Cons

Advantages: Highly structured, systematic process Thorough requirements definition Clear milestone with business management

sign-offs Disadvantages:

Does not account well for evolving requirements during project

Time-consuming (and costly) process

10/21

Page 12: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Motivation of RAD

Limitation of SDLC Pressures for businesses to speed up Shorter development lifecycles Competition in changing global environment

“Why wait 3 years to develop systems likely to be obsolete upon completion?”

RAD methodology was born!

11/21

Page 13: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Definition of RAD

Rapid Application Design A system development methodology

created to radically decrease the time needed to design and implement information systems

<James Martin, “RAD, CIRCA”>

12/21

Page 14: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

The 4 Essentials of RAD (1/2)

Management Executives. Support for the RAD

People Participation in JAD type Specialized team for RAD: SWAT

“Skilled With Advanced Tools”

Joint application design (JAD) - Group Decision Support System- Users, Managers and Analysts work together for several days- System requirements are reviewed- Structured meetings

13/21

Page 15: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

The 4 Essentials of RAD (2/2)

Methodologies RAD life cycle: Users play key roles

Tools Fourth-generation languages and CASE tools

that facilitate prototyping and code generation

Computer-Aided Software Engineering (CASE) – Any software tool to transfer some of the systems development workload from the human developer to the computer by automating one or more steps of a software development methodology

14/21

Page 16: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

RAD Life Cycle

Executives, managers, users determine requirements JRP workshops to agree requirements, overall planning

JAD session to develop basis designCASE tool is used

Generate codeEnd users validate design

Delivery of new system to users

15/21

Page 17: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Definition of Prototyping

The overall process of developing IS, which enables creation of system (or part of system) more quickly, then revising after users have tried it

< Martin, “Managing Information Technology” >

Selected features : only some essential features included in prototype, more added later

16/21

Page 18: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Prototyping Examples

Graphic user interface: usually needs several modification to meet the user requirements

A completely operational prototype can be used as a pilot

17/21

Install in one part of organization at a time. Learn and adapt

Pilot Strategy

Prototyping is similar to decide what shall you be dressed in. This girl is the user. Various designs of dresses are the prototypes. If the user does not like the proposed one, developers do modification until it meets the user’s requirements.

Page 19: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Prototyping Life Cycle

18/21

Prototype cycle

Page 20: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Prototyping Pros & Cons

Advantages: Communications between the developer and user are

improved The user plays a more active role in system development The information specialists and the user spend less time and

effort in developing the system Implementation is much easier because the user knows

what to expect

Disadvantages: End prototype often lacks security and control features

May not undergo as rigorous testing

Final documentation may be less complete

More difficult to manage user expectations

19/21

Page 21: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Prototyping

RAD

SDLC

SPEED

STABILITY

3 Types of System Development

Large and complex system

Hybrid type of SDLC and Prototyping

When requirements are hard to define

20/21

Page 22: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

References

O’Brien, James, “Introduction to Information Systems”, McGraw-Hill

Martin, James, “Managing Information Technology” ,Prentice Hall

Martin, James, “RAD, circa - Cooperative Intelligent Real-Time Control Architecture”,1991

Kenneth, at al, “Management Information Systems”, Prentice hall

Raymond, at al, “Management Information Systems”, Prentice hall

Russell, Kay, “Quickstudy”, http://www.computerworld.com

21/21

Page 23: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

“MIS is one of the most appreciated course by the graduates”

Special Thanks To

POSMIS

Page 24: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Questions?

Page 25: S YSTEM D EVELOPMENT M ETHODS 노형종, 문정곤, 허승구 Class Term Project 2005 Spring POSTECH IE 381 Management Information Systems

Pizza Party!