1 / 44

Work Track Trace Plug-in Outlook

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. I. INTRODUCTION. 1. Team introduction. I. INTRODUCTION. 2. Project introduction.

xarles
Download Presentation

Work Track Trace Plug-in Outlook

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Content

  3. I. INTRODUCTION

  4. I. INTRODUCTION 1. Team introduction

  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.

  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.

  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.

  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.

  9. II. SOFTWARE PROJECT PLAN

  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

  11. II. SOFTWARE PROJECT PLAN 1. Proposed system and scope • Development Environment:

  12. II. SOFTWARE PROJECT PLAN 1. Proposed system and scope • Testing & Deployment Environment:

  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 QualityAssurance Business Analyst Configuration Manager Developer Tester PhucNH TienPN DuyTQ DuyTQ ChauNLN TrangNT DuyTQ TienPN PhucNH ChauNLN TrangNT

  15. II. SOFTWARE PROJECT PLAN 2. Project organization • Tools and Technique: • Astah professional tool • StyleCop tool • SVN tool • Microsoft Visio • Microsoft Project

  16. II. SOFTWARE PROJECT PLAN 3. Project plan JANUARY FEBRUARY MARCH APRIL Intro R1 Project Plan R2 SW Requirement R3 Design R4 Code Unit Testing Testing R5 User Manual R6

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

  18. III. REQUIREMENT SPECIFICATION

  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

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

  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

  26. III. REQUIREMENT SPECIFICATION 3. Non-Functional 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 • <?xml version="1.0" encoding="utf-8"?> • <WTT> • <Action>ProjectAdded</Action> • <Value> • <ProjectID>{Project ID }</ProjectID> • <AccountID>{Account ID} </AccountID> • </Value> • </WTT>

  29. IV. SOFTWARE DESIGN

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

  37. V. SOFTWARE TESTING 1. Test Target • 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

  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

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

  42. V. SOFTWARE TESTING 6. Test Report

  43. V. SOFTWARE TESTING 7. Bug Report

  44. VI. DEMO, Q&A

More Related