System Design

Submitted To: Submitted By:

Ms. Rohini Sharma Amandeep Gautam
81005507001
Smiley Garg.
7040301163

1
Introduction
Systems design is the process or art of defining the
architecture, components, modules, interfaces, and data
for a system to satisfy specified requirements.

One could see it as the application of systems theory

to product development.

2
Design Objectives:
 System design is to deliver the requirements as
specified in the feasibility report.

The main objectives of the design are:

1.Practicality
2.Efficiency
3.Cost
4.Flexibility
5. Security

There is some overlap with the disciplines of systems

analysis, systems architecture and systems engineering.
3
Requirements analysis-
 Requirements analysis in software engineering,
encompasses those tasks that determining the needs to
meet for a new or altered product, taking account of the
possibly conflicting requirements of the various
stakeholders, such as users.

 Requirementanalysis is critical to the success of a

development project.

 Requirements must be actionable, measurable, testable,

related to identified business needs or opportunities,
and defined to a level of detail sufficient for system
design.

4
Diagram

5
Benchmarking :

 Benchmarking is the process of comparing the cost, cycle

time, productivity, or quality of a specific process or
method to another that is widely considered to be an
industry standard or best practice.

 Benchmarking provides a snapshot of the performance of

your business and helps you understand where you are in
relation to a particular standard.

 Theresult is often a business case for making changes in

order to make improvements.

6
 Benchmarking is most used to measure performance
using a specific indicator resulting in a metric of
performance that is then compared to others.

7
Architectural Design :
 creates a blueprint for the design with the necessary
specifications for the hardware, software, people and data
resources.

Design :
 Designers will produce one or more 'models' of what
they see a system eventually looking like, with ideas from
the analysis section either used or discarded.

A document will be produced with a description of the

system, but nothing is specific they might say 'touch
screen' or 'GUI operating system', but not mention any
specific brands.

8
Computer programming and Debugging :
 in the software world, or detailed design in the
consumer, enterprise or commercial world - specifies
the final system components.

System testing :
 evaluates the system's actual functionality in relation
to expected or intended functionality, including all
integration aspects.

9
 System Design Considerations:-
 System Design
 Software Architecture
 Attributes of a Good Design

System Design
 System design begins with the understanding of user
requirements, gained by the developer through:-
1. Attending meetings with users and experts .
2. Reading the software requirements document and functional
specification document.
3. Participating in user and contractor review meetings.
4. Active involvement of the developer in requirements
definition is essential to the project's success.
10
Software Architecture
 A system architecture is the conceptual design that defines the structure
and/or behavior of a system.

 An architecture description is a formal description of a system,

organized in a way that supports reasoning about the structural
properties of the system.

 It defines the system components or building blocks and provides a plan

from which products can be acquire, and systems developed, that will
work together to implement the overall system.

 Early in the software design process, the software architecture is

defined. This divides the software into components that can be
characterized by a set of attributes:
11
 Attributes of a Good Design
 Testable Against Requirements - In a good design, every
requirement is testable.

 Structured - A good design uses a clear structure that can be

readily understood by other designers reading the code.

 Modular - A good design is modular and exhibits high

cohesiveness and low coupling.

 Reusable - A good design is reusable and repeatable.

 Extensibility - New capabilities can be added to the software

without major changes to the underlying architecture.
12
 Compatibility - The software is able to operate with other products that are designed for
interoperability with another product. For example, a piece of software may be backward-
compatible with an older version of itself.

 Fault-tolerance - The software is resistant to and able to recover from component failure.

 Reliability - The software is able to perform a required function under stated conditions
for a specified period of time.

 Robustness - The software is able to operate under stress or tolerate unpredictable or

invalid input. For example, it can be designed with a resilience to low memory conditions.

13
 Maintainability - The software can be restored to a specified
condition within a specified period of time. For example,
antivirus software may include the ability to periodically
receive virus definition updates in order to maintain the
software's effectiveness.

 Packaging - Printed material such as the box and manuals

should match the style designated for the target market and
should enhance usability. All compatibility information should
be visible on the outside of the package. All components
required for use should be included in the package or specified
as a requirement on the outside of the package.

14
Security - The software is able to withstand hostile acts and
influences.

Usability - The software user interface must be intuitive to its

target user/audience. In many cases, online help should be
included and also carefully designed

15