project progress document optimization 5 april 2007

29
Project Progress Document Optimization 5 April 2007 Team members: Chris Catalano Chun-Yu Chang Chris Joson David Matthes

Upload: gratiana-hamsey

Post on 02-Jan-2016

39 views

Category:

Documents


0 download

DESCRIPTION

Project Progress Document Optimization 5 April 2007. Team members: Chris Catalano Chun-Yu Chang Chris Joson David Matthes. Project Milestones. DateDescription 15 Feb 07Proposal and Presentation 22 Feb 07 Status Report (10 Min) 08 Mar 07Progress Report (20 Min) - PowerPoint PPT Presentation

TRANSCRIPT

Page 1: Project Progress Document Optimization 5 April 2007

Project ProgressDocument Optimization

5 April 2007

Team members: Chris CatalanoChun-Yu ChangChris JosonDavid Matthes

Page 2: Project Progress Document Optimization 5 April 2007

Project Milestones

Date Description15 Feb 07 Proposal and Presentation22 Feb 07 Status Report (10 Min)08 Mar 07 Progress Report (20 Min)22 Mar 07 Status Report (10 Min)05 Apr 07 Formal Progress Presentation (30 Min)26 Apr 07 Dry Run of Final Presentation11 May 07 Final Project Presentation

Final Report

Page 3: Project Progress Document Optimization 5 April 2007

Agenda

•Background•SysML Models•SysML Usability•Webpage•General Status•Questions

Page 4: Project Progress Document Optimization 5 April 2007

EDD Background

• Electronic Data Discovery System• EDD system takes electronic documents and formats them

into a desired package for the lawyers to review.• Problem:

• The process is complex/costly and requires multiple stages to produce the final deliverable.

• Goal:• Our goal is to model and compare the performances of

three different EDD systems.• Evaluate the effectiveness of SysML to achieve our goal.

Page 5: Project Progress Document Optimization 5 April 2007

SysML Diagrams•Use SysML Diagrams to model and capture our problem domain.

•Context Diagram – describes the context of the EDD System

•Requirement Diagram – describes the hierarchy and allocation of EDD requirements

•Component Diagram – describes the building blocks of the EDD System

•Activity Diagram – describes the activities of the EDD System

•Parametric Diagram – describes the constraints and equations of the EDD System.

Page 6: Project Progress Document Optimization 5 April 2007

Context Diagram

Page 7: Project Progress Document Optimization 5 April 2007

Requirements Diagram

Page 8: Project Progress Document Optimization 5 April 2007

EDD Components

Describes the characteristics

Describes Behaviors

What is this diagram?

Page 9: Project Progress Document Optimization 5 April 2007

Component Model

Decompositions

Page 10: Project Progress Document Optimization 5 April 2007

Components Model (cont)

Decompositions

Page 11: Project Progress Document Optimization 5 April 2007

Activity Model of Current Process

Page 12: Project Progress Document Optimization 5 April 2007

Processing Server9 executables

Engineer9 Copies

Unix Client6 Pearl Scripts

Review Team6 Quality Checks

Mac Client

Page 13: Project Progress Document Optimization 5 April 2007

Processing Server1 executable performs 13 activities

Engineer2 CopiesUnix Client2 Pearl Scripts

Review Team2 Quality Checks Mac Client

Page 14: Project Progress Document Optimization 5 April 2007

Comparing Alternatives With NPV

Page 15: Project Progress Document Optimization 5 April 2007

Comparing Alternatives with Net Present Value

• Net Present Value is a technique to compare the three systems financially

• The cash flows in and out can be decomposed and modeled probabilistically then fed into the NPV model as inputs

• The goal is to model NPV for each alternative over 3 years

• We can also tweak the model inputs for sensitivity analysis

Page 16: Project Progress Document Optimization 5 April 2007

NPV Parametric Diagram: In-Flows

QuickTime™ and aTIFF (LZW) decompressor

are needed to see this picture.

To drive Revenue we can:Increase the availability to accept incoming projectsIncrease the processing rate of the machinesIncrease the number of machinesIncrease the number of staff Charge more for each project…

Page 17: Project Progress Document Optimization 5 April 2007

NPV Assumptions

•Example of Assumptions for Initial Runs:•All Jobs are completed in the month they are started•Jobs are processed as fast as possible•There is no cost or time lost in migrating from the baseline system•The pricing scheme does not change between alternatives or year-to-year•The lowest revenue for a job is $2,500•And assorted assumptions about the distributions of model inputs…

Page 18: Project Progress Document Optimization 5 April 2007

NPV Example Model Output

NPV Density Function

0

0.01

0.02

0.03

0.04

0.05

$0

$2,500,000$5,000,000$7,500,000$10,000,000$12,500,000$15,000,000$17,500,000$20,000,000$22,500,000$25,000,000$27,500,000

Dollars

Probability

Baseline

Autonomy

Baseline: Mean: 12 MillionStandard Deviation: 2.4 Million

Autonomy: Mean: $15.9 MillionStandard Deviation: 3.8 Million

Page 19: Project Progress Document Optimization 5 April 2007

SysML Usability

•Multi-Attribute Utility AssessmentEvaluation Hierarchy

Page 20: Project Progress Document Optimization 5 April 2007

