PROJECT REPORT

ON

ON-LINE TENDER MANAGEMENT

INDEX

S.NO. HEADING PAGE NO.

1. Abstract 4

1
 2. Introduction 6
 Company Profile 9
 Implementation Environment
 Front-End 26
 Back-End 11
 Hardware and software 30
Requirements
 Software Development Lifecycle 31

3. Conclusion 69

4. Bibliography 70

ABSTRACT

In current tender system a lot of paper work is involved. The system is based on
manual bid system which is a very time consuming process. No proper records
available which leads to difficulty in manual report generation. People who are
interested in tender have to travel long distances to gather at a common place.

2
Also manual work is always prone to errors and errors in such system can have
pretty bad consequences.

All the above issues are resolved in online Tender Management

System. Companies who want to enter their tender need to register online
through the website. After registering the company adds the various items which
are needed by the company as per its requirement. Now, when Client visits the
site it registers itself and can view the various tender. Thus, now can apply for the
tenders that are they fill up the various details required.

Company opens the tenders and select the appropriate of all tenders
after the deadline given to clients is over. All the tenders are displayed on the
website leading to transparency between clients and company.

In the span of the development of this project, I studied software

concepts, technical language details, testing issues, bug fixing and mobile
applications.

I started with studying the existing system and then pin pointing to the
specifications needed in the new system being developed. Later on I focused
more on coding details. After the coding was complete, thorough testing was
performed for verifying the system.

3
 Introduction….

Why .NET?

1. Interoperability between languages and execution environments

4
 2. Uniformity in schema or formats for Data Exchange using XML,

XSL

3. Extend or use existing code that is valid

4. Programming complexity of environment is reduced

The .NET Framework is…

1. A component model for the internet

2. The new approach to building large scale distributed systems for the

Internet

3. Provides the capability to integrate multiple devices

4. Built around the tools and protocols (XML, WSDL, SOAP, HTTP) that

are becoming standard on the Internet

The .NET in ASP.NET stands for the .NET Framework, a set of objects
and blueprints from Microsoft for building applications. All applications
developed under the .NET Framework; including ASP.NET applications,
have certain key features that ensure compatibility, security, and stability.

Fig:- .NET Framework Architecture

5
The .NET Framework Design Goals

1. Component Development for the Internet

2. "Cross-Language Development”
3. Inheritance, Debugging, Exception handling
4. Reliability and Security
5. Simple Development and Deployment
6. Device-agnostic

ASP.NET:
ASP.NET is a technology that allows us to build and control dynamic Web
pages easily. It also provides many enhancements to take advantage of
new technology as we can interact with databases, personalize Web
pages for visitors, display page on mobile devices (such as cell phones),
and even build an entire e-commerce site from scratch.

6
Previously internet works on request/response model that is an integral
part of client/server model. Although this is a marvelous way of
communicate and distribute information, it's rather simple and static. When
the process is over, once client receives the requesting page from the
server the server has no idea what the client is doing unless it makes
another request.

There is another model for communicating between server and clients,

known as event-driven model.ASP.NET work on this model, it detects
action and responds to them i.e. the server waits around for something to
happen on the client. Once it does, the server takes action and performs
some piece of functionality. Of course, a Web, server can not know what
you are thinking, but it can respond to your actions. If you type some text
on Web page, the server responds to it. If you click an image, the server
responds.

Company Profile:

7
Founded in 2000, with the mission of "Bringing People and Computers
Together...Successfully", C.S.Computer Edu, the IT Learning Solutions
Corporation, is known for its pioneering work in the field of IT education and
training. The company provides a comprehensive education environment to
individuals and enterprises, offerings training that is customized to the varied
needs of audiences with diverse backgrounds.

VISION

To be the leader in the development of industry oriented quality education and

training and be the country's premier Institution for certification in the field of
Information, Electronics and Communications Technology (IECT).

MISSION:

To be the single source for quality assurance in computer education among the
nation's institutes

Objectives:

 Establish itself as an Institution of excellence for imparting education and

training to generate quality manpower in the areas of Information,
Electronics and Communications Technology (IECT).

 Facilitate education and training Institutions in the non-formal sector.

 Develop a mechanism for dynamic revision of course curricula and

development of learning materials in the textbook, CD-ROM and web-
based form.

 Impart continuing education/refresher training/re-training and corporate

training to engineering graduates, working professionals and others.

8
 Develop and implement new schemes of Courses in emerging areas as
required by Industry and others.

 Undertake development projects and provide services in IT and related areas.

 Develop and establish a system for web-based delivery of education and

training.

Implementation Environment:

9
 Back-End:

DBMS
SQL SERVER:
SQL Server is an SQL-compliant RDBMS. SQL-compliant means it use the ANSI
(American National Standard Institute) version of Structured Query Language or
‘SQL’. Structured Query Language is a command that allow us to modify or
retrieve information from the database.
Client server means that SQL Server is designed to store data in the central
location (the server) and deliver it on demand to numerous other locations (the
client). SQL Server is also a Relational Database Management System
(RDBMS).

FEATURES OF SQL SERVER 2000:

1 Information representation

1 Unique definition of rows

1 Systematic treatment of Null values

1 Guaranteed access

1 High level Update, Insert, and Delete

1 Retrieving information from the database.

1 Accepting query language statements.

1 Enforcing security specifications.

1 Enforcing data integrity specifications

1 Enforcing transaction consistency

1 Managing data sharing

10
 1 Optimizing queries

13 Managing System catalogs

Enterprise Manager:

SQL Server Enterprise Manager is a graphical tool that allows easy

configuration and management of Microsoft SQL Server and SQL 2000
program group.

SQL Server Enterprise Manager can also be used to:

1. Manage logins, permission and users.

2. Create a database

3. Take back-up of database and transaction logs.

4. Manage tables

Query Analyzer:
The SQL Server Query Analyzer allows us to create adhoc queries and
run them interactively. We may also execute Transact-SQL statements
stored in text file and view the result in result plane or result grid. The
Query Analyzer also has a color-coded editor to assist the user with
checking of syntax. It also has context sensitive help.

Queries are processed in two steps:

Interpret- First the Queries are checked for syntax.

Execute- Then the processing take place.

11
Tables Used In The Project

1. Sysname

Field Name Data Type Size

ID Int 4
Xtype Tinyint 1
typestat Tinyint 1
xusertype Smallint 2
Length Smallint 2
Xprec Tinyint 1
Xscale Tinyint 1
Colid Smallint 2
Xoffset Smallint 2
Bitpos Tinyint 1
reserved Tinyint 1
colstat Smallint 2
cdefault Int 4
domain Int 4
number Smallint 2
colorder Smallint 2
autoval Varbinary 8000
offset Smallint 2
collationid Int 4
language Int 4
status Tinyint 1
type Tinyint 1
usertype Smallint 2
printfmt Varchar 255
prec Smallint 2
scale Int 4
iscomputed Int 4
isoutparam Int 4
isnullable Int 4
collation Sysname 128
tdcollation binary 5

