MOSP Summer 2004

1
MOSPSummer 2004

• 2004. 6. 25
• Team GEO

2
Agenda

• Introduction
• Development Plan
• Achievements
• Processes
• Scope Estimation
• Action Item Tracking
• Defect Log Time Log
• Reflective Practice
• Difficulties
• QA

3
Team Introduction

• Members Roles
• Mentors
• ICU - Hojin Choi, Danhyung Lee, Sungwon Kang
• CMU - Gil Taran

YounBok JunSuk KwangChun
SoYoung JungHee
4
Project Overview

• Project Name
• PMCenter (Project Management Center)
• Customer
• KT
• Objective
• To make web-based software project management
  system customized for KT
• Scope
• To support overall project life cycle from
  project initiation to closing

5
Plan for Summer Semester
Construction
Transition
Iteration 1
Iteration 2
Iteration 3
6
Development Environment

• Design
• Tool Borland Together
• Implementation ASP.NET
• Server OS - Windows 2000 Server
• Language - C
• Tool Visual Studio .Net
• Database MS SQL
• Support
• Configuration management tool Visual Source Safe

7
Achievements

• 1st iteration (finished)
• UI design
• Development environment setup
• Use case prototyping for scope estimation
• Supporting system development
• Action item management system
• 2nd iteration (on going)
• Scope finalization
• From 23 to 15 use cases
• UI refinement
• Detailed design
• Common control development
• Supporting system development
• Defect log Time log management system

8
Scope Estimation Process
Select 5 use cases from 23 use cases
Prototyping ( One use case per member)
Measure Time and Progress
Estimate Scope
Get Customers Approval
9
Scope Estimation Result
UUCP Unadjusted Use Case Point
10
Action Item Management

• Purpose
• To resolve difficulties in tracking action items
• To figure out each members responsibility
• To ease communication among members
• To balance work load among members

11
Defect Log Time Log Management

• Purpose
• To track project progress weekly
• To improve quality by defect management
• Features
• Based on PSP forms
• To be web-based system
• Where to use data
• Analysis of members activities
• Evaluation of estimation by comparing actual time
  and planned time for each use case
• Analysis of spending time for each development
  stage and use case

12
Reflective Practice

• Topic
• Test Automation
• Purpose
• Core course reflection
• Analysis of software artifact
• Focus on
• Performance Testing
• Tool
• Microsoft Application Center Test

13
Reflective Practice

• Performance test (Experiment)
• Comparing two different methods of DB query

Database Query Stored Procedure vs. Non-Stored
Procedure
14
Difficulties

• Project management
• Planning (Estimation)
• Tracking (Project progress)
• Requirement analysis
• Some core feature is ambiguous
• Lack of time for learning by doing

15
Q A

• To GEO
• To Mentors
• Reverse Engineering is not good? How about
  rebuilding detailed design document after
  finishing coding?
• Customer emphasize to provide working system but
  does not concern about the process or
  methodology. However, MSE require it. How could
  we compromise these two different viewpoints?