Work Track Trace
Plug-in Outlook
Supervisor: Mr. Huynh Anh Dung
Students:
To Quang Duy
Pham Ngoc Tien
Nguyen Luong Ngoc Chau
Nguyen Hoang Phuc
Nguyen Thi Trang
CONTENT
I. INTRODUCTION
II. SOFTWARE PROJECT PLAN
III. REQUIREMENT SPECIFICATION
IV. SOFTWARE DESIGN
V. SOFTWARE TESTING
VI. DEMO, Q&A
I. INTRODUCTION
1. Team introduction
2. Project introduction
I. INTRODUCTION
1. Team introduction
Member
Role
DuyTQ
+ Project Leader
+ Coder
TienPN
+ Coder
+ Business Analyst
PhucNH
+ Architecture
+ Coder
TrangNT
+ Tester
+ QA
+ Business Analyst
ChauNLN
+ Tester
+ QA
+ Business Analyst
I. INTRODUCTION
2. Project introduction
2.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.
I. INTRODUCTION
2. Project introduction
2.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.
I. INTRODUCTION
2. Project introduction
2.2 Literature
Limitations of existing solution:
+ Offline task management.
+ Cost time for update status report.
+ Task flow management is not clear.
I. INTRODUCTION
2. Project introduction
2.3 Proposal
+ Create Add in for Outlook to manage task.
+ Add task flow management.
+ Center data stored.
+ Multi user accessing.
+ Inform email using Outlook.
II. SOFTWARE PROJECT PLAN
1. PROPOSED SYSTEM AND SCOPE
2. PROJECT ORGANIZATION
3. PROJECT PLAN
4. RISK MANAGEMENT
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
II. SOFTWARE PROJECT PLAN
1. Proposed system and scope
 Envelopment Environment:
- .NET 3.5
- Windows 7
- ADO.NET
- Windows Vista
- C#
- Microsoft Visual Studio 2008.
- Microsoft SQL Server 2008 Express edition.
- Window Server 2003 R2
-Windows XP SP2
- UTF-8 encoding.
- MS Office Outlook: version 2003, 2007, 2010
II. SOFTWARE PROJECT PLAN
2. Project Organization
Waterfall Software Development Model
II. SOFTWARE PROJECT PLAN
2. Project organization
Project Leader
(DuyTQ)
Technical
Leader
PhucNH
ChauNLN
Quality
Assurance
TienPN
TrangNT
Business
Analyst
DuyTQ
Configuration
Manager
DuyTQ
DuyTQ
Developer
ChauNLN
TienPN
PhucNH
Tester
TrangNT
II. SOFTWARE PROJECT PLAN
2. Project organization
Tools and Technique:
 Astah professional tool
 StyleCop tool
 SVN tool
 Microsoft Visio
 Microsoft Project
II. SOFTWARE PROJECT PLAN
3. Project plan
JANUARY
Intro
FEBRUARY
MARCH
APRIL
R
1
Project
Plan
R
2
SW
Requirement
R
3
Design
R
4
Code
Unit
Testing
Testing
R
5
User
Manual
R
6
II. SOFTWARE PROJECT PLAN
4. Risk management
Requirements
Communication
Estimate
Changes
Human Resource
III. REQUIREMENT SPECIFICATION
1. USER REQUIREMENT SPECIFICATION
2. FUNCTIONAL REQUIREMENT
3. NON-FUNCTINAL REQUIREMENT
4. DATA STRUCTURE
III. REQUIREMENT SPECIFICATION
1. User requirement specification
Account Manage
• The system allow user act in project:
– User can be add new 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
III. REQUIREMENT
v SPECIFICATION
1. User requirement specification
• The system allow user act in task:
– In this task, user can be control PIC 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 personal in charge
III. REQUIREMENT SPECIFICATION
2. Functional requirement
System User
III. REQUIREMENT SPECIFICATION
2. Functional requirement
Project Member
III. REQUIREMENT SPECIFICATION
2. Functional requirement
Task Flow
III. REQUIREMENT SPECIFICATION
3. Non-Functional requirement
 Supportability Requirement
 Multi –languages
 User guidelines
 Fix bugs and update version
 Performance requirement
