CONTENTS

1. Abstract .........................................................................................................3 2. Introduction....................................................................................................5-7 2.1. 2.2. General Introduction Project Description

3. System Analysis.............................................................................................8-11 3.1. 3.2. 3.3. Objectives of System User Requirements Hardware And Software Requirements

4. Software Design.............................................................................................15-46

5. Database Design.............................................................................................47-85 6. Input and Output Screens 7. Conclusion......................................................................................................94 8. Bibliography...................................................................................................95-97

-1-

ABSTRACT
Corporate address book mainly developed for an organization to store their employees personal data. The System consists of various users like the Administrator, HR manager and Employees. Everyone have their own

responsibilities.HR manager has the privileges to add/delete the employees. Administrator registers the employees and allocates the IDs for the employees. Employees can login and store their personal data.

Corporate address book is a system provided to the corporate adding, deleting, editing the important addresses. Keeping employees contact records up-todate plays a vital role in promoting effective communications.

Features: Making records of addresses of the employees. Making records of details of employees Adding and deleting the employees. Allocating ids to the employees

-2-

-3-

INTRODUCTION: Corporate address book is a system which provides the addresses and details of the employees. After registering with system, administrator allocates a personal id to the employee. Employee can store his personal data in that account. Employee has a facility to view an address book by category wise. Employee can modify his profile.

HR manager maintains the address book.

If any person joins the

organization, his details entered in the address book. At the same time he may delete the employee from the system. He can view the details of the total employees registered to the system.

Administrator has very important role compare to other persons are working with the system. He can have a facility to view address book and details of all the employees and HR managers too. Admin has a right to edit the details of the employees. He can delete employee from a system. This is a system which provides full details and addresses of the employees are working in the organization.

Features: It provides the details and addresses of employees in the organization. Registered Employee can store personal information in his account. HR managers duty to adds / deletes the employee from the system. Admin has a right to view / edit the details and addresses of the employees Admin can add new category to the select category option. -4-

-5-

SYSTEM: Designing and implementing the new links. Designing and implementing the users. Arranging new links as subject wise.

SYSTEM ANALYSIS: System analysis will be performed to determine if it is feasible to design information based on policies and plans of the organization and on user requirements and to eliminate the weaknesses of the present system. The new system should be cost effective. To augment management, improve productivity and services. To enhance user / system interface. To improve information quality and usability. To upgrade systems reliability, availability, flexibility and growth potential.

Objectives of system: The main objective of the system is to maintain a record of the addresses and details of the employees working in the organization. They keep update the document by adding and deleting the addresses and details. It will be available to the top to bottom of the employees.

-6-

Objectives: 1. The job has developed with convenient modules of setting and editing of address details as per the requirements so that they can be implemented easily and productively. 2. A comprehensive report generation technique is in place to put on screen the various categories of reports as per requirements. 3. HR manager is only responsible for the performance of team, he doesnt have full access. But administrator can view all records, this brings in security to the system 4. Employees can view their profiles and also they can modify their profile. 5. Employees have a facility to view address book and he will have a option to change the password. 6. Admin has a right to add new category to the tool and he makes available this option to the employees.

User Requirements: 1. Setting and editing details of employees working in the different departments in the organization 2. Employees can view his/her address book 3. Employee can change his/ her profile and password 4. The system runs on any platform 5. A Help File pertaining to different possible queries. 6. Employee can view by selecting category wise.

-7-

HARDWARE & SOFTWARE SPECIFICATIONS 3.1 HARDWARE REQUIREMENTS:

Processor Processor Speed RAM Hard Disk

: : : :

Intel P-IV system 250MHz to 833MHz 512MB RAM 40GB

3.2 SOFTWARE REQUIREMENTS:

Operating System Database Server side technology Server side scripting Client side scripting Web-Server

: : : : : :

Windows XP Sql Server ASP.Net ASP HTML IIS

-8-

