Chapter 1 INTRODUCTION

Our project titled, as TaskPro is basically a WEB BASED project. The system is developed to provide a platform for the organization which needs monitoring of different projects and employees working on. It provides human resource management along with monitoring activities performed by the employees.

PROJECT OVERVIEW
The system is designed and developed keeping in view that it should be user friendly,

Navigation should be easy to use, and our main focus in this application will be software house. The Sr. Project Manager will define the project and assign it to the Project Manager. Project Manager will see that which team or employees are eligible to that project and then he will assign the task to team or employees. The each employee will update the assigning task daily and Team Lead, Project Manager and Sr. Project Manager can see the progress report of each employee and also the progress of the project. There will also be other modules that are necessary for any organization. They also provide a very good technical support in the form of tutorial so that user can easily use the system and can enjoy the facilities provide by the system. The interface of the system is developed keeping in mind that it should be good looking, attract at first sight, easy to understand and self-explanatory. The system is also equipped with state of security features, which enables only the authorized people to view or modify the sensitive information. The information is protected by login and password, which can be assigned to each single user of the system.

PROJECT SCOPE
1

1.2

PROJECT SCOPE
The scope of a system means that which areas are being covered by the system. The scope

clearly defines the boundaries of the proposed system. The system includes the following functionality. It will used to define project and create different activities to further categorize the projects. It will help administrator to manage users of system and their relative permissions. It will keep record of employees availability and their skills and management in assigning him to different activities of the projects It will help top management to view progress on particular project or employee with out calling any meeting. It will help employee to manage their To-Do by maintaining a To-Do list as well as automatically maintain their login history. Time Line and Gantt Charts will allow users to manage time for particular task or project along with notifications.

1.3

PROPOSED SOLUTION

The TaskPro will provide the best way to administrator, Project Managers and employees to get benefits from the system. It will provide the users such environment which enables them to communicate with each other more efficiently and more interactively. User will be given the facilities such as managing Projects, Task, To-Dos, Reminder, User handling and other management related stuff to handle the project.

Administrator Project Manager Project Manager Team Lead Developer Team Lead

Application Interface GUI

Web server
Login

Administrator Module(User Management) Managerial Module(View, Delete, Update and Assign Project/task,)

Data Base

Developer

User Module(View, Submit and Update Task)

4.4
5.1.

PROPOSED SYSTEM COMPONENTS

User Management

This module will maintain the overall records of users in software house it will keep the information about users like user name, password, email, CNIC number etc. the user record can be add, update, view and delete. 5.2. Project Distribution

This module will keep the information about the project such as project id, title, starting date, ending date etc. Also give information about the assigned project to the user and shows the status of each project. 5.3. Task Distribution

User will divide the project into number of tasks and measure its level of priority. This module includes the identification of task, distribution of task and hierarchy of the task. 5.4. Messages 3

It will provide the users such environment which enables them to communicate with each other more efficiently and more interactively. 5.5. Reports Generating

This module will allow the users to generate the progress report of each employee and also the progress of the project.

1.5

PROPOSED SYSTEM OUTPUT

As this is a web based application user can access it through internet. Admin will create users, define there respective responsibilities and monitor the activities of the users. Sr. Project Manager is responsible for defining and assigning a project to respective Project Manger. Project is divided into the number of tasks by Project Manager, who assigns them to the team or developer. Gantt Charts and Time Line of a project are generated by the system on given stats of projects or tasks. Users can communicate with each other more efficiently and more interactively. The progress reports of each employee and project are generated.

1.6MAIN FEATURES OF THE PROPOSED SYSTEM

1.6.1 Create New Account

Before using this application user must have an account. The administrator will create the account of any user. 1.6.2 Update / Delete Existing Account

The existing account can be updated and deleted by the administrator as per the user requirement is concern or as per administrator requirement is concerned.

1.6.3

Identification of Task

User will divide the project into number of tasks using Gantt charts and measure its level of priority. 1.6.4 Task Distribution

To distribute the task between the assigned team or employee this assignment will be done by watching the profile of the employees.

1.7 INTRODUCTION TO TOOLS & TECHNOLOGIES USED

To implement our idea we have selected PHP to implement the business logic, HTML will be used in the presentation layer and MySQL will be used as the database for this purpose. As the PHP is a web based language only so to implement the functionality which attract by user we implement JQuery. To draw use case diagrams we have used Microsoft Office Visio. Here is the complete list of tools and technologies we have used in this project. Dream Weaver WAMP Server Adobe Photoshop CS5 Microsoft Office 2007 Microsoft Windows XP

Chapter 2 REQUIREMENT ANALYSIS

Software Requirement Specification (SRS)
2.1 Introduction Our project title, as TaskPro is a web based application which can be utilized anywhere in the organizations which are working manually. It is provides convenience and strong collaboration between Sr. Project Manager, Project Manager and Team members to perform different software development management activities. Hence provides an environment where team members and project managers working in any particular software house communicate and coordinate with each other in order to manage their activities. 2.2 Purpose The main purpose of the system is to provide the user with following facilities. Administration Related Definition of users roles and responsibilities. User Authorization Grant and revocation of the User Access Rights. Monitoring of Users activities. Secure Information Management Employee Appraisal and Appreciation Management Related Manage projects Manage TO-DOs and tasks Manage reminders Definition of Work Break Down Structure(WBS) User Related User can enter work description by specifying the project, tasks and expected hours. 6

 System will provide the facility to the user to manage his TO -DOs. System will provide facility to the user to update status of assigned work (completed or not). System will provide the facility to generate reports and make views of different projects tasks TO -DOs and reminders. System will allow the user to view login history of any particular user.

2.3Proposed Solution overview

Our purpose system is designed and development keeping n view that it facilitates the employees and management to communicate while working on any project. It includes identification of resources, supply chain of resources, hierarchy of the task, user profile and report generation. The employee information is helpful for the management to find the right developer for the right task. The task is given on daily and weekly basis and in response report will be generated. 2.3.1 Modules of the Proposed Solution Admin Module Definition of users roles and responsibilities. User Authorization Grant and revocation of the User Access Rights. Monitoring of Users activities. Secure Information Management Employee Appraisal and Appreciation Project Management Module Project Definition Assigning Projects to Projects Manager Definition of Work Break Down Structure(WBS) Activity Management Module Defining Activities and their Mutual Dependencies. Defining of work break down structure. 7

 Defining Task Assign Task Update Tasks status Message Module Compose Message Inbox Sent Messages Notifications File Module Upload Project Documents Download Project Documents Delete Project Documents Create Project Directory at the time of project Creation Reporting Module On Demand Report Generation Report Distribution

