420 likes | 569 Views
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.
E N D
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
I. INTRODUCTION 1. Team introduction
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 • 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 MS Office Outlook 2003, 2007, 2010 MS Office Outlook 2003, 2007, 2010 • ADO.NET • C# • Microsoft Visual Studio 2008. • Microsoft SQL Server 2008 Express edition.
II. SOFTWARE PROJECT PLAN 2. Project organization Waterfall Software Development Model
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
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 FEBRUARY MARCH APRIL Intro R1 Project Plan R2 SW Requirement R3 Design R4 Code Unit Testing Testing R5 User Manual R6
II. SOFTWARE PROJECT PLAN 4. Risk management • Requirements • Communication • Estimate • Changes • Human Resource
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 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 SPECIFICATION 1. 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 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 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 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 • 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
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