ABSTRACT

The Easy Leave is an Intranet based application that can be accessed

throughout the organization or a specified group/Dept. This system can be used to
automate the workflow of leave applications and their approvals. The periodic
crediting of leave is also automated. There are features like email notifications,
cancellation of leave, automatic approval of leave, report generators etc in this
Tool.
The project has been planned to be having the view of distributed
architecture, with centralized storage of the database. The application for the
storage of the data has been planned. Using the constructs of MS-SQL Server and
all the user interfaces have been designed using the ASP.Net technologies. The
database connectivity is planned using the “SQL Connection” methodology. The
standards of security and data protective mechanism have been given a big choice
for proper usage. The application takes care of different modules and their
associated reports, which are produced as per the applicable strategies and
standards that are put forwarded by the administrative staff.
The entire project has been developed keeping in view of the distributed
client server computing technology, in mind. The specification has been
normalized up to 3NF to eliminate all the anomalies that may arise due to the
database transaction that are executed by the general users and the
organizational administration. The user interfaces are browser specific to give
distributed accessibility for the overall system. The internal database has been
selected as MS-SQL server 200.The basic constructs of table spaces, clusters and
indexes have been exploited to provide higher consistency and reliability for the
data storage. The MS-SQL server 200 was a choice as it provides the constructs of
high-level reliability and security. The total front end was dominated using the
ASP.Net technologies. At all proper levels high care was taken to check that the
system manages the data consistency with proper business rules or validations.

-1-
The database connectivity was planned using the latest “SQL Connection”
technology provided by Microsoft Corporation. The authentication and
authorization was crosschecked at all the relevant stages. The user level
accessibility has been restricted into two zones namely.

-2-
 CONTENTS

1. INTRODUCTION

INTRODUCTION TO PROJECT
INDUSTRY & COMPANY PROFILE
PURPOSE OF THE PROJECT
PROBLEM IN EXISTING SYSTEM
SOLUTION OF THESE PROBLEMS

2. SYSTEM ANALYSIS

2.1. INTRODUCTION
2.2. SYSTEM WORKFLOW
2.3. STUDY OF THE SYSTEM
2.4. HARDWARE & SOFTWARE REQUIRMENT
2.5. PROPOSED SYSTEM
2.6. INPUT & OUTPUT
2.7. PROCESS MODELS USED WITH JUSTIFICATION

3. FEASIBILITY REPORT

3.1. TECHNICAL FEASIBILITY

3.2. OPERATIONAL FEASIBILITY
3.3. ECONOMIC FEASIBILITY

4. SOFTWARE REQUIREMENT SPECIFICATIONS

4.1. FUNCIONAL REQUIREMENTS

4.2. PERFORMANCE REQUIREMENTS

5. SELECTED SOFTWARE

INTRODUCTION ASP.NET
5.1. ASP.NET
5.2. SQL SERVER

-3-
6. SYSTEM DESIGN

6.1. INTRODUCTION
6.2. SYSTEM WORKFLOW
6.3. NORMALIZATION
6.4. E-R DIAGRAM

7. SYSTEM TESTING AND IMPLEMENTATION

7.1 INTRODUCTION
7.2 STRATEGIC APPROACH OF SOFTWARE TESTING
7.3 UNIT TESTING

8. CONCLUSION

-4-
 Chapter 1
INTRODUCTION

-5-
 INTRODUCTION TO PROJECT

The Easy Leave is an Intranet based application that can be accessed throughout
the organization or a specified group/Dept. This system can be used to automate
the workflow of leave applications and their approvals. The periodic crediting of
leave is also automated. There are features like email notifications, cancellation of
leave, automatic approval of leave, report generators etc in this Tool.
The project has been planned to be having the view of distributed
architecture, with centralized storage of the database. The application for the
storage of the data has been planned. Using the constructs of MS-SQL Server and
all the user interfaces have been designed using the ASP.Net technologies. The
database connectivity is planned using the “SQL Connection” methodology. The
standards of security and data protective mechanism have been given a big choice
for proper usage. The application takes care of different modules and their
associated reports, which are produced as per the applicable strategies and
standards that are put forwarded by the administrative staff.

-6-
 INDUSTRY PROFILE

The Software industry includes business for development, maintenance and

publication of software that are using different business models, mainly either
“license/ maintenance basd” or “ Cloud Based” (such as SaaS, PaaS, IaaS, MBaaS,
MSaaS, DCaaS, etc.) The industry also include software services such as training,
documentation, consulting and date recovery. The software and computer services
industry spends mote than 11% of its net sales for Research & Development which
is in comparison with other industries the second highest share after
pharmaceuticals & biotechnology.

The first company founded to provide software products and services

was Computer Usage Company in 1955.[2] Before that time, computers were
programmed either by customers, or the few commercial computer vendors of the
time, such as Sperry Rand and IBM.

The software industry expanded in the early 1960s, almost immediately

after computers were first sold in mass-produced quantities. Universities,
government, and business customers created a demand for software. Many of
these programs were written in-house by full-time staff programmers. Some were
distributed freely between users of a particular machine for no charge. Others
were done on a commercial basis, and other firms such as Computer Sciences
Corporation (founded in 1959) started to grow. Other influential or typical software
companies begun in the early 1960s included Advanced Computer
techniques, Automatic Data Processing, Applied Data Research, and Informatics
General.[3][4] The computer/hardware makers started bundling operating
systems, systems software and programming environments with their machines.

When Digital Equipment Corporation (DEC) brought a relatively low-

priced microcomputer to market, it brought computing within the reach of many
more companies and universities worldwide, and it spawned great innovation in
terms of new, powerful programming languages and methodologies. New software

-7-
was built for microcomputers, so other manufacturers including IBM, followed
DEC's example quickly, resulting in the IBM AS/400 amongst others.

The industry expanded greatly with the rise of the personal computer ("PC")
in the mid-1970s, which brought desktop computing to the office worker for the
first time. In the following years, it also created a growing market for games,
applications, and utilities. DOS, Microsoft's first operating system product, was the
dominant operating system at the time.

In the early years of the 21st century, another successful business

model has arisen for hosted software, called software-as-a-service, or SaaS; this
was at least the third time[citation needed] this model had been attempted. From
the point of view of producers of some proprietary software, SaaS reduces the
concerns about unauthorized copying, since it can only be accessed through the
Web, and by definition no client software is loaded onto the end user's PC.

Size Of Industry
The global software products market amounts to US$968.25 billion in 2021
and had a compound annual growth rate (CAGR) of 4%. Major companies include
Microsoft, HP, Oracle, Dell and IBM.
Business models within the software industry
Business models of software companies have been widely discussed.
Network effects in software ecosystems, networks of companies, and their
customers are an important element in the strategy of software companies.

-8-
PURPOSE OF THE PROJECT

This project is aimed at developing a web based Leave Management Tool, which is
of importance to either an organization or a college. This is an Intranet based
application that can be accessed throughout the organization or a specified
group/Dept. This system can be used to automate the workflow of leave
applications and their approvals. The periodic crediting of leave is also automated.
There are features like email notifications, cancellation of leave, automatic
approval of leave, report generators etc in this Tool.

PROBLEM IN EXISTING SYSTEM

 Cannot Upload and Download the latest updates.
 No use of Web Services and Remoting.
 Risk of mismanagement and of data when the project is under development.
 Less Security.
 No proper coordination between different Applications and Users.
 Fewer Users - Friendly.

