In the Name of Almighty

Allah, Most Beneficent and

Most Merciful

1
JUNIOR LABORATORY SCHOOL SYSTEM

Final Project
Master of Science
In
Computer Science

Supervised By
Muhammad Ali Imran
Submitted By
Muhammad Naeem

2
 CERTIFICATE

This is to certify that Muhammad Naeem and registration No:2016-ag-4317 has

been successfully completed his technical report in partial fulfillment of the
degree of MSc Computer Science.

Advisory Committee:

Advisor:
Mr. ALI IMRAN

Member 1:
Ms. ALI AUN

Member 2:
Mr. AMIR WAHEED

3
 Acknowledgement

In the name of Allah, the Beneficent and the most Merciful!

First of all we would like to thanks Allah Almighty who provided us opportunity,
courage and showered his blessings to work on this project.
Special Thanks to our supervisor Mr. Ali imran who guided and helped us design
many vital parts of our Final Year project. They helped us to understand many issues
during the first stage of project which all are helpful for project report and
presentation.
Furthermore, we would like to thank our Head of Department Mr. Ali Aun and other
staff who gave us permission to utilize the resources and required equipment to
complete the task.
Last but not least, we would like to thank our parents for their unconditional support,
both financially and emotionally throughout my degree.

4
 DECLRATION
I hereby declare that the contents of the thesis, “ISAS Fee Management System” are
product of my own research and no part has been copied from any published source
(except the references, standard mathematical or genetic models/formulate/protocols
etc.).I further declare that this work has not been submitted for award of any other
diploma/degree. The university may take action if the information provided is found
inaccurate at any stage. (In case of any default the scholar will be proceeded against as
per HEC plagiarism policy).

_____________________________
Signature of the Student

Name: Muhammad Naeem

2016-ag-4317

5
 Abstract

This document is meant for describing all the features and procedures that
were followed while developing the system. This document specially mentions the
details of the project how it was developed, the primary requirement, as well as
various features and functionalities of the project and the procedures followed in
achieving these objectives.
JUNIOR LABORATORY SCHOOL SYSTEM
forms the lifeline of the business institute to manage the student and its fee. It
is very essential for an Institute to handle the Fee and their scale. It is very useful for
an Institute to test its student fee continuously for their mutual development. The IT
initiatives have encouraged various Organizations to develop systems to facilitate their
day to day operations. The Attendance System will include various parts (Fee, Student
Entry, etc.) for conducting fee Sheet. This system helps in conducting Attendance
quickly and can thus help in saving time and the operations will be carried out
efficiently.

With the effective use, any Institute can apply the “JUNIOR LABORATORY
SCHOOL SYSTEM” for conducting quick attendance and getting better results in
less time.

6
 Table of Contents
CHAPTER 1:.......................................................................................................................................11
1.1 Objectives.............................................................................................................................11
1.2 Purpose.................................................................................................................................11
1.3 Scope....................................................................................................................................12
2 Introduction..................................................................................................................................13
2.1 Design and implementation constraints:...............................................................................13
2.1.1 Hardware and software Requirements:.........................................................................13
2.2 Requirements:.......................................................................................................................13
Functional Requirements..............................................................................................................13
2.2.1 Non Functional Requirements......................................................................................15
2.3 System Development Life Cycle............................................................................................16
2.4 System Analysis...................................................................................................................17
2.4.1 Design...........................................................................................................................17
Testing..........................................................................................................................................17
2.5 Use Case Diagram................................................................................................................18
2.6 Entity Relationship Diagram................................................................................................19
2.7 Class Diagram:.....................................................................................................................20
2.8 System Design:.....................................................................................................................21
2.8.1 Input design..................................................................................................................21
2.8.2 Input form design.........................................................................................................21
2.8.3 Code design..................................................................................................................21
2.8.4 Output design................................................................................................................22
2.8.5 Consideration and report design..................................................................................22
Database design............................................................................................................................22
2.9 Table Design:.......................................................................................................................23
2.9.1 Order-Table..................................................................................................................23
2.9.2 Admin Table.................................................................................................................23
2.9.3 Product Table................................................................................................................23
3 CHAPTER 3: System Components.................................................................................................24

7
 3.1 Planning................................................................................................................................24
