Overview of System analysis and Design

Contents:

Introduction to system analysis and design

Types of Information Systems(Transaction Processing system,
Management Information System, Decision Support System and
Expert System)
Systems Development Life cycle(SDLC)
Systems analysis and design tools :Prototyping, Joint Application
Design, CASE Tools, RAD
System Analyst-Introduction,Role,Skills

Introduction: Important Terms

Data:
Data is raw unprocessed facts and figures that have no context or purposeful
meaning.
Data are raw facts about the organization and its business transactions. Most data
items have little meaning and use by themselves.
Information:
Information is processed data that has meaning and a context System and
Information System.
Information is data that has been refined and organized by processing and
purposeful intelligence. The latter, purposeful intelligence is crucial to the definition
People provide the purpose and the intelligence that produces true information.

Fig: Data and Information

System and Information System:
A system is a set of related components that produces specific results.
A system is an interrelated set of business procedures used within one
business unit working together for a purpose
A system exists within an environment
A boundary separates a system from its environment
A system has nine characteristics which are as follows:
1. Components
2. Interrelated Components
Compiled by: Hiranya Prasad Bastakoti

Page 1

3.
4.
5.
6.
7.
8.
9.

Boundary
Purpose
Environment
Interfaces
Input
Output
Constraints

An information system (IS) is an arrangement of people, data, processes,

communications, and information technology that interact to support and improve
day-to-day operations in a business, as well as support the problem-solving and
decision-making needs of management and users.
The Components of an Information System:
Input: activity of gathering and capturing raw data
Processing: converting or transforming data into useful outputs
Output: production of useful information, usually in form of documents and reports
Feedback: output used to make changes to input or processing activities

Compiled by: Hiranya Prasad Bastakoti

Page 2

Fig: Information System

Information Technology:
Information technology is a contemporary term that describes the combination of
computer technology (hardware and software) with telecommunications technology
(data, image, and voice networks).
Systems analysis
Systems analysis is a problem-solving technique that decomposes a system into its
component pieces f or the purpose of studying how well those component parts
work and interact to accomplish their purpose.
Information technology is a contemporary term that describes the combination of
computer technology (hardware and software) with telecommunications technology
(data, image, and voice networks).
Information systems analysis:
Information systems analysis is defined as those development phases in a project
that primarily focus on the business problem, independent of any technology that
can or will be used to implement a solution to that problem.

System analysis and Design:

Systems analysis and design is a step-by-step process for developing
high-quality information systems. An information system combines
information technology, people, and data to support business requirements.
For example, information systems handle daily business transactions,
improve company productivity, and help managers make sound decisions .
Types of Information Systems

Management Information Systems (MIS) Tactical

Compiled by: Hiranya Prasad Bastakoti

Page 3

 A management information system (MIS) is an information system application

that provides for management-oriented reporting. These reports are usually
generated on a predetermined schedule and appear in a prearranged format
MIS convert data from internal and external sources into information for
managers.
The source of data for an MIS usually comes from numerous databases.
These databases are usually the data storage for Data Processing Systems.
MIS summarise and report on the organisations basic operations.
MIS produce reports for managers interested in historic trends on a regular
basis.
o

MIS operate at the tactical level

Decision Support Systems (DSS) Tactical

DSS provide information and models in a form to help tactical and
strategic decision-making.
They support management decision-making by integrating:
Company performance data
Business rules in a decision table
Analytical tools and models for forecasting and planning
A simple user interface to query the system.
DSS are useful when making ad-hoc, one-off decisions.
The sources of data for DSS tend to be a combination of summary
information gathered from lower-level DPS and MIS.
OR

A decision support system (DSS) is an information system application that

provides its users with decision-oriented information whenever a decisionmaking situation arises. When applied to executive managers, these systems are
sometimes called executive information systems (EIS).

A Decision Support System (DSS) is an interactive computer-based system

or subsystem intended to help decision makers use communications
technologies, data, documents, knowledge and/or models to identify and
solve problems, complete decision process tasks, and make decisions.

Compiled by: Hiranya Prasad Bastakoti

Page 4

Decision Support System is a general term for any computer application