2.4

Specification Requirements
2.4.1 Functional Requirements Update Account Use Case Name Precondition Basic Path Update account User is logged in. 1. User sign in using their account ids. 2. User selects the profile option. 3. Profile for specific user will be displayed. 4. User selects the update option to modify their accounts. 5. Account information is displayed and user modify whatever wants. Alternative Paths 6. After modification user submits the form. None 8

Post condition Exception Paths Other Delete Account Use Case Name Precondition Basic Path

Account updated successfully. The user may abandon the modification at anytime. None

Delete account User is logged in. 1. User sign in using their account ids. 2. User selects the profile option. 3. From their, user chooses delete option to remove his/her account from the application. 4. Confirmation message displayed that your account has been deleted. None Account deleted successfully. The user may abandon the deletion at anytime. None

Alternative Paths Post condition Exception Paths Other Task Identification Use Case Name Precondition Basic Path

Task identification User is logged in. 1. User sign in using their account ids. 2. User selects the profile option. 3. From their user chooses task identification option to identify task from the application. None Task identified successfully. The user may abandon task identification at anytime. None

Alternative Paths Post condition Exception Paths Other

Task Distribution Use Case Name Precondition Basic Path Task distribution. User is logged in. 1. User sign in using their account ids. 2. User selects the profile option. 9

3. From there user chooses task distribution to identify task Alternative Paths Post condition Exception Paths Other from the application. None Account distributed successfully. The user may abandon the task distribution at anytime. None

2.4.2 External Interface Requirements

User Interfaces The interface of the system if user friendly. The data retrieval is made easy and simply, so that even a layman administrator can handle the data efficiently. Create user form. Accounts modification and deletion interfaces. Defining and assigning projects interfaces. Defining and assigning task interfaces. Managing different sort of organizational records.

Hardware interfaces Minimum 512MB RAM. Minimum required memory 3GB. Pentium IV.

Software Interfaces It will work under the versions of windows XP and higher versions. It is required to operate under windows environment. Following are the required software interfaces. Dream weaver WAMP server Adobe Photoshop CS5 Microsoft Office 2007 Microsoft Windows XP

10

2.4.3Performance Requirements
2.4.3.1 Response Time

The primary purpose of our web based application is to facilitate the users for communication as fast as possible. So the response time of this application is less than 20 seconds, means that user can send and receive messages within 20 seconds. Response time is not just related with the communication it also refers to how fast and accurate your application is to respond to the end users.

2.5

General Constraints
2.5.1.1 Security

Security is one of the key issues in measuring the performance of any system. Over application is fully secure from unauthorized access. Only those users can access those have an account on this application. All the user are secure and saved in database and end users are not allow to view the database created and managed by the developers. 2.5.1.2 2.5.1.2.1 Hardware Constraints For Server: 2.5.1.2.2 Dual-Core 2.0. 1GB RAM. Minimum 160GB hard disk.

For Client: Pentium IV Minimum 512MB RAM. Minimum required memory 3GB.

2.6 PROJECT OBJECTIVES

The objectives of the project describe that what is to be ultimately achieved and how efficiently it is to be achieved. Web based system are always efficient in performing any task. 11

The proposed system is required to fulfill the following objectives. To assure the availability of the right information at the right time. Means that every required information should be available when users want to access that information To make the information storage, processing and retrieval efficient. It is basically related to the performance of the proposed system that how efficient your system in providing in any kind of information, how much fast your system is in any kind of data processing or data retrieving from the database. The interface of the proposed system should be self explanatory and easy to understand that what the purpose of each interface is and how the interfaces are linked with each other. The proposed system can easily be enhanced as requirements of end users grow and can also be modified with so much ease.

12

2.7

USE CASES

Log In: Actors: Administrator, Sr. Project Manager, Project Manager and Employees. Pre Condition: User wants to login for using the services provided by the application. Post Condition: User gets successfully log in. Description: User enters its login id and password to login so that can use the services. When it submits this information login id field and password field are validated on client side for possible validation errors. Then it is searched in the database to check whether a valid person is requesting to login. Then login session of the user starts. Actor Response System Response User enters login name and password System validated field values on client that are required fields of he system to side login. User submit these information If System found correct data after validating fields than system successfully login and redirect the user to the main page of the system. Log Out: Actors: Administrator, Sr. Project Manager, Project Manager and Employees. Pre Condition: User after using the services (provided by the application) wants to log out. Post Condition: User gets successful log out. 13

Description: When user wants to log out it presses the logout button. Then its session is terminated and it is informed about its successful log out. Actor Response 1. The use case is executed when admin clicks on log out button System Response 1. The system will prompt user for conformation. 2. System will successfully sign out the user.

Create Employee
Actors: Administrator Pre Condition: Administrator wants to create employee account by defining their roles to create / assign or project / activity. Post Condition: Administrator creates account successfully. Description: Administrator enters its employee name, father name, login name, role, gender, cell, email, address, CNIC, and password to create employee account so that they can use the services. When it submits this information employee account is created in a database successfully. Actor Response System Response Administrator enters required filed System validated field values on client values and assigned roles by selecting side by using java script if found invalid user rile from drop down provided to data type or empty display an error the user. Administrator information submits massage. these System successfully create user

account in to the database

Define Project:
Actors: Sr. Project Manager 14

Pre Condition: Sr. Project Manager wants to define project. Post Condition: Sr. Project Manager create project successfully in a database.

Description: Sr. Project Manager enters its project code, name, description and category. When it submits this information project is created successfully in a database. Actor Response System Response Sr. Project Manager enters required System validated field values on client values that are provided to them. side by using java script if found invalid data type or empty display an error When user click on submit button massage. System successfully define project in to project in to the database

Assign Project:
Actors: Sr. Project Manager Pre Condition: Sr. Project Manager wants to assign project that is already created to specific project manager Post Condition: Project assigned to Project Manager successfully. Description: Sr. Project Manager selects project name, project manager name from drop down list and enters project assigned date. When it submits this information project assigned to specific project manager that is elected by Sr. Project Manager successfully. Actor Response System Response Sr. Project Manager click define System redirect user to define project 15

