Middle Of Semester Presentation

1
Middle Of Semester Presentation

• Mi Yul Park

05-05-2005
2
AGENDA
Agenda

• Project Introduction
• Project Status
• Detailed Artifacts
• SRS
• Risks
• Estimation
• Lessons learned
• Plan for next semester
• Questions

3
Involved People
Project Introduction

• Technical Advisor James E. Tomayko
• CMU Mentor Mel Rosso-LIopart
• ICU Mentor Sung Won Kang
• End-user MSE students

4
Background
Project Introduction

• Time management
• Plan ? Time Log ? Analyze
• Problem Existing time logging tools are not
  optimal for MSE program
• It is difficult to share data
• Frequent meeting causes forgetfulness, and hence
  accuracy of time-log is degraded
• MSE Time Tracker
• will link to CVS repository
• will provide a mechanism that a user can record
  spent time accurately

5
Context Diagram
Project Introduction
6
Project Objectives
Project Introduction

• Develop a useful tool for MSE students to track
  time
• Learn by practice
• Deliver the product on time

7
Table of contents
Table of contents

• Project Introduction
• Project Status
• Detailed Artifacts
• SRS
• Risks
• Estimation
• Lessons learned
• Plan for next semester
• Questions

8
Project Artifacts
Project Status

• Proposal
• Software Development Plan
• Survey Report
• Paper Prototype
• Software Requirements Specification
• Estimation Report
• Risk List
• Test Plan
• High Level Design
• Prototype

• Completed Artifacts
• On-going Artifacts

9
Timeline
Project Status
10
Table of contents
Table of contents

• Project Introduction
• Project Status
• Detailed Artifacts
• SRS
• Risks
• Estimation
• Lessons learned
• Plan for next semester
• Questions

11
Requirements Elicitation (1/3)
Project Artifacts

• End user interview
• Informal interview
• Objects MSE students
• Content
• What tools do you use to record time?
• What drawbacks does the tool have?
• What is your idea to improve the tool?
• Survey Report
• Market Research on existing time logging tools

12
Requirements Elicitation (2/3)
Project Artifacts

• Paper Prototype
• User Interface Design
• Gives an outline of designed features
• Based on Eclipse platform
• Software Requirements Specification
• Gives real requirements in detail
• Prioritized requirements

13
Sample Requirements Time palette (3/3)
Project Artifacts
SRS


Paper prototype
14
Risks High level risks
Project Artifacts
(VH/H/H) Probability is very high/ impact is
high / level is high
15
Estimation

• Estimation Method Function Point
• Result total loc per hour 4664 / 154 30.29
  LOC/hour
• Total function point 88 FP (48 timelog, 40
  analysis)
• Size estimation 88 FP 53 4664 LOC1
• Time constraints 11 weeks 14 hours 154 hrs
• Productivity of the developer is not verified
• Confidence of estimation is degraded because of
  unfamiliarity with FP
• ? Select Iterative development method instead of
  reducing the scope and perform estimation
  iteratively.

(1) Ref. Applied Software Measurement, Caper
Jones, McGraw Hill, 1996
16
Table of contents
Table of contents

• Project Introduction
• Project Status
• Detailed Artifacts
• SRS
• Risks
• Estimation
• Lessons learned
• Plan for next semester
• Questions

17
Lessons Learned
Lessons Learned

• Requirement elicitation Survey report and Paper
  prototype are useful
• Estimation Skill Practice Function Point
• Meeting minutes make meetings more productive

18
Table of contents
Table of contents

• Project Introduction
• Project Status
• Detailed Artifacts
• SRS
• Risks
• Estimation
• Lessons learned
• Plan for next semester
• Questions

19
Plan for Next Semester
Plan for next semester

• High Level Design
• Prototyping
• Detail Design
• Implementation
• Test Case
• Test Report

20
Table of contents
Table of contents

• Project Introduction
• Project Status
• Detailed Artifacts
• SRS
• Risks
• Estimation
• Lessons learned
• Plan for next semester
• Questions

21
Questions (1/2)
Questions

• High Level design designing architecture is too
  tricky for the beginner developer to go though
  alone
• How can I handle this problem?
• SRS - how to evaluate or quantify quality
  attributes such as usability or modifiability
• I used Task solving time or Menu level. Is there
  any other approach?
• E.g.,) Task solving time of the naïve user shall
  be less than 20 minutes

22
Questions (2/2)

• Management how to handle the slipped schedule
  in time-critical project
• Just keep overworking or reduce the number of
  tasks?

23
Any Questions?
24
(No Transcript)