COMPANY NAME

1. INTRODUCTION

1.1 COMPANY PROFILE

XYZ PRIVATE LIMITED

XYZ is a solution provider comprising leading edge technologists and utility business

experts with extensive experience in Research, Product & Software development,

Implementation & Systems Integration and Training. We are fully committed to ensuring that

every products and software solutions on our technology meets and exceed customer’s

expectations.

1.2 EXISTING SYSTEM AND NEED FOR PROPOSED SYSTEM

EXISTING SYSTEM

NEED OF PROPOSED SYSTEM

In the globalization of the world every one is busy so they have very less time do the

things. If the visitor just want to meet the person for just giving invitation of program other any

other thing which is just few minutes work in that case he/she will going to spend lots of time

on the searching the location of that particular persons.

PROJECT NAME 1
COMPANY NAME

1.3 SCOPE OF SYSTEM

Using this system we are able to do following things.

 Finding the exact location of member to whom visitor wants to meet.

 Finding out the shortest path to reach particular member’s location.

PROJECT NAME 2
COMPANY NAME

1.4 OPERATING ENVIRONMENT

SERVER MACHINE

HARDWARE SPECIFICATION

PROCESSOR PENTIUM 4 OR CORE TO DUO

OPERATING SYSTEM WINDOWS FAMILY/VISTA

RAM

SOFTWARE SPECIFICATION

CLIENT MACHINE

HARDWARE SPECIFICATION

PROCESSOR

OPERATING SYSTEM

RAM

SOFTWARE SPECIFICATION

PROJECT NAME 3
COMPANY NAME

 .NET ………………….

2. PROPOSED SYSTEM

2.1 PROPOSED SYSTEM

The proposed system will help the visitor to get the information of the person to

whom he/she had come to meet.

2.2 OBJECTIVES OF SYSTEM

This is system developed for the easily communicate with the visitor through system.

2.3 USER REQUIREMENTS

WHAT IS REQUIREMENT?

A Requirement is a feature that must be included in a new system. It may include a

way of capturing or processing data, producing information, controlling the business activity,

PROJECT NAME 4
COMPANY NAME

or supporting management. The determination of requirements thus entails studying the

existing system and collecting details about it to find out what these requirements are.

It may range from a high-level abstract statement of a service or of a system

constraint to a detailed mathematical functional specification.

 This is inevitable as requirements may serve a dual function

 May be the basis for a bid for a contract - therefore must be open to interpretation;

 May be the basis for the contract itself - therefore must be defined in detail;

 Both these statements may be called requirements.

2.3.1 FACT FINDING TECHNIQUES

HERE MENTION ONLY TECHNIQUES USED BY YOUR PROJECT WITH

DETAILS HOW USED IN YOUR PROJECT

Fact finding deals with finding and investigating more features of system. This is called as

preliminary investigation. During this activity we apply following system analysis methods

namely Interviews, Questionnaires and documentation.

i. INTERVIEWS:

Interview with authorized client gave us most of information. We arranged meeting

to understand the flow, drawbacks of the existing system and to understand the requirements

PROJECT NAME 5
COMPANY NAME

of the current system. The information provided during interviews them in analysis of the

current system and construction of data flow.

ii. QUESTIONARIES:

We provided various questionnaires to existing system user. In order to understand

the Existing System. Number of questions has been asked. Especially the open and close

ended questions. We ask questions to the manager regarding bidding system such as:

 Are you aware of the existing system?

 What do you think about drawbacks of existing system?

 Can you give details about the working of the existing system?

 Can you explain the actual flow of system?

iii. OBSERVATION:

In our first step we observed the existing system. This helped us to understand how

the existing system works and how it actually interacts with user. We observe that because of

lack of friendliness user was not satisfied and not comfortable with the system. These

observations helped us to identify some potential problems in existing system and gave idea

about future system.

2.3.2 FEASIBILITY STUDY

MENTION WHAT FEASIBILITY STUDY DONE FOR YOUR PROJECT

NEED FOR FEASIBILITY STUDY

 Answer the question whether to install the new system or not.

 Determine the potential of existing system.

PROJECT NAME 6
COMPANY NAME

 To know what should be there in system.

 Define the problems and objectives involved in project.

 Avoid constant repairs at the later levels when the system is implemented.

 Avoid crash implementation of system.

TECHNICAL FEASIBILITY

MENTION IN DETAIL ABOUT THE TECHNICAL FEASIBILITY STUDY DONE FOR YOUR

PROJECT

Whatever hardware and software required for our system not present in current system.

Some parts such as handling. We are trying to diverting people from traditional way of finding

the path or location to which person they want to meet.

ECONOMICAL FEASIBILITY

Due to various tangible and intangible benefits the system proves economical

feasibility to company.

A] TANGIBLE FEASIBILITY

 The cost of maintaining paper and files are reduced and so the time of manually

maintaining them is reduced.

 Numbers of persons in job are reduced.

PROJECT NAME 7
COMPANY NAME

 The money saved by computerizing the system can be spending in advertisement and

marketing.

B] INTANGIBLE FEASIBILITY

 Data is stored into memory, with proper backup, so no loss of data.

 Immediate updates are possible.

 Manual work is reduced leaving more manpower to be utilized in other creative work.

OPERATIONAL FEASIBILITY

MENTION IN DETAIL

The staff working in present system is very much tedious as well as time, energy

consuming. The new system provides way when one or more than one person (visitor) which

want to meet particular person who is working in the institute. The visitor will ask the details

of the person like in which building he/she is? Path or location of that office? How to reach

over their? Etc. so it is automatically reduced the job of security guard as well as other

employees who are busy in their work. And this system will help to the visitor by directly

showing the path without asking details and other things to people.

PROJECT NAME 8
COMPANY NAME

3. ANALYSIS AND DESIGN

3.1 MODULE HIERARCHY DIAGRAM

3.2 USE CASE DIAGRAM

PROJECT NAME 9
COMPANY NAME

3.3 SEQUENCE DIAGRAM

3.4 ACTIVITY DIAGRAM

PROJECT NAME 10
COMPANY NAME

3.5 CLASS DIAGRAM

PROJECT NAME 11
COMPANY NAME

3.6 COMPONENT DIAGRAM

3.7 DEPLOYMENT DIAGRAM

3.8 ENTITY RELATIONSHIP DIAGRAM (ERD)

3.9 DATA DICTIONARY

3.10 TABLE DESIGN

PROJECT NAME 12
COMPANY NAME

3.11 TEST CASES AND TEST REPORTS

TEST CASES

Input Screen Name: Login for Admin

TEST REPORTS

PROJECT NAME 13
COMPANY NAME

4. USER MANUAL

4.1 USER MANUAL

(REFERS TO MANUAL GIVEN TO END USER)

4.2 OPERATIONS MANUAL

(REFERS TO DETAILED MANUAL which even the company project person can refer for

maintenance purpose.)

PROJECT NAME 14
COMPANY NAME

4.3 SAMPLE PROJECT CODE

PROJECT NAME 15
COMPANY NAME

5. LIMITATIONS OF THE SYSTEM

PROJECT NAME 16
COMPANY NAME

6. FUTURE ENHANCEMENTS

PROJECT NAME 17
COMPANY NAME

7. CONCLUSION

PROJECT NAME 18
COMPANY NAME

8. GLOSSARY

PROJECT NAME 19
COMPANY NAME

9. BIBLIOGRAPHY

10. ANNEXURE

Annexure 1: Description of technology and tools used

PROJECT NAME 20
COMPANY NAME

Annexure 2: User Interface with data

Annexure 3: Output Reports with data

PROJECT NAME 21