Fundamentals of Information Systems, Second Edition 1 Systems Development Chapter 8.

Fundamentals of Information Systems, Second Edition

1

Systems Development

Chapter 8


2

Principles and Learning Objectives

• Effective systems development requires a team effort of stakeholders, users, managers, systems development specialists, and various support personnel, and it starts with careful planning.

– Identify the key participants in the systems development process and discuss their roles.

– Define the term information systems planning and list several reasons for initiating a systems project.


3


• Systems development often uses different approaches and tools such as traditional development, prototyping, rapid application development, end-user development, computer-aided software engineering, and object-oriented development to select, implement, and monitor projects.

– Discuss the key features, advantages, and disadvantages of the traditional, prototyping, rapid application development, and end-user systems development life cycles.

– Discuss the use of computer-aided software engineering (CASE) tools and the object-oriented approach to systems development.


4


• Systems development starts with investigation and analysis of existing systems.

– State the purpose of systems investigation.– Discuss the importance of performance and cost

objectives.– State the purpose of systems analysis and discuss

some of the tools and techniques used in this phase of systems development.


5


• Designing new systems or modifying existing ones should always be aimed at helping an organization achieve its goals.

– State the purpose of systems design and discuss the differences between logical and physical systems design.

– Outline key steps taken during the design phase.– Define the term RFP and discuss how this document

is used to drive the acquisition of hardware and software.


6


• The primary emphasis of systems implementation is to make sure that the right information is delivered to the right person in the right format at the right time.

– State the purpose of systems implementation and discuss the various activities associated with this phase of systems development.


7


• Maintenance and review add to the useful life of a system but can consume large amounts of resources, so they benefit from the same rigorous methods and project management techniques applied to systems development.

– State the importance of systems and software maintenance and discuss the activities involved.

– Describe the systems review process.


8

An Overview of Systems Development


9

Top Uses for New Systems in Various Industries


10

Participants in Systems Development


11

Information Systems Planning


12

Systems Development Life Cycles and Approaches


13

The Traditional SDLC


14

Prototyping is an Iterative Approach to Systems Development


15

Rapid Application Development (RAD)

• Employs tools, techniques, and methodologies designed to speed application development.

• Joint Application Development (JAD) - RAD makes extensive use of this for data collection and requirements analysis.


16

Advantages and Disadvantages of RAD


17

Use of Project Management Tools

• Project schedule

• Project milestone

• Project deadline

• Critical path

• Program Evaluation and Review Technique (PERT)

• Gantt chart


18

Gantt Chart


19

Selected Project Management Software


20

Computer-Aided Software Engineering (CASE) Tools

Automate many of the tasks required in a systems development effort and enforce adherence to the SDLC, thus instilling a high degree of rigor and standardization to the entire systems development process

• Upper-CASE tools - CASE packages that focus on activities associated with the early stages of systems development.

• Lower-CASE tools - focus on the later stages of systems development and are capable of automatically generating structured program code.

• Integrated-CASE tools - provide links between upper- and lower-CASE packages.


21

Object-Oriented Systems Development

• Identify potential problems and opportunities within the organization that would be appropriate for the OO approach

• Define the kind of system users require

• Design the system

• Program or modify modules

• Evaluation by users

• Periodic review and modification


22

Use Case Diagram for a Kayak Rental Application


23

Systems Development Maturity Based on the Capability Maturity Model (CMM)


24

Systems Investigation


25

Systems Investigation

• Attempts to answer the following questions:

– What primary problems might a new or enhanced system solve?

– What opportunities might a new or enhanced system provide?

– What new hardware, software, databases, or procedures will improve an existing system?

– What are the potential costs (variable and fixed)? – What are the associated risks?


26

Feasibility Analysis


27

Systems Investigation Report


28

Systems Analysis


29

Systems Analysis

• Data collection - seeks additional information about the problems

• Data Analysis - manipulates collected data so that it is usable for the development team


30

Internal and External Sources of Data


31

The Steps in Data Collection


32

Data and Activity Modeling


33

Requirements Analysis

• Asking directly• Determining critical success factors (CSFs)• Developing the IS plan


34

The Systems Analysis Report

• The report should cover the following:

– The strengths and weaknesses of the existing system from a stakeholder’s perspective

– The user/stakeholder requirements for the new system (also called the functional requirements)

– The organizational requirements for the new system– A description of what the new information system

should do to solve the problem


35

Converting Organizational Goals into Systems Requirements


36

A Typical Table of Contents for aReport on an Existing System


37

Systems Design


38

Systems Design

• Logical design - involves planning the purpose of each system element.

• Physical design - refers to how the tasks are accomplished, including how the components work together and what each component does.


39

Request for Proposal

One of the most important documents generated during systems development.

• Results in a formal bid that is used to determine who gets a contract for new or modified systems.

• Specifies in detail required resources.


40

A Typical Table of Contents for a

Request for Proposal


41

Advantages and Disadvantages of Acquisition Options


42

Freezing Design Specifications


43

A Typical Table of Contents for a Systems Design Report


44

Systems Implementation


45

Typical Steps in Systems Implementation


46

Types of Testing


47

Start-up Approaches


48

Systems Maintenance and Review


49

Systems Maintenance

• Reasons for program maintenance include:

– Changes in business processes– New requests from stakeholders, users, and

managers– Bugs or errors in the program– Technical and hardware problems– Corporate mergers and acquisitions– Government regulations– Change in the operating system or hardware on which

the application runs– Unexpected events, like the terrorist attacks of

September


50

Examples of Review Types


51

Summary

• Systems development team - consists of stakeholders, users, managers, systems development specialists, and various support personnel.

• Five phases of the traditional SDLC - investigation, analysis, design, implementation, and maintenance and review.

• Systems investigation - designed to assess the feasibility of implementing solutions for business problems.


52

Summary

• Systems analysis - the examination of existing systems, which begins once approval for further study is received from management.

• Systems design – purpose is to prepare the detailed design needs for a new system or make modifications to an existing one.

• Systems implementation - to install a system and make everything, including users, ready for its operation.

• Systems maintenance - involves checking, changing, and enhancing the system to make it more useful in obtaining user and organizational goals.