Problems of existing system.............................................................................................................24
Planning Objective............................................................................................................................25
3.2 Technical Feasibility..............................................................................................................25
3.2.1 Operational Feasibility..................................................................................................26
System Analysis................................................................................................................................26
3.2.2 Input Design..................................................................................................................27
3.2.3 Input Form Design........................................................................................................27
3.2.4 Code Design..................................................................................................................28
3.2.5 Output Design...............................................................................................................28
3.2.6 Consideration in Report Designing...............................................................................28
Database Designing......................................................................................................................29
3.3 Table Designing....................................................................................................................31
3.4 System Development............................................................................................................31
3.4.1 Software Selection........................................................................................................31
3.4.2 Hardware Selection.......................................................................................................31
3.4.3 Server-side Hardware Requirements.............................................................................31
3.4.4 Client-side Hardware Requirements.............................................................................32
3.4.5 Client-side Software Requirements...............................................................................32
3.4.6 Programming Language................................................................................................32
3.4.7 Data Environment.........................................................................................................33
3.4.8 SQL Server.....................................................................................................................33
3.10 User Manual.........................................................................................................................37
3.10.1 Home page....................................................................................................................37
3.10.2 Admin Login..................................................................................................................38
3.10.3 View Submit Fee...........................................................................................................39
3.10.4 Submit Fee of Student..................................................................................................40
3.10.5 User Manual.................................................................................................................41
4 Conclusion and Result..................................................................................................................42
5.1 Output of the Developed System.........................................................................................42
Speed and Accuracy......................................................................................................................42
Eliminating Data Redundancy.......................................................................................................42

8
 User Friendly................................................................................................................................43
Managerial Acceptability..............................................................................................................43
Security.........................................................................................................................................43
Time Saving..................................................................................................................................43
5.2 Conclusion............................................................................................................................44
5.3 Summary..............................................................................................................................44

9
 LIST OF FIGURES
Figure 1 Waterfall Model.................................................................................................22
Figure 2 System development life cycle............................................................................23
Figure 3 Use case diagrams...............................................................................................26
Figure 4 Entity Relationship Diagram...............................................................................27
Figure 5 Class Diagram.....................................................................................................28
Figure 6 Data Flow Diagram.............................................................................................29
Figure 7 logical database designs......................................................................................32
Figure 8 The Relationship b/w IS & IT.............................................................................40
Figure 9 The Five Interlocking Objectives in a Preliminary investigation.......................41
Figure 10 Steps of Normalization......................................................................................56
Figure 11 Home page.........................................................................................................63
Figure 12 Admin Login.....................................................................................................64
Figure 13 View Submit Fee...............................................................................................65
Figure 14 Submit Fee of Student.......................................................................................66
Figure 15 Add Student Data..............................................................................................67

LIST OF TABLES

Table 1 Order Table...........................................................................................................34

Table 2 Admin Table.........................................................................................................34
Table 3 Product Table........................................................................................................35

10
 CHAPTER 1:
Importance of computer

Computer is an electronic device used in almost every field even where it is

most unexpected. That is why this age is called as the area of IT. And now we cannot
imagine a world without computers. It is made up of two things one is the hardware
and other is software. All physical components of computer like keyboard, mouse,
monitor etc. comes under the hardware

Whereas all the programs and languages used by the computer are called software .
These days computers are tools for not only engineers and scientists but also they are
being used by millions of people around the world. Computer has become very
important now days because it is very much accurate, fast and can accomplish many
tasks easily. Otherwise to complete those tasks manually much more time is required.
It can do very big calculations in just a fraction of a second. Moreover it can store
huge amount of data in it. We also get information on different aspects using internet
on our computer.

1.1 Objectives

When we have already entered the 21st century, we may not afford to listen
words like Sorry, Misrouting, Confusion, Late deliveries, loss of Packets, No-
response, No feedback etc. From any organization, we are committed to render “A”
class services to all our patronage. We have tried to make all these mis-happening &
feel pleasure to couriers in this courier world.

1.2 Purpose
The following documentation is a project the “JUNIOR LABORATORY
SCHOOL SYSTEM”. It is a detailed summary of all the drawbacks of the old system
and how the new proposed system overcomes these shortcomings. The new system
takes into account the various factors while designing a new system. It keeps into the
account the Economical bandwidth available for the new system. The foremost thing
that is taken care of is the need and requirements of the user.

