Project Report Sample Part - 5 (System Design, Introduction, Entity-Relationship Design, Data Dictionary, Database in Project, Input / Output Design)
System
Design
INTRODUCTION:
The design is a solution to “how to” approach, compared to analysis, a
“what is” orientation. It translates the system requirements in to ways of
operationalizing them. The design phase focuses on the detailed implementation,
which is recommended in the feasibility study. Emphasis is on translation of
performance specification into design specifications. The design phase is a
transaction from a user-oriented document to a document oriented to the
programmers or database personnel.
System design goes through two phases of development: logical and
physical Design. DFD shows the logical flow of a system and defines the
boundaries of the system. For a candidate system, it describes the input
(source), output (destination), database (data stores), & procedures (data
flow) – all in a format that meets the user requirements. Physical design is
the preparation of designs that showed what the systems physically look like.
Entity – Relationship Model:
As a database
designer one should use an Entity Relationship (ER) diagram as a tool to build the logical database design of a system. An
ER diagram represents the following three elements:
·
Entities: An entity is an object with a
distinct set of properties that is easily identified. Entities are the building
blocks of a database. You represent an entity using a rectangular box that
contains the name of the entity.
·
Attributes: An attribute is a property of
an entity that differentiates it from other entities and provides information
about the entity. An attribute type is a property of an entity type.
·
Relationships: A relationship is a
crucial part of the design of a database. It is used to establish a connection
between a pair of logically related entities. Separate entities can have
relationship with each other. Relationship is represented between two entities
using a diamond labeled with the name of the relationship.
Following ER Model
marks:
Entity
Attribute  |
Multi-value
Attribute
Relationship
 |
Composite
Attribute |
|||
 |
|||
E – R Diagram of Project:
 |
||||||
|
|
|||||
login
 |
ADMN. LOGIN |
Data
Dictionary:
A data
dictionary is a structured repository of data about data. It is a set of
rigorous definitions of all the data elements and data structures. A data
dictionary has many advantages. The most obvious is documentation: it is
valuable reference in any organization. Another advantage is improving analyst
communication by establishing consistent definitions of various elements, terms
and procedures. A data dictionary is an important step in building a database.
Most database management systems have a data dictionary as a standard feature.
Here the entire data structure and data item used in the current system
as well as in the candidate system would be shown along with the relationship.
The relations could be:
- Sequence Relation: This shows the collection of data items used in system.
- Optional Relation: The optional data items if any.
- Iterative Relation: The relation shows the multiple existences of data items corresponding to single data structure entry.
- Selection: This relation would be used to depict the selection of values for a single data item forms multiple sources.
LOGIN:
Field Name
|
Data type
|
ID
|
Varchar2(20)
|
NAME
|
Varchar2(20)
|
PASSWORD
|
Varchar2(20)
|
NEW USER:
Field Name
|
Data type
|
ID
|
Varchar2(20)
|
NAME
|
Varchar2(20)
|
ADDRESS
|
Varchar2(20)
|
PASSWORD
|
Varchar2(20)
|
EMAIL
|
Varchar2(20)
|
PHONE
|
Varchar2(20)
|
INITIAL
|
Varchar2(20)
|
ACTYPE
|
Varchar2(20)
|
Login for saving
Field Name
|
Data type
|
ID
|
Varchar2(20)
|
NAME
|
Varchar2(20)
|
PASSWORD
|
Varchar2(20)
|
Input/output Design:
Input design is the process of
converting user originated to a computer-based format. A systems flowchart
specifies master files (database), transaction files, and computer programs.
Input data are collected and organized into groups of similar data. Once
identified appropriate input media are selected for processing.
Input
data is to make data entry as easy logical and free form errors as possible. In
entering data, operators need to know the following:
·
The allocated space for each field
·
Field sequence that must match that in the
source document.
·
The format in which data fields are entered.
Output design is the most important
and direct source of information to the user. Efficient intelligible output
design should improve the system’s relationships with the user and help in
decision making. A major form of output is a hard copy from the printer. Printouts
are designed around the output requirements of the user. The output devices to
consider depend on factors such as compatibility of the devices with the system
response time requirement of the device with the system.
The
standards for pried output suggest the following:
·
Give each output a specific name or title.
·
Provide a sample of the output layout.
·
State whether each output field is to include
significant zeros, spaces between fields and alphabetic or any other data.
·
Specify the procedure for proving the accuracy
of output data.
In
online applications, information is displayed on the screen. The layout sheet
for displayed output is similar to the layout chart used for designing input.
Project Output:
Home Page:
<Home Page Snapshot>
INDEX
PAGE
<Index Page Snapshot>
User Login Page
<User Login Page Snapshot>
Transaction Page
<Transaction Page Snapshot>
Deposit Page
<Deposit Page Snapshot>
Withdrawal Page
<Withdrawal Page Snapshot>
Transfer Page
<Tranfer Page Snapshot>
Update Page
<Update Page Snapshot>
Change Password Page
<Change Password Page Snapshot>
Mini Statement Page
< Snapshot>
Comments
Post a Comment