SOLUTION OF THESE PROBLEMS

The development of the new system contains the following activities, which try to
automate the entire process keeping in view of the database integration approach.

1. User friendliness is provided in the application with various controls.

2. The system makes the overall project management much easier and
flexible.

3. Readily upload the latest updates, allows user to download the alerts by
clicking the URL.

4. There is no risk of data mismanagement at any level while the project

development is under process.

5. It provides high level of security with different level of authentication.

-9-
Company Profile

- 10 -
 COMPANY PROFILE

Company Name: SINFO TECH PRIATE LIMITED

Industry: Software Services & IT Industry
Founder& Chairman: SIIVA RAM KRESHNA. VASANTHA
Founded: 07th May 2020
Head Quarters: Vijayawada
Country: India
Area Served: India

About Sinfo Tech Private Limited

SINFO TECH is a leader in IT services, digital and business solutions. We

partner with our clients to simplify, strengthen and transform their businesses to
help them reach success. We ensure the highest levels of certainty and satisfaction
through our deep-rooted commitments.
With our comprehensive industry expertise, network of innovation and delivery
centers, we make sure that all our clients get exactly what they want.
Established in 2020, SINFO TECH has grown to significant heights. Through our
outstanding service record, collaborative partnerships, innovation and corporate
responsibility, we have become a significant player in IT services.
Vision
Our vision is to contribute to the success of our clients. We contribute to our
client’s success in whatever enormity by ensuring that we understand the
complete picture.
Our vision is to deliver so much value to our customers that they know that
we are their strategic partners for success.
Our vision is to ensure that we grow because our clients grow.

- 11 -
SINFO TECH prides itself on the long-term relationships

SINFO TECH has worked extensively on multiple technologies spanning

various domains addressing issues in various industries. The Company has evolved
over time and has built in-house proficiencies and expertise in various areas from:
• Mobile App development
• Web development
• Backend process automation
• Parallel Processing systems
• Systems with large transactional volumes requiring distributed processing
• Systems with inbuilt redundancy both within a facility and across multiple
facilities

- 12 -
Leadership
Siiva Ram Kreshna Vasantha
(Founder & Chairman)

He started SINFO TECH with a vision to create an organization that

combined IT with innovative ideas to build solutions that benefited a wide range of
users and industries. Exceptionally Self- Motivated and Directed. He analyzes,
evaluates and motivates team- oriented collaborative environment. A part from
handling the end-to-end chain of work and with 10 years of experience in
corporate development emerging business.
He Post Graduated from the Business Management and Business
Administration Program from the University of Andhra. He has a B.S. in Computer
Science from the Acharya Nagarjuna University.

Aravind Krishna Kurapati

(Chief Operating Officer)

He holds a Degree in Software Engineering from Madras University. He has

been Director - Operations of SINFO TECH. He is considered a pioneer in the field,
highly respected amongst his peers and his views are sought in the field of
software technology.
Srinivasarao Gude
(Director – F&A)

Gude Srinivasa Rao has a proven record of success in financial and

operations management and leadership. He has appeared ICAI and holds a B. Com
in Accounting from the Acharya Nagarjuna University. He has vast experience in
Internal Operations.

- 13 -
Koganti Sukanya Chowdary
Associate Director – Technical

She holds a Degree in Computer Science Engineering from JNTU. She has
been Associate Director - Technical of SINFO TECH. She has instituted ground
breaking software development practices ensuring optimal utilization of resources,
on time delivery and best in class software quality and services all geared towards
ensuring customer satisfaction for SINFO TECH.

Siva Krishna Gorla

Project Manager and Tech Lead

He holds a Master Degree in Computer Science Engineering from JNTU. He

has been Project Manager and Tech Lead of SINFO TECH. And he has over 10+
years of experience In corporate development and emerging business. He leads
the technical team with precision and passion. Siva encourage team work,
approach and innovation.

- 14 -
 Chapter 2

SYSTEM ANALYSIS

- 15 -
2.1. INTRODUCTION
After analyzing the requirements of the task to be performed, the next step is to
analyze the problem and understand its context. The first activity in the phase is
studying the existing system and other is to understand the requirements and
domain of the new system. Both the activities are equally important, but the first
activity serves as a basis of giving the functional specifications and then successful
design of the proposed system. Understanding the properties and requirements of
a new system is more difficult and requires creative thinking and understanding of
existing running system is also difficult, improper understanding of present system
can lead diversion from solution.

2.2. ANALYSIS MODEL

The model that is basically being followed is the WATER FALL MODEL, which
states that the phases are organized in a linear order. First of all the feasibility
study is done. Once that part is over the requirement analysis and project
planning begins. If system exists one and modification and addition of new module
is needed, analysis of present system can be used as basic model.
The design starts after the requirement analysis is complete and the coding
begins after the design is complete. Once the programming is completed, the
testing is done. In this model the sequence of activities performed in a software
development project are: -
 Requirement Analysis
 Project Planning
 System design
 Detail design
 Coding
 Unit testing
 System integration & testing

- 16 -
 Here the linear ordering of these activities is critical. End of the phase and
the output of one phase is the input of other phase. The output of each phase is to
be consistent with the overall requirement of the system. Some of the qualities of
spiral model are also incorporated like after the people concerned with the project
review completion of each of the phase the work done.
WATER FALL MODEL was being chosen because all requirements were known
beforehand and the objective of our software development is the
computerization/automation of an already existing manual working system.

Changed
Requirements
Communicated
Requirements

Requirements
Specification
Requirements
Engineering

Design
Specification
Design

Executable
Software
Programming Modules Maintenance

Integrated
Software
Process
Integration Product

Delivered
Software
Product Product Delivery Product
Input Output

Fig 2.2: Water Fall Model

- 17 -
2.3. STUDY OF THE SYSTEM
GUI’S

In the flexibility of the uses the interface has been developed a graphics concept in mind,
associated through a browses interface. The GUI’S at the top level have been categorized
as

1. Administrative user interface

2. The operational or generic user interface

The administrative user interface concentrates on the consistent information that is

practically, part of the organizational activities and which needs proper authentication for
the data collection. The interfaces help the administrations with all the transactional states
like Data insertion, Data deletion and Date updation along with the extensive data search
capabilities.

The operational or generic user interface helps the users upon the system in transactions
through the existing data and required services. The operational user interface also helps
the ordinary users in managing their own information helps the ordinary users in
managing their own information in a customized manner as per the assisted flexibilities.

NUMBER OF MODULES

The system after careful analysis has been identified to be presented with the following
modules:

The modules involved are:

 Administration
 Employee
 Search
 Report
 Authentication

- 18 -
Administrator:-
In this module the Administrator has the privileges to add all the Employees and
register them in the organization and check the information of the Employee and
check the status of the leave when they have taken and what type of leave they
have taken and search is done based on the employee and report is generated
based on employee.

Search:-
This module contain complete search like Leave search, Type of Leave, Employee
based on the leave and starting and ending day of leave.

Employee:-

In this module employee has the privileges to use his username and password for
login and he can see the request given by the customer and he can pass the
process to the Business Manager and maintain the record of the customers.

Reports:-
This module contains all the information about the reports generated by the
Employees based on the Performance and by the leave status.