projects link page User selects specific project to assign System shows list of already Project Manager Manager from the database. When Sr. Project Manager submits this Project assigned to selecting Project information Manager in to the database successfully

Define Project Team:

Actors: Project Manager Pre Condition: Project Manager wants to create project team to work on given project. Post Condition: Project team created successfully in the database. Description: Project Manager enters its team code, team name and description and selects multiple employees name from list. When it submits this information project team is created successfully in the database. Actor Response System Response Project Manager click define project System redirect user to define project team link team page. Project Manager enters all required System validated all theat fields on client fields. side byusing java script, if found any incorrect data type or null value display Project Manager selects an error message to the user. multiple System shows all employees whose roles are only user.

employees

Assign Project Team:

Actors: Project Manager Pre Condition:

16

Project Manager wants to assign project team pm specified project that given to him. Post Condition: Project team assigned successfully. Description: Project Manager selects project and team from drop down list. When it submits this information project team assigned to specified project in a database successfully. And only these team members can work or have access on a given project. Actor Response System Response Project Manager selects specific team System shows all defined project team to work on project form drop down list from database to the user in the drop provided down list. Project Manager selects specific project System shows all defined projects

to assign project from drop down list retrieving from database to the user in the provided. drop down list. When Project Manager submits this Selected team assigned to selected information defined project with its own team members in to the database successfully.

Define Activity:
Actors: Project Manager Pre Condition: Project Manager wants to define activity. Post Condition: Project team creates activity successfully in the database. Description: Project Manager enters its activity group code, name and description and selects project in which he want to create activity group from drop down list. When it submits this information activity group is created successfully in the database. 17

Actor Response System Response Project Manager selects project name System shows all defined project names from drop down list in which user want from database. to create activity. Project Manager enters required field System validated all that fields on client values. side by using java script, if found invalid data type or null value display an error message to the user. When Project Manager submits this System will successfully define activity information in database of corresponding projects name.

Define Task:
Actors: Project Manager Pre Condition: Project Manager wants to define Task. Post Condition: Project team creates task successfully in the database of specified project. Description: Project Manager enters its activity code, name and description. When it submits this information activity task is created successfully in the database. Actor Response System Response Project Manager selects project name System shows all defined project names from drop down list in which user want from database. to create activity Project Manager selects activity name System shows all defined activity names from drop down list in which user want from database. to create task. Project Manager enters required field System validated all that fields on client values. side by using java script, if found invalid data type or null value display an error message to the user. 18

When Project Manager submits this System will successfully define task in information. database of corresponding project.

Assign Task:
Actors: Project Manager Pre Condition: Project Manager wants to assign Task. Post Condition: Project Manager assign task to specified team member successfully in the database of specified project. Description: Project Manager first view unsigned tasks and then selects employee name from drop down list , enters assigned date, due date and check notify selected employee check box to deliver message. When it submits this information activity assigned to specified employee in a database successfully

Actor Response System Response Project Manager click on assign task System redirect project Manager to link assign task page. Project Manager selects specific to task System shows list of already defined task to assign to user from drop sown list after retrieving it from the database. provided to them. When Project Manager submits this Task assigned to selecting user in to the information database successfully.

Update / Submit Activity:

Actors: Employee Pre Condition: Employee wants to submit activity when it finished work. 19

Post Condition: Activity submit in a database successfully. Description: When employee wans to submit it click the submit button. Then its activity is submitted and it is informed about its successful submission. Actor Response Employee click on user penal link. System Response System redirect the user towards submit

activity page. If Activity assigned to the user it is to System will shows all activities assigned be displayed and when user click in to that particular user if assigned activity Edit link. exists in user database and system shows the update activity user control. Employee update the assigned activity System successfully update the status of status and click on update button. the assigned activity in to the database.

Attach Document:
Actors: Sr. Project Manager, Project Manager or Employee Pre Condition: User wants to attach project documents related to their work. Post Condition: Attachment of documents takes place on the server side successfully. Description: When user wants to attach documents it click the project document tab where user also able create folder by providing folder name in a root tree and attach documents by providing path of that document which want to be uploaded by clicking browse button and user type description and version of that document. When user click upload button, then documents uploaded on server side successfully. Actor Response System Response User select project name from drop System will show all defined projects 20

down list. after retrieving from database. User click on upload button after System upload the file on server side browse specific file that user wants to successfully in the specified project upload. directory that user selects.

Download Document:
Actors: Project Manager or Employee Pre Condition: Employee wants to download project documents related to their assigned activity. Post Condition: Download take place on Client PC successfully. Description: When user wants to download it click the save link, then documents downloaded on client side successfully by providing location where you want to save document. Actor Response User click project document link. System Response System will redirect the user towards the

project document page. User selects the project name from drop System will show that specified project down list provided to view project documents by retrieving form database. documents. User click file name link. System will open save file dialogue box to save document on client side.

Notify Employee:
Actors: Project Manager or Employee Pre Condition: Employee wants to notify selected when activity assigned or project documents are uploaded. Post Condition: Messages given to members successfully. 21

Description: When user wants to compos messages they select recipient to who notify have to be send, selects importance of message by selecting normal or high from drop down list, type subject and description of a message. When it submits information messages send to specify recipients in their inbox successfully. Actor Response System Response User check notify selected employee System will transfer messages to selected link employee inbox and prompt for new message received when user login.

Generate Report:
Actors: Sr. Project Manager, Project Manager or Employee Pre Condition: Sr. Project Manager, Project Manager or Employee wants to view progress report of assigned projects. Post Condition: User view report about project processing successfully. Description: When user wants to view report about project processing he simple click view report and after doing that report is generated from database for user view. Actor Response User click to view reports System Response System will generates database successfully. report from

Update Account:
Actors: Administrator Pre Condition: User must be authenticated. Post Condition: System will make the updating. Description: 22

Before this use case can be initiated, the user has already signed in. Actor Response System Response The use case is executed when admin User select the profile option clicks on update account button. Profile for specific user will be displayed. User selects the update option to modify their accounts. Account information is displayed and user modified whatever he/she wants. After modification user submit the form.