-9-

4.About UML: Unified Modeling Language: The Unified Modeling Language allows the software engineer to express an analysis model using the modeling notation that is governed by a set of syntactic semantic and pragmatic rules.

A UML system is represented using five different views that describe the system from distinctly different perspective. Each view is defined by a set of diagram, which is as follows. User Model View i. This view represents the system from the users perspective. ii. The analysis representation describes a usage scenario from the end-users perspective.

Structural model view i. In this model the data and functionality are arrived from inside the system. ii. This model view models the static structures.

Behavioral Model View It represents the dynamic of behavioral as parts of the system, depicting the interactions of collection between various structural elements described in the user model and structural model view.

- 10 -

Implementation Model View In this the structural and behavioral as parts of the system are represented as they are to be built.

Environmental Model View In this the structural and behavioral aspects of the environment in which the system is to be implemented are represented.

UML is specifically constructed through two different domains they are: UML Analysis modeling, this focuses on the user model and structural model views of the system. UML design modeling, which focuses on the behavioral modeling, implementation modeling and environmental model views.

Use case Diagrams represent the functionality of the system from a users point of view. Use cases are used during requirements elicitation and analysis to represent the functionality of the system. Use cases focus on the behavior of the system from external point of view.

Actors are external entities that interact with the system. Examples of actors include users like administrator, bank customer etc., or another system like central database.

- 11 -

UML DIAGRAMS
UML Diagrams
USE CASE DIAGRAM A use case diagram is a diagram that shows a set of use cases and actors and relationships. Contents Use case commonly contain Use cases Actors Dependency, generalization and association relationships

Overall Use Case

<<include>> Login Validation

Address Book

Employee Category

Administrator

Member

- 12 -

Administrator Use Case

Login

Permission

Employees

Administrator

Address Book

Category

Member

Logout

- 13 -

HR Manager Use Case

Login

Permission

HR Manager

Employees

Change Password

Logout

- 14 -

Employee Use Case

Login

Address Book

Category

Employee Member

Change Password

Logout

- 15 -

Class Diagram

HRManager ID : string username : string type : string query : string scheme : string createquery() create() update() delete() view() close() 1..1 Admin username : string password : string permission : string create() update() delete() clear() view() close() 1..1 1..1

Registration login username : string password : string validation : void view() close() validation() 1..1 1..1

1..1

1..1 1..1

0..n 1..n Address Book ID : string type : string streetname : string place : string description : string date : date create() update() delete() close() view() Employees ID : string Type : string Address : string email : string query : string create() update() delete() close() view() 0..n 0..n

1..1

0..n

0..n

0..n

0..n

Category ID : string type : string name : string create() update() delete() view() close() 0..n

0..n

Member ID : string type : string name : string category : string create() update() delete() view() close() 0..n

- 16 -

ACTIVITY DIAGRAM:
An activity diagram shows the flow from activity to activity. An activity is an ongoing nonatomic execution within a state machine. Activities ultimately result in some action, which is made up of executable atomic computations that result in a change in state of the system or the return of a value. Activity diagrams commonly contain Activity states and action states Transitions Objects constrains. Like all other diagrams, activity diagrams may contain notes and

Login Process

Providing Credentials Retry <<No>> Validation

<<YES>> Services

- 17 -

Registration Process

Provide Services

admin validation <<yes>> <<NO>> Invalidate details Providing Credentials

- 18 -

Administrator Process

Login

validation

Employee

Address Book

Category

Member

Create/Upd ate/Delete

Permissions

Logout

- 19 -

HR Manager Process
Login

validation

Employees

Create/Upd ate/Delete

Permission s

Logout

- 20 -

Employee Process

Login

validation

Address Book

Category

Member

Create/Upd ate/Delete

Logout

- 21 -

