Distributed Monitoring and Distributed Monitoring and MiningMining

Advisor: Dr. Stuart Faulk Advisor: Dr. Stuart FaulkTeam: Ahmed Osman, Isaac Pendergrass, Shail Shimpi, Tom MooneyTeam: Ahmed Osman, Isaac Pendergrass, Shail Shimpi, Tom Mooney

OMSE-555/556 Software Engineering Practicum I & II

Mid-Term I StatusWinter 2013

Project CharterProject Charter

Winter 2013 2OMSE 555/556 Software Engineering Practicum

To develop an software system that will interface with the open source collaboration software (such as Assembla1) to:Gather tracking and communication data.Analyze the data.Display results for:

Monitoring project progress Identifying project issues

1Collaboration Software with capabilities for assisting distributed teams in communication, collaboration, and project management.

Mission StatementMission Statement

Winter 2013 3OMSE 555/556 Software Engineering Practicum

Our team consists of enthusiastic software engineering students and agree to the following mission statement.

The mission of the Distributed Monitoring and Mining Project is to effectively apply software engineering principles & processes learned in the OMSE courses and develop a system that will be practically useful in monitoring a software project and allow future teams to expand the system’s functionality or scope.”

Process MethodologyProcess Methodology

Winter 2013 4OMSE 555/556 Software Engineering Practicum

Project Planning

Software Requirements and Analysis

Architecture and Design

OMSE 555/556 Course Goals

2. Software Project Management Plan (SPMP)

3. Software Requirements Document4. Software Test Plan (STP)

5. Software Architecture Document6. API Documentation

1. Project Proposal

Develop & Test Version

DeliverVersion

Elicit Feedback

Revise Release Version

7. Software Tutorial8. Software User DocumentationProcess Product

Technical Decisions Made…Technical Decisions Made…

Winter 2013 5OMSE 555/556 Software Engineering Practicum

To build the application system interfacing with Assembla Open Source Collaboration software.

Google Analytics Visual Studio 2012 C#, ASP .Net, IIS Server SpecFlow (www.specflow.org)

Project StatusProject Status

Winter 2013 6OMSE 555/556 Software Engineering Practicum

Iteration

Start Date Duration

(Weeks)

End Date Activities 

Deliverables

0 1/31/013

3 2/13/2013

Finalize Project Plan

Produce SRS and Concept of Operations.

Midterm presentation

• Software Requirements Specification (SRS)

• Concept of Operations (ConOps)

• Midterm Presentation

1 2/14/2013 2 2/27/2013 Iteration Planning Development Retrospective

Build 1/prototype

2 2/28/13 3 3/18/13 Iteration Planning Development Retrospective Prepare end of term

presentation

Stories for iteration 2,Build 2,End of term PPT

3 4/4/13 2 4/17/13 Iteration Planning Development Retrospective

Build 3

4 4/18/13 2 5/1/13 Iteration Planning Development Retrospective

Build 4

5 5/2/2013 2 5/16/2013 Iteration Planning Development Retrospective

Build 5

6 5/16/13 2 5/29/13 Iteration Planning Development Retrospective

Build 6

7 5/30/2013 2 6/10/13 Iteration Planning Development Retrospective

Final build

Project Status (cont.)Project Status (cont.)

Winter 2013 7OMSE 555/556 Software Engineering Practicum

Software Process Step

Deliverables Status

Project Planning Project Proposal

Software Project Management Plan (SPMP)

Completed (1/24/13)

Completed (1/31/13)

Software Requirements & Analysis

Concept of Operations

Software Requirements Specification (SRS)

Draft (2/7/13)

Draft (2/14/13)

Architecture and Design

Software Architecture Document (SAD)

Implementation/Development (Iterative)

Prototype

Product Release(s)

Project ManagementProject Management

Winter 2013 8OMSE 555/556 Software Engineering Practicum

Virtual meetings, twice weekly. (Collaborate) Breakout-room session after classes. Meeting agendas posted to Wiki prior to the meetings Meeting Minutes recorded and posted to Wiki. Redmine used for project collaboration and version control. Email employed for resolving high priority issues/topics. Primary and secondary member is assigned to each project

role (Project Manager, Architect, etc). All members will bear developer’s role. Resource availability estimated for the duration of the

project.

Risk ManagementRisk Management

Winter 2013 9OMSE 555/556 Software Engineering Practicum

Identified RisksTime ConstraintLoss of WorkLoss of CommunicationLoss of Personnel

Correct Risks Identified? Yes and MaybeCommunication outages have occurred infrequently, but have been handled.More time needed.

Problems/InsightsProblems/Insights

Winter 2013 10OMSE 555/556 Software Engineering Practicum

Redmine is missing some key functionalityParent/children tasksNotifications (Hit or miss)Diff/Merge issues with word (.docx) files.Intermittent audio issues with Collaborate.IIS Servers unavailable through CAT.

Questions?Questions?

Winter 2013 11OMSE 555/556 Software Engineering Practicum