1. Supervisor: Mr. Huynh Anh Dung Students: To Quang Duy Pham Ngoc Tien Nguyen Luong Ngoc Chau Nguyen Hoang Phuc Nguyen Thi Trang

2. I. INTRODUCTION II. SOFTWARE PROJECT PLAN III. REQUIREMENT SPECIFICATION IV. SOFTWARE DESIGN V. SOFTWARE TESTING VI. DEMO, Q&A

3. 1. Team introduction 2. Project introduction

4. 1. Team introduction MemberRole DuyTQ+ Project Leader + Coder TienPN+ Coder + Business Analyst PhucNH+ Architecture + Coder TrangNT+ Tester + QA + Business Analyst ChauNLN+ Tester + QA + Business Analyst

5. 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. + 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.

6. 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. + 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.

7. 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. Limitations of existing solution: + Offline task management. + Cost time for update status report. + Task flow management is not clear.

8. 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. + Create Add in for Outlook to manage task. + Add task flow management. + Center data stored. + Multi user accessing. + Inform email using Outlook.

9. 1. PROPOSED SYSTEM AND SCOPE 2. PROJECT ORGANIZATION 3. PROJECT PLAN 4. RISK MANAGEMENT

10. 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  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

11. 1. PROPOSED SYSTEM AND SCOPE TESTDEPLOYMENTDEVELOPMENT Window Server 2003 R2 Windows XP SP2 Windows Vista Windows 7 ADO.NET C# Windows 7 Microsoft Visual Studio 2008. Microsoft SQL Server 2008 Express edition. MS Office Outlook 2003, 2007, 2010

12. 2. Project organization Waterfall Software Development Model

13. 2. Project organization Project Leader (DuyTQ) Technical Leader Quality Assurance Business Analyst Configuration Manager Developer Tester PhucNH ChauNLN TrangNT TienPN DuyTQ TienPN PhucNH TrangNT ChauNLN

14. 2. Project organization  Tools and Technique: Astah professional tool StyleCop tool SVN tool Microsoft Visio Microsoft Project  Tools and Technique: Astah professional tool StyleCop tool SVN tool Microsoft Visio Microsoft Project

15. 3. Project plan JANUARYFEBRUARYMARCHAPRIL Intro Project Plan SW Requirement Design Code Testing Unit Testing User Manual R1R1 R1R1 R2R2 R2R2 R3R3 R3R3 R4R4 R4R4 R5R5 R5R5 R6R6 R6R6

16. 4. Risk management  Requirements  Communication  Estimate  Changes  Human Resource  Correctness  Requirements  Communication  Estimate  Changes  Human Resource  Correctness

17. 1. USER REQUIREMENT SPECIFICATION 2. FUNCTIONAL REQUIREMENT 3. NON-FUNCTINAL REQUIREMENT 4. DATA STRUCTURE

18. 1. User requirement specification  Account Manage The system allow user act in project: – User can be import MPP/MPX file or add new project information to control – Allow user has quick view all task status of project or search task information – Allow user view task information detail. – Allow system user export project detail information to MPP file  Account Manage The system allow user act in project: – User can be import MPP/MPX file or add new project information to control – Allow user has quick view all task status of project or search task information – Allow user view task information detail. – Allow system user export project detail information to MPP file

19. 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 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

20. 2. Functional requirement System User

21. 2. Functional requirement Project Member

22. 2. Functional requirement Task Flow

23. 3. Non-Functional requirement  Supportability Requirement  Multi –languages  User guidelines  Fix bugs and update version  Performance requirement  Supportability Requirement  Multi –languages  User guidelines  Fix bugs and update version  Performance requirement

24. 3. Non-Functional requirement  Software system attribute:  Usability  Availability  Security  Maintainability requirement  Portability  Software system attribute:  Usability  Availability  Security  Maintainability requirement  Portability

25. 4. Data structure - Database Database Diagram

26. 4. Data structure - XML + Using when tranfer data in email + Example: Project Invitation XML Structure ProjectAdded {Project ID } {Account ID} + Using when tranfer data in email + Example: Project Invitation XML Structure ProjectAdded {Project ID } {Account ID}

27. 1. TEST TARGET 2. TEST MODEL 3. FEATURES TO BE TESTED 4. CHECKLIST/ TEST VIEWPOINT 5. TEST EXECUTION 6. TEST REPORT

28. 1. TEST TARGET  Spec Coverage: -Verify specifications -Verify user requirement -Detect defects -Manage risk  Spec Coverage: -Verify specifications -Verify user requirement -Detect defects -Manage risk

29. 2. TEST MODEL V LIFECYCLE MODEL

30. 3. FEATURES TO BE TESTED NOREQUIREMENTS 1System allows users to create projects 2System allows users to view projects detail, member and roles 3System allows users to create and assign tasks via email 4System 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 8System allows users to report tasks done through email 9System provides users error messages

31. 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  Code review checklist  Case and Requirement Mapping Review Checklist  GUI checklist Common checklists Validation conditions Navigation conditions Usability Conditions Data Integrity Conditions

32. 5. TEST EXECUTION Bug Management Flow

33. 6. TEST REPORT