Authentication:-
This module contains all the information about the authenticated user. User
without his username and password can’t enter into the login if he is only the
authenticated user then he can enter to his login.

PROJECT INSTRUCTIONS:

 Based on the given requirements, conceptualize the Solution Architecture. Choose the domain
of your interest otherwise develop the application for ultimatedotnet.com. Depict the various
architectural components, show interactions and connectedness and show internal and external
elements. Design the web services, web methods and database infrastructure needed both and
client and server.

- 19 -
 Provide an environment for upgradation of application for newer versions that are available in
the same domain as web service target.

2.4. HARDWARE SPEDIFICATIONS

HARDWARE REQUIREMENTS:

 PIV 2.8 GHz Processor and Above

 RAM 512MB and Above
 HDD 20 GB Hard Disk Space and Above

SOFTWARE REQUIREMENTS:

 WINDOWS OS (XP / 2000 / 200 Server / 2003 Server)

 Visual Studio .Net 2005 Enterprise Edition
 Internet Information Server 5.0 (IIS)
 Visual Studio .Net Framework (Minimal for Deployment)
 SQL Server 2000 Enterprise Edition

2.5. PROPOSED SYSTEM

To debug the existing system, remove procedures those cause data redundancy,
make navigational sequence proper. To provide information about audits on
different level and also to reflect the current work status depending on
organization/auditor or date. To build strong password mechanism.

NEED FOR COMPUTERIZATION

We all know the importance of computerization. The world is moving ahead

at lightening speed and every one is running short of time. One always wants to
get the information and perform a task he/she/they desire(s) within a short period
of time and too with amount of efficiency and accuracy. The application areas for
the computerization have been selected on the basis of following factors:

 Minimizing the manual records kept at different locations.

- 20 -
 There will be more data integrity.
 Facilitating desired information display, very quickly, by retrieving information
from users.
 Facilitating various statistical information which helps in decision-making?
 To reduce manual efforts in activities that involved repetitive work.
 Updating and deletion of such a huge amount of data will become easier.

2.6. INPUT AND OUTPUT

The main inputs, outputs and major functions of the system are as follows
Inputs:
 Admin enters his or her user id and password.
 Employee enter his or her user id and password.
 Employee send request for Leave.
 Employee can check for status for Leave.
 Admin can edit the employee details and so on..
Outputs:
 Admin gets his homepage.
 Employee get his homepage.
 Employee leave request data will be stored in database..
 Displays leave Status.
 Admin view employee details.

- 21 -
2.7. PROCESS MODELS USED WITH JUSTIFICATION
ACCESS CONTROL FOR DATA WHICH REQUIRE USER AUTHENTICATION

The following commands specify access control identifiers and they are typically
used to authorize and authenticate the user (command codes are shown in
parentheses)

USER NAME (USER)

The user identification is that which is required by the server for access to its file
system. This command will normally be the first command transmitted by the user
after the control connections are made (some servers may require this).

PASSWORD (PASS)

This command must be immediately preceded by the user name command, and,
for some sites, completes the user's identification for access control. Since
password information is quite sensitive, it is desirable in general to "mask" it or
suppress type out.

- 22 -
 Chapter 3
Feasibility Report

- 23 -
Feasibility

Preliminary investigation examine project feasibility, the likelihood the

system will be useful to the organization. The main objective of the feasibility
study is to test the Technical, Operational and Economical feasibility for adding
new modules and debugging old running system. All system is feasible if they are
unlimited resources and infinite time. There are aspects in the feasibility study
portion of the preliminary investigation:

 Technical Feasibility
 Operation Feasibility
 Economical Feasibility

3.1. Technical Feasibility

The technical issue usually raised during the feasibility stage of the
investigation includes the following:

 Does the necessary technology exist to do what is suggested?

 Do the proposed equipments have the technical capacity to hold the data
required to use the new system?
 Will the proposed system provide adequate response to inquiries, regardless of
the number or location of users?
 Can the system be upgraded if developed?
 Are there technical guarantees of accuracy, reliability, ease of access and data
security?

Earlier no system existed to cater to the needs of ‘Secure Infrastructure

Implementation System’. The current system developed is technically feasible. It
is a web based user interface. Thus it provides an easy access to the users. The
database’s purpose is to create, establish and maintain a workflow among various
entities in order to facilitate all concerned users in their various capacities or roles.
Permission to the users would be granted based on the roles specified. Therefore,

- 24 -
it provides the technical guarantee of accuracy, reliability and security. The
software and hard requirements for the development of this project are not many
and are available as free as open source. The work for the project is done with
the current equipment and existing software technology. Necessary bandwidth
exists for providing a fast feedback to the users irrespective of the number of
users using the system.

3.2. Operational Feasibility

Proposed projects are beneficial only if they can be turned out into
information system. That will meet the organization’s operating requirements.
Operational feasibility aspects of the project are to be taken as an important part
of the project implementation. Some of the important issues raised are to test the
operational feasibility of a project includes the following: -

 Is there sufficient support for the management from the users?

 Will the system be used and work properly if it is being developed and
implemented?
 Will there be any resistance from the user that will undermine the possible
application benefits?

This system is targeted to be in accordance with the above-mentioned

issues. Beforehand, the management issues and user requirements have been
taken into consideration. So there is no question of resistance from the users that
can undermine the possible application benefits.

The well-planned design would ensure the optimal utilization of the computer
resources and would help in the improvement of performance status.

3.3. Economic Feasibility

A system can be developed technically and that will be used if installed must still
be a good investment for the organization. In the economical feasibility, the

- 25 -
development cost in creating the system is evaluated against the ultimate benefit
derived from the new systems. Financial benefits must equal or exceed the costs.

The system is economically feasible. It does not require any addition

hardware or software. Since the interface for this system is developed using the
existing resources and technologies. There is nominal expenditure and economical
feasibility for certain.

- 26 -
 Chapter 4

SOFTWARE REQUIREMENT
SPECIFICATION

- 27 -
 SOFTWARE REQUIREMENT SPECIFICATION

The software, Site Explorer is designed for management of web sites from a remote
location.

INTRODUCTION

Purpose: The main purpose for preparing this document is to give a general insight into
the analysis and requirements of the existing system or situation and for determining the
operating characteristics of the system.

Scope: This Document plays a vital role in the development life cycle (SDLC) and it
describes the complete requirement of the system. It is meant for use by the developers
and will be the basic during testing phase. Any changes made to the requirements in the
future will have to go through formal change approval process.

DEVELOPERS RESPONSIBILITIES OVERVIEW:

The developer is responsible for:

 Developing the system, which meets the SRS and solving all the requirements of the
system?
 Demonstrating the system and installing the system at client's location after the
acceptance testing is successful.
 Submitting the required user manual describing the system interfaces to work on it
and also the documents of the system.
 Conducting any user training that might be needed for using the system.
 Maintaining the system for a period of one year after installation.

- 28 -
4.1. FUNCTIONAL REQUIREMENTS:
OUTPUT DESIGN

Outputs from computer systems are required primarily to communicate the results
of processing to users. They are also used to provides a permanent copy of the results for
later consultation. The various types of outputs in general are:
 External Outputs, whose destination is outside the organization.
 Internal Outputs whose destination is with in organization and they are the
 User’s main interface with the computer.
 Operational outputs whose use is purely with in the computer department.
 Interface outputs, which involve the user in communicating directly with