Delete Account:
Actors: Administrator Pre Condition: User must be authenticated. Post Condition: System will delete an account. Description: Before this use case can be initiated, the user has already signed in. Actor Response System Response The use case is executed when admin clicks on User selects the profile option. delete account button. From there user chooses delete ioption to remove his/her account from the application. Confirmation message displayed that account has been deleted.

23

Chapter 3 SOFTWARE DESIGN

3.1 USE CASE DIAGRAM

TaskPro
Submit Activity View Project

Update Activity

Define Project

Developer

Download Document

Assign Project

Login

Generate Report
*

Project Director
*

Define Activity

Define Task
*

Assign Task

Aunthenticcate User

Project Manager

Define Project Team

Create Employee

System Administrator

Define Team

Modify Employee

Attach Document

Notify Employee

24

3.2

CLASS DIAGRAMS

ROLE Employee -e_id : int -e_name : String -e_email : String -e_address : String -e_nic : String +viewassignactivity () : bool +submitactivity () : bool +notifyactivity () : bool extends extends extends has * -r_id : int -r_name : String -r_desc : String +addrole() +modifyrole() +deleterole()

Compose/ Notify

Message * -m_id : int -m_name : String -m_eid : int -m_from : String -m_subject : String -m_body : String -m_read : String +composemessage () +viewmessage () +sendmessage () +deletemessage ()

May or may not

Sr. Project Manager +addusers() +definerole() +defineproject() +assignproject () +viewproject() 1

Project Manager +defineteam() +defineactivities () +definetask() +assigntask() +projectdocumentation() can define * Project Team 1

Administrator +adduseraccount() +modifyuseraccount() +deleteuseraccount()

Team Members -* * +addmembers() +deletemember() +modifymembers() +viewmemberslist ()

Task -composed of 1 -t_id : int -p_id : int -t_name : String -t_desc : String +addtask() +modifytask() +deletetask() +viewtask() -* -composed of 1 has can upload or Download *

-pt_id : int -pt_name : String -pt_desc : String +addteam() +modifyteam() +deleteteam() Assigne to 1 Project -p_id : int -p_name : String -p_desc : String -cat_id : int +addproject() +assignproject() +modifyproject() +deleteproject() +searchproject() +viewproject()

Category * -cat_id -cat_name -cat_desc +addcat() +modifycat() +deletecat()

Documentation -d_id -p_id -d_file -d_desc -doc_size +uploaddoc() +downloaddoc() +viewdoc() +deletedoc()

25

3.3 ACTIVITY DIAGRAMS

3.3.1 Assign Project

Sr.Project Manager

Software system

Database

Request Unassigned Projects Find Unassigned Projects Search in Database No Project Found

Select Project

Request Project Manager

Find Project Manager

No Project Manager Found

Search In Database

Sekect Project Manager

Enter Required Data Save Request

Update Database

3.3.2 Assign Project Team

26

Project Manager

Software system

Database

Request Defined Project Find Defined Project Search in database No Project Found

Select Activity

Found

Request Defined Team Find Team

No Defined Team

Search in Database

Select Team

Found

Submit Data Save Request

Team Assigned

Update Database

27

3.3.3 Define Project Team

Project Manager

Software system

Database

Request Project Team Member

Find Project Assigned Members Search in database

No Team Member Found

Found

Select Team Member

Submit Data Save Request

Project team defined

Update Database

3.3.4 Define Project / Task

28

Project Manager

Software system

Database

Request Define Project /Task Page

Submit Data

Save Request

Already Defined

Project / Task Defined

Update Database

29

3.3.5 Assign Task

Project Manager Software system Database

Request Unassigned Activities Find Unassigned Activities Search in database No Task Found

Found
Select Activity

Request Team Member Find Team Member

No Employee

Search in Database

Select Team Member

Found

Submit Data Save Request

Update Database

3.4

SEQUENCE DIAGRAM
30

3.4.1 Create User

Admin

User Management

Database

Request For CreateUser Display Form

CreateUser() Response () Responce ()

Enter Name Enter Password Enter Adress/ Email ChooseDesignation Submit Form User Sucessfully Created S ubmit () Response() Response ()

3.4.2 View User

Admin

User Management

Database

Request User View Display User L ist

view User() Response () Response ()

31

3.4.3 Update User

Admin

User Management

Database

Request For UpdateUser View Record() Display Record Response() Responce ()

Modify Record UpdateRecord Sucessfully Updated

Update()

Response()

Response ()

3.4.4 Delete User

Object2

User Management

Database

Request For DeleteUser User Deleted Successfully

Delete() Response () Response()

32

3.4.5 Define Project

Sr. Project Manager

Project Management

Database

Request DefineProject Display Form

DefineProject() Response Response()

Enter Project Name Enter Code Enter Description DueDate Submit Form Project Succesfully Defined Submit() Response() Response

3.4.6 Assign project

Sr. Project Manager

Project Management

Database

Request For Unassigned Project Unassigned Project Displayed

Unassigned() Response Response()

Select Project Manager Submit Form Project Assigned Succesfully Submit () Responce () Response()

33

3.4.7 Define Activity

Project Manger

Activity Management

Database

Request For defineActivities L Of Project Displayed ist

Show Project () Response () Response ()

DefineActivities Activity Name Activity Description Add Activity Activity Succesfully Created Add Activity() Response Response

3.4.8 Assign Task

Project Manager

Activity Management

Database

Request For Unassigned Task Unassigned Task Displayed

UnassignedTask() Response Response ()

Select Developer Submit Form Task Assigned Succesfully Submit() Responce () Response()

34

3.4.9 Generate Report

Developer

Reports

Database

Request For GenerateReport List Of Project Displayed

