TOPIC:-

REPROT ON ANALYSIS—TO—
DESIGN
ON TRANSITION

Submitted to:-
submitted by:-

10808697
Ms. JAGWIDER KAUR GAURAV
MALIK
ROLLNO:-b53
SECTION:-rn2801
CLASS:-DIP (IT)

CONTENTS:-
 INTRODUCTION

 FRAME WORK FOR ANALYSISOF SYSTEM FACTS

 ANALYSIS ISSUES

• CAPACITY

o DESIGN STRATEGIES

• CONTROL

o DESIGN STRATEGIES

• INFORMATION ACCESSBILITY

o DESIGN STRATEGIES

• COMPLEXITY

o DESIGN STRATEGIES

 OBJECTIVES OF INFORMATION SYSTEM DESIGN

 SPECIFY THE LOGICAL DESIGN ELEMENTS

 SUPPORT BUSINESS ACTIVITIES

  MEET USER REQUIREMENTS

 EASY TO USE

• HUMAN ENGINEERING

• ERGONOMIC DESIGN

 PROVIDE SOFTWARE SPECIFICATION

 CONFORM TO DESIGN STANDARDS

 WHAT FEATURES MUST BE DESIGNED

 ELEMENTS OF THE DESIGN

 DESIGN OF OUTPUT

 DESIGN OF FILES

 MANAGING THE DESIGN PROCESS FOR INTITUTIONAL

APPLICATION

 OBTAINIG DELIVERABLES DESCRIBING SYSTEM DESIGN

 MONITORING DESIGN PROGRESS

 SUMMARY

 INTRODUCTION:-
Determining systems requirements requires analysis of the facts
in hand. Descriptions and documentation developed as a result of
the fact-finding effort are studied to evaluate current system
performance and establish requirements to be met in a new
design. The design is a solution—the translation of requirements
into ways of meeting them. The design will determine the success
of the system. Through the design, systems analysts can
dramatically influence the effective than others.

We will look at the objectives of

systems design, concerns that range from meeting business
needs to using computer technology effectively. The essence of
system design is the selection and specification of the features of
an information system. Thus, we will also explore how to manage
the design process for institutional applications and the
documentation that is delivered at the completion of the design
effort. We will give special attention to system design for end-user
developed applications.

 FRAME WORK FOR ANALYSISOF SYSTEM

FACTS
A useful frame work for examining system facts and establishing
general user requirements includes the areas of capacity,
control, access to information, and complexity.

 CAPACITY:-

Capacity is the ability of the current system of

people, equipment, space and procedures to achieve the
basic objectives and purpose of the system. The analyst
must determine whether the current capacity will support
the general information systems activities of accepting
input, processing, storing and retrieving data, producing
results, or transmitting information and messages.

DESIGN STRATEGIES OF CAPACITY:-

1. INCREASE CAPABILITIES:

Add more people, equipment, or other resources to

the system to increase the magnitude of work that can
be achieved.

2. LOWER EXPECTATIONS:

Reduce the performance requirements by changing

lead times for the start of a task or completion times.

3. REDEFINE NATURE OF TASK:

Change the activities through shifting of

responsibilities, adjusting levels of specialization or
generalization, or altering performance standards .
 CONTROL:-

Control generally means “keeping things on track.” In a

more formal sense, it pertains to a set of mechanisms to
increase the likelihood that activities affecting an
organization’s objectives will be carried out properly.
Control can be viewed in terms of procedures, content,
audit, and responsibility. From a systems design
viewpoint, the following are among the strategies to
consider when dealing with systems control:
DESIGN STRATEGIES OF CONTROL:-

1. DESIGN TO AVOID CONTROL LAPSES:

Develop the system to prohibit the occurrence of

lapses in controls so that invalid events cannot occur.
This may be very difficult or extremely costly to do.

2. DESIGN TO DETECT AND REPORT CONTROL

PROBLEMS:

Ensure that procedures are built into the system to

identify difficulties or inaccuracies and report them as
an exception to be corrected by an authorized person.

3. DESIGN TO DETECT AND FIX CONTROL LAPSES:

Provide a means for taking corrective action and

reporting that the action has been taken.

 INFORMATION ACCESSBILITY:-

When perplexed by
access to information, an analyst should consider whether there is
an information problem or a procedural question .Careful analysis
of facts may reveal that, even though the necessary information
exists, people may tend to rely on memory or hunch because
retrieving it is too much work. The method of retrieval may be
awkward or the information may be presented in the wrong form.