that enhances a person or groups ability to make decisions.
Also, Decision Support Systems refers to an academic field of research
that involves designing and studying Decision Support Systems in their
context of
Use

Decision Support Systems (DSS) help executives make better decisions

by using historical and current data from internal Information Systems and
external sources. By combining massive amounts of data with sophisticated
analytical models and tools, and by making the system easy to use, they
provide a much better source of information to use in the decision-making
process.
Example: a what-if analysis to determine where to spend advertising dollars

Executive Information System (EIS) - Strategic

EIS provide senior managers with systems to assist in taking strategic and
tactical decisions.

Purpose to analyse, compare and identify trends to help the strategic

direction of the organisation.
EIS incorporate data about external events. They:
draw summarised information from internal MIS and DSS.
filter, compress, and track critical data.
reduce time and effort required to obtain information useful to strategic
management.
employ advanced graphics software to provide highly visual and easy-to-use
representations of complex information and current trends.
do not provide analytical models.
EIS allow the user to look at specific data that has been summarised from
lower levels within the organisation and then drill down to increase the level
of detail - data warehouse analysis
Expert System:
An expert system is a computer program that tries to emulate human
reasoning. It does this by combining the knowledge of human experts and
then, following a set of rules, draws inferences.

Compiled by: Hiranya Prasad Bastakoti

Page 5

 An expert system is made up of three parts:

o

A knowledge base stores all of the facts, rules and information

needed to represent the knowledge of the expert.

An inference engine interprets the rules and facts to find solutions to

user queries.

A user interface allows new knowledge to be entered and the system

queried.

Expert systems are used for the following purposes:

o

To store information in an active form as organisational memory.

To create a mechanism that is not subject to human feelings, such as

fatigue and worry.

To generate solutions to specific problems that are too substantial and

complex to be analysed by human beings in a short period of time.

Transactional Processing System:

Transaction processing systems are information system applications that capture
and process data about business transactions.

Includes data maintenance, which provides for custodial updates to

stored data.
Business process redesign (BPR) is the study, analysis, and redesign of
fundamental business (transaction) processes to reduce costs and/or
improve value added to the business
Examples: sales processing, inventory systems, accounting systems
Office automation systems
Office automation (OA) systems support the wide range of business office
activities that provide for improved work flow and communications between
workers, regardless of whether or not those workers are located in the same
office.

Personal information systems are those designed to meet the needs of

a single user. They are designed to boost an individuals productivity.
Work group information systems are those designed to meet the
needs of a work group. They are designed to boost the groups
productivity.

Compiled by: Hiranya Prasad Bastakoti

Page 6

Systems Development Life Cycle (SDLC):

A Series of steps used to manage the phases of development for an
information system
System development life cycle is an organizational process of developing
and maintaining systems. It helps in establishing a system project plan,
because it gives overall list of processes and sub-processes required
developing a system.
OR

Systems Development Life Cycle (SDLC) represents a set of general

categories that show the major steps, over time, of an information systems
development project.

It provides a comprehensive formal framework for designing and developing

systems for the effective and efficient processing of information.

There is no universal, standardized version of the SDLC, but the phrase has
two distinct meanings.
An SDLC can be a general conceptual framework for all the activities
involved in systems development or acquisition.

Compiled by: Hiranya Prasad Bastakoti

Page 7

 An SDLC can also be a very structured and formalized design and

development process.
The systems development life cycle (SDLC) is a conceptual model used in project
management that describes the stages involved in an information system
development project, from an initial feasibility study through maintenance of the
completed application.
Various SDLC methodologies have been developed to guide the processes involved,
including the Waterfall model (which was the original SDLC method), Rapid
Application Development (RAD), Joint Application development (JAD),Spiral
Model and so on.
SDLC Stages:

Phase 1: Systems Planning and Selection

The first phase of the SDLC in which an organizations total information
system needs are analyzed and arranged, and in which a potential
information systems project is identified and an argument for continuing
or not continuing with the project is presented.
The first phase in the SDLC, systems planning and selection has two primary
activities. First, someone identifies the need for a new or enhanced system.
Information needs of the organization are examined, and projects to meet these
needs are identified. The organizations information system needs may result from:
Requests to deal with problems in current procedures
The desire to perform additional tasks
The realization that information technology could be used to capitalize on an
existing opportunity
Compiled by: Hiranya Prasad Bastakoti

