ePROJECT Online Help Desk FPT APTECT

Project Name: Online Help Desk RAR file contains: Documentation (folder): contains documents for developer, installation guide, and user manual. CompiledWeb (folder): contains files and folders for running the web site Online Help Desk. Web (folder): contains the source code and database file (App_Data sub folder). Status_Report file Feedback file.

LE THANH BINH - Student635001

VUONG QUOC HUNG - Student557205

HUYNH KHANH HUY - Student407715

This is to certify that

1 Le Thanh Binh Student635001

2 Vuong Quoc Hung Student557205

3 Huynh Khanh Huy Student407715

Has successfully Designed and Developed.

Online Help Desk

TABLE OF CONTENTS

REVIEW 1 4

1 ACKNOWLEDGEMENTS: 5

2 INTRODUCTION: 5

3 PROBLEM DEFINITION: 5

4 SOLUTION: 5

5 CUSTOMER REQUIREMENT SPECIFICATION (CRS): 6

6 ARCHITECTURE & DESIGN OF THE PROGRAM: 7

7 HARDWARE/ SOFTWARE REQUIREMENT: 9

8 DATA FLOW DIAGRAM (DFD): 10

9 ALGORITHMS (FLOW CHARTS DIAGRAM): 15

10 USE CASES: 21

TASK SHEET OF REVIEW 1 24

REVIEW 2 25

1 Entities: 26

2 Entity Relationship Diagram (ERD): 30

3 Table Defination: 31

4 Database Relationship Diagram: 34

TASK SHEET OF REVIEW 2 35

REVIEW 3 36

USER PAGES 37

ADMINISTRATOR PAGES 57

TASK SHEET OF REVIEW 3 70

CHECKLISTS 71

REVIEW 1

Acknowledgements, Problem,

Solution, and Design

Although, there have been many attempted but by the time the limited practice should not be able to avoid the mistakes and omissions Hope is the understanding of eProject Team at the Head Office And finally, we would like to offer many thanks to all my friends for their valuable suggestions and constructive feedback.

This project is aimed at developing an Online Help Desk (OHD) for the facilities in thecampus This is an Intranet based application that can be accessed throughout the campus.This system can be used to automate the workflow of service requests for the variousfacilities in the campus This is one integrated system that covers different kinds of facilitieslike class-rooms, labs, hostels, mess, canteen, gymnasium, computer centre, faculty club etc

3 PROBLEM DEFINITION:

Registered users (students, faculty, lab-assistants and others) will be able to log in arequest for service for any of the supported facilities These requests will be sent to theconcerned people, who are also valid users of the system, to get them resolved There arefeatures like email notifications/reminders, addition of a new facility to the system, reportgenerators etc in this system

A person should be able to:

 Login to the system through the first page of the application

 Change the password after logging into the system

 See the status of the requests created by him/her (the status could be one ofunassigned/assigned/work in progress/closed/rejected)

 See the list of requests (both open and closed) created by him/her over the past

 Sreate a new request by specifying the facility, the severity of the request (theremay be several levels of severity defined) and a brief description of the request

 Close a request created by him/her by giving an appropriate reason

 See the requests that are assigned to him/her by the facility-heads and update thestatus of requests (after working on them)

 View the incoming requests (if he/she is a facility-head) and assign them toregistered users of the system

 Get help about the OHD system on how to use the different features of the system

 There is also an ‘Administrator’ for doing the Admin-level functions such as creatinguser accounts, adding new facilities to the system etc

6 ARCHITECTURE & DESIGN OF THE PROGRAM:

The application will be made of a Web-based distributed three-tier architecture tosupport multiple user transaction at the same time

Web-Tier

Middle-Tier

Database-Tier

User interface with HTML and ASPX pages

C#(Code-behind) files containing business logic

SQL Server 2005

Web-Based Distributed 3-Tier Architecture of the Project