11
1.3 Scope

This project is consisting online order taking and Check Online Information
about ISAS Fee Management System. Application will be used helpful customer.
Many customer take order trough cart system and customer tracking location is the
best way for delivery man to find the customer location. Whenever customer move
from his location delivery man can see hi movement location and also the same
method apply on delivery man location. Modules of the will include following
components:

1. Website

1. Web Base Application

2. Admin Panel

Main features of the developed system are as follows:

 No wastage of time. To get Menu

 Get our contact information through our website
 Security of data is high.
 No data redundancy.
 Administration can see Data and Rider easily.
 Easy to get customer details.
 Easy to get Order Details.
 Easy to manage product.
 Information About Us on website
 More reliable.
 User friendly.

12
 2 Introduction

2.1 Design and implementation constraints:

 Database
The system shall use the MySQL Database, which is open source and free.
 Operating System
The Development environment shall be Windows 7/8/XP.
 Language
Php, html5, js
 Tools

Wamp server

2.1.1 Hardware and software Requirements:

Software
 Dream weaver

 xammp server

Hardware
 Hard disk :40 GB

 RAM : 1 GB

 Processor : Pentium(R)Dual-core CPU

 Operating System: windows

2.2 Requirements:

Functional Requirements

Requirement #: Functional Requirement 1

Requirement type: Functional

Title: go to browser visit application

13
Description: A user should be able to visit our website and see new trends about
Software. Source: Requirement Engineers team

Rationale: In order for a user to check fee detail for student.

Requirement #: Functional Requirement 2

Requirement type: Functional

Title: go to browser visit application

Description: A user who manage “fee” should visit my application.

User should be able to see detail about fee, go our application.

Source: Requirement Engineers team

Rationale: In order for a user to check fee detail for student.

Requirement #: Functional Requirement 3

Requirement type: Functional

Title: go to browser visit application

Description: A user who manage “fee” should visit my application.

User should be able to see detail about fee, go our application.

Source: Requirement Engineers team

Rationale: In order for a user to check fee detail for student.

Requirement #: Functional Requirement 4

Requirement type: Functional

14
Title: Manage the student’s fee

Description: User should be able to manage the student’s list e.g.

 Add a new student

 View an existing student’s list

 Save the list

 Delete any student.

Source: Requirement Engineers team

Rationale: In order for the User to manage the fee

2.2.1 Non Functional Requirements

Performance

 Response Time:
 The website shall give response in 5 second.
 Capacity:
 The website must support up to 50 people.
 User-interface:
 The user-interface screen shall respond within 5 seconds

Availability:

The ISAS Fee Management System Website shall be available all the time.
The website shall be low downtime.

Reliability:

The ISAS Fee Management System Website shall be reliable in use.

Usability:

The ISAS Fee Management System Website shall be easy to use for all users
either they belong to any field of life.

.
15
Diagram of Waterfall Model:

Figure 1 Waterfall Model

2.3 System Development Life Cycle

Figure 2 System development life cycle

16
2.4 System Analysis

The goal of system analysis is to determine where the problem is, in an attempt to fix
the system. This step involves breaking down the system in different pieces to analyze
the situation, analyzing project goals, breaking down what needs to be created and
attempting to engage users so that definite requirements can be defined.

2.4.1 Design

In systems design the design functions and operations are described in detail,
including screen layouts, business rules, process diagrams and other documentation.
The output of this stage will describe the new system as a collection of modules or
subsystems.

The design stage takes as its initial input the requirements identified in the approved
requirements document. For each requirement, a set of one or more design elements
will be produced as a result of interviews, workshops, and/or prototype efforts.

Testing
The code is tested at various levels in software testing, Unit, system and user
acceptance testing’s often performed. This is a grey area as many different opinions
exist as to what the stages of testing are and how much, if any iteration occurs.
Iteration is not generally part of the waterfall model, but usually some occur at this
stage. In the testing the whole system is tested one by one

Following are the types of testing:

 Defect testing the failed scenarios, including defect tracking

 Path testing
 Data set testing
 System testing
 Integration testing
 Black-box testing
 White-box testing
 Regression testing