OUTPUT DEFINITION
The outputs should be defined in terms of the following points:

 Type of the output

 Content of the output
 Format of the output
 Location of the output
 Frequency of the output
 Volume of the output
 Sequence of the output

It is not always desirable to print or display data as it is held on a computer. It

should be decided as which form of the output is the most suitable.

For Example
 Will decimal points need to be inserted
 Should leading zeros be suppressed.

Output Media:
In the next stage it is to be decided that which medium is the most appropriate for
the output. The main considerations when deciding about the output media are:

- 29 -
  The suitability for the device to the particular application.
 The need for a hard copy.
 The response time required.
 The location of the users
 The software and hardware available.
Keeping in view the above description the project is to have outputs mainly coming under
the category of internal outputs. The main outputs desired according to the requirement
specification are:
The outputs were needed to be generated as a hot copy and as well as queries to be
viewed on the screen. Keeping in view these outputs, the format for the output is taken
from the outputs, which are currently being obtained after manual processing. The
standard printer is to be used as output media for hard copies.

INPUT DESIGN

Input design is a part of overall system design. The main objective during the input
design is as given below:

 To produce a cost-effective method of input.

 To achive the highest possible level of accuracy.
 To ensure that the input is acceptable and understood by the user.

INPUT STAGES:
The main input stages can be listed as below:

 Data recording
 Data transcription
 Data conversion
 Data verification
 Data control
 Data transmission
 Data validation
 Data correction

- 30 -
INPUT TYPES:
It is necessary to determine the various types of inputs. Inputs can be categorized as
follows:
 External inputs, which are prime inputs for the system.
 Internal inputs, which are user communications with the system.
 Operational, which are computer department’s communications to the system?
 Interactive, which are inputs entered during a dialogue.

INPUT MEDIA:
At this stage choice has to be made about the input media. To conclude about the
input media consideration has to be given to;
 Type of input
 Flexibility of format
 Speed
 Accuracy
 Verification methods
 Rejection rates
 Ease of correction
 Storage and handling requirements
 Security
 Easy to use
 Portability

Keeping in view the above description of the input types and input media, it can be
said that most of the inputs are of the form of internal and interactive. As
Input data is to be the directly keyed in by the user, the keyboard can be considered to be
the most suitable input device.

ERROR AVOIDANCE
At this stage care is to be taken to ensure that input data remains accurate form
the stage at which it is recorded upto the stage in which the data is accepted by the

- 31 -
system. This can be achieved only by means of careful control each time the data is
handled.

ERROR DETECTION
Even though every effort is make to avoid the occurrence of errors, still a small
proportion of errors is always likely to occur, these types of errors can be discovered by
using validations to check the input data.
DATA VALIDATION
Procedures are designed to detect errors in data at a lower level of detail. Data
validations have been included in the system in almost every area where there is a
possibility for the user to commit errors. The system will not accept invalid data.
Whenever an invalid data is keyed in, the system immediately prompts the user and the
user has to again key in the data and the system will accept the data only if the data is
correct. Validations have been included where necessary.
The system is designed to be a user friendly one. In other words the system has
been designed to communicate effectively with the user. The system has been designed
with pop up menus.

USER INTERFACE DESIGN

It is essential to consult the system users and discuss their needs while designing
the user interface:

USER INTERFACE SYSTEMS CAN BE BROADLY CLASIFIED AS:

1. User initiated interface the user is in charge, controlling the progress of the
user/computer dialogue. In the computer-initiated interface, the computer selects the
next stage in the interaction.
2. Computer initiated interfaces

In the computer initiated interfaces the computer guides the progress of the
user/computer dialogue. Information is displayed and the user response of the computer
takes action or displays further information.

- 32 -
USER_INITIATED INTERGFACES
User initiated interfaces fall into tow approximate classes:
1. Command driven interfaces: In this type of interface the user inputs commands or
queries which are interpreted by the computer.
2. Forms oriented interface: The user calls up an image of the form to his/her screen and
fills in the form. The forms oriented interface is chosen because it is the best choice.

COMPUTER-INITIATED INTERFACES
The following computer – initiated interfaces were used:
1. The menu system for the user is presented with a list of alternatives and the user
chooses one; of alternatives.
2. Questions – answer type dialog system where the computer asks question and takes
action based on the basis of the users reply.

Right from the start the system is going to be menu driven, the opening menu
displays the available options. Choosing one option gives another popup menu with more
options. In this way every option leads the users to data entry form where the user can
key in the data.

ERROR MESSAGE DESIGN:

The design of error messages is an important part of the user interface design. As
user is bound to commit some errors or other while designing a system the system should
be designed to be helpful by providing the user with information regarding the error
he/she has committed.

This application must be able to produce output at different modules for different
inputs.

4.2. PERFORMANCE REQUIREMENTS

Performance is measured in terms of the output provided by the application.

Requirement specification plays an important part in the analysis of a system. Only

when the requirement specifications are properly given, it is possible to design a system,
which will fit into required environment. It rests largely in the part of the users of the

- 33 -
existing system to give the requirement specifications because they are the people who
finally use the system. This is because the requirements have to be known during the
initial stages so that the system can be designed according to those requirements. It is
very difficult to change the system once it has been designed and on the other hand
designing a system, which does not cater to the requirements of the user, is of no use.

The requirement specification for any system can be broadly stated as given below:
 The system should be able to interface with the existing system
 The system should be accurate
 The system should be better than the existing system

The existing system is completely dependent on the user to perform all the duties.

- 34 -
 Chapter 5

SELECTED SOFTWARE

- 35 -
5.1 ASP.NET

Server Application Development

Server-side applications in the managed world are implemented through runtime
hosts. Unmanaged applications host the common language runtime, which allows your
custom managed code to control the behavior of the server. This model provides you with
all the features of the common language runtime and class library while gaining the
performance and scalability of the host server.
The following illustration shows a basic network schema with managed code
running in different server environments. Servers such as IIS and SQL Server can perform
standard operations while your application logic executes through the managed code.

SERVER-SIDE MANAGED CODE

ASP.NET is the hosting environment that enables developers to use the .NET
Framework to target Web-based applications. However, ASP.NET is more than just a
runtime host; it is a complete architecture for developing Web sites and Internet-
distributed objects using managed code. Both Web Forms and XML Web services use IIS
and ASP.NET as the publishing mechanism for applications, and both have a collection of
supporting classes in the .NET Framework.
XML Web services, an important evolution in Web-based technology, are
distributed, server-side application components similar to common Web sites. However,
unlike Web-based applications, XML Web services components have no UI and are not
targeted for browsers such as Internet Explorer and Netscape Navigator. Instead, XML
Web services consist of reusable software components designed to be consumed by other
applications, such as traditional client applications, Web-based applications, or even other
XML Web services. As a result, XML Web services technology is rapidly moving application
development and deployment into the highly distributed environment of the Internet.
If you have used earlier versions of ASP technology, you will immediately notice the
improvements that ASP.NET and Web Forms offers. For example, you can develop Web
Forms pages in any language that supports the .NET Framework. In addition, your code
no longer needs to share the same file with your HTTP text (although it can continue to do
so if you prefer). Web Forms pages execute in native machine language because, like any