III. REQUIREMENT SPECIFICATION
3. Non-Functional requirement
 Software system attribute:
Usability
Availability
Security
Maintainability requirement
Portability
III. REQUIREMENT SPECIFICATION
4. Data structure - Database
Configurat ion
KeyID
Value
Note
RecordUpdator
RecordUpdateTime
RecordRegistrant
RecordRegistTime
DeleteFlag
TaskPIC
AccountID
TaskID
AddedDate
RemovedDate
Effort
Status
Note
RecordUpdator
RecordUpdateTime
Project Account
Account
AccountID
Password
AccountID
ProjectID
RoleID
Name
Note
Phone
RecordUpdateor
RecordUpdateTime
RecordRegistrant
RecordRegistTime
DeleteFlag
RecordUpdator
RecordUpdateTime
RecordRegistrant
RecordRegistTime
DeleteFlag
RecordRegistrant
RecordRegistTime
DeleteFlag
Project
ProjectID
Task
ProjectName
TaskID
StartDate
ProjectID
FinishDate
Name
Status
StartDate
Note
EndDate
RecordUpdator
Duration
RecordUpdateTime
Status
RecordRegistrant
Percentage
RecordRegistTime
Note
DeleteFlag
Role
RoleID
RecordUpdator
ProjectID
RecordUpdateTime
Name
RecordRegistrant
Note
RecordRegistTime
PCreateTask
DeleteFlag
PUpdateTask
PDeleteTask
PUpdateProject
PDeleteProject
PProjectManager
DefaultRole
Removable
RecordUpdator
RecordUpdatTime
Issue
IssueID
SubTask
RecordRegistrant
ParentTaskID
RecordRegistTime
TaskID
SubTaskID
DeleteFlag
Name
RecordUpdator
Note
RecordUpdateTime
Status
RecordRegistrant
RecordUpdator
RecordRegistTime
RecordUpdateTime
DeleteFlag
RecordRegistrant
RecordRegistTime
DeleteFlag
Database Diagram
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>
IV. SOFTWARE DESIGN
I. SOFTWARE STRUCTURE
II. HARDWARE STRUCTURE
III. COMPONENTS
IV. COMPONENTS DIAGRAM
V. PACKAGES
VI. COMMON SEQUENCE
IV. SOFTWARE DESIGN
1. Software Structure
IV. SOFTWARE DESIGN
2. Hardware Structure
IV. SOFTWARE DESIGN
3. Components
IV. SOFTWARE DESIGN
4. Components Diagram
IV. SOFTWARE DESIGN
5. Packages
IV. SOFTWARE DESIGN
6. Common Sequence
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
V. SOFTWARE TESTING
1. Test Target
Spec Coverage:
-Verify specifications
-Verify user requirement
-Detect defects
-Manage risk
V. SOFTWARE TESTING
2. Test Model
V LIFECYCLE MODEL
V. SOFTWARE TESTING
3. Features To Be Tested
NO
REQUIREMENTS
1
System allows users to create projects
2
System allows users to view projects detail, member and roles
3
System allows users to create and assign tasks via email
4
System allows users to view tasks details, PIC
5
System allows users to view projects and tasks progress via
status and percentage of work done
6
System allows users to change password and account
information
7
System allows users to access to server to use WTT plug-in by
configuring
8
System allows users to report tasks done through email
9
System provides users error messages
V. SOFTWARE TESTING
4. Checklist/ Test Viewpoint
Code review checklist
Case and Requirement Mapping Review
Checklist
GUI checklist
Common checklists
Validation conditions
Navigation conditions
Usability Conditions
Data Integrity Conditions
V. SOFTWARE TESTING
5. Test Execution
Bug Management Flow
V. SOFTWARE TESTING
6. Test Report
V. SOFTWARE TESTING
7. Bug Report
Total Test Cases
313
Total Bugs
96
Finish Test Date
19-04-2011
VI. DEMO, Q&A