12
 2. Syscomments

Field Name Data Type Size

Id Int 4
number Smallint 2
colid Smallint 2
status Smallint 2
ctext Varbinary 8000
texttype Smallint 2
language Smallint 2
encrypted Bit 1
compressed Bit 1
Text Nvarchar 4000

3. sysdepends

Field Name Data Type Size

Id Int 4
depid Int 4
number Smallint 2
depnumber Smallint 2
status Smallint 2
deptype tinyint 1
depdbid smallint 2
selall bit 1
resultobj bit 1
readobj bit 1

4. Sysfilegroups

Field Name Data Type Size

groupid smallint 2
allocpolicy smallint 2
status int 4
groupname sysname 128

13
 5. Sysfiles

Field Name Data Type Size

field smallint 2
groupid smallint 2
size int 4
maxsize int 4
growth int 4
status int 4
perf int 4
name nchar 128
filename nchar 260

6. Sysfiles1

Field Name Data Type Size

status int 4
field smallint 2
name nchar 128
filename nchar 260

7. Sysforeignkeys

Field Name Data Type Size

constid int 4
fkeyid int 4
rkeyid int 4
fkey smallint 2
rkey smallint 2
keyno smallint 2

8. Sysfultextcatalogs

Field Name Data Type Size

ftcatid smallint 2
name sysname 128
status smallint 2
path nvarchar 260

14
9. Sysfultextnotify

Field Name Data Type Size

tableid int 4
rowinfo smallint 2
ftkey varbinary 896

10. Sysindexes

Field Name Data Type Size

id Int 4
status VarChar 45
first Binary 6
indid Smallint 2
root Binary 6
minlen Smallint 2
keycnt Smallint 2
groupid Smallint 2
dpages Int 4
reserved Int 4
used Int 4
rowcnt Bigint 8
rowmodctr Int 4
reserved3 Tinyint 1
reserved4 Tinyint 1
xmaxlen Smallint 2
maxirow Smallint 2
origffillfactor Tinyint 1
statversion Tinyint 1
reserved Int 4
firstIAM Binary 6
impid Smallint 2
lockflags Smallint 2
pgmodctr Int 4
keys Varbinary 1088
name Sysname 128
statblob Image

15
maxlen 8000
rows

11. Sysindexkeys

Field Name Data Type Size

id int 4
indid smalint 4
colid smallint 25
keyno smallint 200

12. Sysmembers

Field Name Data Type Size

memberuid smallint 4
groupuid smallint 25

13. Sysobjects

Field Name Data Type Size

name sysname 128
id int 4
xtype char 2
uid smalint 2
info smallint 2
status int 4
base_schema int 4
_ver
replinfo int 4
parent_obj int 4
crdate datetime
ftcatid smallint 2
schema_ver
stats_schema_
ver
type
userstat

16
sysstat
indexdel
refdate
version
deltrig
instrig
updtrig
seltrig
category
cache

14. Syspermissions

Field Name Data Type Size

id int 4
grantee smallint 2
grantor smallint 2
actadd smallint 2
actmod smallint 2
seladd varbinary 4000
selmod varbinary 4000
updadd varbinary 4000
updmod varbinary 4000
refadd varbinary 4000
refmod varbinary 4000

15. Sysproperties

Field Name Data Type Size

id int 4
smallid smallint 2
type tinyint 1
name sysname 128
value sql_variant

16. Sysprotects

17
Field Name Data Type Size
id int 4
uid smallint 4
action tinyint 50
protecttype tinyint
columns varbinary
grantor smallint

17. Sysreferences

Field Name Data Type Size

constid int 4
fkeyid int 4
rkeyid int 4
rkeyindid smallint 2
keycnt smallint 2
forkeys varbinary 32
refkeys varbinary 32
fkeybid
rkeybid
fkey1
fkey2
fkey3
fkey4
fkey5
fkey6
fkey7
fkey8
fkey9
fkey10
fkey11
fkey12
fkey13
fkey14
fkey15
fkey16
rkey1
rkey2
rkey3
rkey4
rkey5
rkey6

18
rkey7
rkey8
rkey9
rkey10
rkey11
rkey12
rkey13
rkey14
rkey15
rkey16

18. Sysusers

Field Name Data Type Size

Uid smallint 4
status smallint
name sysname
Sid varbinary
roles varbinary
createdate datetime
updatedate datetime
altuid smallint
password varbinary
Gid
environ
hasdbaccess
islogin
isntname
isntgroup
isntuser
issqluser
isaliased
issqlrole
isapprole

19. tbapp

Field Name Data Type Size

19
appcod int 4
appdat datatime
apptndcod int 4
appusrcod int 4

20. tbappdsc

Field Name Data Type Size

appdsccod int 4
appdscitmcod int 4
appitmqty int 4
appitmrat int 4
appitmdsc varchar 100

21. tbclt

Field Name Data Type Size

cltcod int 4
cltnam varchar 50
cltadd varchar 50
cltphn varchar 50
cltfax varchar 50
clteml varchar 50
cltcntper varchar 50
cltctycod int 4

22. tbcnt

Field Name Data Type Size

cntcod int 4
cntnam varchar 50

23. tbcty

20
Field Name Data Type Size
ctycod int 4
ctynam varchar 50
ctystacod int 4

24. tbitm

Field Name Data Type Size

itmcod int 4
itmnam varchar 50
itmdsc varchar 200
itmcltcod int 4

25. tblog

Field Name Data Type Size

logcod int 4
lognam varchar 50
logpwd varchar 50
logrol varchar 50

26. tbsta

Field Name Data Type Size

stacod int 4
stanam varchar 50
stacntcod int 4

27. tbtnd

Field Name Data Type Size

tndcod int 4
tndcltcod int 4
tndsecamt int 4
tndlstappdat datetime
tndopnappdat datetime
tnddat datetime
tndtrmandcon varchar 200

21
28. tbtnddet

Field Name Data Type Size

tnddettndcod int 4
tnddetitmcod int 4
tnddetitmqty int 4

29. tbtndres

Field Name Data Type Size

tndrestndcod int 4
tndresappcod int 4
tndresrem varchar 100
tndresdat datetime

30. tbusr

Field Name Data Type Size

usrcod int 4
usrnam varchar 50
usradd varchar 100
usrphn varchar 50
usrfax varchar 50
usrmbl varchar 50
usreml varchar 50
usrctycod int