- 36 -
other managed application, they take full advantage of the runtime. In contrast,
unmanaged ASP pages are always scripted and interpreted. ASP.NET pages are faster,
more functional, and easier to develop than unmanaged ASP pages because they interact
with the runtime like any managed application.
The .NET Framework also provides a collection of classes and tools to aid in
development and consumption of XML Web services applications. XML Web services are
built on standards such as SOAP (a remote procedure-call protocol), XML (an extensible
data format), and WSDL ( the Web Services Description Language). The .NET Framework
is built on these standards to promote interoperability with non-Microsoft solutions.
For example, the Web Services Description Language tool included with the .NET
Framework SDK can query an XML Web service published on the Web, parse its WSDL
description, and produce C# or Visual Basic source code that your application can use to
become a client of the XML Web service. The source code can create classes derived from
classes in the class library that handle all the underlying communication using SOAP and
XML parsing. Although you can use the class library to consume XML Web services
directly, the Web Services Description Language tool and the other tools contained in the
SDK facilitate your development efforts with the .NET Framework.
If you develop and publish your own XML Web service, the .NET Framework
provides a set of classes that conform to all the underlying communication standards,
such as SOAP, WSDL, and XML. Using those classes enables you to focus on the logic of
your service, without concerning yourself with the communications infrastructure required
by distributed software development.
Finally, like Web Forms pages in the managed environment, your XML Web service will
run with the speed of native machine language using the scalable communication of IIS.

ACTIVE SERVER PAGES.NET

ASP.NET is a programming framework built on the common language runtime that
can be used on a server to build powerful Web applications. ASP.NET offers several
important advantages over previous Web development models:
 Enhanced Performance. ASP.NET is compiled common language runtime code
running on the server. Unlike its interpreted predecessors, ASP.NET can take
advantage of early binding, just-in-time compilation, native optimization, and caching

- 37 -
 services right out of the box. This amounts to dramatically better performance before
you ever write a line of code.
 World-Class Tool Support. The ASP.NET framework is complemented by a rich
toolbox and designer in the Visual Studio integrated development environment.
WYSIWYG editing, drag-and-drop server controls, and automatic deployment are just a
few of the features this powerful tool provides.
 Power and Flexibility. Because ASP.NET is based on the common language runtime,
the power and flexibility of that entire platform is available to Web application
developers. The .NET Framework class library, Messaging, and Data Access solutions
are all seamlessly accessible from the Web. ASP.NET is also language-independent, so
you can choose the language that best applies to your application or partition your
application across many languages. Further, common language runtime
interoperability guarantees that your existing investment in COM-based development is
preserved when migrating to ASP.NET.
 Simplicity. ASP.NET makes it easy to perform common tasks, from simple form
submission and client authentication to deployment and site configuration. For
example, the ASP.NET page framework allows you to build user interfaces that cleanly
separate application logic from presentation code and to handle events in a simple,
Visual Basic - like forms processing model. Additionally, the common language runtime
simplifies development, with managed code services such as automatic reference
counting and garbage collection.
 Manageability. ASP.NET employs a text-based, hierarchical configuration system,
which simplifies applying settings to your server environment and Web applications.
Because configuration information is stored as plain text, new settings may be applied
without the aid of local administration tools. This "zero local administration" philosophy
extends to deploying ASP.NET Framework applications as well. An ASP.NET Framework
application is deployed to a server simply by copying the necessary files to the server.
No server restart is required, even to deploy or replace running compiled code.
 Scalability and Availability. ASP.NET has been designed with scalability in mind,
with features specifically tailored to improve performance in clustered and
multiprocessor environments. Further, processes are closely monitored and managed
by the ASP.NET runtime, so that if one misbehaves (leaks, deadlocks), a new process

- 38 -
 can be created in its place, which helps keep your application constantly available to
handle requests.
 Customizability and Extensibility. ASP.NET delivers a well-factored architecture
that allows developers to "plug-in" their code at the appropriate level. In fact, it is
possible to extend or replace any subcomponent of the ASP.NET runtime with your own
custom-written component. Implementing custom authentication or state services has
never been easier.
 Security. With built in Windows authentication and per-application configuration, you
can be assured that your applications are secure.

LANGUAGE SUPPORT
The Microsoft .NET Platform currently offers built-in support for three languages:
C#, Visual Basic, and JScript.

WHAT IS ASP.NET WEB FORMS?

The ASP.NET Web Forms page framework is a scalable common language runtime
programming model that can be used on the server to dynamically generate Web pages.
Intended as a logical evolution of ASP (ASP.NET provides syntax compatibility with
existing pages), the ASP.NET Web Forms framework has been specifically designed to
address a number of key deficiencies in the previous model. In particular, it provides:
 The ability to create and use reusable UI controls that can encapsulate common
functionality and thus reduce the amount of code that a page developer has to write.
 The ability for developers to cleanly structure their page logic in an orderly fashion (not
"spaghetti code").
 The ability for development tools to provide strong WYSIWYG design support for pages
(existing ASP code is opaque to tools).

ASP.NET Web Forms pages are text files with an .aspx file name extension. They
can be deployed throughout an IIS virtual root directory tree. When a browser client
requests .aspx resources, the ASP.NET runtime parses and compiles the target file into a
.NET Framework class. This class can then be used to dynamically process incoming
requests. (Note that the .aspx file is compiled only the first time it is accessed; the
compiled type instance is then reused across multiple requests).

- 39 -
 An ASP.NET page can be created simply by taking an existing HTML file and
changing its file name extension to .aspx (no modification of code is required). For
example, the following sample demonstrates a simple HTML page that collects a user's
name and category preference and then performs a form postback to the originating page
when a button is clicked:
ASP.NET provides syntax compatibility with existing ASP pages. This includes
support for <% %> code render blocks that can be intermixed with HTML content within
an .aspx file. These code blocks execute in a top-down manner at page render time.

CODE-BEHIND WEB FORMS

ASP.NET supports two methods of authoring dynamic pages. The first is the method
shown in the preceding samples, where the page code is physically declared within the
originating .aspx file. An alternative approach--known as the code-behind method--
enables the page code to be more cleanly separated from the HTML content into an
entirely separate file.

INTRODUCTION TO ASP.NET SERVER CONTROLS

In addition to (or instead of) using <% %> code blocks to program dynamic
content, ASP.NET page developers can use ASP.NET server controls to program Web
pages. Server controls are declared within an .aspx file using custom tags or intrinsic
HTML tags that contain a runat="server" attributes value. Intrinsic HTML tags are
handled by one of the controls in the System.Web.UI.HtmlControls namespace. Any
tag that doesn't explicitly map to one of the controls is assigned the type of
System.Web.UI.HtmlControls.HtmlGenericControl.
Server controls automatically maintain any client-entered values between round
trips to the server. This control state is not stored on the server (it is instead stored within
an <input type="hidden"> form field that is round-tripped between requests). Note
also that no client-side script is required.
In addition to supporting standard HTML input controls, ASP.NET enables
developers to utilize richer custom controls on their pages. For example, the following
sample demonstrates how the <asp:adrotator> control can be used to dynamically
display rotating ads on a page.

