Upload
susan-welch
View
219
Download
0
Tags:
Embed Size (px)
Citation preview
DISTRIBUTED TEAM COLLABORATION PROCESSES II
OMSE 556 FINAL REPORT (SPRING 2012)
Ivan Dontsov, Andy Phenix, Maureen Rottschaefer
Project Proposal
“The primary objective of this OMSE 2012 Practicum Project is to extend and refine the process specification tool (developed during the 2010 Practicum) and address some of its limitations.
In particular, the project will address the ‘most obvious extension’ to provide a more user-friendly interface and easier administrative support.”
Roles (planned) OMSE 556
Software Project Manager (SPM)(Andy Phenix)
Software Architect (SA)
(Ivan Donstov)
OMSE 555 / 556Project Team
OMSE Customer(Stuart Faulk)
Requirements Manager (RM)
(Maureen Rottschaefer)
OtherOMSE 555 / 556Project Teams
Software Developer / Tester
(Andy Phenix)
Software Developer / Tester
(Ivan Donstov)
Software Developer / Tester
(Maureen Rottschaefer)
Primary Role
Secondary Role
Roles (actual) OMSE 556
Software Project Manager (SPM)(Andy Phenix)
Software Architect (SA)
(Ivan Donstov)
OMSE 555 / 556Project Team
OMSE Customer(Stuart Faulk)
Requirements Manager (RM)
(Maureen Rottschaefer)
OtherOMSE 555 / 556Project Teams
IT / Software Developer
(Andy Phenix)
Software Developer / Tester
(Ivan Donstov)
Software Developer / Tester
(Maureen Rottschaefer)
Primary Role
Secondary Role
Project Plan Adjusted
Contingency – Focus only on ‘core’ Functionality
Jan-12 Jun-12Apr-12
Jan-12 - Mar-12Phase 1 - Base-lining
Mar-12Baseline Requirements CompleteCandidate Architecture Complete
Mar-12 - May-12Phase 2 - Core Functionality
May-12 - Jun-12Phase 3 - Enhancements, Revisions
May-12Core Functionality Complete
Jun-12Final Delivery
OMSE 555 OMSE 556
Project Plan Adjusted
Contingency – Focus only on ‘core’ Functionality
Jan-12 Jun-12Apr-12
Jan-12 - Mar-12Phase 1 - Base-lining
Mar-12Baseline Requirements CompleteCandidate Architecture Complete
Mar-12 - May-12Phase 2 - Core Functionality
May-12 - Jun-12Phase 3 - Enhancements, Revisions
May-12Core Functionality Complete
Jun-12Final Delivery
OMSE 555 OMSE 556
Project Plan Revised2.3.3. Build Technical Prototypes
2.3.4. Design System Interfaces
2.4.1. Develop Test Plan
2.5.1. Build Development & Testing Environments
2.3.5. Develop & Unit Test Software
2.5.2. Deployment
2.4.2. Functional Testing
2.6.1. Develop User Documentation
2.3.4. Design System Interfaces
2.3.5. Develop & Unit Test Software
2.5.2. Deployment
2.5.2. Final Deployment
2.4.2. Functional Testing
2.6.1. Develop User Documentation
1.1.1 Revise Project Plan
1.1.4 Progress Reporting and Audits
1.1.4 Progress Reporting and Audits
3/22
/12
3/29
/12
4/5/
12
4/12
/12
4/19
/12
4/26
/12
5/3/
12
5/10
/12
5/17
/12
5/24
/12
5/31
/12
6/7/
12
6/14
/12
Project Status - Development
Planned vs ActualIteration 0 – Technical Prototype CompleteIteration 1 – In Progress CompleteIteration 2 – In Progress Complete
Testing, DocumentationBehind Schedule
Status of Deliverables
Deliverable Status Comments
Plans Software Project Management Plan (SPMP)
Complete
Software Test Plan (STP) - Not started
Technical Documents and Software
Software Requirements Specification (SRS)
Draft 5th revision
Software Architecture Document (SAD) Draft 4th revision
Software User Documentation - Not Started
Source Code (including installation and configuration instructions).
Complete ‘Alpha’ version
Use Cases Implemented
Use Case Status Comments
[DTCPII-001] View process specifications Complete
[DTCPII-002] Begin new process specification Complete
[DTCPII-003] User Login Complete
[DTCPII-004] Input process component data Complete
[DTCPII-005] Publish process specification Complete
[DTCPII-006] Delete process data Complete
[DTCPII-007] Delete all data for specified user Complete
[DTCPII-008] System delete Complete
[DTCPII-009] Data download Complete
Technical Platform
.Net / Mono Web-based Application
ASP.Net MVC FrameworkjQueryAJAX
Apache / mod_mono MySQL MoMA
Project Proposal
“The primary objective of this OMSE 2012 Practicum Project is to extend and refine the process specification tool (developed during the 2010 Practicum) and address some of its limitations.
In particular, the project will address the ‘most obvious extension’ to provide a more user-friendly interface and easier administrative support.”
Existing OMSE 551 Tool Set up Assembla user account Checkout xml templates from Subversion repository Copy templates and fill out xml content Commit updates to Subversion repository Repeat until all content created Navigate to website Enter Assembla user account and click ‘Load User’ Click ‘Build Site’ to process xml content Click ‘View Built Process Site’ to view process
specification
New Tool
Logon to website Click ‘Create New…’ Fill in form fields Click ‘Save’ Click ‘Preview’ to view process
specification
Lessons Learned
Project Management IssuesRoles and ResponsibilitiesCommunication ProcessesPhased Approach
DSEPSLimited Use
Project Risks
Risk Probability
(L/M/H)
Impact
(L/M/H)
Mitigation Plan
Limited resources H M Project team will manage scope accordingly (see section 3.2 below), and each team member will assume multiple project roles (see section 2.2 above)
Unavailability of secondary stakeholders
M L Project team will assume the primary stakeholder role, and validate requirements with the secondary stakeholders
Confusion around practicum project process
H H Addressed by week 4 recalibration meeting
New development process / project team
M M Project team will review DSEPS