17
Requirement Analysis

The primary objective of the requirement analysis is to analyze the information

relating top system requirements and then organize documents and present the
requirement of management.

2.5 Use Case Diagram

Use Case diagrams show the interaction between use cases, which represent
system functionality, and actors, which represent the people or systems that provide or
receive information from the system. Use cases represent the requirements of the
system from the user’s perspective. So, use cases are the functionality that the system
provides. Actors are the stakeholders of a system but not all stakeholders are actors.

This use case diagram track the user status and admin login.

18
 Figure 3 Use case diagrams

2.6 Entity Relationship Diagram

An ERD is a data modeling technique that can help define business processes

and can be used as the foundation for a relational database.

Figure 4 Entity Relationship Diagram

19
2.7 Class Diagram:

Figure 5 Class Diagram

20
 Figure 6 Data Flow Diagram
2.8 System Design:

The most creative and challenging phase of the system life cycle is system design. It
refers to

technical specification that was applied in implementing the system. The purpose of
system design is to transform the information models that were developed during
analysis to model that confirm to target technology which was used for system
implementation. The stages that are involved in system design phases are:

 Input design
 Output design
 Database design

2.8.1 Input design

The input design includes the development of procedures and specifications for all
aspect of data entry and data input. Data capture refers to the identification and
recording of source data. Data entry is the process of converting source data into a
computer readable form.

2.8.2 Input form design

Most common way of data entry is form filling. Data can be retrieved display and
credit after entry using the same display. Following points are considered during the
form design:

 Messages remains on the screen long enough to be read.

 Screen presentation is consistent.

2.8.3 Code design

It plays an important role where several fields have a number of known values. Thus
its significant can be ignore. Codes are used due to following reasons

 Save computer storage

 Checking code is easier
 Speed up data retrieval
 Uniqueness can be enforced

21
 2.8.4 Output design
Output design phase of any system have system output which can be in the
form of queries and reports. The form of the reports and queries should be decided in
the beginning of the system design so it is necessary of the successful implementation
of the system that its outputs.

2.8.5 Consideration and report design

 Executive users
 Executive preferences
 Alternative design
 Culture
 Executive feedback
 Screen space limitations
 Text

Database design
The data is stored in computer in the form of tables so far an accurate and free of
anomalies system the tables designing is further divided into two parts;

 Logical database design

 Physical database design

22
2.9 Table Design:
2.9.1 Order-Table

Table 1 Order Table

2.9.2 Admin Table

Table 2 Admin Table

2.9.3 Product Table

Table 3 Product Table

23
 3 CHAPTER 3: System Components

3.1 Planning
In this phase, the requirements are gathered and defined after a comprehensive
system study of the various business processes. The purpose of planning phase is to
identify clearly the nature and scope of the problem, the project scope, constraints and
estimated cost and benefits and together enough information. Planning usually starts
with the written request that identify the information system and describe the desired
changes or improvements. This involve interviewing internal and external users,
preparation of detailed flow diagrams showing the process or processes for which
going to be develop the inputs and outputs in term of how the data is to be recorded or
entered.

The key idea is that the development of new information systems is

considered in the context of a well-thought-out business strategy, while purchase of
information system that are planned for development. Thus, the business strategy
drives the information technology strategy. The project is evaluated in term of
fulfillment of the mission statement and goals of the organization. So, this project
fulfils the mission statement of Ideal housing scheme Faisalabad as this provides ease
to the consumer. Planning is not a comprehensive data gathering activity.

Problems of existing system

 Interface of the existing system

 Data entry methods

 Documents they are using currently for data entry, e.g. Voucher, Purchase
order etc.

 Requirements of the users

 Requirements of the managing staff

24
  Project’s scope and constraints.

Planning Objective

The five objectives of planning are:

1. Understanding the nature of the system

2. Fixing the scope and constraints of the system request

3. Identify the advantages of the system

4. Estimate the time and cost for the system

5. Present a report to management describing the project and detailed

When planning is completed, performed the following six steps to ensure success:

 Obtained an authorization for the planning.

 Identified the information that is needed together.

 Obtained organization charts for department undergoing study

 Conductive interviews to obtain information

 Reviewed the system documentation and observed the operations to obtain