- 40 -
1. ASP.NET Web Forms provide an easy and powerful way to build dynamic Web UI.
2. ASP.NET Web Forms pages can target any browser client (there are no script library or
cookie requirements).
3. ASP.NET Web Forms pages provide syntax compatibility with existing ASP pages.
4. ASP.NET server controls provide an easy way to encapsulate common functionality.
5. ASP.NET ships with 45 built-in server controls. Developers can also use controls built
by third parties.
6. ASP.NET server controls can automatically project both uplevel and downlevel HTML.
7. ASP.NET templates provide an easy way to customize the look and feel of list server
controls.
8. ASP.NET validation controls provide an easy way to do declarative client or server data
validation.

5.2 SQL SERVER

A database management, or DBMS, gives the user access to their data and helps
them transform the data into information. Such database management systems include
dBase, paradox, IMS, SQL Server and SQL Server. These systems allow users to create,
update and extract information from their database.
A database is a structured collection of data. Data refers to the characteristics of
people, things and events. SQL Server stores each data item in its own fields. In SQL
Server, the fields relating to a particular person, thing or event are bundled together to
form a single complete unit of data, called a record (it can also be referred to as raw or an
occurrence). Each record is made up of a number of fields. No two fields in a record can
have the same field name.
During an SQL Server Database design project, the analysis of your business needs
identifies all the fields or attributes of interest. If your business needs change over time,
you define any additional fields or change the definition of existing fields.

SQL SERVER TABLES

SQL Server stores records relating to each other in a table. Different tables are
created for the various groups of information. Related tables are grouped together to form
a database.

- 41 -
PRIMARY KEY
Every table in SQL Server has a field or a combination of fields that uniquely
identifies each record in the table. The Unique identifier is called the Primary Key, or
simply the Key. The primary key provides the means to distinguish one record from all
other in a table. It allows the user and the database system to identify, locate and refer
to one particular record in the database.

RELATIONAL DATABASE
Sometimes all the information of interest to a business operation can be stored in
one table. SQL Server makes it very easy to link the data in multiple tables. Matching an
employee to the department in which they work is one example. This is what makes SQL
Server a relational database management system, or RDBMS. It stores data in two or
more tables and enables you to define relationships between the table and enables you to
define relationships between the tables.

FOREIGN KEY
When a field is one table matches the primary key of another field is referred to as
a foreign key. A foreign key is a field or a group of fields in one table whose values match
those of the primary key of another table.

REFERENTIAL INTEGRITY
Not only does SQL Server allow you to link multiple tables, it also maintains
consistency between them. Ensuring that the data among related tables is correctly
matched is referred to as maintaining referential integrity.

DATA ABSTRACTION
A major purpose of a database system is to provide users with an abstract view of
the data. This system hides certain details of how the data is stored and maintained.
Data abstraction is divided into three levels.

Physical level: This is the lowest level of abstraction at which one describes how the
data are actually stored.

- 42 -
Conceptual Level: At this level of database abstraction all the attributed and what
data are actually stored is described and entries and relationship among them.

View level: This is the highest level of abstraction at which one describes only part of
the database.

ADVANTAGES OF RDBMS

 Redundancy can be avoided

 Inconsistency can be eliminated
 Data can be Shared
 Standards can be enforced
 Security restrictions ca be applied
 Integrity can be maintained
 Conflicting requirements can be balanced
 Data independence can be achieved.

DISADVANTAGES OF DBMS
A significant disadvantage of the DBMS system is cost. In addition to the cost of
purchasing of developing the software, the hardware has to be upgraded to allow for the
extensive programs and the workspace required for their execution and storage. While
centralization reduces duplication, the lack of duplication requires that the database be
adequately backed up so that in case of failure the data can be recovered.

FEATURES OF SQL SERVER (RDBMS)

SQL SERVER is one of the leading database management systems (DBMS) because
it is the only Database that meets the uncompromising requirements of today’s most
demanding information systems. From complex decision support systems (DSS) to the
most rigorous online transaction processing (OLTP) application, even application that
require simultaneous DSS and OLTP access to the same critical data, SQL Server leads the
industry in both performance and capability

SQL SERVER is a truly portable, distributed, and open DBMS that delivers unmatched
performance, continuous operation and support for every database.

- 43 -
SQL SERVER RDBMS is high performance fault tolerant DBMS which is specially designed
for online transactions processing and for handling large database application.

SQL SERVER with transactions processing option offers two features which contribute to
very high level of transaction processing throughput, which are

 The row level lock manager

ENTERPRISE WIDE DATA SHARING

The unrivaled portability and connectivity of the SQL SERVER DBMS enables all the
systems in the organization to be linked into a singular, integrated computing resource.

PORTABILITY
SQL SERVER is fully portable to more than 80 distinct hardware and operating
systems platforms, including UNIX, MSDOS, OS/2, Macintosh and dozens of proprietary
platforms. This portability gives complete freedom to choose the database sever platform
that meets the system requirements.

OPEN SYSTEMS
SQL SERVER offers a leading implementation of industry –standard SQL. SQL
Server’s open architecture integrates SQL SERVER and non –SQL SERVER DBMS with
industries most comprehensive collection of tools, application, and third party software
products SQL Server’s Open architecture provides transparent access to data from other
relational database and even non-relational database.

DISTRIBUTED DATA SHARING

SQL Server’s networking and distributed database capabilities to access data stored
on remote server with the same ease as if the information was stored on a single local
computer. A single SQL statement can access data at multiple sites. You can store data
where system requirements such as performance, security or availability dictate.

UNMATCHED PERFORMANCE
The most advanced architecture in the industry allows the SQL SERVER DBMS to
deliver unmatched performance.

- 44 -
SOPHISTICATED CONCURRENCY CONTROL
Real World applications demand access to critical data. With most database
Systems application becomes “contention bound” – which performance is limited not by
the CPU power or by disk I/O, but user waiting on one another for data access . SQL
Server employs full, unrestricted row-level locking and contention free queries to minimize
and in many cases entirely eliminates contention wait times.

NO I/O BOTTLENECKS
SQL Server’s fast commit groups commit and deferred write technologies
dramatically reduce disk I/O bottlenecks. While some database write whole data block to
disk at commit time, SQL Server commits transactions with at most sequential log file on
disk at commit time, On high throughput systems, one sequential writes typically group
commit multiple transactions. Data read by the transaction remains as shared memory so
that other transactions may access that data without reading it again from disk. Since
fast commits write all data necessary to the recovery to the log file, modified blocks are
written back to the database independently of the transaction commit, when written from
memory to disk.

- 45 -
 Chapter 6
SYSTEM DESIGN

- 46 -
6.1. INTRODUCTION
Software design sits at the technical kernel of the software engineering
process and is applied regardless of the development paradigm and area of
application. Design is the first step in the development phase for any engineered
product or system. The designer’s goal is to produce a model or representation of
an entity that will later be built. Beginning, once system requirement have been
specified and analyzed, system design is the first of the three technical activities -
design, code and test that is required to build and verify software.

The importance can be stated with a single word “Quality”. Design is the
place where quality is fostered in software development. Design provides us with
representations of software that can assess for quality. Design is the only way that
we can accurately translate a customer’s view into a finished software product or
system. Software design serves as a foundation for all the software engineering
steps that follow. Without a strong design we risk building an unstable system –
one that will be difficult to test, one whose quality cannot be assessed until the
last stage.

During design, progressive refinement of data structure, program structure,

