Post on 22-Dec-2015
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
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 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.
I. INTRODUCTION
2. Project introduction2.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 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.
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
TEST DEPLOYMENT
DEVELOPMENT
• Window Server 2003 R2• Windows XP SP2• Windows Vista• Windows 7
• ADO.NET• C#• Microsoft Visual Studio
2008.• Microsoft SQL Server 2008
Express edition.
MS Office Outlook 2003, 2007, 2010
MS Office Outlook 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
Quality Assurance
Business Analyst
Configuration Manager Developer Tester
PhucNH
ChauNLN TrangNT
TienPN DuyTQ DuyTQ
DuyTQ TienPN PhucNH
TrangNTChauNLN
II. SOFTWARE PROJECT PLAN
2. Project organization
Tools and Technique: Astah professional toolStyleCop toolSVN toolMicrosoft VisioMicrosoft Project
II. SOFTWARE PROJECT PLAN
3. Project plan
JANUARY FEBRUARY MARCH APRIL
Intro
Project Plan
SW Requirement Design Code
Testing
Unit Testing
User Manual
R1
R2
R3
R4
R5
R6
II. SOFTWARE PROJECT PLAN4. Risk management
RequirementsCommunicationEstimateChangesHuman Resource
III. REQUIREMENT SPECIFICATION
1. USER REQUIREMENT SPECIFICATION
2. FUNCTIONAL REQUIREMENT
3. NON-FUNCTINAL REQUIREMENT
4. DATA STRUCTURE
III. REQUIREMENT SPECIFICATION1. 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 or search task information base on task status, start date or finish date
– Allow user view task information detail. – Allow system user export project detail
information to MPP file
III. REQUIREMENT SPECIFICATION1. User requirement specification
• The system allow user act in task: – Allow user create new task or subtask– In this task, Project Manager or creator can be update
task information, create new subtask, or add Personal In Charge, 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 SPECIFICATION2. Functional requirement
System User
III. REQUIREMENT SPECIFICATION2. Functional requirement
Project Member
III. REQUIREMENT SPECIFICATION2. Functional requirement
Task Flow
III. REQUIREMENT SPECIFICATION3. Non-Functional requirement
Supportability Requirement Multi –languages User guidelines Fix bugs and update version
Performance requirement
III. REQUIREMENT SPECIFICATION3. Non-Functional requirement
Software system attribute:UsabilityAvailabilitySecurityMaintainability requirementPortability
III. REQUIREMENT SPECIFICATION4. Data structure - Database
AccountAccountID
Password
Name
Phone
RecordUpdateor
RecordUpdateTime
RecordRegistrant
RecordRegistTime
DeleteFlag
ConfigurationKeyID
Value
Note
RecordUpdator
RecordUpdateTime
RecordRegistrant
RecordRegistTime
DeleteFlag
IssueIssueID
TaskID
Name
Note
Status
RecordUpdator
RecordUpdateTime
RecordRegistrant
RecordRegistTime
DeleteFlag
ProjectProjectID
ProjectName
StartDate
FinishDate
Status
Note
RecordUpdator
RecordUpdateTime
RecordRegistrant
RecordRegistTime
DeleteFlag
ProjectAccountAccountID
ProjectID
RoleID
Note
RecordUpdator
RecordUpdateTime
RecordRegistrant
RecordRegistTime
DeleteFlag
TaskTaskID
ProjectID
Name
StartDate
EndDate
Duration
Status
Percentage
Note
RecordUpdator
RecordUpdateTime
RecordRegistrant
RecordRegistTime
DeleteFlag
TaskPICAccountID
TaskID
AddedDate
RemovedDate
Effort
Status
Note
RecordUpdator
RecordUpdateTime
RecordRegistrant
RecordRegistTime
DeleteFlag
RoleRoleID
ProjectID
Name
Note
PCreateTask
PUpdateTask
PDeleteTask
PUpdateProject
PDeleteProject
PProjectManager
DefaultRole
Removable
RecordUpdator
RecordUpdatTime
RecordRegistrant
RecordRegistTime
DeleteFlag
SubTaskParentTaskID
SubTaskID
RecordUpdator
RecordUpdateTime
RecordRegistrant
RecordRegistTime
DeleteFlag
Database Diagram
III. REQUIREMENT SPECIFICATION4. 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 DESIGN1. Software Structure
IV. SOFTWARE DESIGN2. Hardware Structure
IV. SOFTWARE DESIGN3. Components
IV. SOFTWARE DESIGN4. Components Diagram
IV. SOFTWARE DESIGN5. Packages
IV. SOFTWARE DESIGN6. 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 TESTING1. Test Target
Spec Coverage:- Verify specifications- Verify user requirement- Detect defects- Manage risk
V. SOFTWARE TESTING2. Test Model
V LIFECYCLE MODEL
V. SOFTWARE TESTING3. Features To Be Tested
NO 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
V. SOFTWARE TESTING4. Checklist/ Test Viewpoint
Code review checklistCase and Requirement Mapping Review ChecklistGUI checklist
Common checklistsValidation conditionsNavigation conditionsUsability Conditions Data Integrity Conditions
V. SOFTWARE TESTING5. Test Execution
Bug Management Flow
V. SOFTWARE TESTING6. Test Report
V. SOFTWARE TESTING7. Bug Report
Total Test Cases 313
Total Bugs 96
Finish Test Date 19-04-2011
VI. DEMO, Q&A