DESIGN STRATEGIES OF INFORMATION ACCESSBILITY:-

1. ELIMINATE THE NEED FOR THE INFORMATION:

Some information can be retrieved and used by an

automated system without user intervention. The
analyst may also choose to redesign systems or
procedures so that decision and process rules are
built in, eliminating the need for information retrieval
in all but exceptional cases.

2. EASE ACCESS TO INFROMATION:

System can be designed to streamline requester

commands and rely on default alternatives that fit
the most frequently recurring situations.

3. ELIMINATE THE NEED FOR PROCESSING:

Frequently needed details can be presorted in a form

that does not require manipulation or processing.
Availability and accessibility will both improve.

4. CHANGE THE METHOD OF PRESENTATION:

 Alternative formats, including graphics, color
enhancement, and even animation, can be selected.

• COMPLEXITY:-

Involved, interrelated, or 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 OF COMPLEXITY:-

1. SIMPLIFY:

This can be achieved by removing unnecessary steps or

eliminating the recording of information that will not be
used. Providing more explicit standards or directions can
also simplify otherwise complex processes.

2. PARTITION:

Dividing a complex process into separate tasks often

reduces complexity. The analyst should consider which
tasks should be handled by people and which are most
appropriate for a computer.
 3. RESEQUENCE:

Changing the order in which a process occurs can

reduce apartment complexity. Essential information can
become available and answers to difficult questions can
suddenly become obvious.

 OBJECTIVES OF INFORMATION SYSTEM DESIGN

Requirements are translated into design specification. What

does the systems analysts intend to achieve when designing an
information system? This section describes the objectives of
systems design and explores the nature of the design, as well as
the explicit results expected.

 SPECIFY THE LOGICAL DESIGN ELEMENTS:-

 System design involves first logical design and physical
construction of the system. When analyst formulates a
logical design, they write the detailed specification for
the new system, they describe its features: the output,
input, files and databases, and procedures—all in a
manner that meets project requirements. The
statements this feature is termed the design
specification of the system.

Physical construction, the activity following logical

design, produces program software, files, and a working
system. Design specifications instruct programmers
about what the system should do. The programmers in
turn write the programs that accept input from users,
process data, produce the reports, and store data in
files.

LOGICAL DESIGN
PHYSICAL DESIGN
FEATURE SPECIFICATIONS
PORODUCT
Data entry Decision
support

Reporting
Communication

Reporting File
maintenance
BACKUP
 OUTPUT INPUT
SPECIFICATION SPECIFICATION
TRANSACTIO
N
MASTER
REPORT
MASTER

FILE AND PROCESSIN REQUIREME

DATABASE G NTS
SPECIFICATI SPECIFICATI DATA
ON ON

 SUPPORT BUSINESS ACTIVITIES:-

A
fundamental objective in the design of an information
system is to ensure that it supports the business
activity for which it is developed. The computer always
is secondary to the results the system is intended to
produce. Similarly, the design must fit the way a firm
does business. If a sales system is designed to work
best for orders that are paid in cash, when in fact the
firm offers a liberal “
sales—on—credit” policy, man--information system
functions well technically, it will not fit the business
activities.
 MEET USER REQUIREMENTS:-

User
requirements are translated into system characteristics
during design. We say that an information system
meets user needs if it accomplishes the following.

I. Performs the right procedures properly.

II. Presents information and instruction in an

acceptable and effective fashion.

III. Produces accurate results.

IV. Provides an acceptable interface and method of

interaction.

V. Is perceived by users as a reliable system.

 EASY TO USE:-

Do the benefits of NOT using an

information system exceed those achieved by relying
on the system? This may appear to be an illogical
question, since the correct information is always
preferred to the incorrect .but a seasoned system
 always will know that many technical features of an
information system –such as reliability, accuracy, and
processing speed –are secondary to the human aspects
of a system design.

Therefore, analysts strive to design the system to be

engineered for people and to include ergonomic
features.

• HUMAN ENGINEERING:-

I. Incorporates system features that are

easy to understand and use

II. Deters user error or carelessness

III. Provides enough flexibility to fit a

variety of individual user needs

IV. Adapts to increasing user familiarity

with the system

V. Generally functions in a manner that

seems natural to the user
  ERGONOMIC DESIGN:-

Ergonomic refers to the physical