b) Module Admin:

 Information about Facilities

 Information about Status

 Information about Severity

 Information about Help topics and Questions

II Requirements Functions:

a) Function of the User:

 Login to Website

 Change password himself/herself

 Change user information himself/herself

 View FAQs

 View Messages

 Create a new request and view requests created by him/her over the past

 Update asignee of requests (facility-heads)

 Update status of requests (assignees)

b) Function of the Admin:

 Login to Administrator Pages

 Change password himself/ herself

 Insert, update, delete Users

 Insert, update, delete Facilities

 Insert, update, delete Status list

 Insert, update, delete Severity list

 View and update status of requests

 Insert, update, delete FAQs

 Send message to any users

7 HARDWARE/ SOFTWARE REQUIREMENT:

I Hardware & OS:

 A minimum computer system that will help you access all the tools in the courses is a Pentium 166 or better

 256 Megabytes of RAM or better

 Windows 2003/2008 Server, Windows XP or Windows 7

8 DATA FLOW DIAGRAM (DFD):

Request

Users

Messages

FAQs

Online Help Desk

Figure 1 Context Diagram - Online Help Desk Process

Users

Logon Manage

Requests Requests Facilities

Logoff

Logon Update

User Info Logoff

Figure 3 Update User Info Process

Logon (Admin)

Change Password Logoff

Figure 6 Change Password Admin Process

Users

Logon (Admin) Manage Users Logoff

Figure 7 Manage Users Process

Users Facilities

Logon (Admin)

Manage Status LogoffStatus

Figure 9 Manage Status Process

Users

Logon (Admin)

Manage Severity LogoffSeverity

Figure 10 Manage Severity Process

Users Requests Facilities

Logon (Admin)

Manage Topics LogoffTopics

Figure 12 Manage Topics Process

Users

Logon (Admin)

Manage Questions LogoffTopics Questions

Figure 13 Manage Questions Process

Users Messages

Figure 1: Flow Chart for Login Object

Figure 2: Flow Chart for Add Object

Figure 3: Flow Chart for Edit Object

Figure 4: Flow Chart for Delete Object

Figure 5: Flow Chart for Search Object

10 USE CASES:

10.1. ACTOR:

Actor Name Description

10.2 CONTEXT DIAGRAM:

USERS:

ADMIN:

TASK SHEET OF REVIEW 1

09-Aug-

Completed

02 RequirementCustomer

Specification

2012

Completed

03 Architecture &Design of the

Program

2012

13-Aug-

Completed

04 Data Flow Diagram

15-Aug-2012

2012

17-Aug-Vuong QuocHung

05 Flow Chart Diagram

15-Aug-2012

2012

17-Aug-Huynh KhanhHuy

REVIEW 2 Entity, Entity Relationship

Diagram, Database

Users Requests Facilities Status

Severity Topics Questions Messages

Status

Entity Relationship Diagram (ERD):

Users

PK UserName Password KindOfUser

FullName Email Address Phone

Active

Topics

PK TopicId TopicName

Requests

PK RequestId FK1 Requestor FK2 Facility RequestDate FK3 Severity FK4 Asigness FK5 Status Remark

Facilities

PK FacilityId FacilityName FK1 Header

Status

PK StatusId StatusName

Severity

PK SeverityId

SeverityName

Table Defination:

Users:

Severity:

Facilities:

Requests:

Remark Varchar(200) Not null

Database Relationship Diagram:

Facilities

FacilityID FacilityName Head

Messages

MessageID Recipient Subject Body DateSend

Requests

RequestID Requestor Facility Severity RequestDate Asignee Status Remark

TASK SHEET OF REVIEW 2

19-Aug-

Completed

02 Entity Relationship

Diagram

2012

21-Aug-

Completed

03 Table Definition &

Database

2012

25-Aug-

Completed

REVIEW 3 User Interface

USER PAGES

User Master Page

Brief Description This first page is use log on system

