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

8. 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. + 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. 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  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. II. SOFTWARE PROJECT PLAN 1. Proposed system and scope  Development Environment: Technology.NET 3.5 ADO.NET C# Software Windows 7 Microsoft Visual Studio 2008. Microsoft SQL Server 2008 Express edition. Supported platform Window Server 2003 R2 Windows 7

12. II. SOFTWARE PROJECT PLAN 1. Proposed system and scope  Testing & Deployment Environment: SoftwareMS Office Outlook: version 2007 Supported platform Window Server 2003 R2 Windows 7

13. II. SOFTWARE PROJECT PLAN 2. Project Organization Waterfall Software Development Model

14. 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 TienPN PhucNH TrangNT ChauNLN

15. II. SOFTWARE PROJECT PLAN 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

16. II. SOFTWARE PROJECT PLAN 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

17. II. SOFTWARE PROJECT PLAN 4. Risk management  Requirements  Communication  Estimate  Changes  Human Resource  Requirements  Communication  Estimate  Changes  Human Resource

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

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

20. III. 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 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

21. III. REQUIREMENT SPECIFICATION 2. Functional requirement System User

22. III. REQUIREMENT SPECIFICATION 2. Functional requirement Project Member

23. III. REQUIREMENT SPECIFICATION 2. Functional requirement Task

24. III. REQUIREMENT SPECIFICATION 2. Functional requirement Task Status Flow

25. III. REQUIREMENT SPECIFICATION 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

26. III. REQUIREMENT SPECIFICATION 3. Non-Functional requirement  Software system attribute: Usability Availability Security Maintainability requirement  Software system attribute: Usability Availability Security Maintainability requirement

27. III. REQUIREMENT SPECIFICATION 4. Data structure - Database Database Diagram

28. III. REQUIREMENT SPECIFICATION 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}

29. I. SOFTWARE STRUCTURE II. HARDWARE STRUCTURE III. COMPONENTS IV. COMPONENTS DIAGRAM V. PACKAGES VI. COMMON SEQUENCE

30. IV. SOFTWARE DESIGN 1. Software Structure

31. IV. SOFTWARE DESIGN 2. Hardware Structure

32. IV. SOFTWARE DESIGN 3. Components

33. IV. SOFTWARE DESIGN 4. Components Diagram

34. IV. SOFTWARE DESIGN 5. Packages

35. IV. SOFTWARE DESIGN 6. Common Sequence

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

37. V. SOFTWARE TESTING 1. Test Target  Spec Coverage: -Verify specifications -Verify user requirement -Detect defects  Spec Coverage: -Verify specifications -Verify user requirement -Detect defects

38. V. SOFTWARE TESTING 2. Test Model V LIFECYCLE MODEL

39. V. SOFTWARE TESTING 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

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

41. V. SOFTWARE TESTING 5. Test Execution Bug Management Flow

42. V. SOFTWARE TESTING 6. Test Report

43. V. SOFTWARE TESTING 7. Bug Report