SEQUENCE DIAGRAM
An interaction diagram shows an interaction, consisting of a set of objects and their relationships, including the messages that may be dispatched among them. A sequence diagram is an interaction diagram that emphasizes the time ordering of messages. Graphically, a sequence diagram is a table that shows objects arranged along x-axis and messages, ordered in increasing time, along the y-axis.

Contents
Sequence diagrams commonly contain the following: Objects Links Messages Like all other diagrams, sequence diagrams may contain notes and constrains.

- 22 -

Administrator Sequence

:login : Administrator 1: login request response

:permission

:employee

:address book

:category

:member

valid 2: create 3: create response

4: create response

5: create response

6: create response

- 23 -

HR Manager Sequence

: HR Manager

:login

:permission

:employee

1: login request response

valid

2: create 3: create response

- 24 -

Employee Sequence

: Employee

:register

:login

:address book

:category

:member

1: submit form verify confirmation

2: login request response

valid

3: create response

4: create response

5: create response

- 25 -

COLLABORATION DIAGRAM
Collaboration is a society of classes, interfaces, and other elements that work together to provide some cooperative behavior thats bigger than the sum of all its parts. Collaboration is also the specification of how an element, such as a classifier or an operation, is realized by a set of classifiers and associations playing specific roles used in a specific way

Contents
Collaboration diagrams commonly contain the following: Objects Links Messages

Like all other diagrams, sequence diagrams may contain notes and constrains.

- 26 -

Administrator Collaboration
2: valid

4: 2: create :login 1: 1: login request :permission

5: 3: create

3: response

6: response :employee

: Administrator

9: 5: create

10: response 7: 4: create 11: 6: create 12: response 8: response :category

:address book :member

- 27 -

HR Manager Collaboration
1: valid

:login 2: 1: login request

3: response 5: 3: create : HR Manager 4: 2: create 6: response

:permissio n

:employee

- 28 -

Employee Collaboration
2: verify

5: valid :register 1: 1: submit form 4: 2: login request 3: confirmation 6: response : Employee 7: 3: create :login

8: response 11: 5: create 9: 4: create 12: response 10: response :address book

:member :category

- 29 -

COMPONENT DIAGRAM:
Address Book Category Member

Administrator

Employee

HR Manager

Database ADO.NET

DEPLOYMENT DIAGRAM
A deployment diagram is a diagram that shows the configuration of run time Graphically, a deployment diagram is collection of vertices and arcs. processing nodes and the components that live on them.

Contents
Deployment diagram commonly contain the following things: Nodes Dependency and association relationships

- 30 -

Like all other diagrams, deployment diagrams may contain notes and constraints. Deployment diagrams may also contain components, each of which must live on Deployment diagrams may also contain packages or subsystems, both of which

some node. are used to group elements of your model into larger chunks.
Database Server

MSSQL Server

Application Server VS.NET

USER ASP.NET Application

Web Browser

- 31 -

ER-Diagram

- 32 -

- 33 -

Table Name:

Employee Details

- 34 -

Employee Registration Details

UCategory Details - 35 -

- 36 -

Home Page

- 37 -

HR Manager Login

- 38 -

HR Manager Role Dependent Menu Screen

- 39 -

- 40 -

Add New Employee

- 41 -

Delete Employee

- 42 -

Change Password

- 43 -

Logout

- 44 -

- 45 -

Conclusion:

The project has been appreciated by all the users in the organization. It is easy to use, since it uses the GUI provided in the user dialog. User friendly screens are provided. The usage of software increases the efficiency, decreases the effort. It has been efficiently employed as a project management mechanism. It has been thoroughly tested and implemented.

- 46 -

- 47 -

BIBLIOGRAPHY

The following books were referred during the analysis and execution phase of the project SOFTWARE ENGINEERING By Roger.S. Pressman

COMPLETE HTML Steven Holzner

UNIFIED MODELING LANGUAGE By Grady Booch, Ranbaugh, Jacobson

MSDN 2005 By Microsoft

- 48 -