ITM 362 Lecture - 2

2/23/2011
ITM 362; SYSTEMS ANALYSIS

AND DESIGN
LECTURE TWO
1. THE SYSTEM
DEVELOPMENT LIFE CYCLE
(SDLC).
Systems Analysis and Design Lecture Slides

by: Maxwell Dorgbefu Jnr.
Key Ideas
• An opportunity to create business value from
using information technology initiates a project.
• Feasibility analysis helps determine whether or
not to proceed with the IS project.
• Projects are selected based on business needs
and project risks.


by: Maxwell Dorgbefu Jnr. 1
2/23/2011
Key Ideas
• The project sponsor is a key person who
identifies business value to be gained from
using information technology.
• The approval committee reviews system
requests from groups throughout the
organization and selects projects for the benefit
of the business.

System Development Life Cycle(SDLC)
• The Systems Development Life Cycle (SDLC) is a

general term used to describe the method and
process of developing a new information system.
• Without the structure and organization provided
by SDLC approach, projects are at risk for missed
deadline, low quality etc.
• SDLC provides
– Structure
– Methods
– Controls
– Checklist
Needed for successful information system development.


2/23/2011
Why SDLC ?
• We need SDLC in Information Systems
development to:
– Facilitate project review
– Improve communication
– Provide a more efficient/effective system
– Guide the system development
– Improve management and control
– Ensure systems are within budget and meet
user/client’s taste.

SDLC Phases - 1
Sets of related activities are organized into phases:
1. Preliminary investigation
2. System Analysis
3. System Design
4. System Development
5. System Implementation and
6. System Support and Maintenance


2/23/2011
SDLC Phases - 1
1.
Preliminary
Investigation
Starting Point
4. System
Systems Analysis and Design Development
Lecture Slides by: Maxwell
Dorgbefu Jnr.
The Preliminary Investigation

• Determine if a new system is needed
• Three primary tasks:
– Define the problem
• By observation and interview, determine what
information is needed by whom, when, where
and why
– Suggest alternative solutions
– Prepare a short report


2/23/2011
Analysis Phase
Primary objective: to understand and document the
information needs and processing requirements of
the new system.
– Gather information (e.g. interview, read, observe etc.)
– Define system requirements (reports, diagrams etc.)
– Build prototypes for discovery of requirements
– Prioritize requirements
– Generate and evaluate alternative solutions
– Review recommendations with management

Analysis Phase
• Understand the existing system
– Gather data
– Analyze data
• Establish system requirements


2/23/2011
Analysis- Data Gathering

• Written documents
• Interviews
– Structured
– Unstructured
• Questionnaires
• Observation
– Visits by appointment
– Participant observation
• Sampling
Analysis-Analyze Data
• How the current system works
• Determine system requirements
• Basis for documentation
• Tools
– Data flow diagram (DFD)
– Decision tables


2/23/2011
Analysis – System Requirements
• Detailed list of things the system must be able

to do
• Design is based upon system requirements
• Agreement upon requirements is needed
before proceeding

Analysis – Report to Management
• Summarize problems
• Describe requirements
• Cost analysis
• Recommendations for next step
• Obtain authorization to proceed


2/23/2011
Design Phase
• Objective: to design the solution (not to

implement it though)
• The two sub phases of the design phase are:
–Preliminary design
–Detail design

Design Phase – Preliminary Design
Major system aspects

• Centralized or distributed
• Online or batch
• PC-based?
• How will input be captured?
• Necessary reports


2/23/2011

• Make or buy decision
• Packaged software
– Meet at least 75% of requirements?
– Change business procedures for part or all of
remainder?
– Customize for part of all of remainder?
• Custom software
– Programmers write code
• Outsourcing
– System is developed by external organization

• Build a prototype
– Limited working system of subset
• Does not need true functionality
– Output looks like anticipated system output
• Working model that can be modified and fine-
tuned
– Uses high-level software tools – CASE
– Best for small-scale systems


2/23/2011
Presentation
• All alternatives
• Selected plan
• Prototype of the system

Design Phase – Detail Design
Parts of detail design phase

• Output requirements
• Input requirements
• Files and databases
• Systems processing
• Systems controls and backup


2/23/2011
Output requirements Input requirements

• Medium • Medium
• Type of reports • Content
• Contents • Input forms
• Validation
• Volume

Files and Databases

– Organization
– Access
– Format of records
– Coordinate with database administrator
regarding external databases and updating


2/23/2011

Systems Controls and Backup
• Ensure that input is processed correctly
• Prevent fraud and tampering
• System journals
• Backup of system files

Report to Management
• Detailed design specifications report
• Presentation


2/23/2011
Development Phase
• Doing the work to bring the new system into

being
• This phase involves
– Scheduling
– Coding/Programming and
– Testing

Development Phase
• Programming
– Refine the design
– Converting detailed logic flowcharts and
pseudocode into programs
• Testing
– Unit testing
– System testing
– Volume testing


2/23/2011
Implementation Phase
• Information system is built, tested and installed
(actual programming of the information system)
• Activities
– Construct software components
– Verify and test
– Develop prototypes for tuning
– Convert data
– Train and document
– Install the system

Implementation - Conversion
• Direct/plunge/crash approach – entire new system
completely replaces entire old system, in one step
• Parallel approach - both systems are operated side by
side until the new system proves itself
• Pilot approach - launched new system for only one
group within the business -- once new system is
operating smoothly, implementation goes company-wide
• Phased/incremental approach - individual parts of
new system are gradually phased-in over time, using
either crash or parallel for each piece.

2/23/2011
Support and Maintenance Phase

• Objective is to keep the information system running after
its installation.
• Maintain system
– Small patches, repairs, and updates
• Enhance system
– Small upgrades or enhancements to expand system
capabilities
– Larger enhancements may require separate
development project
• Support users
– Help desk and/or support team
Questions & Comments ???.....
End of Lecture !!!
See you next week.



ITM 362 Lecture - 2

Enviado por

Dados do documento

Descrição original:

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

ITM 362 Lecture - 2

Enviado por

Direitos autorais:

Formatos disponíveis

2/23/2011

ITM 362; SYSTEMS ANALYSIS

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

System Development Life Cycle(SDLC)

• The Systems Development Life Cycle (SDLC) is a

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

The Preliminary Investigation

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Analysis- Data Gathering

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Analysis – System Requirements

• Detailed list of things the system must be able

Systems Analysis and Design Lecture Slides

Analysis – Report to Management

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

• Objective: to design the solution (not to

Systems Analysis and Design Lecture Slides

Design Phase – Preliminary Design

Major system aspects

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Design Phase – Preliminary Design

Systems Analysis and Design Lecture Slides

Design Phase – Preliminary Design

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Design Phase – Preliminary Design

Systems Analysis and Design Lecture Slides

Design Phase – Detail Design

Parts of detail design phase

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Design Phase – Detail Design

Output requirements Input requirements

Systems Analysis and Design Lecture Slides

Design Phase – Detail Design

Files and Databases

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Design Phase – Detail Design

Systems Analysis and Design Lecture Slides

Design Phase – Detail Design

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

• Doing the work to bring the new system into

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides

Systems Analysis and Design Lecture Slides