22
 STORED PROCEDURES USED

 Delapp  Fndtnd
 Delappdsc  Fndtnddet
 DelClt  Fndtndres
 Delcnt  Fndusr
 Delcty  Insapp
 Delitm  Insappdsc
 Dellog  Insclt
 Delsta  Insitm
 Deltnd  Inscnt
 Deltnddet  inscty
 Deltndres
 Delusr
 Dspapp
 Dspappdsc
 Dspclt
 Dspcnt
 Dspcty
 Dspitm
 Dsplog
 Dspsta
 Dsptnd
 Dsptnddet
 Dsptndres
 Dspusr
 Fndapp
 Fndappdsc
 Fndclt
 Fndcltcty
 Fndcnt
 Fndcty
 Fndctysta
 Fnditm

FRONT-END

23
 ScreenShot Of Home Page

ScreenShot Of Project Information

24
25
ScreenShot Of Products Used

26
ScreenShot Of Tender Information

27
 HARDWARE REQUIREMENTS

The system must have the following hardware requirements:

1 Pentium IV Processors
2 256 MB of RAM
3 5GB of Hard Disk
4 Server Machine
5 Client Machine

SOFTWARE REQUIREMENTS

The system must have the following software requirements:

1 Visual Basic .Net (version 2.0)

2 Visual Basic .Net Framework (version 2.0)
3 SQL Server 2000/2005

28
 Software Development Lifecycle

FEASIBILILTY ANALYSIS
Feasibility study is done so that an ill-conceived system is recognized early in
definition phase. During system engineering, however, we concentrate our
attention on four primary areas of interest. This phase is really important as
before starting with the real work of building the system it was very important
to find out whether the idea thought is possible or not.

1 Economic Feasibility: An evaluation of development cost weighted

against the ultimate income or benefit derived from the developed system.

2 Technical Feasibility: A study of function, performance and constraints

that may affect the ability to achieve an acceptable system.

3 Operational Feasibility: A study about the operational aspects of the

system.

1.1 ECONOMIC ANALYSIS

Among the most important information contained in feasibility study is Cost
Benefit Analysis and assessment of the economic justification for a computer
based system project. Cost Benefit Analysis delineates costs for the project
development and weighs them against tangible and intangible benefits of a
system. Cost Benefits Analysis is complicated by the criteria that vary with the
characteristics of the system to be developed, the relative size of the project
and the expected return on investment desired as part of company’s strategic
plan. In addition, many benefits derived from a computer-based system are
intangible (e.g. better design quality through iterative optimization, increased
customer satisfaction through programmable control etc.)As this is an in-
house project for the company, to be used for its own convenience and also it

29
 is not that big a project. So neither it requires a huge amount of money nor
any costly tools or infrastructure need to be set up for it.

1.2 TECHNICAL ANALYSIS

During technical analysis, the technical merits of the system are studied and
at the same time collecting additional information about performance,
reliability, maintainability and predictability.
Technical analysis begins with an assessment of the technical viability of the
proposed system.

1 What technologies are required to accomplished system function and

performance?

2 What new materials, methods, algorithms or processes are required and

what is their development risk?

3 How will these obtained from technical analysis form the basis for another
go/no-go decision on the test system? If the technical risk is severe, if
models indicate that the desired function can not be achieved, if the
pieces just won’t fit together smoothly-it’s back to the drawing board.

As the software is vary much economically feasible, then it is really important

for it to be technically sound. The software will be build among:

1 MS SQL SERVER as Back End

2 ASP.NET as Front End

1.3 Operational Feasibility

The project is operationally feasible. This project is being made for the
convenience of the patients and doctors only. This system will greatly reduce

30
 a huge burden of doctors. So because of the above stated advantages the
users of the system will not be reluctant at all.

SYSTEM ANALYSIS

INTRODUCTION:

System analysis is the process of studying the business processors and

procedures, generally referred to as business systems, to see how they can
operate and whether improvement is needed.
This may involve examining data movement and storage, machines and
technology used in the system, programs that control the machines, people
providing inputs, doing the processing and receiving the outputs.

INVESTIGATION PHASE
The investigation phase is also known as the fact-finding stage or the analysis of
the current system. This is a detailed study conducted with the purpose of
wanting to fully understand the existing system and to identify the basic
information requirements. Various techniques may be used in fact-finding and all
fact obtained must be recorded.

A thorough investigation was done in every effected aspect when determining

whether the purposed system is feasible enough to be implemented.

INVESTIGATION
As it was essential for us to find out more about the present system, we used the
following methods to gather the information: -

1. Observation: - Necessary to see the way the system works first hand.

31
2 Document sampling: - These are all the documents that are used in the
system. They are necessary to check all the data that
enters and leaves the system.

3 Questionnaires: - These were conducted to get views of the other employees

who are currently employed in the system.
ANALYSIS OF THE INVESTIGATION

Strengths of the System

1. No complex equipment: - The equipment that is used is very simple and no

special skills have to be mastered to be able to
operate the system. Therefore no training is required
for the employees.

2. Low cost: - There is little money spent in maintaining the present

system other than buying the necessary office
equipment and the ledgers.

CONSTRAINTS AND LIMITATIONS

The constraints and limitation within a system are the drawbacks that occur
during the implementation of the system. These limitations and constraints can
crop up in almost every system; the most important fact is to find a way to
overcome these problems.

Software design is the first of three technical activities – design, code

generation, and test that are required to build and verify the software.
Each activity transforms information in manner that ultimately results in
validated computer software.

32
The design task produces a data design, an architectural design, an
interface design and component design.

The design of an information system produces the details that clearly

describe how a system will meet the requirements identified during system
analysis. The system design process is not a step by step adherence of
clear procedures and guidelines. When I started working on system
design, I face different types of problems; many of these are due to
constraints imposed by the user or limitations of hardware and software
available. Some times it was quite difficult to enumerate that complexity of
the problems and solutions thereof since the variety of likely problems is
so great and no solutions are exactly similar however the following
consideration I kept in mind during design phased.

Design objectives:-

The primary objective of the design is to deliver the requirements as

specified in the feasibility report. These are the some of the objectives,
which I kept in mind.

 Practicality: The system is quite stable and can be operated

by the people with average intelligence.

 Efficiency: I tried to involve accuracy, timeliness and

comprehensiveness of the system output.

 Cost: It is desirable to aim for the system with a minimum

cost subject to the condition that it must satisfy the entire
requirement.

 Flexibility: I have tried that the system should be modifiable

depending on the changing needs of the user. Such
modifications should entail extensive reconstructing or
recreation of software. It should also be portable to
different computer systems.

33
  Security: This is very important aspect which I followed in
this designing phase and tried to covers the areas of
hardware reliability, fallback procedures, and physical
security of data.