Page 8

The systems analyst prioritizes and translates the needs into a written plan for the
IS department, including a schedule for developing new major systems.
Requests for new systems spring from users who need new or enhanced systems.
During the systems planning and selection phase, an organization determines
whether resources should be devoted to the development or enhancement of each
information system under consideration. A feasibility study is conducted before the
second phase of the SDLC to determine the economic and organizational impact of
the system.
The second task in the systems planning and selection phase is to investigate the
system and determine the proposed systems scope. The team of systems analysts
then produces a specific plan for the proposed project for the team to follow. This
baseline project plan customizes the standardized SDLC and specifies the time and
resources needed for its execution. The formal definition of a project is based on the
likelihood that the organizations IS department is able to develop a system that will
solve the problem or exploit the opportunity and determine whether the costs of
developing the system outweigh the possible benefits. The final presentation to the
organizations management of the plan for proceeding with the subsequent project
phases is usually made by the project leader and other team members.
Phase 2: Systems Analysis
Phase of the SDLC in which the current system is studied and alternative
replacement systems are proposed.
The second phase of the systems development life cycle is systems analysis. During
this phase, the analyst thoroughly studies the organizations current procedures and
the information systems used to perform tasks such as general ledger, shipping,
order entry, machine scheduling, and payroll. Analysis has several subphases. The
first sub phase involves determining the requirements of the system. In this
subphase, you and other analysts work with users to determine what the users want
from a proposed system. This subphase involves a careful study of any current
systems, manual and computerized, that might be replaced or enhanced as part of
this project. Next, you study the requirements and structure them according to their
interrelationships, eliminating any redundancies. As part of structuring, you
generate alternative initial designs to match the requirements. Then you compare
these alternatives to determine which best meets the requirements within the cost,
labor, and technical levels the organization is willing to commit to the development
process.
The output of the analysis phase is a description of the alternative solution
recommended by the analysis team. Once the recommendation is accepted by the
organization, you can make plans to acquire any hardware and system software
necessary to build or operate the system as proposed.

Compiled by: Hiranya Prasad Bastakoti

Page 9

Phase 3: Systems Design

Phase of the SDLC in which the system chosen for development in
systems analysis is first described independently of any computer
platform (logical design) and is then transformed into technology-specific
details (physical design) from which all programming and system
construction can be accomplished.
The third phase of the SDLC is called systems design. During systems design,
analysts convert the description of the recommended alternative solution into
logical and then physical system specifications. You must design all aspects of the
system from input and output screens to reports, databases, and computer
processes. Logical design is not tied to any specific hardware and systems software
platform. Theoretically, the system you design could be implemented on any
hardware and systems software. Logical design concentrates on the business
aspects of the system; that is, how the system will impact the functional units within
the organization. Figure 1-12 shows both the logical design for a product and its
physical design, side by side, for comparison. You can see from
the comparison that many specific decisions had to be made to move from the
logical model to the physical product. The situation is similar in information systems
design.
In physical design, you turn the logical design into physical, or technical,
specifications. For example, you must convert diagrams that map the origin, flow,
and processing of data in a system into a structured systems design that can then
be broken down into smaller and smaller units for conversion to instructions written
in a programming language. You design the various parts of the system to perform
the physical operations necessary to facilitate data capture, processing, and
information output. During physical design, the analyst team decides which
programming languages the computer instructions will be written in, which
database systems and file structures will be used for the data, and which hardware
platform, operating system, and network environment the system will run under.
These decisions finalize the hardware and software plans initiated at the end of the
analysis phase. Now you can acquire any new technology not already present in the
organization. The final product of the design phase is the physical system
specifications, presented in a form, such as a diagram or written report, ready to be
turned over to programmers and other system builders for construction.
Phase 4: Systems Implementation and Operation
Final phase of the SDLC in which the information system is coded, tested,
and installed in the organization, and in which the information system is
systematically repaired and improved.

Compiled by: Hiranya Prasad Bastakoti

Page 10