information

 Correlated the information required and presented results recommendations to

management

After the completion of this phase, a report is presented to top management. This
Technical Feasibility

 Operational Feasibility

 Economic Feasibility

3.2 Technical Feasibility

The purpose of assessing the technical feasibility is to gain an understanding of
the business ability to construct the developed system. This analysis should include an
assessment of the developed group’s understanding of the possible target hardware,

25
software and operating environment to be used as well as system size, complexity and
group’s experience with similarly system.

3.2.1 Operational Feasibility

An operational Feasibility system is one that is used effectively after it has been
developed benefits. In operational feasibility the following issues were inquired:

 Management support for the project?

 Training requirements for users of new system?

 Company’s support for providing the necessary resources for training?

System Analysis

System analysis phase is the second phase of the System Development life
cycle, also called as fact finding phase, and this is the second step in the object
oriented system analysis and design. This methodology asks the analyst to determine
what the objects of the system are, how they behave over time or in response to
events, and what responsibilities and relationship an object has to other objects. You
need to look at the objects as a system, their commonalities differences and how the
system needs to manipulate those objects. The purpose of this phase is to learn exactly
how the current system operates, to determine and document what the system should
do, and to recommend alternative solutions. Understanding the new system is very
important because it is impossible to design a new system without knowing the
existing system.

Analysis is the process of studying a problem to find the best solution to the
problem. It gives the target for design and implementation, In this phase, we build
models of the system. Transfer the business narrative into a graphical representation of
business information needs and rules. Confirm the model with the analysts and experts
(Fred, 1998).

Identification of the problem needed to be solved.

Defining the desired outcome.

26
Identifying and selecting one from among a number of alternative solutions that
address the problem and would result in the desires outcome.

Study and analyze the business requirements. Interview users any managers, to
identify the information requirements. Incorporate the enterprise and application
mission statements as well as any future system specification.

System Design

The most creative and challenging phase of the system life cycle is system
design. It refers to the technical specification that was be applied in implementing the
system. The purpose of system design is to transform the information models that
were developed during analysis to model that confirm to target technology, which was
be used for system implementation. The stages that are involved in System design
phase are: (Kendall, 2007).

 Input Design

 Output Design

 Database Design

3.2.2 Input Design

Input design includes the development of procedures and specifications for all
aspect of data capture, data entry and data input. Data capture refers to the
identification and recording of source data. Data entry is the process of converting
source data into a computer readable form. During data input the computer readable
source data is actually input to the information system.

Following are the different mechanisms adopted to snake the input design desirable.

3.2.3 Input Form Design

Most common way of data entry is form filling. Data can be retrieved, displayed and
credit after entry using the same display. One property of this system is that its forms
give a user-friendly interface. The form layouts are modeled in a manner, which

27
resembles to the existing paper work, with which users are familiar. Following points
are considered during the form design:

 Messages remain on the screen long enough to be read.

 Screen presentation is consistent.

 All messages included error messages are understandable.

 All screen displays are attractive and un-crowded.

 The information on a single screen is displayed in a meaningful logical order.

3.2.4 Code Design

It plays an important role where several fields have a field number of known
values. Thus its significance can be ignored. Codes are used due to following reasons

 Save computer storage.

 Checking code is easier.

 Speed up data retrieval.

 Uniqueness can be enforced.

3.2.5 Output Design

Output design phase of any system ha system outputs, which can be in the form
of queries and reports. The form of the report and queries should be decided in the
beginning of the system design, so it is necessary of the successful implementation of
the system that its outputs should meet the requirement of the property management.
In designing inputs following factors are kept in mind:

3.2.6 Consideration in Report Designing

 Executive users

 Executive preferences

 Alternative designs

 Culture

 Executive feedback

28
  Executives-designed screens

 System’s Features/constraints

 Screen space limitations

Database Designing

The data is stored in computer in form of tables, so far an accurate and free of
anomalies system the table designing I of key importance. Database designing is
further divided into two parts:

 Logical database design

 Physical database design

Logical Database Design

The process of constructing a model of the information used in an enterprise
based on a specific data model, but independent of a particular DBMS and other
physical considerations.

Physical Database Design

The process of producing a description of the implementation of the database