INITIAL STUDY AND FEASIBILITY ANALYSIS

INITIAL STUDY

INTRODUCTION:

The first step in the Software Development Life Cycle (SDLC) is the
preliminary investigation to determine the feasibility of the system. The
purpose of the preliminary investigation is to evaluate project requests. It
is not a design study nor does it include the collection of details to
describe the business system in all aspect. Rather it is the collection of the
information that helps committee members to evaluate the merits of the
project request and make an informed judgment about the feasibility of the
proposed project.

The preliminary investigation should accomplish the following

objectives.

1. Clarify and understand the project request

2.Determine the size of the project.

3.Assess costs and benefits of alternative approaches.

4.Determine the technical and operational feasibility of alternative

approaches

5.Report the findings to management; with recommendations outlining the

acceptance or rejection of the proposal.

34
REQUIREMENT AND FEASIBILITY ANALYSIS

INTRODUCTION:

WHAT IS A FEASIBILITY STUDY?

Prior to stating whether the system we have to develop is feasible or not we
believe that we should emphasize on what is implied by the word “Feasibility”.
Feasibility is the measure of how beneficial or practical the development of the
system will be to the organization. It is a preliminary survey for the systems
investigation. It aims to provide information to facilitate a later in-depth
investigation.

The report produced at the end of the feasibility study contains suggestions and
reasoned arguments to help management decide whether to commit further
resources to the proposed project.

Within the scheduled duration we were assigned to study both the positive and
negative aspects of the current manual system, in which we have come up with a
number of drawbacks that prevent the progress of the clinic if it is continued to
function manually.

Having gone through all measures of feasibility we report to the management to

figure out if the objectives of the new system are met.

For e.g. - Is the system within the budget allowed for it?

Will the organizations needs, be met by the new proposed system as

Originally envisaged?

If and when the objectives of the system are met and the new system is
approved, then the more specific details in the proposal should be considered
and approved.

TYPES OF FEASIBILITY

35
There are various measures of feasibility that helps to decide whether a
particular project is feasible or not. These measures include-

1 Operational Feasibility
2 Technical Feasibility
3 Economical and Financial Feasibility

Each of these types will be explained in detail throughout the project report.

OPERATIONAL FEASIBILITY
A proposed system is beneficial only if it can be turned into an information
system that will meet the operational requirements of an organization. A system
often fails if it does not fit within existing operations and if users resist the
change.

Important issues a systems developer must look into are:

1 Will the new system be used if implemented in an
organization?
2 Are there major barriers to implementation or is proposed
system accepted without destructive resistance?

The whole purpose of computerizing the Tender System is to handle the work
much more accurately and efficiently with less time consumption. There will be
additional work to be completed, because now the contractors can submit their
tenders online. Their database is maintained separately.

Compared to the semi-computerized system the chances of avoiding errors in a

computerized system is much higher because the user need not stress himself
unnecessarily resulting in recklessness. Unlike the semi-computerized system

36
there would be backup data for all the information concerning the daily
transactions occurred within the organization.
If we are considering the performance and response time for each task, it is very
much faster since there is less paper work to be completed. When entering data
into the system to relieve the user from additional work and typing incorrect data,
the system provides options such as combo boxes, check boxes, option buttons
and etc. if the users type in incorrect data they would be informed immediately
about the error by the error detection control.

Another important fact to be regarded is the security control, which is handled by

the system. Since data regarding each contractor and the company is
confidential, security is a key issue. Information falling into the wrong hands
could jeopardize the entire organization. Unlike in semi-computerized systems
the proposed system offers adequate control to protect the organization against
fraud and embezzlement and guarantees the accuracy and security of data and
information. This is handled by the system providing each department and
individuals with separate login names and passwords.

The new system is more user-friendly, which enables the end-user to complete
his/her work efficiently and accurately with interest. After taking the above fact
into consideration we can state the operating of the proposed system within the
organization is feasible.

In this phase of the feasibility study the following two main topics
1 Technical Performance Aspect
2 Acceptance within the organization

Technical performance aspect is explained in the technical feasibility report and

there is no new information is needed in this to explain it again, but as for the
acceptance within the organization the following points are important and those
are explained according to the topics

37
 1. Whether the system provides right information to the right place.

In the current system which is the semi computerized system the information
may be lost in the process of sending from one place to another. This is mainly
due to human interaction in the process of the transferring information from one
place to another.

2. Whether the new system affect the current users in the system

The new proposed system will affect the users in the following areas
 Accuracy
 Efficiency
 Productivity
 Robustness
 Lesser time consuming

3. Skill and attitude

This system is developed according to the experience of the current employees

and the management structure, so for this system to function within the current
employee community. The employees do not need to have new skills other than
the skills which are gained in the current system.

4. Job restructuring and training

For the new system to have an effect in the organization the employees should
be give a proper training in operating the software and computer systems. If the
employee does not have the minimal experience should be given the proper
training

38
If the organization is reluctant to give a full training to the employees who require
the full knowledge organization can restructure the structure of the departments.

TECHNICAL FEASIBILITY
Based on the outline design of system requirements in terms of inputs, outputs,
files, procedures and staff, the technical issues raised during technical feasibility
include:
1 Does the necessary technology exist to do what is
proposed?
2 Does the proposed equipment have the technical capacity to
hold the data required to use in the new system?
3 Adequate responses provided by the proposed system?
4 Is the system flexible enough to facilitate expansion?
5 Is there any technical guarantee of accuracy, reliability, ease
of access and data security?

The system developer’s task is to view needed capabilities in light of currently

available technology. Since the existing system is semi-computerized it is clear to
us that there is no efficiency in the use of technology within the organization. The
solution is the implementing the new computerized system, which works hand in
hand with high technology.

A database has to be maintained in order to update and backup data whenever a

transaction occurs. To create databases we use SQL server.

After taking the above facts into consideration we can state that the new
proposed system is technically feasible.

SYSTEM SECURITY

39
System security is a vital aspect when it comes to developing a system. The
system should ensure the facility of preventing unauthorized personnel from
accessing the information and the data within the system. The system should
provide total protection for each user’s information so that the integrity of data is
sustained and also prevent hackers from hacking the system.

The proposed system ensures the security and the integrity of data. This is done
by providing a password login system for each authorized users. And for example
the System Administrator has access to all kinds of information.

By providing this facility information is properly managed and information is

protected. For example the system administrator’s day to day tasks are lessened
and easier because he doesn’t have to have a constant eye on the system and
worry about hackers hacking the system.

ECONOMICAL AND FINANCIAL FEASIBILITY

In making recommendations a study of the economics of the proposed system
should be made. The proposed system must be justifiable in terms of cost and
benefit, to ensure that the investment in a new/changed system provide a
reasonable return.

