Work Track Trace Plug-in Outlook

Supervisor: Mr. Huynh Anh Dung

Students: To Quang DuyPham Ngoc TienNguyen Luong Ngoc ChauNguyen Hoang Phuc Nguyen Thi Trang

1

CONTENT

I. INTRODUCTION

II. SOFTWARE PROJECT PLAN

III. REQUIREMENT SPECIFICATION

IV. SOFTWARE DESIGN

V. SOFTWARE TESTING

VI. DEMO, Q&A

2

I. INTRODUCTION

1. Team introduction

2. Project introduction

3

I. INTRODUCTION

1. Team introduction

To Quang Duy

Nguyen Thi Trang

Pham Ngoc Tien

Nguyen Luong Ngoc Chau

Nguyen Hoang Phuc

Huynh Anh Dung

4

I. INTRODUCTION

2. Project introduction2.1 Background

+ Most of communication at work using Email.+ Most of email is used with purpose in task controlling.+ Lost of people use offline software to manage task.

5

I. INTRODUCTION

2. Project introduction2.2 Literature

+ 1984: MS first released Microsoft Project.+ 1997: MS first release Microsoft Outlook 97.+ Lost of project management software such as: Task Manager, VIP Organizer, Planner, Easy Task Link.

6

I. INTRODUCTION

2. Project introduction2.2 Literature

Limitations of existing solution:+ Offline task management.+ Cost time for update status report.+ Data consistency.+ Task flow management is not clear.

7

I. INTRODUCTION

2. Project introduction2.3 Proposal

+ Create Add in for Outlook to manage task.+ Add task flow management.+ Center data stored.+ Multi user accessing.+ Inform email using Outlook.

8

II. SOFTWARE PROJECT PLAN

1. PROPOSED SYSTEM AND SCOPE

2. PROJECT ORGANIZATION

3. PROJECT PLAN

4. RISK MANAGEMENT

9

II. SOFTWARE PROJECT PLAN

1. Proposed system and scope

Proposed:- WTT Outlook Plug-in: Controlling tasks in Outlook.

- The server provide services to working with task. Scope:

- Create a project/Create task.- Project management/Task management. - Export/ Import MPP file- Supports Microsoft Office 2003/2007/2010

10

II. SOFTWARE PROJECT PLAN

1. Proposed system and scope

Development Environment:Technology .NET 3.5

ADO.NETC#

Software Windows 7Microsoft Visual Studio 2008.Microsoft SQL Server 2008 Express edition.

Supported platform

Window Server 2003 R2Windows 7

11

II. SOFTWARE PROJECT PLAN

Testing & Deployment Environment:

Software MS Office Outlook: version 2007Supported platform

Window Server 2003 R2

Windows 7

1. Proposed system and scope

12

II. SOFTWARE PROJECT PLAN

2. Project Organization

Waterfall Software Development Model

13

II. SOFTWARE PROJECT PLAN

2. Project organization

Project Leader (DuyTQ)

Technical Leader

Quality Assurance

Business Analyst

Configuration Manager Developer Tester

PhucNH

ChauNLN TrangNT

TienPN DuyTQ DuyTQ

DuyTQ TienPN PhucNH

TrangNTChauNLN

14

II. SOFTWARE PROJECT PLAN

2. Project organization

Tools and Technique: Astah professional toolStyleCop toolSVN toolMicrosoft VisioMicrosoft Project

15

II. SOFTWARE PROJECT PLAN

3. Project planJANUARY FEBRUARY MARCH APRIL

Intro

Project Plan

SW Requirement Design Code

Testing

Unit Testing

User Manual

R1

R2

R3

R4

R5

R616

II. SOFTWARE PROJECT PLAN

4. Risk management

RequirementsCommunicationEstimateChangesHuman Resource

17

III. REQUIREMENT SPECIFICATION

1. USER REQUIREMENT SPECIFICATION

2. FUNCTIONAL REQUIREMENT

