14
Distributed Monitoring & Mining OMSE PRACTICUM I FINAL PRESENTATION MARCH 21, 2013 THOMAS MOONEY SHAILESH SHIMPI AHMED OSMAN ISAAC PENDERGASS REQUIREMENTS ENGINEER QA MANAGER/ TEST ENGINEER ARCHITECT PROJECT MANAGER

Distributed Monitoring & Mining

  • Upload
    ezhno

  • View
    40

  • Download
    0

Embed Size (px)

DESCRIPTION

Distributed Monitoring & Mining. OMSE PRACTICUM I FINAL PRESENTATION. M arch 21, 2013. Thomas mooney shailesh shimpi ahmed Osman isaac pendergass. Architect . Project Manager . QA Manager/ Test engineer . Requirements engineer. - PowerPoint PPT Presentation

Citation preview

Page 1: Distributed Monitoring & Mining

Distributed Monitoring & MiningOMSE PRACTICUM I FINAL PRESENTATIONMARCH 21, 2013

THOMAS MOONEY SHAILESH SHIMPI AHMED OSMAN ISAAC PENDERGASSREQUIREMENTS ENGINEER QA MANAGER/ TEST

ENGINEER ARCHITECT

PROJECT MANAGER

Page 2: Distributed Monitoring & Mining

“”

… as software systems become more complex, automated analysis may be the only way that we can keep up with their size and scope.

Page 3: Distributed Monitoring & Mining

Our Purpose

Project Status Prototype and Demo Lessons learned so far Planned changes for next term Upcoming plans

To augment current collaboration tools by collecting and modeling historical project data to alert project stakeholders when signs of trouble are detected.

Page 4: Distributed Monitoring & Mining

Project Status

Deliverables Planned

Project Proposal Software Project Management Plan (SPMP) Concept of Operations (ConOps) Software Requirements Specification (SRS) Prototype

Page 5: Distributed Monitoring & Mining

Project Status (cont.)

Deliverables Completed

Project Proposal Software Project Management Plan (SPMP) Concept of Operations (ConOps) Software Requirements Specification (SRS) Prototype

In Progress Software Architecture Document (SAD) QA Plan/Test Plans Metrics Document

Page 6: Distributed Monitoring & Mining

Prototype Prototype Technical Details

ASP.net Application MySQL Database Mono Server for Deployment SVN for Source Control

Assembla - Distributed Software Colloboration Tool Assembla Projects are called Projects Spaces OAuth2 Authentication Data downloaded from approximately 68,000 public project

Google Predictor - Prediction Engine Firstly, the metric is trained with training data Selected project space data is sent from DMM application Predictor responses back with results (project is on track or failing)

Page 7: Distributed Monitoring & Mining

Demonstration

Page 8: Distributed Monitoring & Mining

Lessons Learned      “You can’t always get what you want.” Initial metric definitions scrapped due to API restrictions. Approximately half of secondary metrics unavailable due to incomplete

project record entries.

Current Redmine usage confirms pattern. Email preferred over forum communication. Outside document revision systems preferred. SkyDrive and Google Docs offer greater flexibility in terms of team collaboration.

We must choose metrics based on data that has a reasonable probability of being recorded in order to build models that are useful in determining user-project status.

Page 9: Distributed Monitoring & Mining

Lessons Learned (cont.)           “…don’t let me be misunderstood.” Less tractable communication issues arise more often from

misinterpretation than from simple omission. Special care must be taken to ensure that transmissions are precise

and to the point. Problems arising from misinterpretation are generally tougher to

remedy as they are closer to the specific natures of the individuals involved.

This is an important point as it serves to illuminate the main difficulty encountered in distributed development.  Learning to cope with deficiencies in communication will help our own effort as well as providing insight that may help our customers as well.

Page 10: Distributed Monitoring & Mining

Lessons Learned (cont.)                 “If you don’t know me by now…” Inadequately Defined Problem Space

We had an idea, but needed more context. Forced to explore problem space to get better understanding of

requirements. Delay in completion of SRS

Page 11: Distributed Monitoring & Mining

Planned Changes

Tightening of Process Controls Adaptation of current process to reflect preferred modes of operation

where possible. Methods that do not promote our end goal will be discontinued and

replaced. Potentially increased usage of “Issues” feature in Redmine

Issue tracking Responsibility tracking Schedule

Page 12: Distributed Monitoring & Mining

Upcoming Plans Finalizing the Software Architecture Document SAD Developing the actual application with more development

iteration Use the requirements traceability matrix to keep track of the

requirements and implementation and testing Quality Plan

Establishing Quality plan Adding integration testing and unit testing Adding Deployment and packaging plans

Page 13: Distributed Monitoring & Mining

Upcoming Plans (Cont.) Complete Infrastructure Build-out

Complete Risk Management activities Implement Continuous Integration

Web Server Setup Work with IT to enable database on Mono for local cache

Adding More Metrics Adding tickets opened per milestones metrics and retrain the data at

Google Adding more seamless connection between The application and

Google Predictive

Page 14: Distributed Monitoring & Mining

Questions?