Cost-benefit analysis of information is complicated by the fact that many of the

systems cost elements are poorly defined and that benefit can often be highly
qualitative and subjective in nature.

In our proposed system various costs are evaluated. Even though finding out the
costs of the proposed project is difficult we and assume and estimate the costs
and benefits as follows.

According to the computerized system we propose, the costs can be broken

down to two categories.

40
 1. Costs associated with the development of the system.
2. Costs associated with operating the system.

SOFTWARE REQUIREMENT SPECIFICATION

The software requirement specification is produced at the culmination of

the analysis task. The function and performance allocated to software as
part of system engineering are refined by establishing a complete
information description, a detailed functional description, a representation
of system behavior, an indication of performance requirement and design
constraints appropriate validation criteria, and other information pertinent
to requirement.

The introduction to software requirements specification states the goals

and objectives of the software, describing it in the context of the computer
based system.

The Information Description provides a detailed description of the problem

that the software must solve. Information content, flow and structure are
documented.

A description of each function required to solve the problem is presented

in the Functional Description.

Validation Criteria is probably the most important and ironically the most
often neglected section of the software requirement specification.

Software requirement specification can be used for different purpose.

Here are the major uses.

Statement of user needs:

41
A main purpose of the product specification is to define the need of the
product’s user. Some times, the specification may be a part of a contract
sign between the producer and the user. It could also form part of the user
manuals. A user‘s needs are sometimes not clearly understood by the
developer. If this is the case, a careful analysis – involving much
interaction with the user should be devoted to reaching a clear statement
of requirements, in order to avoid possible misunderstandings.

Sometimes, at the beginning of a project, even the user has no clear idea
of what exactly the desired product is. Think for instance of user interface ,
a user with no previous experience with computer products may not
appreciate the difference between , say menu driven interaction and a
command line interface. Even an exact formation of system functions and
performance may be missing an initial description produced by an
inexperienced user.

A statement of the requirements for the implementation:

Specifications are also used as a reference point during product

implementation. In fact, the ultimate goal of the implementation is to
build a product that needs specification. Thus the implementers use
specifications during design to make design decisions and during
the verification activity to check that the implementation compiles
with specifications.

42
 Procedure for Implementation

Project plan
System test
implementation
Implementation plan

Conversion plan of the

implementation plan finalized

Perform file conversion

Perform parallel processing

Log results of conversion

Diagnose and correct

Any
discrepancies
discrepancies
?

Implementation Discontinue parallel

results processing

Complete conversion
Implementation
documents
Prepare plan for post
implementation

43
SYSTEM DESIGN

INTRODUCTION:

System design is the process of developing specifications for a candidate system that
meet the criteria established in the system analysis. Major step in system design is the
preparation of the input forms and the output reports in a form applicable to the user.The
main objective of the system design is to make the system user friendly. System design
involves various stages as:

1 Data Entry

1 Data Correction

1 Data Deletion

1 Processing

1 Sorting and Indexing

1 Report Generation

System design is the creative act of invention, developing new inputs, a

database, offline files, procedures and output for processing business to
meet an organization objective. System design builds information
gathered during the system analysis.

CHARACTERSTICS OF A WELL DEFINED SYSTEM

In design an efficient and effective system is of great importance to

consider the human factor and equipment that these will require to use.
System analyst must evaluate the capabilities and limitations of the
personal and corresponding factors of the equipment itself.

44
The characteristics associated with effective system operations are:

 Accessibility

 Decision Making Ability

 Economy
 Flexibility
 Reliability
 Simplicity

Personnel:

If the operating system is convinced that the new system will not benefit
them, it appears one, and the system is in serious trouble. To overcome
this resistance participation by operating personal during all phases of the
changeover is necessary because they constitute the organization, which
must use alive in with newly design system. An effective system produces
not only information at the lowest cost pertinent and timely for making
decision.

SCHEMA DESIGN:

INTRODUCTION:

In database design, several views of data must be considered along with

the persons who use them. In addition to data structuring, where
relationships are reflected between and within entities, we need to identify
the application program’s logical views of data within an overall logical
data structure. The logical view is what the data look like, regardless of
how they are stored. The physical view is the way data exist in physical
storage. It deals with hoe data are stored, accessed, or related to other
data in storage.

45
The schema is the view that helps the DBMS decide in storage act upon
as requested by the application program.

RELATIONAL MODEL:

Certain rules followed in creating and relating databases in the relational

databases. This governs how to relate data and prevent redundancy of the
data in the databases. The first set of rules called relational rules ensures
that the database is a relational database. The second set called the
normalization rules simplifies the database and reduce the redundancy of
the data.

CODE DESIGN

When large volumes of data are being handled, it is important that the
item be identified, stored or selected easily and quickly. To accomplish
this, each data item must have unique identification and must be related to
other items of the same type. Codes can provide brief identification of
each item, which replace longer description that would be more awkward
to store and manipulate.

The ability to interrupt codes, evaluate coding schemes and devices new
or improved codes are important skills for a system analyst. Common
types of codes are:

SEQUENCE CODES:

A sequence code has no relation to the characteristics of an item. Here a

dictionary is required. The data is arranged alphabetically and numbered
sequentially. When a new data item is added it is given the next sequence
number. The advantage of this code is that it has the ability touched with
an unlimited number of digits.

46
SIGNIFICANT DIGIT CODE:

It is a code in which the number describes measurable physical

characteristics of the item.

ALPHABETIC CODE:

Here, the item are specified by the user of letter and number
combinations,

SELF CHECKING CODE:

It uses a check digit to check the validity of codes. These types of codes
are an important means of controlling the validity of data that are being
processed.

VALIDATION CHECKS:

A common problem with computer system is that it is very easy to put

incorrect data into them. So the input data is validated to minimize errors
and data entry. For certain data specific code has been given and
validations are done which enable the user to enter the required data and
correct them if they have entered wrong codes, e.g. you could mistype a
link name or a URL in a database resulting in reports being occurred in the
wrong link name. if you put incorrect data into the computer system then
you will get incorrect results out of it. Processing incorrect inputs will
produce incorrect outputs. This lead to the acronym: GIGO (Garbage In
Garbage Out).

Sometimes incorrect data can actually cause a computer system to stop

work temporarily. This is a particular problem in batch processing systems
when data may be processed overnights. If incorrect data stops a batch
processing systems for working then a whole night processing time may
be lost.

47
People who develop computer systems go to a lot of trouble to make it
difficult for incorrect data to be entered. The two main techniques used for
this purpose are:

 VERIFICATION

 VALIDATION

VERIFICATION:

A verification check ensures that data i9s correctly transferred into a

