Carporate_4

7/30/2019 Carporate_4

1/48

CONTENTS

1. Abstract .........................................................................................................3

2. Introduction....................................................................................................5-7

2.1. General Introduction

2.2. Project Description

3. System Analysis.............................................................................................8-11

3.1. Objectives of System

3.2. User Requirements

3.3. 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 -


2/48

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-to-

date 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/48

- 3 -


4/48

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/48

- 5 -


6/48

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 -


7/48

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 -


8/48

HARDWARE & SOFTWARE SPECIFICATIONS

3.1 HARDWARE REQUIREMENTS:

Processor : Intel P-IV system

Processor Speed : 250MHz to 833MHz

RAM : 512MB RAM

Hard Disk : 40GB

3.2 SOFTWARE REQUIREMENTS:

Operating System : Windows XP

Database : Sql Server

Server side technology : ASP.Net

Server side scripting : ASP

Client side scripting : HTML

Web-Server : IIS

- 8 -


9/48

- 9 -


10/48

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 -


11/48

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 -


12/48

UML DIAGRAMSUML 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

Validation

Employee

Login

Address Book

Category

Member

Administrator

- 12 -


13/48

Administrator Use Case

Login

Employees

Address Book

Category

Member

Permission

Logout

Administrator

- 13 -


14/48

HR Manager Use Case

Login

Permission

Employees

Change Password

Logout

HR Manager

- 14 -


15/48

Employee Use Case

Login

Address Book

Category

Member

Change Password

Logout

Employee

- 15 -


16/48

Class Diagram

Admin

username : string

password : string

permission : string

create()

update()

delete()

clear()

view()

close()

Registration

login

username : string

password : string

validation : void

view()

close()

validation()

Employees

ID : string

Type : string

Address : string

email : string

query : string

create()

update()

delete()

close()

view()

HRManager

ID : string

username : string

type : st ring

query : string

scheme : st ring

createquery()

create()

update()

delete()view()

close()

Address Book

ID : string

type : string

streetname : string

place : string

description : string

date : date

create()

update()

delete()

close()

view()

Category

ID : string

type : string

name : string

create()

update()

delete()

view()

close()

Member

ID : string

type : stringname : string

category : string

create()

update()

delete()

view()

close()

1..1 1..1

1..n

1..1

0..n

1..1

0..n0..n

0..n

0..n

0..n

0..n

1..1

1..1

1..10..n

1..1

0..n

1..1

0..n

- 16 -


17/48

ACTIVITY DIAGRAM:

An activity diagram shows the flow from activity to activity. An activity is an ongoing

non- atomic 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

Like all other diagrams, activity diagrams may contain notes and

constrains.

Login Process

Validation

Retry

Services

Providing

Credentials

- 17 -


18/48

Registration Process

admin validation

Invalidatedetails

ProvideServices

Providing

Credentials

- 18 -


19/48

Administrator Process

Login

Employee Address

Book

Category Member

Create/Upd

ate/Delete

Permissions

Logout

validation

- 19 -


20/48

HR Manager Process

Login

validation

Employees

Create/Upd

ate/Delete

Permission

s

Logout

- 20 -


21/48

Employee Process

Login

validation

Address

Book

Category Member

Create/Upd

ate/Delete

Logout

- 21 -


22/48

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 -


23/48

Administrator Sequence

: Administrator

:login :permission :employee :address book : category :member

1: login requestvalid

response

2: create

3: create

4: create

response

response

5: create

response

6: create

response

- 23 -


24/48

HR Manager Sequence

: HR Manager :login :permission :employee

valid

2: create

3: create

response

1: login request

response

- 24 -


25/48

Employee Sequence

: Employee

:login :address book :category :member

:register

3: create

response

4: create

response

5: create

response

1: submit formverify

confirmation

2: login request valid

response

- 25 -


26/48

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 -


27/48

Administrator Collaboration

: Administrator

:login :permission

:employee

:address

book

:category

:member

2: valid

1: 1: login request

3: response

7: 4: create

8: response

9: 5: create

10: response

11: 6: create12: response

4: 2: create

5: 3: create

6: response

- 27 -


28/48

HR Manager Collaboration

: HR Manager

:login

:permissio

n

:employee

1: valid

2: 1: login request

3: response

4: 2: create

5: 3: create

6: response

- 28 -


29/48

Employee Collaboration

: Employee

:login

:address

book

:category:member

:register

2: verify

5: valid

4: 2: login request

6: response

7: 3: create

8: response

9: 4: create10: response

11: 5: create

12: response

1: 1: submit form

3: confirmation

- 29 -


30/48

COMPONENT DIAGRAM:

HR Manager

Database

ADO.NET

Administrator Employee

Address

BookCategory Member

DEPLOYMENT DIAGRAM

- A deployment diagram is a diagram that shows the configuration of run time

processing nodes and the components that live on them.

- Graphically, a deployment diagram is collection of vertices and arcs.

Contents

- Deployment diagram commonly contain the following things:

Nodes

Dependency and association relationships

- 30 -


31/48

- Like all other diagrams, deployment diagrams may contain notes and constraints.

- Deployment diagrams may also contain components, each of which must live on

some node.

- Deployment diagrams may also contain packages or subsystems, both of whichare used to group elements of your model into larger chunks.

USER

Web

Browser

ASP.NET

Application

Application Server

VS.NET

Database Server

MSSQL Server

- 31 -


32/48

ER-Diagram

- 32 -


33/48

- 33 -


34/48

Table Name:

Employee Details

- 34 -


35/48

Employee Registration Details

UCategory Details

- 35 -


36/48

- 36 -


37/48

Home Page

- 37 -


38/48

HR Manager Login

- 38 -


39/48

HR Manager Role Dependent Menu Screen

- 39 -


40/48

- 40 -


41/48

Add New Employee

- 41 -


42/48

Delete Employee

- 42 -


43/48

Change Password

- 43 -


44/48

Logout

- 44 -


45/48

- 45 -


46/48

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/48

- 47 -


48/48

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

Carporate_4

Documents

Transcript of Carporate_4