The final phase of the SDLC is a two-step process: systems implementation and
operation. During systems implementation and operation, you turn system
specifications into a working system that is tested and then put into use.
Implementation includes coding, testing, and installation. During coding,
Programmers write the programs that make up the system. During testing,
programmers and analysts test individual programs and the entire system in order
to find and correct errors. During installation, the new system becomes a part of the
daily activities of the organization. Application software is installed, or loaded, on
existing or new hardware; then users are introduced to the new system and trained.
Begin planning for both testing and installation as early as the project planning and
selection phase, because they both require extensive analysis in order to develop
exactly the right approach.
Systems implementation activities also include initial user support such as the
finalization of documentation, training programs, and ongoing user assistance. Note
that documentation and training programs are finalized during implementation;
documentation is produced throughout the life cycle, and training (and education)
occurs from the inception of a project. Systems implementation can continue for as
long as the system exists because ongoing user support is also part of
implementation. Despite the best efforts of analysts, managers, and programmers,
however, installation is not always a simple process. Many well-designed systems
have failed because the installation process was faulty. Note that even a welldesigned system can fail if implementation is not well managed. Because the
management of systems implementation is usually done by the project team.
Products of the SDLC Phases
Phases

Products, Outputs, or Deliverables

Systems planning and

selection

Systems Analysis

System Design
Systems
Implementation

Priorities for systems and projects

Architecture for data, networks, hardware, and IS
management
Detailed work plan for selected project
Specification of system scope
System justification or business case
Description of current system
General recommendation on how to fix, enhance,
or replace current system
Explanation
of
alternative
systems
and
justification for chosen alternative

Detailed specifications of all system elements

Acquisition plan for new technology

Code

and

Compiled by: Hiranya Prasad Bastakoti

Page 11

Operation

Documentation
Training procedures and support capabilities
New versions or releases of software with
associated updates to documentation, training,
and support

Approaches to Development
Prototyping, computer-aided software engineering (CASE) tools, joint application
design (JAD), rapid application development (RAD), participatory design (PD), and
the use of Agile Methodologies represent different approaches that streamline and
improve the systems analysis and design process from different perspectives.

Prototyping:

Designing and building a scaled-down but working version of a desired system is

known as prototyping. A prototype can be developed with a computer-aided
software engineering (CASE) tool, a software product that automates steps in the
systems development life cycle. CASE tools make prototyping easier and more
creative by supporting the design of screens and reports and other parts of a
system interface. CASE tools also support many of the diagramming techniques you
will learn, such as data-flow diagrams and entity-relationship diagrams.

Compiled by: Hiranya Prasad Bastakoti

Page 12

Figure illustrates prototyping. The analyst works with users to determine the initial
or basic requirements for the system. The analyst then quickly builds a prototype.
When the prototype is completed, the users work with it and tell the analyst what
they like and do not like about it. The analyst uses this feedback to improve the
prototype and takes the new version back to the
users. This iterative process continues until the users are relatively satisfied with
what they have seen. The key advantages of the prototyping technique are (1) it
involves the user in analysis and design, and (2) it captures requirements in
concrete, rather than verbal or abstract, form. In addition to being used as a standalone, prototyping may also be used to augment the SDLC.
For example, a prototype of the final system may be developed early in analysis to
help the analysts identify what users want. Then the final system is developed
based on the specifications of the prototype.

Computer-Assisted Software Engineering (CASE) Tools

Computer-aided software engineering (CASE) refers to automated software
tools used by systems analysts to develop information systems. These tools can be
used to automate or support activities throughout the systems development
process with the objective of increasing productivity and improving the overall
quality of systems. CASE helps provide an engineering-type discipline to software
development and to the automation of the entire software life-cycle process,
sometimes with a single family of integrated software tools. In general, CASE assists
systems builders in managing the complexities of information system projects and
helps assure that high-quality systems are constructed on time and within budget.
Automated software tools used by systems analysts to develop
information systems
Used to support or automate activities throughout the systems
development life cycle (SDLC)
Increase productivity
Improve overall quality of systems
Majority of organizations adopt CASE to improve speed and quality of
systems development projects
Purpose of CASE is to facilitate a single design philosophy within an
organization with many projects, systems, and people.
CASE tools runs on variety of mini and mainframe systems.
Objectives of CASE
Improve quality of systems developed
Increase speed of development and design

