Documenti di Didattica
Documenti di Professioni
Documenti di Cultura
-1-
CONTENTS
1. Abstract ......................................................................................................... 3
2. Introduction .................................................................................................... 5-7
2.1.
General Introduction
2.2.
Project Description
Objectives of System
3.2.
User Requirements
3.3.
-2-
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.
Features:
-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:
Admin has a right to view / edit the details and addresses of the employees
-4-
SYSTEM:
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.
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.
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.
-5-
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.
Processor
Processor Speed
250MHz to 833MHz
RAM
512MB RAM
Hard Disk
40GB
-6-
Windows XP
Database
Sql Server
ASP.Net
ASP
HTML
Web-Server
IIS
-7-
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.
-8-
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.
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
Validation
Address Book
Employee
Administrator
Category
Member
- 10 -
Login
Permission
Employees
Address Book
Administrator
Category
Member
Logout
- 11 -
Login
Permission
Employees
HR Manager
Change Password
Logout
- 12 -
Login
Address Book
Category
Employee
Member
Change Password
Logout
- 13 -
Class Diagram
- 14 -
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
Like all other diagrams, activity diagrams may contain notes and constrains.
Login Process
Providing
Credentials
Retry
<<No>>
Validation
<<YES>>
Services
- 15 -
Registration Process
Provide
Services
admin validation
<<yes>>
<<NO>>
Invalidate
details
- 16 -
Providing
Credentials
Administrator Process
Login
validation
Employee
Address
Book
Category
Create/Upd
ate/Delete
Permissions
Logout
- 17 -
Member
HR Manager Process
Login
validation
Employees
Create/Upd
ate/Delete
Permission
s
Logout
- 18 -
Employee Process
Login
validation
Address
Book
Category
Member
Create/Upd
ate/Delete
Logout
SEQUENCE DIAGRAM
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
Like all other diagrams, sequence diagrams may contain notes and constrains.
Administrator Sequence
:login
:permission
:employee
: Administrator
1: login request
valid
response
2: create
3: create
response
4: create
response
5: create
response
6: create
response
- 20 -
:address book
:category
:member
HR Manager Sequence
: HR Manager
1: login request
:login
:permission
valid
response
2: create
3: create
response
- 21 -
:employee
Employee Sequence
: Employee
:login
:register
:address book
:category
:member
1: submit form
verify
confirmation
2: login request
valid
response
3: create
response
4: create
response
5: create
response
C
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.
-
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:
- 22 -
Objects
Links
Messages
Like all other diagrams, sequence diagrams may contain notes and constrains.
Administrator Collaboration
2: valid
4: 2: create
:permission
:login
1: 1: login request
5: 3: create
3: response
6: response
:employee
9: 5: create
: Administrator
10: response
7: 4: create
11: 6: create
12: response
:category
8: response
:address
book
:member
- 23 -
Login Collaboration
1: valid
:login
2: 1: login request
3: response
5: 3: create
4: 2: create
: HR Manager
6: response
:employee
:permissio
n
- 24 -
Employee Collaboration
2: verify
5: valid
:register
1: 1: submit form
4: 2: login request
:login
3: confirmation
6: response
7: 3: create
: Employee
8: response
11: 5: create
:address
book
9: 4: create
12: response
10: response
:member
:category
- 25 -
COMPONENT DIAGRAM:
Address
Book
Category
Administrator
Member
Employee
HR Manager
Database
ADO.NET
DEPLOYMENT DIAGRAM
-
A deployment diagram is a diagram that shows the configuration of run time processing
Contents
-
Nodes
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 which are used
- 26 -
Database Server
MSSQL Server
Application Server
VS.NET
USER
ASP.NET
Application
Web
Browser
- 27 -
ER-Diagram
- 28 -
Table Name:
Employee Details
- 29 -
Members Details
- 30 -
A Category Detail
- 31 -
- 32 -
Welcome.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="Welcome.aspx.cs"
Inherits="Welcome" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>Welcome</title>
</head>
<body>
<form id="form1" runat="server">
<div>
<table width="100%" background="BackGround.jpg">
<tr><td align="center">
<asp:Label ID="lblWelcome" runat="server"
Text="Welcome In On Line Address Book" Font-Bold="true"
Font-Size="22pt" ForeColor="#6600ff"></asp:Label>
</td></tr>
<tr><td> </td></tr>
<tr><td align="center">
<asp:Label ID="lblDoAddress" runat="server" Text="Do Your Address On Line" FontBold="true"
ForeColor="#33cccc" Font-Size="14pt"></asp:Label>
</td></tr>
<tr><td height="50px"> </td></tr>
<tr><td align="center">
<asp:ImageButton ID="Imgm" ImageUrl="~/case2-a.gif" runat="server"
OnClick="StartAddress" />
</td></tr>
<tr><td> </td></tr>
<tr><td align="center">
<asp:Label ID="lblAddress" runat="server" Text="(Address Book)" Font-Bold="true"
ForeColor="#000099"
Font-Size="16pt"></asp:Label>
</td></tr>
<tr><td height="190px"></td></tr>
<tr><td> <asp:Button ID="btnAddressBook" runat="server"
Text="Go Inside The Address Book" BackColor="#ff9900" Height="45px"
OnClick="btnInside_Click" />
</td></tr>
</table>
<table background="BackGround.jpg" cellpadding="0" cellspacing="0" width="100%">
<tr><td align="right">
<asp:Label ID="lblName" runat="server" Text="Rahul Saxena" Font-Bold="true" FontSize="16pt"
ForeColor="#6600ff"></asp:Label><br /><br />
<asp:Label ID="lblEmail" runat="server" Text="Email: 14rahulsaxena@gmail.com"
Font-Bold="true" Font-Size="14pt" ForeColor="#6600ff"></asp:Label>
</td><td width="5%"></td></tr>
<tr><td Height="43px"></td></tr>
</table>
- 33 -
</div>
</form>
</body>
</html>
Welcome.aspx.cs is:
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
public partial class Welcome : System.Web.UI.Page
{
protected void Page_Load(object sender, EventArgs e)
{
}
protected void btnInside_Click(object sender, EventArgs e)
{
Response.Redirect("AllRecord.aspx");
}
protected void StartAddress(object sender, ImageClickEventArgs e)
{
Response.Redirect("AllRecord.aspx");
}
}
AllRecord.aspx
<%@ Page Language="C#" AutoEventWireup="true" CodeFile="AllRecord.aspx.cs"
Inherits="AllRecord" %>
<!DOCTYPE html PUBLIC "-//W3C//DTD XHTML 1.0 Transitional//EN"
"http://www.w3.org/TR/xhtml1/DTD/xhtml1-transitional.dtd">
<html xmlns="http://www.w3.org/1999/xhtml" >
<head runat="server">
<title>All Record</title>
</head>
<body>
<form id="form1" runat="server">
<div>
<table cellpadding="0" cellspacing="0" width="90%" border="0" height="100%">
<tr><td width="10px"></td><td><asp:Image ID="imageContact" runat="server"
ImageUrl="~/clip1-c.gif"/> </td></tr>
<tr><td width="10px"></td><td width="90%" background="BackGround.jpg" align="left">
<asp:Button ID="btnSubmit" runat="server" Text="Add New Address"
OnClick="btnSubmit_Click" />
<asp:Button ID="btnSearch" runat="server" Text="Search A Address"
- 34 -
OnClick="SearchRecord" />
<asp:Image ID="ImgMove" runat="server" ImageUrl="~/ball1-a.gif" />
<asp:Label ID="lblSearch" Text="All Address" runat="server" Font-Bold="true"
ForeColor="#ff6600"
Font-Size="16pt"> </asp:Label>
<asp:Image ID="ImgDate" runat="server" ImageUrl="~/hourglass-b.gif" />
<asp:Label ID="lblShowTime" runat="server" Text="Date" Font-Bold="true">
</asp:Label>
<asp:Label ID="lbltime" runat="server"></asp:Label>
</td></tr>
<tr><td height="5px"></td></tr>
<tr><td width="10px"></td>
<td><table background="BackGround.jpg" cellpadding="0" cellspacing="0"
height="100%" border="0" width="100%">
<tr><td height="25px"></td></tr>
<tr><td width="10px"></td><td align="center" >
<asp:DataGrid ID="GridAllRecord" runat="server" AutoGenerateColumns="false"
Width="90%"
DataKeyField="ID"
PagerStyle-HorizontalAlign="Center" BorderStyle="ridge" GridLines="Both"
BorderWidth="2px" BorderColor ="white" BackColor="white"
CellPadding="3" CellSpacing="1"
OnEditCommand="EditAddress" OnDeleteCommand="AddressDelete"
OnItemCommand="Grid_ItemCommand" AllowSorting="true" PageSize=5
OnPageIndexChanged="GridAllRecord_PageIndexChanged"
AllowPaging="true">
<FooterStyle ForeColor="Black" BackColor="#C6C3C6"></FooterStyle>
<HeaderStyle Font-Bold="True" ForeColor="#FFFFFF"
BackColor="#A53A6A"></HeaderStyle>
<FooterStyle BackColor="beige" />
<PagerStyle Font-Bold="true" Mode=NumericPages Font-Underline="true"/>
<Columns>
<asp:BoundColumn DataField=ID HeaderText="ID" Visible="false">
<ItemStyle BackColor="graytext" />
<HeaderStyle BackColor="graytext" />
</asp:BoundColumn>
<asp:TemplateColumn HeaderText="First Name">
<ItemTemplate>
<asp:LinkButton ID="lnkName" runat="server" Text='<%#DataBinder.Eval
(Container.DataItem,"FirstName") %>' CommandName="RecordShow">
</asp:LinkButton>
</ItemTemplate>
</asp:TemplateColumn>
<asp:BoundColumn DataField=LastName HeaderText="Last Name">
<ItemStyle BackColor=GhostWhite />
</asp:BoundColumn>
<asp:BoundColumn DataField=PersonelEmail HeaderText="Personnel(EMail)">
<ItemStyle BackColor=GhostWhite />
</asp:BoundColumn>
<asp:BoundColumn DataField=Mobile HeaderText="Mobile">
<ItemStyle BackColor=GhostWhite />
- 35 -
</asp:BoundColumn>
<asp:EditCommandColumn EditText="Edit Address" HeaderText="Edit Address">
</asp:EditCommandColumn>
<asp:ButtonColumn CommandName="DeleteAddress" HeaderText="Delete
Address"
Text="Delete"></asp:ButtonColumn>
</Columns>
</asp:DataGrid>
</td>
</tr>
<tr><td height="25px"></td></tr>
</table></td></tr>
<tr><td height="15px"></td></tr>
<%-- <tr><td width="10px"></td><td><asp:Label ID="lblTotalRegisterartion" runat="server"
Text="Total Registered Address :"></asp:Label><asp:Label ID="lblRegistered"
runat="server"></asp:Label></td></tr>--%>
</table>
</div>
</form>
</body>
</html>
AllRecord.aspx.cs
using System;
using System.Data;
using System.Configuration;
using System.Collections;
using System.Web;
using System.Web.Security;
using System.Web.UI;
using System.Web.UI.WebControls;
using System.Web.UI.WebControls.WebParts;
using System.Web.UI.HtmlControls;
using System.Data.SqlClient;
public partial class AllRecord : System.Web.UI.Page
{
string connect = @"Data Source=MCN0100;Initial Catalog=AddressBook; Uid=sa; Pwd=";
SqlConnection con;
SqlCommand cmd = new SqlCommand();
SqlDataAdapter da;
DataSet ds = new DataSet();
protected void Page_Load(object sender, EventArgs e)
{
if (!IsPostBack)
{
rebind();
string Time = DateTime.Now.Date.ToShortDateString();
lbltime.Text = Time;
//TotalUsers();
}
}
public void rebind()
{
con = new SqlConnection(connect);
- 36 -
- 37 -
- 38 -
- 39 -
- 40 -
- 41 -
Home Page
- 42 -
HR Manager Login
- 43 -
Delete Employee
- 44 -
Change Password
Logout
- 45 -
Administrator Login
- 46 -
- 47 -
Edit Members
- 48 -
Delete Members
- 49 -
Employee Registration
Delete Employee
- 50 -
Edit Employee
Change Password
- 51 -
Logout
Employee Login
- 52 -
- 53 -
- 54 -
Edit Members
Delete Members
- 55 -
Edit Profile
Change Password
- 56 -
Logout
- 57 -
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.
COMPLETE HTML
Steven Holzner
UNIFIED MODELING LANGUAGE
By Grady Booch, Ranbaugh, Jacobson
SQL FOR PROFESSIONALS
By Jain
C#.NET Black Book
By Evangeleous Petereous
MSDN 2005
By Microsoft
- 58 -