and procedural details are developed reviewed and documented. System design
can be viewed from either technical or project management perspective. From the
technical point of view, design is comprised of four activities – architectural
design, data structure design, interface design and procedural design.

- 47 -
6.2. SYSTEM WORKFLOW

Change the workflow based on your project

Index.aspx
Main console for
Home page to login
coordinator
,Enter User Id &
Password Submenu.aspx

Vulnerabilities_view.aspx A_vul_dur_peri (Cancellation)

od_param.aspx search.aspx
Allow to view the
vulnerabilities found To enter the two The search page to
for that site. dates input the search condit
ions for which cancel
ation is to be made

audit_vul_dur_peri
Risk_observation.aspx. od_frm.aspx
aspx View of statistical
data report
Allow to view the risk
and observation for Chart1.aspx
that app. No.

Bar chart for all ten

vulnerabilities for Hosting
safe,unsafe and NA statusnew.aspx

Vulnerabilities_detail The search page to

s.aspx input the search condit
ions for which modify
Allow to view the cation is to be made reauditassigndetail
details level wise. s.aspx
Lists the matching
Websites Modify_request.aspx

Allow to modify
selected website audit
request form details Assignment_page2.aspx

Allow to mark a site

for random audit
- 48 -
6.3. NORMALIZATION
It is a process of converting a relation to a standard form. The process is used to
handle the problems that can arise due to data redundancy i.e. repetition of data in the
database, maintain data integrity as well as handling problems that can arise due to
insertion, updation, deletion anomalies.

Decomposing is the process of splitting relations into multiple relations to eliminate

anomalies and maintain anomalies and maintain data integrity. To do this we use normal
forms or rules for structuring relation.

Insertion anomaly: Inability to add data to the database due to absence of other data.

Deletion anomaly: Unintended loss of data due to deletion of other data.

Update anomaly: Data inconsistency resulting from data redundancy and partial update

Normal Forms: These are the rules for structuring relations that eliminate anomalies.

FIRST NORMAL FORM:

A relation is said to be in first normal form if the values in the relation are atomic
for every attribute in the relation. By this we mean simply that no attribute value can be
a set of values or, as it is sometimes expressed, a repeating group.

SECOND NORMAL FORM:

A relation is said to be in second Normal form is it is in first normal form and it

should satisfy any one of the following rules.
1) Primary key is a not a composite primary key
2) No non key attributes are present
3) Every non key attribute is fully functionally dependent on full set of primary key.

THIRD NORMAL FORM:

A relation is said to be in third normal form if their exits no transitive dependencies.

Transitive Dependency: If two non key attributes depend on each other as well as on
the primary key then they are said to be transitively dependent.

- 49 -
 The above normalization principles were applied to decompose the data in multiple
tables thereby making the data to be maintained in a consistent state.

6.4. E – R DIAGRAMS
 The relation upon the system is structure through a conceptual ER-Diagram, which
not only specifics the existential entities but also the standard relations through
which the system exists and the cardinalities that are necessary for the system state
to continue.

 The entity Relationship Diagram (ERD) depicts the relationship between the data
objects. The ERD is the notation that is used to conduct the date modeling activity the
attributes of each data object noted is the ERD can be described resign a data object
descriptions.

 The set of primary components that are identified by the ERD are

 Data object  Relationships

 Attributes  Various types of indicators.

The primary purpose of the ERD is to represent data objects and their relationships.

(PASTE YOUR E – R DIAGRAM)

6.4. DATA FLOW DIAGRAMS

A data flow diagram is graphical tool used to describe and analyze

movement of data through a system. These are the central tool and the basis
from which the other components are developed. The transformation of data from
input to output, through processed, may be described logically and independently
of physical components associated with the system. These are known as the
logical data flow diagrams. The physical data flow diagrams show the actual

- 50 -
implements and movement of data between people, departments and
workstations. A full description of a system actually consists of a set of data flow
diagrams. Using two familiar notations Yourdon, Gane and Sarson notation
develops the data flow diagrams. Each component in a DFD is labeled with a
descriptive name. Process is further identified with a number that will be used for
identification purpose. The development of DFD’S is done in several levels. Each
process in lower level diagrams can be broken down into a more detailed DFD in
the next level. The lop-level diagram is often called context diagram. It consists a
single process bit, which plays vital role in studying the current system. The
process in the context level diagram is exploded into other process at the first
level DFD.
The idea behind the explosion of a process into more process is that
understanding at one level of detail is exploded into greater detail at the next
level. This is done until further explosion is necessary and an adequate amount of
detail is described for analyst to understand the process.
Larry Constantine first developed the DFD as a way of expressing system
requirements in a graphical from, this lead to the modular design.
A DFD is also known as a “bubble Chart” has the purpose of clarifying
system requirements and identifying major transformations that will become
programs in system design. So it is the starting point of the design to the lowest
level of detail. A DFD consists of a series of bubbles joined by data flows in the
system.

DFD SYMBOLS:
In the DFD, there are four symbols
1. A square defines a source(originator) or destination of system data
2. An arrow identifies data flow. It is the pipeline through which the information
flows

- 51 -
3. A circle or a bubble represents a process that transforms incoming data flow
into outgoing data flows.
4. An open rectangle is a data store, data at rest or a temporary repository of
data

Process that transforms data flow.

Source or Destination of data

Data flow

Data Store

CONSTRUCTING A DFD:
Several rules of thumb are used in drawing DFD’S:

1. Process should be named and numbered for an easy reference. Each name
should be representative of the process.
2. The direction of flow is from top to bottom and from left to right. Data
traditionally flow from source to the destination although they may flow back to
the source. One way to indicate this is to draw long flow line back to a source.
An alternative way is to repeat the source symbol as a destination. Since it is
used more than once in the DFD it is marked with a short diagonal.
3. When a process is exploded into lower level details, they are numbered.
4. The names of data stores and destinations are written in capital letters. Process
and dataflow names have the first letter of each work capitalized

- 52 -
 A DFD typically shows the minimum contents of data store. Each data store
should contain all the data elements that flow in and out.
Questionnaires should contain all the data elements that flow in and out.
Missing interfaces redundancies and like is then accounted for often through
interviews.

SAILENT FEATURES OF DFD’S

1. The DFD shows flow of data, not of control loops and decision are controlled
considerations do not appear on a DFD.
2. The DFD does not indicate the time factor involved in any process whether the
dataflow take place daily, weekly, monthly or yearly.
3. The sequence of events is not brought out on the DFD.

TYPES OF DATA FLOW DIAGRAMS

1. Current Physical
2. Current Logical
3. New Logical
4. New Physical

CURRENT PHYSICAL:

In Current Physical DFD proecess label include the name of people or their
positions or the names of computer systems that might provide some of the
overall system-processing label includes an identification of the technology used to
process the data. Similarly data flows and data stores are often labels with the
names of the actual physical media on which data are stored such as file folders,
computer files, business forms or computer tapes.

CURRENT LOGICAL:
The physical aspects at the system are removed as mush as possible so that
the current system is reduced to its essence to the data and the processors that
transform them regardless of actual physical form.

- 53 -
NEW LOGICAL:
This is exactly like a current logical model if the user were completely happy
with he user were completely happy with the functionality of the current system
but had problems with how it was implemented typically through the new logical
model will differ from current logical model while having additional functions,
absolute function removal and inefficient flows recognized.