on secondary storage; it describes the storage structures and achieve efficient access of
the data.

29
3.2.6.1 Normalization

Remove Repeating

Remove Partial
Dependencies

Remove Transitive

Remove
Abnormalities

Remove Multi
Valued

Remove Remaining

Figure 7 Steps of Normalization

30
3.3 Table Designing

Due to logical arrangement of data in tables, the required data can be accessed
in process easily to form, reports and queries in least amount of time.

3.4 System Development

System development is the fourth phase of the System Development life cycle during
which we create, document and test new application software programs. In this phase,
physical effort of the Programmer is involved to develop the system, based on the
detail design specification documents design specification documents. The analyst
continues in its role, coordinating between the customers and the programmers for
understanding and clarification. For software development, it is necessary to identify
functional requirements of the system. For system development the selection of
hardware and software is very important task.

3.4.1 Software Selection

The selection of the software is very important factor to be considered during

the development phase of the new system. This choice depends on many factors
including current environment, amount of data to handle, and cost of programming.
After analyzing the problem and considering the organization’s needs, we have
selected VB.NET as front end tool and SQL SERVER as relational data base
management system for the development of this system because it has the capability to
handle a fairly large amount of data. It also provides relational database management
system available for personal and multi-user system. Hence this system was create
compatibility among other packages and data share easily. In the design phase of any
application development the first strategy to be considered is the tool selection.

So for achieve the task of the web development we have to select suitable tools.

3.4.2 Hardware Selection

For proposed system the minimum requirements of hardware are:

3.4.3 Server-side Hardware Requirements

 Core 2 Quad (or higher) Processor

31
  16GB RAM

 80 GB of Hard Disk

 Fax MODEM Devices (at least 2 devices)

3.4.4 Client-side Hardware Requirements

 Core 2 Due (or higher) Processor

 64 GB RAM or high

 250 GB of Hard Disk

 Wireless/LAN Card

 Peripheral Devices like Mouse and Keyboard

3.4.5 Client-side Software Requirements

 Internet Explorer 5.5/Netscape/Opera/Mozilla Firefox

 Cookies and JavaScript should be enabled.

3.4.6 Programming Language

Programming languages are interpreted in a way that web page authors can use
to perform a variety of operations. Two common examples of programming languages
are VB.Net, To use a page that contains programming language code, a web browser
must be able to interpret the code. Microsoft Internet Explorer version 6.0 can run
both VB.Net .

VBScript is great for transforming lifeless web pages into dynamic, fully interactive
page with real-time response. The VBScript has been used for client side validity.
There are many advantages for client side validity. The major advantage is that when
the user submit the form or make a request, that request does not have to go to web
server for validity, but the VBScript plays an important role and increase the
efficiency of the application by validating the application on the client side.Creating
and modifying data-related objects is performed in one place: the graphical data
environment.

32
 3.4.7 Data Environment
Creating and modifying data-related objects is performed in one place: the
graphical data environment. In the data environment, one can drag and drop objects
onto Active Server Pages (ASP) to automatically create data-bound design-time
controls.

3.4.8 SQL Server

SQL Server includes several new features that make it an excellent database
platform for large-scale online transactional processing (OLTP), data warehousing,
and e-commerce applications. SQL Server 2000 forms a high-performance data
storage service for Web applications running under IIS or accessing the database
through a firewall. Major features of SQL Server 2000 include:

3.5 Scalability and Availability

The same database engine can be used across platforms ranging from laptop
computers running Microsoft Windows® 98 through large, multiprocessor servers
running Microsoft Windows 2000 Data Center Edition.

3.6 Enterprise-Level Database Features

The SQL Server relational database engine supports the features required to
support demanding data processing environments. The database engine protects data
integrity while minimizing the overhead of managing thousands of users concurrently
modifying the database. SQL Server distributed queries allow you to reference data
from multiple sources as if it were a part of a SQL Server database, while at the same
time, the distributed transaction support protects the integrity of any updates of the
distributed data. Replication allows you to also maintain multiple copies of data, while
ensuring that the separate copies remain synchronized. You can replicate a set of data
to multiple, mobile, disconnected users, have them work autonomously, and then
merge their modifications back to the publisher.

3.7 Ease of Installation, Deployment and Use

