1 / 29

Project Progress Document Optimization 5 April 2007

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

gratiana-hamsey
Download Presentation

Project Progress Document Optimization 5 April 2007

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. Project ProgressDocument Optimization5 April 2007 • Team members: • Chris Catalano • Chun-Yu Chang • Chris Joson • David Matthes

  2. Project Milestones • Date Description • 15 Feb 07 Proposal and Presentation • 22 Feb 07Status 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 Presentation • 11 May 07 Final Project Presentation • Final Report

  3. Agenda Background SysML Models SysML Usability Webpage General Status Questions

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

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

  6. Context Diagram

  7. Requirements Diagram

  8. Describes Behaviors Describes the characteristics EDD Components What is this diagram?

  9. Decompositions Component Model

  10. Decompositions Components Model (cont)

  11. Activity Model of Current Process

  12. Processing Server 9 executables Engineer 9 Copies Unix Client 6 Pearl Scripts Review Team 6 Quality Checks Mac Client

  13. Engineer 2 Copies Unix Client 2 Pearl Scripts Processing Server 1 executable performs 13 activities Review Team 2 Quality Checks Mac Client

  14. Comparing Alternatives With NPV

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

  16. NPV Parametric Diagram: In-Flows To drive Revenue we can: Increase the availability to accept incoming projects Increase the processing rate of the machines Increase the number of machines Increase the number of staff Charge more for each project …

  17. 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…

  18. NPV Example Model Output Baseline Autonomy Baseline: Mean: 12 Million Standard Deviation: 2.4 Million Autonomy: Mean: $15.9 Million Standard Deviation: 3.8 Million

  19. SysML Usability Multi-Attribute Utility AssessmentEvaluation Hierarchy

  20. Multi-Attribute Utility AssessmentEvaluation Hierarchy* Overall System Utility Effect On Task Performance System Usability Process Quality Product Quality General Ease Of Use Interface Ease of Learning Flexibility * Adelman & Riedel, Handbook for Evaluating Knowledge Based Systems, 1997

  21. 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 Purpose of the Survey

  22. Sample Survey Questions • 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.

  23. Survey Example • Survey will have participant answer a series of questions

  24. Webpage Development Mason.gmu.edu/~cchang7

  25. General Status

  26. Schedule

  27. Progress To Date • SysML Software Installation – 100% • Currently using Temp licenses (could not access GMU server for floating licenses) • SysML Training – Complete 3/3/07 • SysML Model Development – 80% complete • Web Site Development – 90% complete • SysML Metrics – 80% complete • Baseline Performance Analysis – 100% • Comparison of Systems - 30%

  28. Questions?

More Related