Show Project) ( Response Response

Select Project Click Show Report Display Generated Report Generatereport Response Response()

3.5

COLLEBORATION DIAGRAM

3.5.1 Define Project

1: Request Define Project 4: Display Form 5: Enter Project Name 6: Enter code 7: Enter description 8: Due Date 11: Project Successfully Defined

Project Managment
* * *

Top Package ::Sr.Project Manager

2: Define Project 3: Response() 9: Submit 10: Response()

*

Datebase

35

3.5.2 Define Activity

1: Request Activity Project 4: List of project Displayed 5: Define Activity 6: Activity Name 7: Activity Description 8: Add Activity 11: Activity S uccessfully Created
* *

Activity Managment
*

Top Package ::Project Manager

2: Show Project 3: Response() 9: Add Activity 10: Response()

*

Datebase

3.5.3 Generate Reports

1: Request For Generated Report 4: List of project Displayed 5: Select project 6: Click Show Report 9: Display Generated Report

Reports
* * *

Top Package ::Developer

2: Show Project 3: Response() 9: Generate Report 10: Response()

*

Datebase

36

3.6

COMPONENT DIAGRAMS

37

3.7

DEPLOYMENT DIAGRAMS

38

3.8

ER DIAGRAM (Optional)

3.9

Data Dictionary

TCP/IP
As this project involves management of database at server side so a database design is also crucial in the design model so that it can easily be deployed in the implementation phase.

TCP/IP

TABLE NAME: user

FIELD NAME u_id u_role u_name u_pass u-Cell u_gender u_email u_address u_nic u_status

DATA TYPE
int int varchar varchar varchar varchar varchar varchar varchar tinyint

SIZE
11 1 25 50 15 6 25 100 15 1

CONSTRAINTS

TCP/IP

TABLE NAME: team_user

39

FIELD NAME

DATA TYPE

SIZE

CONSTRAINTS

t_id u_id

int int

11 11

TABLE NAME: team

FIELD NAME DATA TYPE SIZE CONSTRAINTS

t_id t_name t_desc

int varchar varchar

11 25 50

TABLE NAME: task_log

FIELD NAME FIELD NAME

tl_id t_id u_id tl_desc updated_at

int int int varchar datetime

SIZE 11 11 11 500

CONSTRAINTS

TABLE NAME: task

FIELD NAME FIELD NAME

t_id a_id t_code t_name t_desc t_duedate

int int varchar varchar varchar date

SIZE 11 11 15 25 50

CONSTRAINTS

TABLE NAME: role

FIELD NAME FIELD NAME

r_id r_name

int varchar
40

SIZE 11 50

CONSTRAINTS

r_desc t_desc

varchar varchar

50 50

TABLE NAME: project

FIELD NAME FIELD NAME

p_id p_code p_name p_desc define_date status p_cat

int varchar varchar varchar date tinyint int

SIZE 11 7 25 500 1 11

CONSTRAINTS

TABLE NAME: pms

FIELD NAME FIELD NAME

id touser fromuser subject message read deleted datesent

int varchar varchar varchar text enum enum datetime

SIZE 11 40 40 150

CONSTRAINTS

TABLE NAME: doc

FIELD NAME FIELD NAME

d_id p_id d_file d_desc

int int varchar varchar

41

SIZE 11 11 150 50

CONSTRAINTS

d_size uploaded_by uploaded_date

varchar int date

50 11

TABLE NAME: cat

FIELD NAME FIELD NAME

cat_id cat_name cat_desc

int varchar varchar

SIZE 11 20 50

CONSTRAINTS

TABLE NAME: assign_team

FIELD NAME FIELD NAME

at_id p_id t_id

int int int

SIZE 11 11 11

CONSTRAINTS

TABLE NAME: assign_task

FIELD NAME FIELD NAME

at_id at_cod p_id t_id u_id assign_date status due_date

int varchar int int int date int date

SIZE 11 50 11 11 11 11

CONSTRAINTS

42

TABLE NAME: assign_project

FIELD NAME

FIELD NAME

ap_id p_id u_id assign_date status due_date

int int int date varchar date

SIZE 11 11 11 10

CONSTRAINTS

TABLE NAME: activities

FIELD NAME

FIELD NAME

a_id p_id a_cod a_name status a_desc

int int varchar varchar tinyint varchar

SIZE 11 11 10 20 1 60

CONSTRAINTS

43

Chapter 4 PROJECT MANAGEMENT

5.1 5.2 Milestones Project Closeout Report 5.2.1 5.2.2 5.3 5.3.1 5.3.2 5.3.3 5.3.4 Project Deliverables Operations & Maintenance

Risk Management Introduction (Risk Management System) Purpose Risk Management Responsibilities Risk Analysis Summary

5.1 5.2

Milestones Project Closeout Report

A. Project Deliverables 1.1.1 List all Project Deliverables and the date each was accepted by the user. Identify any contingencies or conditions related to the acceptance.
Deliverable Date Accepted Contingencies or Conditions

B. Operations and Maintenance 44

Describe the plan for operation and maintenance of the product, good, or service delivered by the project. State the projected annual cost to operate and maintain the product, good, or service. Identify where and why this projection of cost differs (if it differs) from the Project Proposal. If the operation and maintenance plan is not in place, what is the target date for the plan and what is the impact of not having operations and maintenance for the product, good, or services in place. 1. Operations and Maintenance Plan 1.1.1.1.1.1.1.1

C. Project Resources
List the Resources specified in the Resource Plan and used by the project. Identify to whom each resource was transferred and when it was transferred. Account for all project resources utilized by the project.

Person or Resource (Describe or name the resource used) 1.1.1.1.2 Project Team Organization Who Received Resource Turnover Date

Customer Support

1.1.1.1.3

Facilities

1.1.1.1.4

Equipment

45

1.1.1.1.5

Software Tools

1.1.1.1.6

Other

Individual

Responsibility

5.3.4

Risk Analysis Summary

Using the table provided, list each risk identified, the probability of occurrence, the expected impact level, a description of the impact, and when the risk event is likely to occur.

1. 2. 3.

Probability of Occurrence is the percentage of likelihood that the risk will occur. Impact Level is a score of one to five. One is the least impact and five is the highest impact. Provide time frames in fiscal years and quarters, if known.

5.3.4

Risk Response Summary

Prioritize and describe the plans for responding to each risk identified and evaluated in Section C.

46

Risk Priority Risk Number Risk Name

Responsible Person Mitigation Action(s)

Response Trigger

47

Chapter 5 IMPLEMENTATION
6.1 Visual Basic .NET 6.1.1 6.1.2 6.1.3 6.2 6.2.1 6.2.2 6.2.3 6.2.4 6.2.5 6.2.6 6.3 Solve Todays Problem more effectively Get on the Fast track to building tomorrows application today Upgrade for success Developer productivity Improved performance and scalability Enhanced reliability Easy deployment New application models System requirements for visual studio. NET

ASP.NET

Windows XP 6.3.1 6.3.2 6.3.3 6.3.4 Easy to use Revolutionize the way remote users work Advanced management, deployment and support tools System requirements for windows XP professional

6.4

Microsoft Access 2002 6.4.1 6.4.2 Standard features System requirements for Microsoft office XP

48

Chapter 6 SOFTWARE TESTING

7.1 Deriving Test - Case Specifications

The specifications for testing are derived from customer requirements, from the study of design code of software modules, and from screen or visual interfaces through which the user interacts with the system. Test-case specification in performed for system testing by keeping in mind several issues, which are discussed in the following subtopics;

7.2

State the Test Environment

The software is tested at XY Soft Solution (XYSS) with the required hardware and software requirements. The system used for Inventory Management at XYSS. Each machine in based on a Pentium processor with 10 GB HDD and 256 MB RAM. The software configuration is WindowXP with Visual Basic and MS Assess installed.

7.3

Testing Identification

A specific test should be planned for every test level to test all system components. The test procedure should be detailed so that the system meets all user requirements. The system can be divided into three modules: 1. Module for Security (Login field, password) 2. Data Insertion 3. Output Module The system in executed systematically, and its output is verified.

7.4

Test Procedure
49

A testing strategy is decided for testing the system so that all modules are tested to fulfill all user requirements. A test strategy is methodology that describes the various steps that need to be performed during testing and the time and effort required for performing them. The following strategies are used for testing an automated Inventory Management system.

7.5

Unit Testing

Unit testing is a white-box testing techniques. The main consideration in this test is verification of all modules of the software system. Each module is unit tested, as follows: Unit testing the module to calculate the cost of the inventory: This module is provided its required input. The number of components used, the number of each component used, and the cost of each component used in handling inventories. All calculations for calculating the cost of handling inventory are then executed, and output is recorded. Similarly, all modules listed below can be unit tested. The unit test results are recorded in reports. Unit testing the module to display reports in required format Unit testing the module for managing inventory Unit testing the module for developing cost sheets Unit testing the module for developing other cost-evaluation documents

7.6

Integration Testing

Integration testing is the technique for testing the interfaces of software components. Each software components in unit tested, and all the components are integrated to perform together. The tests are conducted to ensure that the components are working properly after interfacing. All modules are integrated by an incremental approach, and integration testing of the system is performed as follows: Integrate login module and test. Integrate all modules and test.

7.7

System Testing
50

System testing involves the set of tests that ensures that the entire system performs according to specifications. Recovery Testing

The software system is fault tolerant. Fault tolerance is the ability of the software system to recover from errors quickly and resume working again. XYSS has developed a fault-tolerant system, keeping in mind all specifications from FMC. As a result, there are minimum chances of faults. Security Testing

System testing is protection testing that test security methods in the system to avoid invalid intrusions. The system stores secret and sensitive information that is susceptible to invalid intrusions. An intrusion to obtain secret information may cause severe economic damage the organization. There are many reasons for such intrusion: o o o Unhappy employees intrude to cause damage to employers. Hackers do it for fun Some people pass secret information for their own benefit.

Several security checks have been included in the system. The system requires a logon ID and password to initiate. For allowing only authenticated users to log on to the system, each user is assigned a user name and password. Stress Testing A system is evaluated under normal conditions in all previous testing techniques, and no conditions where system can fail are tested. Stress testing evaluates the system under abnormal conditions. The main function of this system is calculation and management of the inventory. All these calculations depend on the number of components and the cost of each component. The system is tested for various costs and number to check accuracy and to ensure that the system performs accurately under all input conditions.

51

Performance Testing Performance testing uses criteria to check that the system functions according to the specifications. The performance of the software is tested at all levels of testing. All unit modules have been tested successfully. The integration of these unit modules produces reports in the required format. Therefore, the system is performing according to FMCs requirements.

7.8

Test Plan

7.8.1 Objectives
System Overview: The inventory management system should automate the process of calculating cost. The software should perform the calculation process in the same manner as the manual system. Document Overview: This document contains the plan and schedule for tests to be performed on the system and the mapping of tests to specified system requirements. Referred Documents: system. The referred documents are SRS and test cases developed for the

7.2

Software Test Environment

Name of test Site(s): XYSS office Resources Software: The software requirements are Visual Basic as front end MS ACCESS 2000 as back end, and MS Visio as a designing tool. Hardware: The minimum hardware requirements are a Pentium III process with 128 MB RAM, 840 GHz speed, and a 10 GB hard disk. Other Materials: Not applicable Licensing Issues: XYSS holds development licenses for all the software tools being used. Installation, Testing, and Control: The inventory management system will be developed at XYSS. Testing will also be performed on XYSS premises. XYSS will do the installation and testing of software at FMC. The control and maintenance of

52

software will be the responsibility of XYSS after the installation. Participating Organizations: XYSS and FMC Personnel: Naeem Iqbal, Nadeem, will perform the test and report to the team leader, .

7.3

Test Identification
Test ID Test Name Test Level Test Type Test Conditions

XYSS# 10001 Authentication Unit and integration testing Input tests, output tests, verification, 00 and validation tests Test will use real-time data from FMC XYSS#10002 Display Inventory Management System Unit tests, output tests, verification and validation tests Test will be real-time data from FMC XYSS#10003 Calculation and Report Generation Unit and integration testing Input tests, output tests, verification and validation tests Test will use real-time data from FMC XYSS#10004 Maintain inventory Unit and integration testing Input tests, output tests, verification and validation tests

53

Test will use real-time data from FMC

7.8.4

Test Schedules
Test ID Test Name Test Personnel Test Site Planned Date

XYSS#10001 Authentication Naeem Iqbal XYSS 29/11/07 XYSS#10002 Display Inventory Management System Nadeem XYSS 29/11/07 XYSS#10003 Calculate Inventory Mr. M. Ali XYSS 28/11/07 XYSS#10004 Maintain Inventory Mr. M. Jamal XYSS 29/11/07

7.5

Requirements Traceability
Test Name Requirement Met

54

Authentication Section 4.1 Display Section 4.2 Calculate Section 4.2 Maintain Inventory Section 4.3

55

7.8.6

Test Cases

A test case is prepared for each test that needs to be performed. The test cases result in the development of test reports, which will be used for test-output analysis. Software: Test ID: INVENTORY MANAGEMENT SYSTEM XYSS#1001 Modulation: Login module

Test Name:

Authentication

Test Description:

This test verifies the user name and password to access the INVENTORY

MANAGEMENT SYSTEM calculation software.

Action Performed Enter user name in the test box provided

Actions Output The user name is displayed in the respective text box

Valid Input Names of all valid users to whom the administrator assign access

Invalid Input Names of all users who are not assigned access by the network administrator Any other string of characters that is not a password of any valid user Invalid or empty value for user name or password or for both

Input Jamal

Required Output Jamal is displayed in the respective text box

Output

Analysi s

Enter Password

The password is displayed in an encrypted form If the entered user name and a password are valid, the user proceeds to the next form

The passwords of respective valid users

Nasir

The password entered is displayed as an asterix

Click Proceed

Valid user name and password

Click OK

The next form appears on the screen

56

Click Exit

The user exits the software

Valid or empty values in the user name or password text boxes New value of password for the respective user appears, retype the value to confirm and press save or exit

Click OK

The user exits the inventory management systemcalculation software Click Change Password

Click Change Password

Form to change the password appears

Different values in the new password test box appear; click save

Enter success in the new password text, box, and the confirm password text box, and click OK

Testing Environment: Tested By: Software:

IBM PC (PIII), 0 GB HDD, 64 MB RAM, Visual Basic 6.0, and MS Access Date: 29/11/2007 Module: Display Inventory

XY Soft Solution

INVENTORY MANAGEMENT SYSTEM

Management System Test ID: XYSS#10002 Test Name: Display INVENTORY

MANAGEMENT SYSTEM Test description: This test displays inventory management system entries in the hierarchal format.

The selection of any node in the tree displays corresponding entries in the respective text boxes provided.
Action Performed Choose a model from the Model combo box Actions Output Assemblies of the chosen model are displayed in a hierarchical Valid Input Names of all the models that FMC products Invalid Input Any model name that FMC does not Input FMC13267 Required Output The corresponding components and subcomponents Output Choose a model from the model combo Analysis Assemblies of the chosen model are displayed

57

provided.

format.

produce.

of the FMC13267 model are displayed in a hierarchical format. The components and subcomponents of the of the cell phone are displayed in the tree structure, and the corresponding values are displayed in the respective boxes

box provided .

in a hierarchical format.

Choose an assembly form the assembly combo box provided.

The components and subcomponents of the of the chosen assembly are displayed in the inventory management system tree, and the list items is displayed in corresponding text boxes

Names of all assemblies that constitute a cell phone

Any other word that does not correspond to an assembly

Cell phone

Testing Environment: Tested By: Software:

IBM PC (PIII), 0 GB HDD, 64 MB RAM, Visual Basic 6.0, and MS Access Date: 28/11/2007 Module: INVENTORY

XY Soft Solution

INVENTORY MANAGEMENT SYSTEM

MANAGEMENT SYSTEM Test ID: SYSTEM Test description:

Action Performed Enter the Actions Output The total cost

XYSS#10003

Test Name:

INVENTORY MANAGEMENT

This test calculates the total cost of the quantity of cell phones ordered.
Valid Input A Invalid Input A Input 500 Required Output The total cost Output Analysis

58

quantity of cell phones required in the quantity text box

of cell phones is displayed in the adjacent cost text box.

quantity less than or equal to the quantity available in stock.

quantity greater than the quantity available in stock.

of 5000 cell phones is displayed

Testing Environment: Tested By: Software: Test ID:

IBM PC (PIII), 0 GB HDD, 64 MB RAM, Visual Basic 6.0, and MS Access Date: 26/11/2007 Module: Inventory

XY Soft Solution

INVENTORY MANAGEMENT SYSTEM XYSS#10004

Test Name:

Maintain inventory

Test description:

This test maintains inventory and helps perform actions, such as add, delete, and

modify for entries in the inventory.

Action Performed Enter the item number Actions Output The item number is displayed in the text box if it is in the correct format, or a message box appears, which gives the correct format of the Enter item name item number The item name is displayed into text box Thee name of item that constitutes a cell phone Any other text that is not part of a cell phone or numeric Choose the The unit of The unit of value A numeric Pound The text Back panel The text, back panel, is displayed in the text box Enter item name The item name is displayed in the text box Valid Input A number entered in the format that represents the item code Invalid Input A text value or any other number that does not confirm to the format specified to represent an item code. Input ITM01 Required Output The item value, IT01, is displayed in the text box. Output Enter the item number Analysis The item umber is displayed in the text box if it is in the correct format, or a message box appears, which gives the correct format of the item number.

59

unit of measurement from the item UOM combo box Enter the quantity in stock

measurement is displayed in the item UOM combo box

measurement, such as gallons or pounds

value or text that does not correspond to the unit of assembly

pound, is displayed in the item UOM combo box

The quantity in stock is displayed in the text box

A numeric value that shows the quantity of cell phones manufactured and available for delivery Click the first record button on the tool bar

Click the first record button on the tool bar

Entries of the last record in the inventory table are displayed in corresponding text boxes

Click the record button on the tool bar placed at the top of the form Click the last record button on the tool bar placed at the top of the form Click the next record button on the tool bar placed at the top of the form Click the previous

The entries corresponding to the first record are displayed in the text boxes provided

Click the last record button on the tool bar

Entries of the last record in the inventory table are displayed in corresponding text boxes

Click the last record button on the tool bar

The entries corresponding to the last record are displayed in the text boxes provided

Click the next record button on the tool bar

Entries of the record next to the one being displayed appear in corresponding text boxes

Click the next record button on the tool bar

The entries corresponding to the record next to the one being displayed appear in the corresponding text boxes The entries corresponding

Click the previous

Entries of the record before

Click the previous

60

record button on the tool bar

the one being displayed appear in corresponding text boxes

record button on the tool bar

record button on the tool bar placed at the top of the form Click the next record button on the tool bar placed at the top of the form Click the save record button after filling entries in text boxes and combo boxes Change the quantity on hand form 100 to 150

to the record before the one being displayed appear corresponding test boxes The entries corresponding to the record next to the one being displayed appear in the corresponding text boxes The entries should be saved in the inventory database

Click the delete record button on the tool bar

The entries of the record being displayed are deleted from the inventory database

Click the delete record button on the tool bar

Click the save record button

The values entered in the respective text boxes are saved in the inventory database

Complete entries in all text boxes and combo boxes provided

Empty values in the ext box or combo box provided

Click on the modify button

The modification in any of the text box values is reflected in the inventory database

Click the modify button on the tool bar placed at the fop of the form

The value of quantity on hand is changed to 150 for that particular record in the inventory database The user should exit the inventory maintenance form

Click the exit button

The user should come out of the current form

Click the exit button

Click the exit button

61

Testing Environment: Tested By: Software: Test ID:

IBM PC (PIII), 0 GB HDD, 64 MB RAM, Visual Basic 6.0, and MS Access Date: 26/11/2007 Module: Inventory

XY Soft Solution

INVENTORY MANAGEMENT SYSTEM XYSS#10004

Test Name:

Maintain inventory

Test description:

This test maintains inventory and helps perform actions, such as add, delete, and

modify for entries in the inventory.

7.8.7 Test Output Analysis

The test output analysis is based one of the following specifications: errors. If the above two specification results in no solution, the system has errors. These errors are re-analyzed by developers and testers. In the automatic inventory management system-calculation system, the test-output analysis of test cases reveals: Summary of test results Deviation from test cases All test components should be thoroughly reviewed for errors. Testing conforms to test specifications if the test results in faults or

7.8.8 Summary of Test Result

The objective of this test is to demonstrate that the performance of the software system meets all requirements of FMC. All modules have been successfully unit tested in the first phase. Then, the modules are incremented to perform integration testing. The performance of the integrated system is

62

according to FMCs specifications. Finally, the system is fully tested for recovery testing, security testing, stress testing, and performance testing. Therefore, the system fulfills all FMCs requirements.

7.8.9 Deviation from Test Cases

There is no deviation from the test case and the system performs according to specifications

7.8.10

Bug Report (as template)

YOUR COMPANYS NAME PROGRAM

XY Soft Solution

PROBLEM REPORT#__________ VER 1.0

Inventory Management System (System Termination) RELEASE 1st SEVERITY (1-3) _____ 1. Fatal 2.Serious 3. Minor

REPORT TYPE (1-6) _____ 1. Coding issue 2. Design issue 3. Suggestion

ATTACHMENTS (Y/N) ________ If yes. Describe: _____________________ _____________________

4. Documentation 5. Hardware 6. Query

PROBLEM SUMMARY_______________________________________________________________ CAN YOU REPRODUCE THE PROBLEM? (Y/N) No

PROBLEM AND HOW TO REPRODUCE IT_______________________________________________ ___________________________________________________________________________________ ___________________________________________________________________________________ ____________________________________________________________________________________ SUGGESTED FIX (optional) ____________________________________________________________

63

____________________________________________________________________________________ ____________________________________________________________________________________ ____________________________________________________________________________________ REPORTED BY DATE 29/11/2007

64

ITEMS BELOW ARE FOR USE ONLY BY THE DEVELOPMENT TEAM

FUNCTIONAL AREA

System Termination

ASSIGNED TO

Mr. Naseer Ahmed

COMMENTS__________________________________________________________________________ STATUS (1-2) _______ 1. Open 2.Closed RESOLUTION VERSION_______________ 7.Witdraw by reporter 8. Need more info 9. Disagree with suggestion

RESOLUTION (1-9) ______ 1. 2. 3. Pending Fixed 4. Deferred 5. As designed

Irreproducible 6. Cant be fixed

RESOLVED BY

Mr. Naseer Ahmed

DATE

29/11/2007 DATE 30/11/2007

RESOLUTION TESTED BY

Mr. Muhammad Ahmed

TREAT AS DEFERRED (Y/N) ______________

65

Chapter 7 CONCLUSIONS & FUTURE WORK

8.1 8.2 ACHIEVEMENTS LIMITATIONS

1.2 ACHIEVEMENTS
I feel very proud after development and implementation of my final project successfully. Before developing through this project although I have a good theoretical knowledge of software engineering, being students of computer science, but it is far away from theory to develop a real life system that completely fulfill the user requirements. I had a very good interaction with my internal supervisor, .and also with my external supervisor .. both helped me to develop the system well in time. During the development of the project I have achieved the following benefits. Project management and scheduling How to interact with the user System analysis and data collection A good knowledge of system designing and modeling Latest tools and technologies Testing strategies User documentation Rational Rose for UML. During testing and implementation finding a bug and its fixture was totally new and healthy experience. One of the very important aspects of the project was how to document our project properly. I have learnt new tools ASP, Visual Basic 6.0, SQL Server 7.0, Adobe Photoshop, and Gif Animator which will help me a long way as I will be starting my careers as IT professional. 66

During the modeling phase I learnt

LIMITATIONS
The project is developed keeping in view the research oriented requirement of a final master project. So it may lack some elegance or sophistication but I am very proud that I have worked in a highly versatile environment and I have taken the right steps towards the right direction in terms of where the technology is going nowadays.

67

Chapter 08 REFERENCES & BIBLIOGRAPHY

References [1] ENSODEX, Driving IT Evolution http://www.ensodex.com/index.htm [2] Web Services Architecture http://www.w3.org/TR/2004/NOTE-ws-arch-20040211/#whatis [3] Ethan Cerami, (2002) Web Services Essentials, 1st Edition, Oreilly Publications, ISBN 0-59600224-6 [4] James Snell, Doug Tidwell & Pavel Kulchenko, (2002) Programming Web Services with SOAP, 1st Edition, Oreilly Publications, ISBN 0596000952 [5] Ethan Cerami, (2002) Web Services Essentials, 1st Edition, Oreilly Publications, ISBN 0-59600224-6 Bibliography [1] Simon St.Laurent, Joe Johnston, Edd Dumbill, (2003) Programming Web Services with XMLRPC, 1st Edition, ISBN 0-596-00119-3 [2] Reliable Message Delivery in a Web Services World: A Proposed Architecture and Roadmap http://msdn.microsoft.com/library/default.asp?url=/library/enus/dnglobspec/html/ws-rmexecsummary.asp [3] Internet based Distributed Computing Projects http://www.aspenleaf.com/distributed

68