Scribd
Upload
0 views

Information Systems Development

Uploaded by

chantellemajuru04
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
0 views

Information Systems Development

Uploaded by

chantellemajuru04
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PPTX, PDF, TXT or read online on Scribd
You are on page 1/ 16

Information Systems

Development

1
Information Systems Development Concepts
To ensure the success of information systems development, a systematic process is
used:
► Software development life cycle (SDLC):
► Set of activities and their relationships to each other to support the development of a
software system
► Software development methodology:
► A collection of techniques for building models applied across the software life cycle
► Guidelines on how to use technology and accomplish software development activities.
Tow broad classes exist: -

I/ Traditional Methods: Heavyweight processes associated with documentation at each stage


of the lifecycle; Characterized by upfront elicitation and documentation of a “complete” set
of requirements, followed by architectural and high-level design, development, and
inspection.

II/ Agile Methods : Lightweight methods that share the same principles stipulated in the Agile
manifesto stated as, we value “ individuals and interaction over processes and tools,
working software over comprehensive documentation, customer collaboration
2 over contract
negotiation, and responding to changes over following a plan”
SDLC Phases

Preliminary
Investigatio
n

System
System Operation Analysis
& Maintenance

System System
Implementation
n
Design

System
Development 3
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

4
Systems Analysis
► In depth study of the existing system to determine what
the new system should do.
► Expand on data gathered in Phase 1
► In addition to observation and interviews, examine:
► Formal lines of authority (org chart)
► Standard operating procedures
► How information flows
► Reasons for any inefficiencies
► Provide cost-benefit analyses of alternatives; and make
recommendations on what (if anything) should be done.
5
System Analysis ct’d

► Documentation Produced :-
► Complete description of current system
and its problems
► Requirements for new system including:
► Subject
► Scope
► Objectives
► Benefits
► Possible development schedule
6
System Design

► Uses specifications from the systems analysis


to design alternative systems
► Evaluate alternatives based upon:
► Economic feasibility - Do benefits justify costs?
► Technical feasibility - Is reliable technology and
training available?
► Operational feasibility - Will the managers and
users support it?
7
System Design - Tools Used
► Computer-Aided Software Engineering (CASE) tools are
software-based products designed to help automate the
production of information systems.
► Examples:
► Diagramming Tools
► Data Repositories
► Prototyping Tools
► Test Data Generators
► Documentation Tools
► Project Management Tools
► Check StarUML, LucidChartArgoUML, Edraw Max, Project Libre
8
System Design - Documentation
► System Design Report
► Describe Alternatives including:
► Inputs/Outputs
► Processing
► Storage and Backup
► Recommend Top Alternative based upon:
► System Fit into the Organization
► Flexibility for the future
► Costs vs. benefits

9
System Development
► Build the system to the design specifications
► Develop the software
►Purchase off-the-shelf software And/ Or
►Write custom software
► Acquire the hardware
► Test the new system
►Module (unit) test - tests each part of system
►Integration testing - tests system as one unit
►System testing
► Create manuals for users and operators

10
System Implementation

► Convert from old system to new system


► Train users
► Compile final documentation
► Evaluate the new system

11
System Implementation –
Conversion methods

► 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.
12
System Implementation

► User Training:-
►Ease into system, make them
comfortable, and gain their
support
►Most commonly overlooked
►Can be commenced before
equipment delivery
►Outside trainers sometimes used
13
Operations & Maintenance
► Types of changes:
► Physical repair of the system components
► Correction of new bugs found (corrective)
► System adjustments to environmental changes
► Adjustments for users’ changing needs
(adaptive)
► Changes to use better techniques when they
become available (perfective)

14
Operations & Maintenance
► Evaluation Methods
► Systems audit - performance compared to
original specifications
► Periodic evaluation - “checkups” from time to
time, modifications if necessary

15
Exercise
Working in pairs, locate authentic documents discussing the differences
between traditional information systems development and agile
information systems development. Tabulate any five differences between
these two.

16

You might also like