computer from the medium that it was originally stored on. Verification
checks are usually used to check that a data entry worker has correctly
typed information written on a data collection form into a computer.

Methods of Verification:

The two most common methods of verification are:

 On-Screen prompts: After a user has entered some data it is

redisplayed on the screen. The user is prompted to read the
data and confirm that it has been entered correctly. If the
user has entered any data incorrectly he should response
that the data is inaccurate and retypes the incorrect parts.

 Dual Inputs: This method is used when data is entered through

the keyboard. The data to be entered is typed in twice by two
different operations. The two copies of data are been
compared, any difference are detected, the operators will be
prompted to retype the sections that differ until both copies
agree/. When the two copies agree the computer assumes
that the data has been entered correctly.

48
VALIDATION:

A validation check is an automatic check made by computer to ensure that

any data entered into the computer is sensible. A validation check does
not make sure that data has been entered correctly. It only ensures that
data is sensible. For this reason validation checks are not usually as
effective as verification checks. They can however be carried out
automatically by the computer and therefore require less work by the
computer operators making them cheaper to use.

Methods of validation:

There are many different methods of validations. The most appropriate

method to use will depend upon what data is being entered. The most
common methods are listed here.

 Presence Checks: checks that data has been entered

into the field and that it has not been left blank, e.g.
checks that Project ID is always entered into each
record in a database of project details.

 Type Checks: checks that an entered value is of

particular type. E.g. checks that a field is varchar, a
number, etc.

 Length Checks: checks that an entered value, e.g.

Project ID is no longer than a particular number of
characters.

 Format Checks: Checks that an entered value has a

particular format. E.g. a date must be consist of “mm-
dd-yy” format.

Validation checks can be performed by any piece of software. If the user

tries to do unauthorized operations the appropriate error messages are
produced by the systems.

49
DATA DICTIONARY:

In our DFD, we give names to data flows, processes, and data stores.
Although the names are descriptive of the data, they do not give details.
So the following the DFD, our interest is to build some structured place to
keep details of the contents of data flow, processes, and data store. A data
dictionary is a structured repository of data about data. It is a set of
rigorous definition of all DFD data element and data structure.

A data dictionary has many advantages. The most obvious is

documentation; it is valuable reference in any organization. Another
advantage is improving analyst/user communication by establishing
consistent definition of various elements, terms and procedures. During
implementation, it serves as a common base against which programmers
who are working on the system compare data description. Also control
information maintained for each data element is cross referenced in the
data dictionary. E.g. program that use a given data element are cross
referenced in a data dictionary, which makes it easy to identify them and
make any necessary changes. Finally, a data dictionary is an important
step in building a database. Most database management system has a
data dictionary as a standard feature.

INPUT DESIGN:

The input design is the link between the information system and the user.
It comprises developing specification and procedure for data preparation
and those steps that are necessary to put transaction data into a usable
form for processing data entry. The activity of putting data into the
computer for processing can be achieved by instructing the computer to
read data from a written or printed document or it can occur by having
people key data directly into the system. The design of inputs focuses on
controlling the amount of inputs required, controlling errors, avoiding
delay, avoiding extra steps and keeping the process simple.

50
The system needs the following information for processing:

 Information regarding Project Details

 Information regarding Project Design Details

 Information regarding Category, Location Details

 Information Employees Details

OUTPUT DESIGN:

In output design, emphasis is given on producing a hard copy of the

information required as the output on the CRT screen in some predefined
manner. Computer output is the most important and direct source of
information to the use. Output design is a process that involves designing
necessary outputs that should be given to various users according to their
requirements. Efficient, intelligible output design should improve the
system’s relationship with the user and help in decision making. Since the
reports are directly referred by the management for taking the decisions
and to draw conclusions, they must be designed with utmost care and the
details in the reports must be simple, descriptive and clear to the user. The
options for the outputs and reports are given the system menu.

IMPLEMENTATION AND TESTING

IMPLEMENTATION

51
INTRODUCTION:

Implementation is the stage in the project where the theoretical design is

turned into the working system and is giving confidence to the new system
for the users i.e. will work efficiently and effectively. It involves careful
planning, investigation of the current system and its constraints on
implementation, design of method to achieve the change over, an
evaluation, of change over methods. A part from planning major task of
preparing the implementation is education of users. The more complex
system is implemented, the more involved will be the system analysis and
design effort required just for implementation. An implementation
coordinating committee based on policies of individual organization has
been appointed. The implementation process begins with preparing a plan
for the implementation for the system. According to this plan, the activities
are to be carried out, discussions may regarding the equipment has to be
acquired to implement the new system.

Implementation is the final and important phase. The most critical stage is
in achieving a successful new system and in giving the users confidence
that the new system will work and be effective. The system can be
implemented only after thorough testing is done and if it found to working
according to the specification. This method also offers the greatest
security since the old system can take over if the errors are found or
inability to handle certain types of transaction while using the new system.

At the beginning of the development phase a preliminary implementation

plan is created to schedule and manage the many different activities that
must be integrated into plan. The implementation plan is updated
throughout the development phase, culminating in a change over plan for
the operation phase. The major elements of implementation plan are test
plan, training plan, equipment installation plan, and a conversion plan.

52
There are three types of implementation:

 Implementation of a computer system to replace a manual system.

 Implementation of a new computer system to replace an existing system.

 Implementation of a modified application to replace an existing one, using

the same computer.

Successful implementation may not guarantee improvement in the

organization using the new system, but improper installation will prevent it.
It has been observed that even the best system cannot show good result if
the analysts managing the implementation do not attend to every
important detail. This is an area where the systems analysts need to work
with utmost care.

IMPLEMENTATION TOOLS:

 Training personnel

 Conversion Procedures

 Post-implementation review

Training of Personnel involved with system

Even well designed system can succeed or fail because of the way they
are operated and used. Therefore, the quality of training received by the
personal involved with the system in various capacities helps or hinders
and may even prevent the successful implementation of management
information system.

53
Those who are directly or indirectly related with the system development
work must know in detail what must know in detail what their roles will be,
how they can make efficient use of the system and what the system will or
will not do for them. Both system operators and users need training.

System Operators Training

Running of the system successfully depend on the personnel working in

the Computer Centre. They are Responsible for providing the necessary
support. Their training must ensure that they are able to handle all
possible operations, both routine and extra-ordinary in nature.

If the system calls for the installation of new equipment, such as new
computer system, special terminals or different data entry machines, the
operators training should include such fundamentals as how to turn the
equipment on and use it, how to power off and a knowledge of what
constitutes normal operations. The operators should also be trained on
different type of malfunctioning, how to recognize them and what steps
should also be taken whenever they arise.

User Training