3. NON-FUNCTINAL REQUIREMENT

4. DATA STRUCTURE

18

III. REQUIREMENT SPECIFICATION

1. User requirement specification

Account Manage• The system allow user act in project: – User can be attack MPP/MPX file or add new

project information to control– Allow user has quick view all task status of project– Allow user view task information detail. – Allow system user export project detail information

to MPP file

19

vIII. REQUIREMENT SPECIFICATION

1. User requirement specification

• The system allow user act in task: – In this task, user can be control PIC (Person In

Charge) and task issues– When task has finished, user can be request

approve from manager– Project manager has permission to accept/reject/

cancel this task– Allow user add task to outlook and project

manager can be remind to PIC

20

III. REQUIREMENT SPECIFICATION

2. Functional requirement

System User21

III. REQUIREMENT SPECIFICATION

2. Functional requirement

Project Member 22

III. REQUIREMENT SPECIFICATION

2. Functional requirement

Task

23

III. REQUIREMENT SPECIFICATION

2. Functional requirement

Task Status Flow 24

III. REQUIREMENT SPECIFICATION

3. Non-Functional requirement

Supportability Requirement Multi –languages User guidelines Fix bugs and update version

Performance requirement

25

III. REQUIREMENT SPECIFICATION

3. Non-Functional requirement

Software system attribute:UsabilityAvailabilitySecurityMaintainability requirement

26

III. REQUIREMENT SPECIFICATION

4. Data structure - Database

ERD 27

III. REQUIREMENT SPECIFICATION

4. Data structure - XML

+ Using when tranfer data in email+ Example: Project Invitation XML Structure<?xml version="1.0" encoding="utf-8"?><WTT> <Action>ProjectAdded</Action> <Value> <ProjectID>{Project ID }</ProjectID> <AccountID>{Account ID} </AccountID> </Value></WTT>

28

IV. SOFTWARE DESIGN

I. SOFTWARE STRUCTURE

II. HARDWARE STRUCTURE

III. COMPONENTS

IV. COMPONENTS DIAGRAM

V. PACKAGES

VI. COMMON SEQUENCE

29

IV. SOFTWARE DESIGN

1. Software Structure

30

IV. SOFTWARE DESIGN

2. Hardware Structure

31

IV. SOFTWARE DESIGN

3. Components

32

IV. SOFTWARE DESIGN

4. Components Diagram

33

IV. SOFTWARE DESIGN

5. Packages

34

IV. SOFTWARE DESIGN

6. Common Sequence

35

V. SOFTWARE TESTING

1. TEST TARGET

2. TEST MODEL

3. FEATURES TO BE TESTED

4. CHECKLIST/ TEST VIEWPOINT

5. TEST EXECUTION

6. TEST REPORT

7. BUG REPORT

36

V. SOFTWARE TESTING

1. Test Target

Spec Coverage:- Verify specifications- Verify user requirement- Detect defects

37

V. SOFTWARE TESTING

2. Test Model

V LIFECYCLE MODEL 38

V. SOFTWARE TESTING

3. Features To Be TestedNO REQUIREMENTS

1 System allows users to create projects2 System allows users to view projects detail, member and roles

3 System allows users to create and assign tasks via email4 System allows users to view tasks details, PIC5 System allows users to view projects and tasks progress via

status and percentage of work done6 System allows users to change password and account

information7 System allows users to access to server to use WTT plug-in by

configuring8 System allows users to report tasks done through email9 System provides users error messages

39

V. SOFTWARE TESTING

4. Checklist/ Test Viewpoint

Code review checklistCase and Requirement Mapping Review

ChecklistGUI checklist

Common checklistsValidation conditionsNavigation conditionsUsability Conditions Data Integrity Conditions

40

V. SOFTWARE TESTING

5. Test Execution

Bug Management Flow 41

V. SOFTWARE TESTING

6. Test Report

42

V. SOFTWARE TESTING

7. Bug Report

43

VI. DEMO, Q&A

44