Compiled by: Hiranya Prasad Bastakoti

Page 13

Ease and improve testing process through automated checking

Improve quality and completeness of documentation
Help standardize the development process
Improve project management
Simplify program maintenance
Promote reusability of modules and documentation

Computer-aided software engineering (CASE) tools are software programs that

automate or support the drawing and analysis of system models and provide for the
translation of system models into application programs. Some CASE tools also
provide prototyping and code generation capabilities.
A CASE repository is a system developers database. It is a place where
developers can store system models, detailed descriptions and specifications, and
other products of system development. Synonyms include dictionary and
encyclopedia.
CASE Facilities: To use the repository, the CASE tools provide some combination of
the following facilities.

Diagramming tools: are use to draw the system models required or

recommended in most system development methodologies. Usually,
the shapes on one system model can be linked to other models and to
detailed descriptions.
Dictionary tools: are used to record, delete, edit, and output detailed
documentation and specifications. The descriptions can be associated
with shapes appearing on system models that were drawn with
diagramming tools.
Design tools: can be used to develop system components such as
inputs and outputs.
Quality management tools: analyze system models, descriptions
and specifications, and designs for completeness, consistency, and
conformance to accepted rules of the methodologies.
Documentation tools: are used to assemble, organize, and report on
system models, descriptions and specifications, and prototype that can
be reviewed by system owners, users, designers, and builders.
Design and code generator tools: automatically generate database
designs and application programs or significant portions of those
programs.

Forward engineering requires the systems analyst to draw system models, either
from scratch or from templates. The resulting models are subsequently transformed
into program code

Compiled by: Hiranya Prasad Bastakoti

Page 14

Reverse engineering allows a CASE tool to read existing program code and
transform that code into a representative system model that can be edited and
refined by the systems analyst.

Fig: CASE Tool

Joint Application Design

In the late 1970s, systems development personnel at IBM developed a new process
for collecting information system requirements and reviewing system designs. The
process is called Joint Application Design (JAD). The idea behind JAD is to
structure the requirements determination phase of analysis and the reviews that
occur as part of the design. Users, managers, and systems developers are brought
together for a series of intensive structured meetings run by a JAD session leader.
By gathering the people directly affected by an IS in one room at the same time to
work together to agree on system requirements and design details, time and
organizational resources are better managed. Group members are more likely to
develop a shared understanding of what the IS is supposed to do. JAD has become
common in certain industries, such as insurance, and in specific companies.
Advantages:
Compiled by: Hiranya Prasad Bastakoti

Page 15

Saves time
Greater support for, and acceptance of new systems
Produces higher quality systems
Easier implementation
Lower training costs

Disadvantages:
Very difficult to get all users to JAD meetings
All the problems that may be caused by any group process

Rapid Application Development Model

Rapid application development (RAD) is an incremental software development
process model that emphasizes an extremely short development cycle. The RAD
model is a high-speed adaptation of the linear sequential model in which rapid
development is achieved by using component-based construction. If requirements
are well understood and project scope is constrained, the RAD process enables a
development team to create a fully functional system within very short time
periods (e.g., 60 to 90 days)

Compiled by: Hiranya Prasad Bastakoti

Page 16

It is used primarily for information systems applications, the RAD approach

encompasses the following phases:
Business modeling: The information flow among business functions is modeled in
a way that answers the following questions: What information drives the business
process? What information is generated? Who generates it? Where does the
information go? Who processes it?
Data modeling: The information flow defined as part of the business modeling
phase is refined into a set of data objects that are needed to support the business.
The characteristics (called attributes) of each object are identified and the
relationships between these objects defined.
Process modeling: The data objects defined in the data modeling phase are
transformed to achieve the information flow necessary to implement a business
function. Processing descriptions are created for adding, modifying, deleting, or
retrieving a data object.
Application generation: RAD assumes the use of fourth generation techniques).
Rather than creating software using conventional third generation programming
languages the RAD process works to reuse existing program components (when
possible) or create reusable components (when necessary). In all cases, automated
tools are used to facilitate construction of the software.
Testing and turnover: Since the RAD process emphasizes reuse, many of the
program components have already been tested. This reduces overall testing time.
However, new components must be tested and all interfaces must be fully
exercised. Obviously, the time constraints imposed on a RAD project demand
scalable scope. If a business application can be modularized in a way that enables
each major function to be completed in less than three months, it is a candidate for
RAD. Each major function can be addressed by a separate RAD team and then
integrated to form a whole.
Advantages
As customer is involved at all stages of development. It leads to product
achieving customer satisfaction.
Usage of powerful development tools results into reduced software
development cycle time.
Makes use of reusable components, to decrease the cycle time
Drawbacks of RAD
For large but scalable projects, RAD requires sufficient human resources to
create the right number of RAD teams.