User may be trained on use equipment, particularly in the case where, e.g.
a micro computer is in use and individual involved is both operator and
user. In such cases, user must be given training on how to operate and
user. In such cases, user must be given training on how to operator the
system also. Questions that may be trivial to the analyst, such as how to
turn on a terminal, how to insert a diskette into a micro-computer or when
it is safe to turn off equipment with out danger of data loss are significant
problems to new users who are not familiar.

Inmost of the cases user training deals with the operation of the system
itself, with proper attention given to data handling techniques. It is
imperative that users be properly trained in methods of entering

54
transaction, editing data, formulating inquiries, deleting and inserting of
records. No training is complete without familiarizing users with simple
systems maintenance activities. Weakness in any aspect of training may
lead of awkward situation that creates user frustration and error.

Conversion Methods

A conversion is the process of changing from the old system to the new
one. It must be properly planned and executed. Four methods are
common in use. They are Parallel Systems, Direct Conversion, Pilot
System and Phase In method. Each method should be considered in the
light of the opportunities that it offers and problems that it may create. In
general, system conversion should be accomplished in shortest possible
time. Long conversion periods create problems for all persons involved
including both analysts and users.

Parallel systems:

The most secure method of converting from an old to new system is to run
both systems in parallel. This method is safest one because it ensures
that in case of any problem in using new system, the organization can still
fall back to the old system without the loss of time and money.

The disadvantages of parallel systems approach are:

 It doubles operating costs.

 The new system may not get fair trial.

Direct conversion:

55
This method converts from the old system to new system abruptly,
sometimes over a weekend or even overnight. The old system is used
until a planned conversion day, when it is replaced by the new system.

Pilot system:

Pilot approach is often preferred in the case of the new system which
involves new techniques or some drastic changes in organization
performance. In this method, a working version of the system is
implemented in one part of the organization, such as a single work area or
department.

Phase –IN- method:

This method is used when it is not possible to install a new system

throughout an organization all at once. The conversion of files, training of
personnel or arrival of equipment may force the staging of the
implementation over a period of time, ranging from weeks to months.

POST IMPLEMENTATION REVIEW

After the system is implemented and conversion is complete, a review

should be conducted to determine whether the system is meeting
expectations and where improvements are needed. A post implementation
review measures the systems performance against predefined
requirement. It determines how well the system continues to meet the
performance specifications.

SYSTEM TESTING

INTRODUCTION:

The purpose of system testing is to identify and correct errors in the

candidate system. Testing is and important element of software quality

56
assurance ad represents the ultimate review of specification, design and
coding. The increasing visibility of the software as a system element and
the cost associated with a software failure are motivated forces for well
planned, through testing.

System testing was conducted in order to detect errors and for comparing
then the final system with the requirement specification reports, i.e.
whether the system meets requirements. During testing the software was
executed with the set of test cases and the output of programs for the test
cases was evaluated to determine if the program is performing as it was
expected to.

57
Testing presents an interesting challenge for the software engineers
attempt to build software from an abstract concept to an acceptable
implementation. In testing engineer create a series of test cases that
occurs when errors are uncovered. Testing is the process of executing a
program for finding errors. A good test is one that has the high probability
of finding an uncovered error. A successful error is one that uncovers
undiscovered errors.

The term error is used to refer the difference between actual output of the
software and the current output. Fault is a condition that causes the
software to fail to perform its required function. Software reliability is
defined as a required function. Software reliability is defined as the
probability that the software will not undergoes failures for a specified
times under specified condition. Failure is the inability of a system or a
component to perform a required function according to its specification.
Different levels of testing were employed for software to make it error free,
fault free and reliable.

Unit Testing:

Unit testing was conducted first. Different modules of the software were
tested against the specifications produced during design of the modules.
Verification of the code produced during the coding phase was done. Each
module was tested separately.

Unit testing focuses verification effort on the smallest unit of software

design module. This uncovers errors within the boundary of a module. Unit
testing is actually White box testing both the external things as well as the
internal codes are tested. In testing, the interfaces are tested in order to
ensure the proper flow of data in and out of the module. The boundary
testing is done to ensure that the module keeps the limit of it. All
independent paths are tested to ensure that all statements are tested at
least once. At last the error path is also tested.

58
Unit testing comprises the set of tests performed by an individual
programmer prior to integration of the unit into a larger system. There are
four categories of test that can be performed on a program unit

 Functional Unit

 Performance Unit

 Stress Unit

 Structure Unit

System Testing:

Then system testing was conducted. Here the entire software system was
tested.

The reference document used for this process was requirement document
and the goal was to see if the software meets its requirements.

System testing includes the thorough testing of the product. System

testing is actually a series of different tests whose primary purpose is to
fully exercise the computer based system. The tests are recovery testing:
this checks the recovery of the system when failure occurs. This is to
ensure that there are recovery procedures for error occurrences.

System testing involves unit testing, integration testing, acceptance

testing. Careful planning and scheduling are required to ensure that
modules will be available for integration into the evolving software product
when needed. A test plan has the following steps:

1 Prepare test plan

1 Specify conditions for user acceptance testing

1 Prepare test data for program testing

1 Prepare test data for transaction path testing

59
 1 Plan user testing

1 Compile/Assemble program

1 Prepare job performance aids

1 Prepare operational documents

Objectives of testing.
First of all objectives should be clear.
1 Testing as a process of executing a program with the intent of finding
errors.
2 To perform testing, test cases are designed. A test case is a particular
made up of artificial situation upon which a program is exposed so as to
find errors. So a good test case is one that finds undiscovered errors.
If testing is done properly, it uncovers errors and after fixing those errors we
have software that is being developed according to specifications.

The above objective implies a dramatic change in viewpoint .The move counter
to the commonly held view than a successful test is one in which no errors are
found. In fact, our objective is to design tests that a systematically uncover
different classes of errors and do so with a minimum amount of time and effort.

Testing principles
Before applying methods to design effective test cases, software engineer must
understand the basic principles that guide the software testing process. Some of
the most commonly followed principles are:
All test should be traceable to customer requirements as the objective of testing
is to uncover errors, it follows that the most severe defects (from the customers
point of view) are those that causes the program to fail to meet its requirements.

Tests should be planned long before the testing begins. Test planning can begin
as soon as the requirement model is complete. Detailed definition of test cases

60
can begin as soon as the design model has been solidated. Therefore, all tests
can be planned and designed before any code can be generated.

The Pareto principle applies to software testing stated simply the Pareto principle
implies that 80 percent of all errors uncovered during testing will likely be
traceable to 20 percent of all program modules. The problem of course, is to
isolate these suspects’ modules and to thoroughly test them.

