This document discusses the system design process for a budget control management system. It covers analyzing requirements, designing goals such as usability, compatibility, and security. Database design including normalization is explained. The entity relationship diagram and normalization process are defined. Form and report design, testing procedures including unit, integration and system testing are outlined. Documentation of the system is also discussed.

1. CHAPTER FOUR
SYSTEM DESIGN 1.
INTRODUCTION OF DESIGN:
We all know that one of the most crucial stages of software development is analysis and design.
The system designer must make thoughtful preparations and decisions. Planning how the various
components of the software will work together to accomplish the intended result is the process of
analyzing and developing software. During this chapter the researchers will discover these
subjects one by one: Analyzing phase, designing phase, design considerations, database design,
entity relationship diagram, ERD symbols, and types of relationships.
1.1 DESIGN GOALS
The flowing goals were kept in mind while designing the system:
Make system easy and flexible for users: End users who aren’t programmers should be apple
to have an extreme amount of control over their purposes, this could be used efficiently and
system could act as catalyst in achieving objectives.
Make the system compatible: it should fit in the total integrated system, future maintenance
an enhancement must less.
Efficiency: It is generally considered to be the most important. Given a piece of hardware on
which the system will run and a piece of software to run it, the design should make full and
efficient use of the facilities provided. The users should interact with the system without any
delay.
Integrity: this means that the system should be accurate as possible. The problem of preserving
the integrity of data can be viewed at a number of levels. At a low level, it concerns ensuring
that the data are not corrupted by hardware or software errors. At higher level, the problem of
preserving integrity concerns maintaining and accurate representation ofthe real world.
Extensibility: New capabilities can be added to the system without major changes to the
underlying architecture.
Fault-tolerance: The system is resistant to and able to recover from component failure.

2. Modularity: the resulting system comprises well defined, independent components. That leads
to better maintainability. The components could be then implemented and tested in isolation
before being integrated to form a desire system.
Reliability: The system is able to perform a required function under stated conditions for a
specified period of time.
Reusability: the system is able to add further features and modification with slight or no
modification.
Security: The system, once loaded, should be safe from physical corruption whether from
hardware or software failure or from unauthorized access. This is a general requirement of the
most systems.
4.2 User Interface Design
Interface design is the process of defining how the system will interact with the external
entities “system users or other systems”. It describes the layout of the pages and the flow of
events, and is also concerned with where and how data are represented on the pages.
However, in a User Interface Design, the needs, experience, and capabilities of the system users
must be taken into account. In addition, the designers should be aware of users’ physical and
mental limitations.
1.2 DATABASE DESIGN: Design for database hierarchy for using MYSQL server with
relational database management system Provides minimum search times when locating specific
records. That will provide Stores data in the most efficient manner possible to keep the
database from
Growing too large, makes data updates as easy as possible and creating more flexible

3. 1.3 ENTITY RELATIONSHIP DIAGRAM (ERD) ER diagram An entity-relationship (ER) diagram is a
specialized graphic that illustrates the interrelationships between entities in a database. ERD
show entities in a database and relationships between tables within that database. It is
essential to have one of these if you want to create a good database design. The patterns help
focus on how the database actually works with all of the interactions and data flows, although
another useful tool is a Data Flow Diagram (DFD) which more directly describes this. ERD is a
detailed, logical representation of the entities, associations and data elements for an
organization or business. ERD is a graphical modeling tool to standardize ER modeling; the
modeling can be carried out with the help of pictorial representation of entities, attributes and
relationships

4. 5.3.1 De-normalization of entity relational diagram
Demoralization is the process of taking a normalized database and modifying table structures to allow
controlled redundancy for increased database performance. Attempting to improve performance is the
only reason to ever denormalize a database. A denormalized database is not the same as a database
that has not been normalized. Denormalizing a database is the process of taking the level of
normalization within the
help of pictorial representation of entities, attributes and relationships
Un-normalized (UDF)
First Normal Form
(1NF)
Second Normal Form
(2NF)
Third Normal Form
(3NF)
Remove repeating groups
Remove practical
dependencies
Remove transitive
deficiencies

5. 5.3.2. Normalization
Normalization is the process of organizing data in a database. This includes creating tables and
establishing relationships between those tables according to rules designed
Both to protect the data and to make the database more flexible by eliminating two factors:
redundancy and inconsistent dependency. Redundant data wastes disk space and creates
maintenance problems. If data that exists in more than one place must be changed, the data
must be changed inexactly the same way in all locations. Inconsistent dependencies can make
data difficult to access; the path to find the data may be missing.
Objectives of Normalizatio
Purpose of normalization
Normalization allows us to minimize insert, update, and delete anomalies and help maintain
data consistency in the database.
 To avoid redundancy by sorting each fact within the database only once
 To put data into the form that is more able to accurately accommodate change
 To avoid certain updating "anomalies"
 To facilitate the enforcement of data constraint
 To avoid unnecessary coding.
1.4 THE DATA DICTIONAR
Data dictionary, or data repository, is central store house of information about System’s data.
We will use it to collect, document, and organize specific facts about system include the data
flows, data stores, external entities, and processes. The data dictionary also defines and
describes all data elements and meaningful combinations of data element
Design forms and Reports

6. The most effective method of offline data entry is a form filling, in which a blank form that
duplicates or resembles the source document is completed on the screen. The user enters the
data and then moves to the next field. The form can have many control features such as menu
bars, toolbars, dialog boxes, text boxes, command buttons, list boxes, scrollbars, drop-down,
group boxes, check boxes, and more others. Data so that additions deletions and Modification
of Files can be made in just one table and them propagated though the rest of database using
the defined relationships.
Figure: Login Button

7. Figure: menu Form

8. Report Design

9. CHAPTER FIVE
SYSTEM DEVELOPMENT
5.0 INTRODUCTION
This chapter will highlight the implementation and operation part of the Budget Control
management system. Design phase was discussed that is translated into code. PHP & MySQL
was the programming language used to implement the system. The implementation phase
affects coding, testing and maintenance deeply. A well written code reduces the testing and
maintenance efforts. The remaining of this chapter discusses the followings: - Coding Phase:-
Test System Implementation: -Development Testing: -Release Testing: -User Instruction: -
Developing User Manuals and Summary.
7.2 TYPES OF TESTING A. Unit testing
The testing of individual program or module is called unit testing. The objective is to identify and
eliminate execution errors that could cause the program to terminate abnormally, and errors that could
have been missed during the checking. B. Integration testing Testing two or more programs that depend
on each other is called integration testing, or link testing. C. System testing After completing integration
testing, system testing will performed, which involves the entire information. A system test includes all
typical processing situations and is intended to assure users, developers. During system testing, user
enter data including samples of actual, or live, data, perform queries, and produce report to simulate
actual operating condition.
7.3 DOCUMENTATION
Documentation describes an information system and helps the users who must interact with it. Accurate
documentation can reduce system downtime, cut cost, and speed up maintenance task. Documentation
is essential for successful system operation and maintenance. In addition to supporting a system’s users,
accurate documentation is essential for developers who must modify the system, add new features or
perform maintenance