Compiled by: Hiranya Prasad Bastakoti

Page 17

 RAD requires developers and customers who are committed to the rapid-fire
activities necessary to get a system complete in a much abbreviated time
frame. If commitment is lacking from either constituency, RAD projects will
fail.
Not all types of applications are appropriate for RAD. If a system cannot be
properly modularized, building the components necessary for RAD will be
problematic. If high performance is an issue and performance is to be
achieved through tuning the interfaces to system components, the RAD
approach may not work.
RAD is not appropriate when technical risks are high. This occurs when a
new application makes heavy use of new technology or when the new
software requires a high degree of interoperability with existing computer
programs.

System Analyst:
A systems analyst studies the problems and needs of an organization to determine
how people, data, processes, communications, and information technology can best
accomplish improvements for the business. When information technology is used,
the analyst is responsible for:

The efficient capture of data from its business source,

The flow of that data to the computer,
The processing and storage of that data by the computer, and
The flow of useful and timely information back to the business and its
people.

Compiled by: Hiranya Prasad Bastakoti

Page 18

Task of System Analyst:

1. Identify the problem.
2. Analyze and understand the problem.
3. Identify solution requirements or expectations.
4. Identify alternative solutions and decide a course of action.
5. Design and implement the best solution.
6. Evaluate the results. If the problem is not solved, return to step 1 or 2 as
appropriate.
Role of System analyst
The system analyst is the person (or persons) who guides through the development
of an information system. In performing these tasks the analyst must always match
the information system objectives with the goals of the organization.
Information System Analysts are people who are involved in analyzing, designing
implementing and evaluating computer based information system to support the
decision making and operating of an organization. System analysts can be
compared with an architect. An architect study needs and goals to design a
building. He makes several designs and submits to the owner. The owner selects
best general design. The architect then makes the detail design considering all
demanded blocks. After implementing the system, the architect set certain test like
use of material, lightening, ventilation etc.
Role of System Analyst differs from organization to organization. Most common
responsibilities of System Analyst are following
i.

Defining requirement: The most important and difficult task of an analyst

is to understand the users requirements. It involves interviewing users and
finding out what information they use in the current system and how they use
it. They are then asked what information they feel they lack, which is provide,
will allow to them to do their job better. The analyst has to them determine
how such information can be generated.

ii.

Prioritizing requirements by consensus: In any organization there are

many users. Each user has some special information needs. It may not be
possible to satisfy needs of everyone due to limited computing capacity,
availability of programmer etc. Even if computer capacity is available, it
would be necessary to take up some of the task first and other later. Thus
there is need to set priorities among the requirements of various users. This
is the best achieved by having a common meeting with all the user and
arriving at a consensus. This responsibility of the system analyst require good
interpersonal relation and diplomacy. He must be able to convince all the

Compiled by: Hiranya Prasad Bastakoti

Page 19

users about the soundness of the group decision and obtain their
cooperation.
iii.

Gathering data, facts and opinions of users: Having determined the

information needs and their priority, the system analyst must develop the
system with the active and willing cooperation of all the users. The users
must be made aware of what information they will get, how it will be deliver
and how they can make use of it. The analyst designing the system must
make use of the user long experience and expertise. With the users help he
must gather the necessary data. While developing the system the analyst
must continuously consult the users and get their views. He must be the
users student in learning various facts about the organization, and their
teacher in telling them how best to use the computer-based system.

iv.

Analysis and evaluation: The system analyst analyses the working of