NEW PHYSICAL:
The new physical represents only the physical implementation of the new
system.

RULES GOVERNING THE DFD’S

PROCESS

1) No process can have only outputs.

2) No process can have only inputs. If an object has only inputs than it must be a
sink.
3) A process has a verb phrase label.

DATA STORE
1) Data cannot move directly from one data store to another data store, a process
must move data.
2) Data cannot move directly from an outside source to a data store, a process,
which receives, must move data from the source and place the data into data
store
3) A data store has a noun phrase label.

- 54 -
SOURCE OR SINK
The origin and /or destination of data.

1) Data cannot move direly from a source to sink it must be moved by a process
2) A source and /or sink has a noun phrase land

DATA FLOW

1) A Data Flow has only one direction of flow between symbols. It may flow in
both directions between a process and a data store to show a read before an
update. The later is usually indicated however by two separate arrows since
these happen at different type.
2) A join in DFD means that exactly the same data comes from any of two or more
different processes data store or sink to a common location.
3) A data flow cannot go directly back to the same process it leads. There must
be atleast one other process that handles the data flow produce some other
data flow returns the original data into the beginning process.
4) A Data flow to a data store means update (delete or change).
5) A data Flow from a data store means retrieve or use.

A data flow has a noun phrase label more than one data flow noun phrase can
appear on a single arrow as long as all of the flows on the same arrow move
together as one package.

- 55 -
 Chapter 7
SYSTEM TESTING AND
IMPLEMENTATION

- 56 -
7.1. INTRODUCTION
Software testing is a critical element of software quality assurance and
represents the ultimate review of specification, design and coding. In fact, testing
is the one step in the software engineering process that could be viewed as
destructive rather than constructive.

A strategy for software testing integrates software test case design methods
into a well-planned series of steps that result in the successful construction of
software. Testing is the set of activities that can be planned in advance and
conducted systematically. The underlying motivation of program testing is to
affirm software quality with methods that can economically and effectively apply to
both strategic to both large and small-scale systems.

7.2. STRATEGIC APPROACH TO SOFTWARE TESTING

The software engineering process can be viewed as a spiral. Initially system
engineering defines the role of software and leads to software requirement
analysis where the information domain, functions, behavior, performance,
constraints and validation criteria for software are established. Moving inward
along the spiral, we come to design and finally to coding. To develop computer
software we spiral in along streamlines that decrease the level of abstraction on
each turn.

A strategy for software testing may also be viewed in the context of the
spiral. Unit testing begins at the vertex of the spiral and concentrates on each unit
of the software as implemented in source code. Testing progress by moving
outward along the spiral to integration testing, where the focus is on the design
and the construction of the software architecture. Talking another turn on outward
on the spiral we encounter validation testing where requirements established as
part of software requirements analysis are validated against the software that has

- 57 -
been constructed. Finally we arrive at system testing, where the software and
other system elements are tested as a whole.

UNIT TESTING

MODULE TESTING

Component Testing
SUB-SYSTEM TESING

SYSTEM TESTING
Integration Testing

ACCEPTANCE TESTING
User Testing

3.3. Unit Testing

Unit testing focuses verification effort on the smallest unit of software design, the
module. The unit testing we have is white box oriented and some modules the
steps are conducted in parallel.

1. WHITE BOX TESTING

This type of testing ensures that
 All independent paths have been exercised at least once
 All logical decisions have been exercised on their true and false sides
 All loops are executed at their boundaries and within their operational bounds
 All internal data structures have been exercised to assure their validity.

- 58 -
To follow the concept of white box testing we have tested each form .we have
created independently to verify that Data flow is correct, All conditions are
exercised to check their validity, All loops are executed on their boundaries.

2. BASIC PATH TESTING

Established technique of flow graph with Cyclomatic complexity was used to derive
test cases for all the functions. The main steps in deriving test cases were:
Use the design of the code and draw correspondent flow graph.
Determine the Cyclomatic complexity of resultant flow graph, using formula:

V(G)=E-N+2 or
V(G)=P+1 or
V(G)=Number Of Regions

Where V(G) is Cyclomatic complexity,

E is the number of edges,
N is the number of flow graph nodes,
P is the number of predicate nodes.
Determine the basis of set of linearly independent paths.

3. CONDITIONAL TESTING
In this part of the testing each of the conditions were tested to both true and false
aspects. And all the resulting paths were tested. So that each path that may be
generate on particular condition is traced to uncover any possible errors.

4. DATA FLOW TESTING

This type of testing selects the path of the program according to the location of
definition and use of variables. This kind of testing was used only when some local
variable were declared. The definition-use chain method was used in this type of
testing. These were particularly useful in nested statements.

- 59 -
5. LOOP TESTING
In this type of testing all the loops are tested to all the limits possible. The
following exercise was adopted for all loops:
 All the loops were tested at their limits, just above them and just below them.
 All the loops were skipped at least once.
 For nested loops test the inner most loop first and then work outwards.
 For concatenated loops the values of dependent loops were set with the help of
connected loop.
 Unstructured loops were resolved into nested loops or concatenated loops and
tested as above.

Each unit has been separately tested by the development team itself and all the
input have been validated.

- 60 -
 Chapter 8
CONCLUSION

- 61 -
 It has been a great pleasure for me to work on this exciting and challenging
project. This project proved good for me as it provided practical knowledge of not
only programming in ASP.NET and VB.NET web based application and no some
extent Windows Application and SQL Server, but also about all handling procedure
related with “PROJECT NAME”. It also provides knowledge about the latest
technology used in developing web enabled application and client server
technology that will be great demand in future. This will provide better
opportunities and guidance in future in developing projects independently.

BENEFITS:

The project is identified by the merits of the system offered to the user. The
merits of this project are as follows: -

 It’s a web-enabled project.

 This project offers user to enter the data through simple and interactive forms.
This is very helpful for the client to enter the desired information through so
much simplicity.
 The user is mainly more concerned about the validity of the data, whatever he
is entering. There are checks on every stages of any new creation, data entry
or updation so that the user cannot enter the invalid data, which can create
problems at later date.
 Sometimes the user finds in the later stages of using project that he needs to
update some of the information that he entered earlier. There are options for
him by which he can update the records. Moreover there is restriction for his
that he cannot change the primary data field. This keeps the validity of the data
to longer extent.
 User is provided the option of monitoring the records he entered earlier. He can
see the desired records with the variety of options provided by him.
 From every part of the project the user is provided with the links through
framing so that he can go from one option of the project to other as per the
requirement. This is bound to be simple and very friendly as per the user is

- 62 -
 concerned. That is, we can sat that the project is user friendly which is one of
the primary concerns of any good project.
 Data storage and retrieval will become faster and easier to maintain because
data is stored in a systematic manner and in a single database.
 Decision making process would be greatly enhanced because of faster
processing of information since data collection from information available on
computer takes much less time then manual system.
 Allocating of sample results becomes much faster because at a time the user
can see the records of last years.
 Easier and faster data transfer through latest technology associated with the
computer and communication.
 Through these features it will increase the efficiency, accuracy and
transparency,

LIMITATIONS:

 The size of the database increases day-by-day, increasing the load on the
database back up and data maintenance activity.
 Training for simple computer operations is necessary for the users working on
the system.

- 63 -