SYSTEM DESIGN AND DEVELOPMENT

SYSTEM DESIGN AND DEVELOPMENT

Design is the first step in the development phase for every engineered product or system.
Computer software designing techniques like engineering design approaches in the other
disciplines, changes continuously as new methods, better analysis and broader understanding
evolve.
System design involves translating information requirements and conceptual design into
technical specification and general flow of processing. After the user requirements are
identified, related information is gathered to verify the problem and after evaluating the
existing system , a new system is proposed . the proposed system consist of various tables ,
their maintenance and report generation.

The system design is the most challenging and creative phase. The first step is to determine
how output is produced and in what format. Samples of input and output are presented. Next
the input data and master data are to be designed to meet the requirements of the proposed
output.

INPUT DESIGN

Input design is the process of converting user-designated inputs to a computerized

format. The input data are collected and organized in to group of similar data. Input design
includes determining the record media, method of input speed of capture and entry into system.
Input design consists of developing specifications and procedure for data preparations, those
necessary steps to put transaction data into usable form for processing, data entry and activity
of entering the data for processing. Error entered by the user can be controlled by the input
design. The goal of designing the input data is to make data entry easy, logical and free from
errors as possible.

System analysis decides the following input design details

 What data to input ?

 What medium to be used ?
 How the data should be arranged or coded ?
 The dialogue , which is used to guide the user, input data .
 Methods for preparing input and correction steps.
 LOGIN

Username

Password

LoginLO
Login
Forgot password?

REGISTER DEPARTMENT

Dep Name

No of employees

Dep Id

Register
EMPLOYEE REGISTRATION

Emp Id

Dept Id

Name

Age

DOB

Gender Male Female

Phone

Address

Email Id

SUBMIT
WORK REGISTRATION

Work

Work Id

ADD

UPLOAD FILES

File Name BROWSE

UPLOAD

UPDATE WORK STATUS

Work

Status

UPDATE
OUTPUT DESIGN

The output is the most important and direct source of information to the user. The
output should be provided in a most efficient formatted way. Based on the options given by the
users and the administrator various types of output screens have been generated.

The computer output is the most important and direct source of information to the user.
Efficient and intelligible output design improves the system‘s relationship with the user and
helps in decision-making. Output design was studied going actively during the study phase.
The objective of the output design is defined the contents and format of all documents and
reports in an attractive and useful format.

WORK STATUS

SL.NO WORK EMPLOYEE ID STATUS

DOWNLOAD FILES

SL.NO FILE NAME SIZE

DOWNLOAD
DOWNLOAD
DOWNLOAD
VIEW COMPLAINT AND REPLY

SL.NO EMPLOYEE ID COMPLAINT

View

View

Complaint

Reply

Reply

VIEW FEEDBACK

SL.NO EMPLOYEE ID FEEDBACK

View

View

View
DATABASE DESIGN

Database design is the process of producing a detailed data model of a database. This
logical 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. 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. 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 relationships between the different data elements.

 Superimpose a logical structure upon the data on the basis of these relationships

NORMALIZATION

Normalization is the process of decomposing a set of relations with anomalies to

produce smaller and well-structured relations that contain minimum redundancy. It is a formal
process of deciding which attributes should be grouped together in a relation.

Normalization applied during database design are

 First Normal Form(1NF)

 Second Normal Form(2NF)

 Third Normal Form (3NF)

FIRST NORMAL FORM

A relation is said to be in 1NF if it satisfies the constrains that it contains primary key

SECOND NORMAL FORM

Second Normal form (2NF) is based on the concept of functional dependency. A

relation R is in 2NF if it is in 1NF and every non key attribute A of R is fully dependent on the
primary key. That is, relation is said to be in 2NF if each attribute A in R meets one of the
following criteria:

(a) It appears in the primary key.

(b) It is fully functionally dependent on the primary key.

The tables designed in the proposed system, contain a primary key for uniquely identifying
each user. For e.g.: table Employee Type has E_ID has a primary key for unique identification
of the Product. The table Unit Registration has Untidy as the primary key. All non-key
attributes of the table is fully dependent on the primary key .

THIRD NORMAL FORM

Third Normal form (3NF) is based on the concept of transitive dependency. A relation
is said to be in 3NF if it is in 2NF and has no transitive dependencies. That is all the non key
attribute should be functionally determined by the primary key. In the proposed system all
attributes of tables are fully depends on the primary key only that is all non-key attributes are
mutually independent.
DATA FLOW DIAGRAM