current information system in the organization and finds out what extend
they meet users needs. He then shifts trough the facts and opinions gather
by him and find the best characteristics of a new or modified system which
will meet the users stated information needs. Various graphical means of data
analysis are useful in the task.

v.

Solving problems: An analyst must suggest study the problem in depth and
suggest alternate solution to the management. The relative difficulties in
implementing each of the alternatives and benefits of each must be
determined so that a manager can pick what he considered at the best
solution.

vi.

Drawing up specifications: A key job of an analyst is to obtain the

functional specification of the system to be designed in a form which can be
understood by the users. The specification must be non-technical so that the
users and managers and managers understand it. The analyst must win the
acceptance of all levels of users of the system such as clerks, middle level
managers and top managers. The specification must be precise and detail so
that it can be used by system implementers. It must also take into account
expansions in the near feature.

vii.

Designing systems: Once the specification is accepted, the analyst designs

the system. The design must be understandable to the system implementer.
The design must be modular to accommodate changes easily. The analyst
must know the latest design tools to assist him in his task. As part of the
design he must also create a system test plan.

viii.

Evaluating system: An analyst must critically evaluate system after it has

in use for reasonable period of time. The time at which evaluation is to be
done, how it is to be done, and how it is to be done and uses comments are
to be gather and used must be decide by the analyst. He must have an open
mind accept valid criticism and must be good critic himself to enable him to
carry out necessary improvements.

What Does A System Analyst Do?

Compiled by: Hiranya Prasad Bastakoti

Page 20

A system analyst is a system-oriented problem solver.

System problem solving is the act of studying a problem
environment in order to implement corrective solutions that take the
form of new or improved systems.
Most systems analysts use some variation of a system problem solving
approach called a system development life cycle.
Attributes of System analyst:
1. Working Knowledge of Information Technology

The systems analyst is an agent of change.

The systems analyst is responsible for showing end-users and management how
new technologies can benefit their business and its operations.
The systems analyst must be aware of both existing and emerging information
technologies and techniques.

2. Programming Experience and Expertise

A systems analyst must know how to program because they are the principle
link between business users and computer programmers.
It is wrong to assume that a good programmer will become a good analyst or
that a bad programmer could not become a good analyst.
Most systems analysts need to be proficient in one or more high-level
programming languages.

3. General Business Knowledge

The systems analysts are expected to immerse themselves in the business

and be able to specify and defend technical solutions that address the
bottom-line value returned to the business.
Systems analysts should be able to communicate with business experts to
gain knowledge of problems and needs.
It is not uncommon for systems analysts to develop so much expertise over
time they move out of information systems and into the user community.

4. Problem-Solving Skills

The systems analyst must have the ability to take a large business problem,
break that problem down into its component parts, analyze the various
aspects of the problem, and then assemble an improved system to solve the
problem.
The systems analyst must learn to analyze problems in terms of causes and
effects rather than in terms of simple remedies.
The systems analyst must be well organized.
System analysts must be able to creatively define alternative solutions to
problems and needs.

Compiled by: Hiranya Prasad Bastakoti

Page 21

5 Communications Skills

The systems analyst must be able to communicate effectively, both orally

and in writing.
The systems analyst should have a good command of the English language.
Almost without exception, communications skills, not technical skills, prove to
be the single biggest factor in career success or failure.
6. Interpersonal Relations Skills

Systems analysts work in teams composed of IS professionals, end-users, and

management.
Being able to cooperate, to comprise, and to function as part of a team, is
critical for success in most projects.
Because development teams include people with dramatically different levels
of education and experience, group dynamics is an important skill to develop.

7. Flexibility and Adaptability

No two systems development projects encountered by a systems analyst are

identical.
There is no single, magical approach or solution applicable to systems
development.
Successful systems analysts learn to be flexible and adapt to special
challenges or situations presented by specific systems development projects.
The systems analyst must be able to recognize when variations upon (or
single-instance exceptions to) development standards are necessary and
beneficial to a particular project.
The systems analyst must be aware of the implications of not following the
standards.
8. Character and Ethics

The nature of the systems analyst's job requires a strong character and sense
of ethics.
Ethics is a personal character trait in which an individual(s) understands the
difference between right and wrong and acts accordingly.

Compiled by: Hiranya Prasad Bastakoti

Page 22