SYSTEMS ANALYSIS

DESIGN AND
DEVELOPMENT CONCEPT
Task: Build a Simple Accounting Software
• You've been offered to build a very basic
accounting software for Falcons Bank Inc.

You'll need to collaborate with 3-4 other

developers.
You'll receive big amount of cash for full
functional software.
Deadline: very, very strict. Say, couple of
months?
 What are you going to do?
• Divide the total project in visible sections,
say:
-User Accounts
-Human Resource
-Etc…
• And started to ask questions to your clients
how they want the program behave, design
database...
• All four developers started coding as fast
as you can to meet deadline.
After some days… you felt like integrating
your works?
• But you figured out you need a change in some
part, you could change it, but others code can
break.
• You hardly understand what your friend means by
variable baln or function register()
• Your disc crashed and your codes are gone?
• You’ve created too many folders like code_old,
code_new, colde_newest, code_latest,
code_final… now what?
• How do you merge everybody’s code to a full
functional system?
 Messed Up?
• Without putting your code in a function, you just
wrote it down, thinking, “Hey, I’ll not use this code
anywhere else! So Why do I need to put it in a
function or class?”
• But, you never know…
- Client may change his mind
- New functionalities may appear in future
- And you’re very likely to duplicate same codes
- Man is mortal. To fix buggy codes you’ll need to
investigate your whole project number of times
you copy pasted same code.
- Hard to find bugs 
 Software Evolves….
• If your software is usable, it will have
changes in it and have future releases.

• Clients will add new fetures or users will

want changes
After some days, you're about to bring some
changes in your code.
And. . .

You don't understand

your own codes 
If you don’t practice standards, It’ll
be very very difficult to maintain
the project later.

So what are
best practices?
 Systems Development Life Cycle
• System Development Methodology
• Standard process followed in an organization
• Consists of:
• Analysis
• Design
• Implementation
• Maintenance
 System Analysis and Design:
What is it?
System
• A set of detailed methods, procedures and
routines established or formulation to carry out
specific activity, perform a duty or solve a
problem.

System Analysis
• The dissection of a system into its component
pieces to study how those component pieces
interact and work.
• The survey and planning
• The study and analysis
• The definition
 System Analysis and Design:
What is it?
System Design
• The process of defining the architecture,
components, modules, interfaces and data for a
system to satisfy specified requirements.

• Systems Analyst performs analysis and design

based upon:
• Understanding of organization’s objectives, structure
and processes
• Knowledge of how to exploit information technology
for advantage
 Systems Analysis and Design:
Core Concepts
• Major goal: to improve organizational systems by
developing or acquiring software and training
employees in its use
• Application software, or a system, supports
organizational functions or processes
• System: Turns data into information and includes:
• Hardware and system software
• Documentation and training materials
• Job roles associated with the system
• Controls to prevent theft or fraud
• The people who use the software to perform their jobs
Components of Computer-Based Information System
Application
 The Systems Development Life Cycle
(SDLC)
• Is a process used to design, develop and test high quality
software. The SDLC should ensure that we can produce
more function, with higher quality, in less time, with less
resources and in a predictable manner.
 The Systems Development Life Cycle
(SDLC)
SDLC is composed of five fundamental phases:
‒ Planning
‒ Analysis
‒ Design
‒ Implementation
‒ Maintenance
• Phases are not necessarily sequential
• Each phase has a specific outcome and
deliverable
Planning
• During this phase, the group that is
responsible for creating the system must first
determine what the system needs to do for the
organization.
• This phase is the fundamental process of
understanding why an information system
should be built.
• The Planning phase will also determine how
the project team will go about building the
information system.
Planning
The project planning phase activities:
Define the problem.
Investigate and identify scope of the new system
ensure that project is feasible,
Produce the project schedule.
Staff the project.
allocate resources
Investigate and identify scope of the new system
Launch the project.
Perform other project planning tasks
Analysis
• The analysis phase answers the questions of who
will use the system, what the system will do, and
where and when it will be used.
• During this phase the project team investigates
any current system(s), identifies improvement
opportunities, and develops a concept for
the new system.
• To analyze the business situation (business
needs) thoroughly to determine requirements, to
structure the requirements and select competing
system features.
Analysis
The analysis phase activities:
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
Prepare and present the system proposal
Design
• it involves the actual creation and design of a
system.
• This involves putting together the different pieces
that will create the system.
• It decides how the system will operate, in terms of
the hardware, software, and network
infrastructure; the user interface, forms, and
reports that will be used; and the programs,
databases, and files that will be needed.
Design
The design phase activities:
Architecture Design
This describes the hardware, software, and network infrastructure that
will be used
Database and File Specifications
These documents define what and where the data willbe stored.
Program Design
Defines what programs need to be written and what they will do
Design and integrate the network
Design the user interfaces
Design the system interfaces
Design and integrate the database
Design and integrate the system controls
Implementation
• Ensure that System is built, tested and installed it involves
the actual programming / construction of a system.
System Construction:
• The system is built and tested to make sure it performs as
designed.
Installation:
• Prepare to support the installed system.
Support Plan:
• Includes a post-implementation review
Implementation
The implementation phase activities:
Construct software components
Verify
Testing
Coding
Debugging
Develop prototypes for tuning
Convert data
Train and document
Install the system
Maintenance
Maintaining and enhancing an information system so
that it continues to meet the needs of the business.
• The database administrator must be prepared to
perform routine maintenance activities within the
database. Some of the required periodic
maintenance activities.
• Keep the system running after its installation.

• Maintenance is performed for two reasons:

• Removing software errors
• Enhancing existing software
Maintenance
The support phase activities:
Provide support to end users
Help desks
Training programs
Maintain and enhance the computer system
Simple program error correction
Comprehensive enhancements
Upgrades
WHERE DO INFORMATION SYSTEMS ANALYSIS
AND DESIGN PROJECTS COME FROM?
• New or changed information systems development projects come
from problems, opportunities, and directives and are always subject to
one or more constraints.

•Problems, often called bugs, can arise at any time during the life of an
information system. There is no such thing as a problem-free or bug-
free information system.
•Opportunities are the most preferred way to kickoff an information
systems development project. This means that the business is hoping
to create a system that will help it with increasing its revenue, profit, or
services, or decreasing its costs.
•Directives are mandates that come from either an internal or an
external source of the business
•Constraints are limitations and compromises that come with the soon
to be developed information system.
PRINCIPLES TO GUIDE INFORMATION
SYSTEMS ANALYSIS AND DESIGN
Over the last three decades a number of systems
analysis and design principles have been presented.
Although not exhaustive, the list includes:
1. The system is for the user (it is not ours; we do not
own the system just because we developed it)
2. A work breakdown structure such as a SDLC should
be established for all information systems
development projects
3. Information systems development is NOT a
sequential process; it allows for activity overlap,
revisiting, inclusion/exclusion, and so on.
PRINCIPLES TO GUIDE INFORMATION
SYSTEMS ANALYSIS AND DESIGN
4. Information systems are capital investments for
the business
5.Tthe project manager should not be afraid to
cancel a project if its success is seriously
challenged
6. Documentation (manual and/or electronic) is a
deliverable product during each activity of the
SDLC
7. Senior management support for the
development project