SQL Server includes a set of administrative and development tools that

improve upon the process of installing, deploying, managing, and using SQL Server

33
across several sites. SQL Server also supports a standards-based programming model
integrated with the Windows DNA, making the use of SQL Server databases and data
warehouses a seamless part of building powerful and scalable systems. These features
allow you to rapidly deliver SQL Server applications that customers can implement
with a minimum of installation and administrative overhead.

3.8 Data Warehousing

SQL Server 2000 includes tools for extracting and analyzing summary data for
online analytical processing. SQL Server also includes tools for visually designing
databases and analyzing data using English-based questions.

3.8.1 Large Memory Support

SQL Server has high-speed optimizations that support very large database
environments. SQL Server version 6.5 and earlier can support databases from 200 GB
through 300 GB. SQL Server and SQL Server version 7.0 can effectively support
terabyte-sized databases.

SQL Server 2000 Enterprise Edition uses the Microsoft Windows 2000
Address Windowing Extensions API to support memory approaching 64 GB of RAM.
This allows SQL Server Enterprise Edition to cache large number of rows in memory,
which reduces overhead and speeds its ability to process queries (Vieira, 2007).

3.9 System Implementation and Valuation

The fifth and final phase of the system development life cycle is the system's
implementation. The implementation phase is firmly aimed at endures smooth and
efficient take over from existing system to a developed system. Here primary concern
is the process of converting the manual based system into a computerized information
system.

There may exist confusion to some extent, between these two terminologies,
conversion and implementation. Conversion is referred to as the significant
relationship between old system and new one whereas the practical job of putting a
theoretically designed system into practice is signified as implementation.

34
 Implementation project involves the activities like planning and scheduling of
implementation process, organizational planning and personnel administration, final
system design and testing, establishment of old to new system. The most important
and considerable process of implementation includes testing the system and
conversion plan. These two topics are discussed in detail.

3.9.1 System Testing

The basic aim of system testing is to know that the system designed for
implementation has achieved its objectives. Tests are performed according to the test
specification ad procedures. It is essential that the system designed is exhaustively
comprehensive in all the respects and it has been kept under certain limitations

Each program has been written in accordance with its specification. Specific
measures have been taken to perform testing on sample data. The following steps have
been taken for testing the system.

Each phase of the system is checked. Test data has been produced to ensure that range
of values that can be expected are acceptable. Comparison between outputs of new
system and manual system has been carried out.All the processing and tabulations are
to the required standard.

All documents produced by the system are completely accurate and properly
interfaced with manual procedures.

All the parts of the system have been interlinked.

In brief, the new developed system is at hand for the system converts.

3.9.2 Proposed Method of Conversion

All the conversion methods have been considered. After thorough analysis,
parallel conversion is recommended for proposed system. The significant objections
against the parallel conversion are the cost and additional workload. But the real
advantage of this system is that in case of its failure, data is not lost because the old
system still runs without any interruption. So the organizational work was not be
affected.

35
The parallel method involves containing; the former system for a certain period of
time after the new system is put into operation. This method was provide an
opportunity to compare its results with those obtained by the previous method.

Both the direct and pilot conversions are not suitable for the proposed system, because
for pilot conversion, the proposed system is not so vast as to fulfill the requirements of
conversion approach. In case of parallel conversion the old system was be available as
back up and the results produced can he compared to those of the old one.

3.9.3 System evaluation

The evaluation is to determine whether desired objectives are accomplished or
not. The properties of the system which were evaluated are:

 Efficiency

 Automation

 Portability

 Security

 User Friendly

 Modularity

36
3.10 User Manual

3.10.1 Home page

Figure 8 Home page

37
3.10.2 Admin Login

Figure 9Admin Login

38
3.10.3 View Submit Fee

Figure 10View Submit Fee

39
3.10.4 Submit Fee of Student

Figure 11Submit Fee of Student

40
3.10.5 User Manual

Navigation button Activity performed

Home
This button shows home page to admin.

Track status This button shows track status form to user.

Search
This button shows search there related
member.

Office detail

This button shows the all office detail.

Manager detail

This button shows all manager detail.

Logout

This button allows to user to logout from

its account.

41
 4 Conclusion and Result
