SYSTEMS ANALYSIS AND DESIGN

What is System?

A set of detailed methods, procedures and routines established or formulation

to carry out specify activity, to perform a duty or solve a problem.

What is System Analysis?

The dissection of a system into its component pieces to study how those
component pieces interact and work:
1. The survey and planning
2. The study and analysis
3. The definition

Systems analysis is a problem solving technique that decomposes a system into its component
pieces for the purpose of the studying how well those component parts work and interact to
accomplish their purpose.

What is Analysis?

Analysis is performed on a small part of the system followed by design and implementation.
The development cycle repeats with analysis, design and implementation of the next part and this
repeats until the project is complete.

What is System Design? Create a diagram(flowchart), modelling…

etc.
The process of defining the architecture, components, modules, interfaces and data for a system to
satisfy specified requirements.
Systems Analysis and Design is an interdisciplinary part of science, which can be related to:
 Systems analysis
 Systems design

Systems analysis is a problem solving technique that decomposes a system into its component
pieces for the purpose of the studying how well those component parts work and interact to
accomplish their purpose.

Systems design is the process of studying a procedure or business in order to identify its goals and
purposes and create systems and procedures that will achieve them in an efficient way.
Analysis and synthesis, as scientific methods, always go hand in hand; they complement one
another. Every synthesis is built upon the results of a preceding analysis, and every analysis requires
a subsequent synthesis in order to verify and correct its results.

This field isclosely related to requirements analysis or operations research. It is also "an explicit
formal inquiry carried out to help someone (referred to as the decision maker)identify a better
course of action and make a better decision than she might otherwise have made.

What is Systems Analyst?

A systems analyst is an IT professional who specializes in analyzing, designing and

implementing information systems. Systems analysts assess the suitability of information systems in
terms of their intended outcomes and liaise with end users, software vendors and programmers in
order to achieve these outcomes. A systems analyst is aperson who uses analysis and design
techniquestosolve business problems using information technology.
Systems analysts may serve as change agents who identify the organizational improvements
needed, design systems to implement those changes, and train and motivate others to use the
systems.

Although they may be familiar with a variety of programming languages, operating systems,
and computer hardware platforms, they do not normally involve themselves in the actual hardware or
software development. They may be responsible for developing cost analysis, design considerations,
staff impact amelioration, and implementation timelines.
A systems analyst is typically confined to an assigned or given system and will often work in
conjunction with a business analyst. These roles, although having some overlap, are not the same.
A business analyst will evaluate the business need and identify the appropriate solution and, to some
degree, design a solution without diving too deep into its technical components, relying instead on a
systems analyst to do so. A systems analyst will often evaluate code, review scripting and, possibly,
even modify such to some extent.

Some dedicated professionals possess practical knowledge in both areas (business and systems
analysis) and manage to successfully combine both of these occupations, effectively blending the line
between business analyst and systems analyst.

Systems
Analyst

Systems Analyst as “Facilitator”

 System Architecture

Information Systems Analysis and Design-Development LifeCycle== Businesses and

organizations use various types of information systems to support the many processes needed to
carry out their business functions. Each of these information systems has a particular purpose or
focus, and each has a life of its own. This “life of its own” concept is called the Systems
Development Life Cycle or SDLC, and it includes the entire process of planning, building, deploying,
using, updating, and maintaining an information system. The development of a new information
system involves several different, but related activities.

SDLC
Life Cycle Stages: Planning Analysis Design Implementation

What How
Problems/Opportunities Solutions
Requirements Specifications
Soft/People Skills Technical Skills

Visibility: Deliverables/Documentation
Methodology*
 Process (Life Cycle)
 Techniques(Modeling) Use modelling
techniques

Data Process
* A system development methodology is a
framework that is used to structure, plan, and UI
control the process of developing an
information system. Prototyping
UI: User Interface Coding
Programming
Implementation
 Structured Project SDLC

Requirements
Analysis Design
Data or Manual
Refined project scope
Cost/Benefit Analysis Design
Specifications
 Users Participation
Planning  Documentation
Preliminary  Modeling Techniques Implementation
Approved Study  CASE/IDE Tools *
Project  Quality Assurance
Proposal
Approved Implemented System
Re-development
Project Proposal Database or
Integrated & Program
Tested System Programming, Structure
Operation &
Maintenance Testing,Training,
Integration, &Installation

* CASE: Computer-Aided Software Engineering(Analysis & Design)

IDE: Integrated Development Environment(Implementation)

SDLC WATERFALL MODEL

Identify & prioritize IS

Planning development projects

Requirements
Analysis AS IS vs TO BE

Logical & physical

Design Design specification

 Programming
Implementation  Testing
 Training
 Installation

Operation
Bug fix & Upgrades,
IT Service Mgt

The procedural checklist and the systematic progression required to evolve an IT. The following
descriptions of the SDLC:

1. Conceptual Planning. This phase is the first step of any system's life cycle. It is during this phase
that a need to acquire or significantly enhance a system is identified, its feasibility and costs are
assessed, and the risks and various project-planning approaches are defined. Roles and
responsibilities for the Asset Manager, Sponsor's Representative, System Development Agent (SDA),
System Support Agent (SSA), and other parties in SDLC policy are designated during this stage and
updated throughout the system's life cycle.
2. Planning and Requirements Definition. This phase begins after the project has been defined
and appropriate resources have been committed. The first portion of this phase involves collecting,
defining and validating functional, support and training requirements. The second part is developing
initial life cycle management plans, including project planning, project management, Configuration
Management (CM), support, operations, and training management.
3.Design. During this phase, functional, support and training requirements are translated into
preliminary and detailed designs. Decisions are made to address how the system will meet functional
requirements. A preliminary (general) system design, emphasizing the functional features of the
system, is produced as a high-level guide. Then a final (detailed) system design is produced that
expands the design by specifying all the technical detail needed to develop the system.
Development and Testing. During this phase, systems are developed or acquired based on detailed
design specifications. The system is validated through a sequence of unit, integration, performance,
system, and acceptance testing. The objective is to ensure that the system functions as expected and
that sponsor's requirements are satisfied. All system components, communications, applications,
procedures, and associated documentation are enveloped/acquired, tested, and integrated. This
phase requires strong user participation in order to verify thorough testing of all requirements and to
meet all business needs.

4. Implementation. During this phase, the new or enhanced system is installed in the production
environment, users are trained, data is converted (as needed), the system is turned over to the
sponsor, and business processes are evaluated. This phase includes efforts required to implement,
resolve system problems identified during the implementation process, and plan for sustainment.
5. Operations and Maintenance. The system becomes operational during this phase. The emphasis
during this phase is to ensure that sponsor needs continue to be met and that the system continues
to perform according to specifications. Routine hardware and software maintenance and upgrades
are performed to ensure effective system operations. User training continues during this phase, as
needed, to acquaint new users to the system or to introduce new features to current users. Additional
user support is provided, as an ongoing activity, to help resolve reported problems.

The End