Testing should begin “in the small “and progress towards testing “in large”. The
first tests planned and executed generally focus on individual modules. As testing
progresses, testing shifts focus in an attempt to find errors in integrated clusters
of modules and ultimately in the entire system.

Exhaustive testing is not possible. The number of paths permutations for

impossible to execute every combination of paths during testing. It is possible
however to adequately cover program logic and to ensure that all conditions in
the procedural design have been exercised.

To be most effective, an independent third party should conduct testing. By “most

effective”, we mean testing that has the highest probability of finding errors (the
primary objective of testing).

Software project management is an umbrella activity within software engineering.

It begins before any technical activity is intimated and continues throughout the
definition, development, and maintenance of computer software.

Three p’s 1 have a substantial influence on software project management –

people, problem, and process. People must be organized into effective teams,
motivated to do high quality software work, and coordinated to achieve effective
communication. The problem communicated from customer to developer,

61
partitioned (decomposed) into its constitute parts, and positioned for work by the
software team. The process must be adapted to the people and the problem. A
common process framework is selected, an appropriate software engineering
paradigm is applied, and a set of work is chosen to get the job done.

The pivotal element in all software projects is people. Software engineers can be
organized in a number of different team structures that range from traditional
control hierarchies to “Open paradigm” team. A variety of coordination and
communication techniques can be applied to support the work of the team. In
general, formal reviews and informal person-to-person communication have the
most value for the practitioners.

The project management activity encompasses measurement and metrics,

estimation, risk analysis, schedules, tracking and control, and control. Each of
these steps was followed during project also.

Test Information flow

Testing is a complete process. For testing we need two types of inputs:

Software configuration –it includes software requirement specification, design

specification and source code of program. Software configuration is required so
that testers know what is to be expected and tested.
Test configuration – it is basically test plan and procedure. Test configuration is
testing plan that is, the way how the testing will be conducted on the system. It
specifies the test cases and their expected value. It also specifies if any tools for
testing are to be used.

Test cases are required to know what specific situations need to be tested. When
tests are evaluated, test results are compared with actual results and if there is
some error, then debugging is done to correct the error. Testing is a way to know

62
about quality and reliability. Error rate that is the occurrence of errors is
evaluated. This data can be used to predict the occurrence of errors in future.

Test case design

We know, test cases are integral part of testing. So we need to know more about
test cases and how these test cases are designed. The most desired or obvious
expectation from the test cases is that it should be able to find most errors with
the least amount of time and effort.
A software product can be tested in two ways. In first approach, only overall
functioning of the product is tested. Inputs are given and outputs ate checked.
This approach is called black box testing. It does not care about the internal
functioning of the product.
The other approach is called white box testing. Here the internal functioning of he
product is tested. Each procedure is tested for its accuracy. It is more intensive
than black box testing. But for the overall product both these techniques are
crucial. There should be sufficient number of tests in both categories to test the
overall product.
Basic methods of Testing

White box testing

White box testing is performed to reveal problems with the internal structure of a
program. This requires the tester to have detailed knowledge of the internal
structure. A common goal of white box testing is to ensure a test case exercises
every path through a program. A fundamental strength that all white box
strategies share is that the entire software implementation is taken into account
during testing, which facilitates error detection even when software specification
is vague or incomplete. The effectiveness or thoroughness of white box testing is
commonly expressed in terms of test or code coverage metrics, which measure
the fraction of code exercised by test cases.

63
Basic Path Testing
It is a white box technique. It was proposed by Tom McCabe. These tests
guarantee to execute every statement in the program at least one time during
testing. Basic set is the set of all execution paths of a procedure.

Black Box Testing

Black box tests are performed to access how well a program meets its
requirements, looking for incorrect or missing functionality. Functional tests
typically exercise code with valid or nearly valid input for which the expected
output is known. This includes concepts such as ‘boundary values’.
Performance tests evaluate response time, memory usage, throughput, device
utilization and execution time. Stress tests push the system to or beyond its
specified limits to evaluate its robustness and error handling capabilities.
Reliability tests monitor system response to representative user input, counting
failures over time to measure or certify reliability.

Black box testing uncovers the following types of errors

 Incorrect or missing functions
 Interface errors
 External database access
 Performance errors
 Initialization and termination errors

64
The following techniques are employed during black box testing:

Integration Testing

One of the most difficult aspects of software development is the integration and
testing of large untested subsystems the integrated system frequently fails in
significant ands mysterious ways, and it is difficult to fix it.
Integration testing exercises several units that have been combined to form a
module, subsystem or system. Integration testing focuses on the interfaces
between units, to make sure the units work together. The nature of this phase is
certainly ‘white box’, as we must have knowledge of the units to recognize if we
have been successful in focusing them together in the module.

ENTITIES- RELATIONSHIP DESIGN

INTRODUCTION:

The data-modeling phase involves modeling the database structure using

a data-modeling method, such as entity-relationship (ER) diagramming,
semantic-object modeling, or object-role modeling. Each of these
modeling methods provides a means of visually representing various
aspects of the database structure, such as the tables, table relationships,
and relationship characteristics.

VARIOUS SYMBOLS OF E-R DIAGRAMS:

 The rectangles represent tables
 The diamond represents a relationship between two tables
 Circles represent connectors.

65
 Double rectangle represents weak entities

DATA FLOW DIAGRAMS

Data Flow Diagrams

It is a way of expressing system requirement in a graphical form; this

leads to a modular design. It is also known as bubble chart, has the
purpose of clarifying system requirements and identifying major
transformations that will become program in system design. So it is the
starting point of the design phase that functionally decomposes the
requirement specifications down to the lowest level of details. A DFD
consist of a series of bubbles joined by lines. The bubbles represent data
transformation and the lines represent data flows in the system.
DFD SYMBOLS:

= Source or Destination of data

= Data flow

= Process that transform data flow

= Data Store

66
Conclusion…

67
 CONCLUSION

The system has been developed for the given condition and is found
working effectively. The developed system is flexible and changes
whenever can be made easy. Using the facilities and functionalities of .Net,
the software has been developed in a neat and simple manner, thereby
reducing the operators work.

The speed and accuracy are maintained in proper way. The user friendly
nature of this software developed in .Net framework is very easy to work
with both for the higher management as well as other employees with little
knowledge of computer. The results obtained were fully satisfactory from
the user point of view.

The system was verified with valid as well as invalid data in each manner.
the system is run with an insight into the necessary modifications that may
require in the future. Hence the system can be maintained successfully
without much network.

68
 BIBLIOGRAPHY:

Database Management System by Vipin C. Desai

System analysis and Design by Elias M. Awad

SQL SERVER by Microsoft Press

ASP.Net by Wrox Publications

JavaScript by R. Allen Wyke, Jason D. Gilliam and

Chariton

69