KPD5023K3

3.0 Analysis and Design

3.1 System Design
3.2 System Architectural Design
3.3 Software Architectural Design and Styles
3.4 Web Presence Design
3.5 Database Design

3.1 System Design

Systems design is the process of defining the architecture, components, modules, interfaces, and data
for a system to satisfy specified requirements.
Systems design could be seen as the application of systems theory to product development.
Systems design then overlaps with systems analysis, systems engineering and systems architecture.
Architectural design
The architectural design of a system emphasizes on the design of the systems architecture which
describes the structure, behavior, and more views of that system and analysis.
Logical design
The logical design of a system pertains to an abstract representation of the data flows, inputs and
outputs of the system. This is often conducted via modelling, using an over-abstract (and sometimes
graphical) model of the actual system. In the context of systems, designs are included. Logical design
includes entity-relationship diagrams (ER diagrams).
Physical design
The physical design relates to the actual input and output processes of the system. This is explained in
terms of how data is input into a system, how it is verified/authenticated, how it is processed, and how it
is displayed. In physical design, the following requirements about the system are decided.
Input requirement,
Output requirements,
Storage requirements,
Processing requirements,
System control and backup or recovery.

Put another way, the physical portion of systems design can generally be broken down into three subtasks:
User Interface Design
Data Design
Process Design
User Interface Design is concerned with how users add information to the system and with how the
system presents information back to them. Data Design is concerned with how the data is represented
and stored within the system. Finally, Process Design is concerned with how data moves through the
system, and with how and where it is validated, secured and/or transformed as it flows into, through and
out of the system. At the end of the systems design phase, documentation describing the three subtasks is produced and made available for use in the next phase.
Physical design, in this context, does not refer to the tangible physical design of an information system.
To use an analogy, a personal computer's physical design involves input via a keyboard, processing
within the CPU, and output via a monitor, printer, etc. It would not concern the actual layout of the
tangible hardware, which for a PC would be a monitor, CPU, motherboard, hard drive, modems,
video/graphics cards, USB slots, etc. It involves a detailed design of a user and a product database
structure processor and a control processor. The H/S personal specification is developed for the
proposed system.

3.2 System Architectural Design

A system architecture or systems architecture is the conceptual model that defines the structure,
behavior, and more views of a system. An architecture description is a formal description and
representation of a system, organized in a way that supports reasoning about the structures and
behaviors of the system.
A system architecture can comprise system components, the externally visible properties of those
components, the relationships (e.g. the behavior) between them. It can provide a plan from which
products can be procured, and systems developed, that will work together to implement the overall
system. There have been efforts to formalize languages to describe system architecture, collectively
these are called architecture description languages (ADLs).
Several types of systems architectures (underlain by the same fundamental principles) have been
identified as follows:
Hardware architecture
Software architecture
Enterprise architecture
Collaborative systems architectures (such as the Internet, intelligent transportation systems,
and joint air defense systems)
Manufacturing systems architectures
Strategic systems architecture

3.3 Software Architectural Design and Styles

The architecture of a system describes its major components, their relationships (structures), and how
they interact with each other. Software architecture and design includes several contributory factors
such as Business strategy, quality attributes, human dynamics, design, and IT environment.

Architecture serves as a blueprint for a system. It provides an abstraction to manage the system
complexity and establish a communication and coordination mechanism among components. It defines
a structured solution to meet all the technical and operational requirements, while optimizing the
common quality attributes like performance and security.
Further, it involves a set of significant decisions about the organization related to software development
and each of these decisions can have a considerable impact on quality, maintainability, performance,
and the overall success of the final product. These decisions comprise of

Selection of structural elements and their interfaces by which the system is composed.
Behavior as specified in collaborations among those elements.
Composition of these structural and behavioral elements into large subsystem.
Architectural decisions align with business objectives.
Architectural styles guide the organization.

3.4 Web Presence Design

A modern website must contain active content, appropriate color schemes, image selection, and userfriendly page layouts and be mobile-friendly and responsively designed.
Many experts recommend creating complementary desktop and mobile website versions that integrate
similar color schemes and brand messaging. This assures users that theyve reached the correct
brands page. This concept is much easier to integrate when the mobile version is created first and the
desktop website is built off of it.
Designers should also consider how their website content will be displayed on different devices. Many
smartphone models differ in their screen size, not to mention the much larger displays of tablets.
To ensure that content is displayed appropriately, designers should leverage responsive frameworks.
One way to differentiate a website is through performance. Many users wont wait for more than a few
seconds for a webpage to load before they abandon it in favor of something else. This makes
performance critical not only for the design processes, but for quality assurance as well. Before the
mobile website is rolled out, QA teams should be sure to thoroughly test the page for load times and
performance under extreme usage levels to be sure it functions as it should in any situation.

Be responsive. "Use a responsive technology framework

Keep the design simple. "A clean design and focused copy can go a long way
Keep content short and sweet. "People sometimes fall in love with their [website] content and it
makes the mobile site too cluttered"
Make it fast -- by serving images that are optimized for mobile.
Don't go overboard with Java. "Avoid excessive JavaScript in your mobile websites where
possible, because it runs differently across different browsers and devices"
Consider video, but add it wisely. "Video is an absolute must-have for any mobile site"
Test to ensure your content can be properly viewed on different devices, platforms and
operating systems. "Remember to test the mobile user experience by operating system to
improve overall site experience with usability testing"

3.5 Database Design

Database design is the process of producing a detailed data model of a database. This data model
contains all the needed logical and physical design choices and physical storage parameters needed to
generate a design in a data definition language, which can then be used to create a database. A fully
attributed data model contains detailed attributes for each entity.
The term database design can be used to describe many different parts of the design of an overall
database system. Principally, and most correctly, it can be thought of as the logical design of the base
data structures used to store the data. In the relational model these are the tables and views. In an
object database the entities and relationships map directly to object classes and named relationships.
However, the term database design could also be used to apply to the overall process of designing, not
just the base data structures, but also the forms and queries used as part of the overall database
application within the database management system (DBMS).

The process of doing database design generally consists of a number of steps which will be carried out
by the database designer. Usually, the designer must:

Determine the data to be stored in the database.

Determine the relationships between the different data elements.
Superimpose a logical structure upon the data on the basis of these relationships.

Within the relational model the final step above can generally be broken down into two further steps,
that of determining the grouping of information within the system, generally determining what are the
basic objects about which information is being stored, and then determining the relationships between
these groups of information, or objects. This step is not necessary with an Object database.

Database designs also include ER (entity-relationship model) diagrams. An ER diagram is a diagram

that helps to design databases in an efficient way.
Attributes in ER diagrams are usually modeled as an oval with the name of the attribute, linked to the
entity or relationship that contains the attribute.