The system evaluation is the process of' measuring the performance of the
existing system with the new developed system, Knowledge of the Property
management structure was helpful in decisions. Also present and future workload of
transactions and the ability of hardware and software to handle the workloads
adequately are evaluated. The evolution is not only necessary but also unavoidable to
keep the system updated in term of business and economic environment as well as
technological change in the electronic data processing. So the system which maintains
accuracy, timeliness and completeness is assessed as successful.

For the evaluation purpose testing is done on many different levels at various
intervals. It is accomplished on subsystems or program modules as work progresses.
Before the system was put into production, all programs desk-checked, checked with
test data, and checked to see if the modules work together with one another as
planned.

5.1 Output of the Developed System

The new system has many implications and have many advantages over the old
system, some of the advantages are:

Speed and Accuracy

The primary objectives of` the new developed system is to provide speed and
accuracy during data processing and report generation.

Information of Accuracy
This system provides timely correct retrieval of information in an accurate and
efficient manner. It is much faster than old system as it can complete a process within
fraction of seconds that was completing even in hours in old system. New developed
system is approximately error free.

Eliminating Data Redundancy

New system removes optimum redundancy, which was present in the old
system. So it have been tried to avoid redundancy as much as possible.

42
 User Friendly

The developed system provided user friendly environment for all users even
not having knowledge about the basics of the system. No specific computer staff is
required; one can easily process further and access the required information.

Managerial Acceptability

The data updating can be made in an easy way so that the management in
obtaining any type of report may not face any problem in dealing with it. In the old
system record was kept in registers data updating was very difficult but as data in
developed system is records in database so data updating is very easy.

Security

Security in a system provide safeguard in protecting system's data from

deliberate damage, accidental damage or access by unauthorized persons.

The developed system is much secured than the old system. It keeps back up of data at
three different servers.

Time Saving

Everyone wants quick response to his queries because decisions are based on
up to date information.

Results:
To provide the property management information and the user data this
developed system is very beneficial for Ideal Housing Scheme. This system is very
efficient and meets the requirements of the property management.

It was help the consumers of Ideal Housing Scheme to check the status of their
accounts timely online via Internet as well as the transaction made and any other can
check the information regarding billing anytime. The authorized staff of Ideal Housing
Scheme can make all the necessary DML operations and this system can be
implemented on the company’s intranet as well. Security is provided that only
authorized users can alter the data or make changes.

43
 5.2 Conclusion

To provide the information of both client and seller is very beneficial for Ideal
Housing Scheme. This system is very efficient and meets the requirements of the
management. It was help the property management to cheek previous record of client
whenever they needed. The management also checked their economic rate and output.
Security is provided that only authorized users can alter the data or make changes.

5.3 Summary

In whole world computer has almost captured all the shapes of life. It is now
the necessary of every business every home organization and any educational institute.
From last few years the development in the fields of computer information technology
and internet are marvelous. The whole world is gradually jumping on the paperless
economy.

The computer is like a double –edged sword. It has the ability to cut as free from
routine activities but it can also slice deeply into profits personal privacy and society
in general.

A system which utilizes electronic means especially computer is computer based

system. The application used in this project eventually lead to an increase usage of
computer and with better perfect and timely report. This is an era of centralized data
processing so the issue of data security was given due importance because the data
security protects the data in data base against unauthorized or accidental disclosure or
destruction.

Through this computer based system the information about the patient is provided in
an efficient manner. The speed and processing time of the system are quick enough
thus better data manipulation and correct results.

Different managerial reports are produced thus providing a ground for the decision
support system. In short the computer based version of this system unveiled a number
of facilities and advantages that he is available to management which helps them in
the doing their job efficiently.

The developed system has the following useful advantages over the manual system.

44
 It satisfies today needs for information.
 System is developed with window which is loaded with tools and program
that ensure the privacy and security of the data and help to operate
computer at peak performance.
 Information is easy to retrieve and is well organized because of graphical
user interface of forms and report. Also information can be represented in
many formats like charts and graphs.
 System is reliable enough to make the timely decisions. No batch file
initialization is needed as was the case with previous system but system
automatically initializes necessary files once started.
 Once the correct data is stored in database it remains correct.
 The speed and the processing time of the system is quick thus giving better
data manipulation and correct calculated results.

45