Multi-Attribute Utility AssessmentEvaluation Hierarchy*

Overall System Utility

Effect On TaskPerformance

System Usability

* Adelman & Riedel, Handbook for Evaluating Knowledge Based Systems, 1997

ProcessQuality

Product Quality General Ease

Of Use

Ease of Learning

Flexibility

Interface

Page 21: Project Progress Document Optimization 5 April 2007

Purpose of the Survey

• Evaluate SysML as a modeling language for designing systems• Evaluate SysML model maturity• Evaluate IBM Rational System Developer• Determine if SysML is a useful tool for system

development• Will hand out to OR680 students using

SysML• Expect about 10 responses

Page 22: Project Progress Document Optimization 5 April 2007

• Questions focus on either SysML as a language or IBM Rational System Developer as a tool

• Most questions will be rated on a scale of 1 to 5• Responses will be averaged together to determine a score

for each category• Sample Questions

• Overall, SysML improves the system design process.• Rational System Developer provides feedback when

processing user commands.• SysML was easy to learn.• I can easily add model elements to the System model.

Sample Survey Questions

Page 23: Project Progress Document Optimization 5 April 2007

Survey Example

10. Modeling a system with SysML is faster than the current process (i.e., Power Point)Strongly Disagree Strongly Agree

1 2 3 4 5

11. The SysML diagrams available were adequate for my project.Strongly Disagree Strongly Agree

1 2 3 4 5

Survey will have participant answer a series of questions

Page 24: Project Progress Document Optimization 5 April 2007

Webpage Development

Mason.gmu.edu/~cchang7

Page 25: Project Progress Document Optimization 5 April 2007
Page 26: Project Progress Document Optimization 5 April 2007

General Status

Page 27: Project Progress Document Optimization 5 April 2007

ScheduleID Task Name Duration Start Finish

1 EDD Project Plan 67 days? Thu 2/1/07 Thu 5/3/07

2 Prepare Proposal 11 days Thu 2/1/07 Thu 2/15/07

3 Develop Project Scope 11 days Thu 2/1/07 Thu 2/15/07

4 Identify Models 6 days Thu 2/8/07 Thu 2/15/07

5 Background Research and Learn SysML 17 days? Thu 2/8/07 Fri 3/2/07

6 Detail SysML Metrics & Measures 7 days Wed 2/14/07 Thu 2/22/07

7 Detail Huron Metrics & Performance 7 days Wed 2/14/07 Thu 2/22/07

8 Contact Aerospace 1 day? Thu 2/22/07 Thu 2/22/07

9 Determine a day to visit Huron 7 days Wed 2/14/07 Thu 2/22/07

10 Research Background Literature 11 days Thu 2/8/07 Thu 2/22/07

11 Research Autonomy 11 days Fri 2/16/07 Fri 3/2/07

12 Research Attenex 11 days Fri 2/16/07 Fri 3/2/07

23 Model Processes in SysML 42 days Fri 2/16/07 Fri 4/13/07

24 Implement Model of Current Process in SysML 21 days Fri 2/16/07 Thu 3/15/07

25 Implement Attenex Model in SysML 21 days Fri 3/2/07 Thu 3/29/07

26 Implement Autonomy Model in SysML 21 days Sat 3/3/07 Fri 3/30/07

27 Optimize Models and Perform Trade Analysis 21 days Fri 3/16/07 Fri 4/13/07

28 Track SysML Issues and Metrics 56 days Fri 2/9/07 Thu 4/26/07

29 Learn SysML 16 days Fri 2/9/07 Fri 3/2/07

30 Use SysML 51 days Fri 2/16/07 Thu 4/26/07

31 SysML Training 0 days Sat 3/3/07 Sat 3/3/07

13 Develop Final Presentation 17 days Wed 4/4/07 Thu 4/26/07

14 In Class Deliverables 56 days Thu 2/15/07 Thu 5/3/07

15 Proposal and Presentation 0 days Thu 2/15/07 Thu 2/15/07

16 Status Report 0 days Thu 2/22/07 Thu 2/22/07

17 Progress Report 0 days Thu 3/8/07 Thu 3/8/07

18 Status Report 0 days Thu 3/22/07 Thu 3/22/07

19 Formal Progress Presentation 0 days Thu 4/5/07 Thu 4/5/07

20 Dry Run of final Presentation 0 days Thu 4/26/07 Thu 4/26/07

21 Final Project Presenation 0 days Tue 5/1/07 Tue 5/1/07

22 Final Report 0 days Thu 5/3/07 Thu 5/3/07

3/3

2/15

2/22

3/8

3/22

4/5

4/26

5/1

5/3

1/28 2/4 2/11 2/18 2/25 3/4 3/11 3/18 3/25 4/1 4/8 4/15 4/22 4/29January February March April

Page 28: Project Progress Document Optimization 5 April 2007

Progress To Date

SysML Software Installation – 100%Currently using Temp licenses (could not access GMU server for floating licenses)

SysML Training – Complete 3/3/07SysML Model Development – 80% completeWeb Site Development – 90% completeSysML Metrics – 80% completeBaseline Performance Analysis – 100%Comparison of Systems - 30%

Page 29: Project Progress Document Optimization 5 April 2007

Questions?