The analysis to design transition

Design is a solution

Translation of requirements into ways of meeting

them.
 How to design an IS?
 How to specify the features of system that will
meet previously stated requirements.
Specifying application requirement

 Requirement investigation
 Requirement anticipation
 Requirement specification

 These are the methods for assembling data

that describes how a system operates.
Review of requirement
investigation objectives

 Emphasis is on basic requirements.

 Understanding ongoing processes.
 Why and How they are performed?
 Identifying data used and information processing
activities.
 Determining process timing and volume and
identifying system control.
Questions

 Are there data stores that are never

referenced?
 Are there processes that serve multiple
purposes?
 Is the inflow of data adequate to perform the
process?
Perception of requirements: analysis
of facts

 The perceptive capabilities of analyst will

influence the result of analysis.
 It will assist in perceiving system weaknesses
and requirements.
 Analysts analyze the details:
What works well?
What is ineffective and inefficient ?
Where adjustments are needed?
Steps to system development

 Preliminary investigation:
 Data collection:
 Assess system data:
 Identify design requirement
 Outline design strategy
 Analyze cost and benefits
 Formulate system proposal
 Present to management
Facts to consider:

 Capacity
 Control
 Access to information
 Complexity
Capacity :

Description: Capability of current system

(people, equipment, procedures) to achieve
its purpose and objective.

 Design Strategies: Increase capabilities

Lower expectations
Redefine nature of task
Control: ”keeping things on track”

Description: Mechanism designed to increase the

likelihood that activities are carried out property
and that unacceptable or unexpected events
are detected and handled as exceptions.
Design strategies:
Design to avoid control lapses.
detect and report control lapses.
detect and fix control lapses.
Information accessibility:

 Description: availability of information needed to

accomplish an objective when it is needed and
in a useful form.
 Design strategies:
 Eliminate need for information
Ease access to information
Eliminate need for processing
change method of presentation
Complexity:

 Description: Involved, interrelated, excessive

numbers of tasks, steps or activities resulting
in unacceptable or incomplete performance;
may lead to problems In capacity, control or
information accessibility.
 Design strategies: Simplify
Partition
Resequence
Lecture 2:Objectives in designing an
information system

 Requirements are translated into design

specifications.
 Design of system consist of logical and
physical design
Logical design elements

 I/O specifications
 File and database specifications
 Processing specifications
 Requirements data
Physical design elements

 Programs:
data entry
reporting communication
reporting file maintenance
backup
 Files: transaction
reports
1.Specify the logical design

 At the time of logical design analyst describe

its features like
o/p,i/p,file and database and procedures.
 Eg: blue print
Physical construction

 The activity following the logical design

 Produce program s/w, files and a working system.
 note: design specifications instruct programmers
about what the system should do.
 And the programmer in turn write the programs that
accept input from the users, process data, produce
report and store data in the files.
2.Support business activities

 Support business activity for which it is

prepared.
 For example, if it is essential for an
organization to move information very quickly
to remain competitive,then the design
specifications of the information must be
based around this essential business
objective.
 Eg: automated teller machines.
Ensure the system features meet user
requirements

 We can say that IS meets user needs if it

accomplishes the following:
1. Perform right procedures properly
2. Presents information and instructions in an
acceptable and effective fashion.
3. Produce accurate results.
4. Provides an acceptable interface and method of
interaction
5. Is perceived by users as a reliable system.
Provide a system engineered for ease
of use by people

Human engineering
 Formulate a system that:
1. Incorporates system features that are easy to
understand and use
2. Deters user error or carelessness.
3. Prevent failure
4. Provide flexibility to fit a variety of individual needs.
5. Generally functions in a manner that seems natural
to the user.
Ergonomic design

 Refers to the physical factors of an IS that

affects the performance, comfort and
satisfaction of direct user.
 Design of terminals, chairs and other
equipments that influences the amount of
fatigue
 These factors affects such concerns as
errors during data entry,user efficiency and
even asbsenteeism.
Provide detailed s/w development
specification

 The specification states input , output and

processing functions and algorithms used to
perform them.
 Selection of programming language, s/w
packages.
Conform to logical design

 Areas included in design standards

1. Data standards
2. Coding standards
3. Structural standards
4. Documentation standards
Lec[3] What features must be
designed?

 The design specification describes the

features of the system, the components or
elements of the system and their appearance
to users.
Elements of the design

 Data flows
 Data stores
 Processes
 Procedures
 Controls
 roles
Data flows

 The movement of data into, around, and out

of the system.
Logical  physical
Data stores

 Temporary or permanent collection of data

Processes

 Activities to accept, manipulate, and deliver

data and information. may be manual or
computer based
Procedures

 Methods and routines for using the

information system to achieve intended
results.
controls

 Standards and guidelines for determining

whether activities are occurring in the
anticipated or accepted manner that is
“under control”.
 Specify actions when problems or
unexpected circumstances are detected.
Roles

 The responsibility of all persons involved with

the new system, including end users,
computer operators and support personnel.
Design of output

 Refers to the “results”.

 Most end users will not actually operate the
information system or enter data through
work stations, but they will use the output
from the system.
SA must accomplish the following:

 Determine what information to present

 Decide whether to display, print, or speak the
information and select the output medium.
 Arrange the presentation of information in an
acceptable format. [layout]
 Decide how to distribute the output to
intended recipients.
Design of files

 It include decision about the nature and content of

files itself such as whether it is to be used for
storing transactions details, historical data, or
reference information.
 Things to consider:
1. Which data items to include in a record format
within the file.
2. Length of each record
3. The sequencing or arrangement of records within
the file.
Design of database interactions

 Large or small computer systems, interact

with databases that span multiple
applications.
 Design is established and monitored by a
database administrator.
 SA does not perform database design but
consult with the database administrator to
determine the most appropriate database
interaction.
SA provide the database administrator
with description of:

1. Data needed from the database

2. Actions that will affect the database.
[update]
The role of administrator includes the
following responsibilities:

 Evaluate the appropriateness of the analysts’

request
 Describe methods for interaction with
database.
 Ensure that the application cannot damage
the database or adversely affect the needs of
other information system application in any
way.
Design of input

 What data to input

 What medium to use
 How the data should be arranged or coded
 The dialogue to users in preventing input
 Data items and transactions needing
validation to detect errors.
 Methods for performing input validation and
steps to follow when errors occur.
Design of control

 Ensure that only authorized users access the

system
 Guarantee that the transaction area
acceptable
 Validate the data for accuracy
Design of procedures

 Data entry procedures

 Run time procedures
 Error handling procedures
 Security and backup procedures.
Design of program specifications

 Program specifications are themselves a

design. they describe how to transform the
system design specifications- for output,
input, files, processing and so on- into
computer software.
Designing computer software is
important to ensure that:

 The actual programs produced perform all

tasks and do so in the manner intended.
 The structure of software into modules
permits suitable testing and validation to be
sure procedures are correct.
 Future modifications can be made in an
efficient manner and with a minimum
disruption to the design of the system.