Software Design

Software design is a mechanism to transform user requirements into some suitable form, which
helps the programmer in software coding and implementation. It deals with representing the
client's requirement, as described in SRS (Software Requirement Specification) document, into
a form, i.e., easily implementable using programming language. The software design phase is
the first step in SDLC (Software Design Life Cycle), which moves the concentration from the
problem domain to the solution domain. In software design, we consider the system to be a set
of components or modules with clearly defined behaviors & boundaries.
Input Design
Input technology has changed dramatically in recent years. The quality of the output is only as
good as the quality of the input. It is the process of converting user originated inputs to
computer based format. Input data are collected, identified and selected for processing. In an
information system, input is the raw data that is processed to produce output. During the input
design, the developers must consider the input devices such as PC, MICR, OMR, etc.
Well designed input forms and screens have following properties −
• It should serve specific purpose effectively such as storing, recording, and retrieving the
information.
• It ensures proper completion with accuracy.
• It should be easy to fill and straightforward.
• It should focus on user’s attention, consistency, and simplicity.
• All these objectives are obtained using the knowledge of basic design principles
regarding −
– What are the inputs needed for the system?
– How end users respond to different elements of forms and screens.
Data Input Methods
It is important to design appropriate data input methods to prevent errors while entering data.
These methods depend on whether the data is entered by customers in forms manually and
later entered by data entry operators, or data is directly entered by users on the PCs.
The objectives of input design are −
• To design data entry and input procedures
• To reduce input volume
• To design source documents for data capture or devise other data capture methods
• To design input data records, data entry screens, user interface screens, etc.
• To use validation checks and develop effective input controls.
Some of the popular data input methods are −
• Batch input method (Offline data input method)
• Online data input method
• Computer readable forms
 • Interactive data input
Output Design
• The design of output is the most important task of any system. During output design,
developers identify the type of outputs needed, and consider the necessary output
controls and prototype report layouts.
The objectives of input design are −
• To develop output design that serves the intended purpose and eliminates the
production of unwanted output.
• To develop the output design that meets the end users requirements.
• To deliver the appropriate quantity of output.
• To form the output in appropriate format and direct it to the right person.
• To make the output available on time for making good decisions.
• types of outputs
External Outputs
• Manufacturers create and design external outputs for printers. External outputs enable
the system to leave the trigger actions on the part of their recipients or confirm actions to
their recipients.
• Some of the external outputs are designed as turnaround outputs, which are
implemented as a form and re-enter the system as an input.
Internal outputs
Internal outputs are present inside the system, and used by end-users and managers. They
support the management in decision making and reporting.
There are three types of reports produced by management information −
• Detailed Reports − They contain present information which has almost no filtering or
restriction generated to assist management planning and control.
• Summary Reports − They contain trends and potential problems which are categorized
and summarized that are generated for managers who do not want details.
• Exception Reports − They contain exceptions, filtered data to some condition or
standard before presenting it to the manager, as information.
Importance of Reports
The following are various advantages of Reports:
• We can organize and present data in groups.
• We can calculate running totals, group totals, grand totals, percentage of totals, etc.
• Within the body of Reports, we can include sub-forms, sub-reports and graphs.
• We can present data in an attractive format with pictures, special fonts and lines.
• We can create a design for a report and save it so that we can use it over and over
again.
Differences between Forms and Reports:
• Forms can be used for both input and output. Reports, on the other hand, are used for output,
i.e., to convey information on a collection of items.
• Typically, forms contain data from only one record, or are at least based on one record such
as data about one student, one customer, etc. A report, on the other hand is only for reading
and viewing. So, it often contains data about multiple unrelated records in a computer file or
database.
• Although we can also print forms and datasheets, reports give more control over how data are
displayed and show greater flexibility in presenting summary information.
Forms Design
• Both forms and reports are the product of input and output design and are business
document consisting of specified data. The main difference is that forms provide fields for
data input but reports are purely used for reading. For example, order forms, employment
and credit application, etc.
• During form designing, the designers should know −
– who will use them
– where would they be delivered
– the purpose of the form or report
• During form design, automated design tools enhance the developer’s ability to prototype
forms and reports and present them to end users for evaluation.
Structure Charts
• Structure chart is a chart derived from Data Flow Diagram. It represents the system in more
detail than DFD. It breaks down the entire system into lowest functional modules, describes
functions and sub-functions of each module of the system to a greater detail than DFD.
• Structure chart represents hierarchical structure of modules. At each layer a specific task is
performed.
• Module - It represents process or subroutine or task. A control module branches to more
than one sub-module. Library Modules are re-usable and invokable from
Symbols used in construction of structured chart
• Module
It represents the process or task of the system. It is of three types.
– Control Module
A control module branches to more than one sub module.
– Sub Module
Sub Module is a module which is the part (Child) of another module.
– Library Module
Library Module are reusable and invokable from any module.
• Conditional Call
It represents that control module can select any of the sub module on the basis of some
condition.

• Loop (Repetitive call of module)

It represents the repetitive execution of module by the sub module. A curved arrow
represents loop in the module.

• Data Flow
It represents the flow of data between the modules. It is represented by directed arrow with
empty circle at the end.

• Control Flow
It represents the flow of control between the modules. It is represented by directed arrow
with filled circle at the end.
• Physical Storage
Physical Storage is that where all the information are to be stored.

• HIPO Diagram

HIPO Diagram
• HIPO (Hierarchical Input Process Output) diagram is a combination of two organized
method to analyze the system and provide the means of documentation.
• HIPO diagram represents the hierarchy of modules in the software system. It decomposes
functions into sub-functions in a hierarchical manner. It depicts the functions performed by
system.
• HIPO diagrams are good for documentation purpose. Their graphical representation makes
it easier for designers and managers to get the pictorial idea of the system structure.
• HIPO does not provide any information about data flow or control flow.
• Both parts of HIPO diagram, Hierarchical presentation and IPO Chart are used for structure
design of software program as well as documentation of the same.

Objectives of Good Form Design

A good form design is necessary to ensure the following −
• To keep the screen simple by giving proper sequence, information, and clear captions.
• To meet the intended purpose by using appropriate forms.
• To ensure the completion of form with accuracy.
• To keep the forms attractive by using icons, inverse video, or blinking cursors etc.
• To facilitate navigation.
Characteristics of Software Design
• Correctness: Software design should be correct as per requirement.
• Completeness: The design should have all components like data structures, modules,
and external interfaces, etc.
• Efficiency: Resources should be used efficiently by the program.
• Flexibility: Able to modify on changing needs.
• Consistency: There should not be any inconsistency in the design.
• Maintainability: The design should be so simple so that it can be easily maintainable by
other designers.