work track trace plug in outlook n.
Download
Skip this Video
Loading SlideShow in 5 Seconds..
Work Track Trace Plug-in Outlook PowerPoint Presentation
Download Presentation
Work Track Trace Plug-in Outlook

Loading in 2 Seconds...

play fullscreen
1 / 42

Work Track Trace Plug-in Outlook - PowerPoint PPT Presentation


  • 144 Views
  • Uploaded on

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.

loader
I am the owner, or an agent authorized to act on behalf of the owner, of the copyrighted work described.
capcha
Download Presentation

PowerPoint Slideshow about 'Work Track Trace Plug-in Outlook' - nibal


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.While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server.


- - - - - - - - - - - - - - - - - - - - - - - - - - E N D - - - - - - - - - - - - - - - - - - - - - - - - - -
Presentation Transcript
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

i introduction1
I. INTRODUCTION

1. Team introduction

i introduction2
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 introduction3
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 introduction4
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 introduction5
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 plan1
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 plan2
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 plan3
II. SOFTWARE PROJECT PLAN

2. Project organization

Waterfall Software Development Model

ii software project plan4
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 plan5
II. SOFTWARE PROJECT PLAN

2. Project organization

  • Tools and Technique:
      • Astah professional tool
        • StyleCop tool
        • SVN tool
        • Microsoft Visio
        • Microsoft Project
ii software project plan6
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 plan7
II. SOFTWARE PROJECT PLAN

4. Risk management

  • Requirements
  • Communication
  • Estimate
  • Changes
  • Human Resource
slide18

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
    • Allow user view task information detail.
    • Allow system user export project detail information to MPP file
slide19
v

III. REQUIREMENT SPECIFICATION

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
iii requirement specification1
III. REQUIREMENT SPECIFICATION

2. Functional requirement

System User

iii requirement specification2
III. REQUIREMENT SPECIFICATION

2. Functional requirement

Project Member

iii requirement specification3
III. REQUIREMENT SPECIFICATION

2. Functional requirement

Task Flow

iii requirement specification4
III. REQUIREMENT SPECIFICATION

3. Non-Functional requirement

  • Supportability Requirement
    • Multi –languages
    • User guidelines
    • Fix bugs and update version
  • Performance requirement
iii requirement specification5
III. REQUIREMENT SPECIFICATION

3. Non-Functional requirement

  • Software system attribute:
    • Usability
    • Availability
    • Security
    • Maintainability requirement
    • Portability
iii requirement specification6
III. REQUIREMENT SPECIFICATION

4. Data structure - Database

Database Diagram

iii requirement specification7
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>
slide28

IV. SOFTWARE DESIGN

1. Software Structure

slide29

IV. SOFTWARE DESIGN

2. Hardware Structure

slide30

IV. SOFTWARE DESIGN

3. Components

slide31

IV. SOFTWARE DESIGN

4. Components Diagram

slide33

IV. SOFTWARE DESIGN

6. Common Sequence

v software testing1
V. SOFTWARE TESTING

1. Test Target

  • Spec Coverage:
    • Verify specifications
    • Verify user requirement
    • Detect defects
    • Manage risk
v software testing2
V. SOFTWARE TESTING

2. Test Model

V LIFECYCLE MODEL

v software testing3
V. SOFTWARE TESTING

3. Features To Be Tested

v software testing4
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 testing5
V. SOFTWARE TESTING

5. Test Execution

Bug Management Flow

v software testing6
V. SOFTWARE TESTING

6. Test Report

slide41

V. SOFTWARE TESTING

7. Bug Report