Controls Description

No Control

Properties

2 Page_Load Check login and display login

information

Brief Description This first page is use log on system

Controls Description

Process Description

Requests.aspx (End-users)

Brief Description This page is use manage requests (If kind of user is End-users)Controls Description

3 btnCreate_Click Redirect to Create Request page CreateRequest.aspx

Page Name CreateRequest.aspx

Brief Description This page is use create new request (If kind of user is End-users)Controls Description

datasource_facilities

datasource_severity

1 btnCreate_Click Create new request Requests.aspx

2 SendMessage Send message about creating this

request to requestor and facility-heads

UpdateRequest.aspx

Page Name CreateRequest.aspx

Brief Description This page is use update request with Id.(If kind of user is

End-users)Controls Description

3 TextBox txtRemark Not null From database

2 SendMessage Send message about updating this

request to requestor and facility-heads

CloseRequest.aspx

Brief Description This page is use close a request by giving an appropriate reason

(If kind of user is End-users)

Controls Description

No Control

Properties

Process Description

1 btnClose_Click Update request status to Closed Requests.aspx

2 SendMessage Send message about updating this

request to requestor and facility-heads

Requests.aspx (Facility-heads)

Brief Description This page is use manage requests (If kind of user is

Facility-heads)Controls Description

Page Name AssignRequest.aspx

Brief Description This page is use assign request (If kind of user is Facility-heads)Controls Description

No Control

Properties

Process Description

1 btnAccept_Click Assign request to user Requests.aspx

2 SendMessage Send message about updating this

request to requestor and assignee

Requests.aspx (Assignees)

Brief Description This page is use manage requests (If kind of user is

Facility-heads)

5 GridView GridView1 From database

Process Description

2 btnShowAll_Click Display all requests This page

Brief Description This page is use update status request (If kind of user is

Facility-heads)Controls Description

No Control

Properties

Process Description

1 btnAccept_Click Update status of request Requests.aspx

2 SendMessage

Send message about updating this request to requestor, facility-heads andassignee

Brief Description This page is use manage messages (All users)

2 btnShowAll_Click Display all requests This page

FAQs.aspx

Brief Description This page is use view help topics and questions (All users)

Controls Description

2 btnShowAll_Click Display all requests This page

Brief Description This page is use update user information (All users)

Controls Description

No

Control

Properties

2 btnSave_Click Update information of user This page

ADMINISTRATOR PAGES

Admin Master Page

Brief Description This first page is use log on system

Controls Description

5 LinkButton btnLogOut Log Out

Process Description

Brief Description This page is use manage requests (view and delete request).Controls Description

Page Name Facilities.aspx

Brief Description This page is use manage facilities

Controls Description

datasource_users

Brief Description This page is use manage status list

Controls Description

Brief Description This page is use manage severity list

Controls Description

Brief Description This page is use manage facilities

Controls Description

Brief Description This page is use manage questions

Controls Description

Process Description

Messages.aspx

1 TextBox txtSubject Not null “”

datasource_users

Process Description

Brief Description This page is use manage users

Controls Description

8 CheckBox ckbActive checked

Process Description

Brief Description This page is use change password of Admin

Controls Description

Not null and match txtNewPass

“”

TASK SHEET OF REVIEW 3

Project

Ref No.

Project Name:

Online Book Store

Date of Preparation of Activity Plan

Complete Date

Completed

03 Database & Store

05 Testing &

Check List of Validation:

Can insert, update, delete and view all tables data after logging in? Yes

Do all the options present in the application display the correct result? YesDoes the application’s functionality resolve the user problem and satisfy

their needs ?

Yes

Has the hardware and software been correctly chosen ? Yes

Submission Checklist:

1 Are the users able to enter the Web site after

validation is performed on the Login Name and

Password?

X

2 Are the users search requests, messages, FAQs

3 Do all the Web page contents devoid of spelling