factors of an information system that affect the
performance, comfort, and satisfaction of direct users.
Ergonomic is a concern in in selection of equipment and in
the design of work areas. Ergonomic factors must also be
considered when selecting colors for the presentation of
information, location of command keys, or methods of
interaction with the system, as we will see. In most
effective system, analysts carefully consider the
ergonomic aspects of a systems design from several
different perspectives.

 PROVIDE SOFTWARE SPECIFICATION:-

The features of an
information system, software must also be carefully
designed. Systems design includes formulating software
specifications. The specification state input, output, and the
processing functions and algorithms used to perform them.
Software modules and routines focusing on what function
each perform and the procedures for accomplishing them
are specified as well. Selection of programming languages,
 software packages, and software utilities occurs during the
logical design process and the recommendation are included
in the software specification.

 CONFORM TO DESIGN STANDARDS:-

The objectives of
systems design are broad and affect many aspects of both
the application and the organization in which the system will
be used. It should be no surprise to learn that well—
managed information systems groups also maintain systems
development standards. Systems design specifications are
established within these standards

Examples of areas include in design standards:

I. DATA STANDARDS

II. CODING STANDARDS

III. STRUCTURAL STANDARDS

IV. DOCUMENTATION STANDARDS

 WHAT FEATURES MUST BE DESIGNED

 The specification describes the features of the
system, the components or elements of the system and their
appearance to users. To many users, the success of a system
relates to whether they believe it has the proper features. This
section describes the features a system analyst must design. It is
important to make clear the elements that must be addressed in
the formal design specifications.

 ELEMENTS OF THE DESIGN:-

The components
of an information system described during requirements analysis
are the focal point in system design. Analysts must design the
following elements:

• DATA FLOWS

• DATA STORES

• PROCESSESS

• PROCEDURES

• CONTROLS

• ROLES
  DESIGN OF OUTPUT:-

When designing output, system

analysts must accomplish the following:

I. Determine what information to present

II. Decide whether to display, print, or “speak” the

information and select the output medium

III. Arrange the presentation of information in an

acceptable format

IV. Decide how to distribute the output to intended

recipients

 DESIGN OF FILES:-

The design of files includes

decisions about the nature and content of the file itself
such as whether it is to be used for storing transaction
details, historical data, or reference information. Among
the decisions made during file design are the following:

I. Which data items to include in a record format

within the file
 II. Length of each record, based on the
characteristics of the data items on which it is
based

III. The sequencing or arrangement of records within

the file

 MANAGING THE DESIGN PROCESS FOR

INTITUTIONAL APPLICATION

Managing of the design process means

taking steps to see that the development effort proceeds
properly and produces the appropriate results. We will
examine the deliverables the analyst is expected to provide,
as well as the areas that should be monitored for progress.

 OBTAINIG DELIVERABLES DESCRIBING SYSTEM

DESIGN

When the design of an information system is

complete, the specifications are documented in a form
 that outlines the features of the application. System
analysts term these specifications the deliverables or
the design book.

THE DELIVERABLES INCLUDE THE FOLLOWING:-

• LAYOUT CHARTS

• RECORD LAYOUTS

• CODING SYSTEMS

• PROGRAM SPECIFICATIONS

• PROCEDURE SPECIFICATION

• DEVELOPMENT PLAN

• COST PACKAGE

 MONITORING DESIGN PROGRESS:-

Like any other large or

important project in business, the design of
information systems must be properly managed to
ensure that the desired results are obtained.

Questions project managers or information systems

managers commonly raise include the following:

• DEVELOPMENT TIME

• DEVELOPMENT COST

• DESIGN ACCEPTABILITY
 SUMMARY
The fact—finding activities in a systems study produce details
that describe current operations and points to areas where
improvement is needed or possible. To evaluate the existing
system, analyst typically considers the current and needed
capacity, including the people, equipment, storage, space, and
procedures involved. If complexity is a problem, systems analysts
will strive to simplify, partition, or sequence activities to make
tasks and processes more manageable. These specifications,
called the logical system design, include the details of output,
input, files, database interaction, controls, and procedures.
Physical construction, which follows logical design, produces
software, files, and a working system.

The specifications for institutional systems

are included in the deliverables: layout charts, record layouts,
coding systems, program and procedure specifications, the
development plan, and cost projections. Hardware and software
selections may be included in some systems if additional
equipment must be acquired or if packaged programs are used.

Both end—users and

systems analysts share responsibility under the end—user
method of development .To reduce risks to the organization, it is
important to download data, avoid user data entry, follow design
standards, document the system, and review all design
specifications.