A data flow diagram (DFD) or a bubble chart is a graphical tool for structured
analysis. DFD models a system by using external entities from which data flow to a process,
which transforms the data and creates output data flows which go other process or external
entities or files. Data in files may also flow to processes as inputs.

DFDs can be hierarchically organized, which help in partitioning and analysing large
systems. As a first step, one dataflow diagram can depict an entire system which gives the
system overview. It is called context diagram of level0 DFD. The context diagram can be
further expanded.

The successive expansion of a DFD from the context diagram to those giving more
details is known as leveling of DFD. Thus a top down approach is used, starting with an
overview and then working out the details. The main merit of the DFD is that it can provide an
overview of what data a system would process, what transformation of data are done, what files
are used, and where the results flow.

Data flow diagram is quite effective, especially when the required design is unclear and
the user and analyst need a notational language for communication. It is one of the most
important tools used during system analysis. It is used to model the system components such
as the system process, the data used by the process, any external entities that interact with the
system and information flows in the system.

The data flow diagram (DFD) is one of the most important tools used by system
analyst. Data flow diagrams are made up of a number of symbols, which represent system
components. Most data flow modelling methods use four kinds of symbols. These symbols are
used to represent four kinds of system components. Processes, data source, data flows and
external entities. Processes are represented by thin line DFD and each data stores has a unique
name and square or rectangle represents external entities.
DATA FLOW DIAGRAM

LEVEL 0 DFD
LEVEL 1.1 DFD
LEVEL 1.2 DFD
TABLE DESIGN

A table is a data structure that organises information in to rows and columns. It can be
used to both store and display data in a structured format. Databases often contain multiple
tables, with each one designed for a specific purpose. Each table may include it’s own set of
field, based on what data the table needs to store. In database tables, each field is considered a
column, while each entry (or record) is considered as a row. A specific value can be accessed
from the table by requesting data from an individual column and row. These are primary key
fields for uniquely identifying a record in a table.

LOGIN

FIELD TYPE CONSTRAINTS DESCRIPTION

ID Int Primary Key User identification number
Username Varchar(50) Not null Get Username from user

Password Varchar(50) Not Null Get Password from user

Department

FIELD TYPE CONSTRAINT DESCRIPTION

DEPT_ID Int Primary Key Unique ID of departments
DEPT_NAME Varchar(50) Not Null Get name of department
Employee
FIELD DATATYPE CONSTRAINTS DESCRIPTION
Emp_id Int Primary Key Unique employee identification

Emp_name Varchar(50) Not Null Specifies Name from user

Dept_id Int Foreign Key Takes value from department table
Emp_age Int Not Null Specifies age of employee
Emp_DOB Date Not Null Specifies DOB of employee
Emp_address Varchar(50) Not Null Specifies address of employee
Emp_ph_No Int Not Null Specifies contact no of employee
Gender Char Not Null Specifies Gender of employee
Emp_Email_id Varchar(50) Not Null Specifies email ID of employee

Work
FIELD DATA TYPE CONSTRAINTS DESCRIPTION
Work_id Int Primary Key Unique work identification number

Work_name Varchar(50) Not Null Specifies work name

Assigned
FIELD DATA TYPE CONSTRAINTS DESCRIPTION
Work id Int Foreign Key Takes value from work table
Emp_id Int Foreign Key Takes value from Employee table
Assign_id Int Primary Key Unique Number for work Assigned

Files
FIELD DATA TYPE CONSTRAINTS DESCRIPTION
F_id Int Primary Key Unique file identification
Emp_Id Int Foreign Key Takes value from employee table
File Varchar(Max) Not Null Specifies file path
Feedback
FIELD DATA TYPE CONSTRAINTS DESCRIPTION
Feed_id Int Primary Key Unique identification of feedback
Feedback Varchar(Max) Not Null Gets feedback from user
Emp_id Int Foreign Key Takes value from employee table

Complaints
FIELD DATA TYPE CONSTRAINTS DESCRIPTION
Comp_id Int Primary Key Unique complaint identification
Complaint Varchar(Max) Not Null Gets complaints from user
Reply Varchar(Max) Not Null Gets replies from user
Emp_id Int Foreign Key Takes value from employee table