System Design

Introduction
The purpose of the Design Phase is to a solution of the problem specified in the requirements document. This is the first step in moving from problem domain to the solution domain. The design of a system is perhaps the most critical factor affecting the equality if the software; it has a major impact on the later phase is the Design Document. This Document is similar to the blueprint or a plan for the solution and is used later during implement, testing and maintenance. The Design activity is often divided into separate phases System Design and Detailed Design. System Design is sometimes also called Top-level Design. This system design aims to identity and modules that should be in the system, the specification of these modules, and how they interact with each other to produce the desired result. At the end of the System Design all the major data structures, file formats, and the major modules in the system and their specification are decided.

Context Flow Diagram (CFD)

It only contains one process node (process 0) that generalizes the function of the entire system in relationship to external entities. In context diagram the entire system is treated as a single process and all its inputs, outputs, sinks and sources are identified and shown.

The notations used in flow diagram are:

Bubble The Bubble represents a process or transformation that is applied to the data which changes in some way. Each bubble is assigned a number.

Box The Box represents an entity in the diagram Arrow The Arrow represents the data flow. All arrows in the data flow diagram are labled.The arrowhead indicates the direction of data flow. Parallel Lines The Parallel Lines represents a repository of data that is to be stored for use by one or more processes.

DFD Level:-0

DATA FLOW DIAGRAM (DFD)

A Data Flow Diagram is a graphical representation of the flow of data through an Information System. A data flow diagram can also be used for the visualization of Data Processing. it is common practice for a designer to draw a context-level DFD first which shows the interaction between the System and outside entities. This context-level DFD is then exploded to show more detail of the system being modeled. A DFD represents flow of data through a system. DFD are commonly used during problem analysis. It views a system as a function that transforms the input into desired output.DFD shows movement of data through the different transformations or processes in the system. Data Flow Diagrams can be used to provide the end user with a physical idea of where the data they input ultimately has an effect upon the structure of the whole system from order to dispatch to restock how any system is developed can be determined through a data flow diagram. The appropriate register saved in database and maintained by appropriate authorities.

Data Flow Diagram Notation

Process

File / Database

Input / Output

Flow

Description of the component

Functional component 1: INPUT: - Administrator adds products and complaints Process definition: - Products and complaints add to the database OUTPUT: - Admin views complaints and products.

Functional component 2: INPUT: - Administrator adds customer orders for product. Process definition: - Customer pays for products. OUTPUT: - Admin views paid details and installment details.

Functional component 3: INPUT: - Administrator takes weekly and monthly report. Process definition: - Admin views paid details and non paid details OUTPUT: - Admin views product details and installment details.