Distributed Monitoring and Mining Advisor: Dr. Stuart Faulk Team: Ahmed Osman, Isaac Pendergrass, Shail Shimpi, Tom Mooney OMSE-555/556 Software Engineering.

Slides:

Advertisements

Similar presentations

Project Management Concepts

Advertisements

The Value of a Project Management Office Copyright: Kathy J. Lang, 2004.

Project Management Process. Managing the Information Systems Project Focus of project management To ensure that information system projects meet customer.

Chapter 7: Key Process Areas for Level 2: Repeatable - Arvind Kabir Yateesh.

Implementation I - demo. Schedule * Project status -achieving the goals of the iteration -project metrics * Used work practices * Work results -presenting.

Sixth Hour Lecture 10:30 – 11:20 am, September 9 Framework for a Software Management Process – Artifacts of the Process (Part II, Chapter 6 of Royce’ book)

GAI Proprietary Information

The Role of Software Engineering Brief overview of relationship of SE to managing DSD risks 1.

SIM SOFTWARE ARCHITECTURE Instructor: Masrah Azrifah Azmi Murad, PhD Room: C masrah.azrifah [at] gmail.com OR masrah [at] fsktm.upm.edu.my.

Project Management and Communication Represented by: Latifa Jaber Al-Ghafran.

Project Management Module 3. Keep focused on the timeline Week Prepare for Kick-off Meeting Assign teams Team forming Review and execute.

IS 421 Information Systems Management James Nowotarski 16 September 2002.

Project Work and Administration

COMP4710 Senior Design Richard Chapman. Outline What is Senior Design? What is Senior Design? Course Structure Course Structure End of Cycle Binder End.

4. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Explain the elements of project management and the responsibilities of a.

Using UML, Patterns, and Java Object-Oriented Software Engineering Chapter 3, Project Organization and Communication.

Systems Development (SD) Presentation Michael Webb IT Director for Medicaid Utah Department of Health UDOH Informatics Brownbag August.

project management office(PMO)

IS&T Project Management: How to Engage the Customer September 27, 2005.

Planning. SDLC Planning Analysis Design Implementation.

© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.

Project Execution.

Project Management and Scheduling

LSU 07/07/2004Communication1 Communication & Documentation Project Management Unit – Lecture 8.

STD 3 “Shirly” Plan. Goals Create an excellent, free, public app for the already publicly available 2010 STD Guidelines Document process for other programs.

Query Health Business Working Group Kick-Off September 8, 2011.

Mobile Application for SAT Preparation Preliminary Project Plan By Project Team: Hi5 Anant Kambli Amit Shukla Ajaykumar Aswathappa Prabin Gautam Rama K.

Ivan Dontsov, Andy Phenix, Maureen Rottschaefer. Agenda  Status  Demo  Lessons Learned.

Discussion Items with Bruce

SA Capstone Requirements and Design Week 10 SYST Winter 2013 Instructors: Jerry Kotuba & Joe Varrasso.

Team Launch Introduction. Real projects are large and complex, and most software is created by teams Merely throwing people together does not result in.

Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Ivan Dontsov, Andy Phenix, Maureen Rottschaefer. Project Outline “The primary objective of this OMSE 2012 Practicum Project is to extend and refine the.

Recap from last week Understand organizations, including the four frames, organizational structures. Explain why stakeholder management and top management.

IT 499 Bachelor Capstone Week 8. Adgenda Administrative Review UNIT Seven UNIT Eight Project UNIT Nine Preview Project Status Summary.

Next Doc Project Team: xxxxx Spring TitlePage Scope Statement Mission Statement3 Business Need4 Project Description5-6 Project Lifecycle Approach7.

Distributed Software Development Transport4You1 Project Plan Gaurav Kushwaha & Dajan Zvekic.

Process Management  Identify and involve stakeholders  Find common vision and mission  Define roles and responsibilities  Monitor/evaluate team effectiveness.

Statistics Monitor of SPMSII Warrior Team Pu Su Heng Tan Kening Zhang.

Basic of Project and Project Management Presentation.

What is a Business Analyst? A Business Analyst is someone who works as a liaison among stakeholders in order to elicit, analyze, communicate and validate.

Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.

National Information Exchange Model Update for the Global Advisory Committee Spring 2008 Meeting April 10, 2008 NIEM Technical Architecture Committee (NTAC)

Georgia Institute of Technology CS 4320 Fall 2003.

INFO 637Lecture #101 Software Engineering Process II Review INFO 637 Glenn Booker.

PMCenter Project SPRING 2004 MOSP Team GEO. 2 Agenda Introduction Semester Goal Project Management Iteration Plan Risk Management Process Handbook.

These materials are prepared only for the students enrolled in the course Distributed Software Development (DSD) at the Department of Computer Science.

Agreement Reaching Process Documentation (Example) Professional Virtual Community Business Opportunity.

Agenda  Project Overview  Project Goal & Scope  Estimates  Deadline  Project Environment  Delivery Plan  Project Plan  Team Structure  Risk Analysis.

Quick Recap Monitoring and Controlling. Lesson 11: Monitoring and Controlling Project Work Topic 11A: Identify the Monitor and Control Project Work Process.

Business Analysis. Business Analysis Concepts Enterprise Analysis ► Identify business opportunities ► Understand the business strategy ► Identify Business.

Project Initiation at The Regence Group 12/19/2015John Garrigues1.

SOLUTION What kind of plan do we need? How will we know if the work is on track to be done? How quickly can we get this done? How long will this work take.

Module 5 Session 5.2 Visual 1 Module 5 Refining Objectives, Scope, and Other Project Parameters Session 5.2 Reviewing the PAR and refining key project.

Resources - Agenda Training - In Scope Thinking ahead Envisioning an outcome Communications Basic plans Risk identification Issue Identification CAP.

Team X Review. The members of Team X propose to develop a therapeutic activity system using a Microsoft Surface unit and a Windows 7 desktop. By working.

The Design Management Team Framing the Scope of Work and Learning the Roles for the LCC Team.

Planning Extreme programming

T Iteration Demo Tikkaajat [PP] Iteration

Team-Based Development ISYS321 Managing the Information Systems Project.

BSBPMG501A Manage Project Integrative Processes Manage Project Integrative Processes Project Integration Processes – Part 2 Diploma of Project Management.

ILC EDMS Selection Committee Progress Report Tom Markiewicz SLAC 29 November 2005.

Milestone Two – Reach Across Houston (RAH) Tuesday, June 14, Team:Matthew Edwards Thomasina Coates Michelle Graham James Henrydoss James McNicholas.

Adaptive Software Development Process Framework. Version / 21 / 2001Page Project Initiation 2.0 Adaptive Cycle Planning 5.0 Final Q/A and.

Overview of Software Project Management cont Review – Class 6 Scheduling Tasks Project Management Activities CEN 4010 Class 8 – 09/22.

Chapter 3, Project Organization and Communication

Software Configuration Management

Adaptive Product Development Process Framework

Joint Application Development (JAD)

Presentation transcript:

Distributed Monitoring and Mining Advisor: Dr. Stuart Faulk Team: Ahmed Osman, Isaac Pendergrass, Shail Shimpi, Tom Mooney OMSE-555/556 Software Engineering Practicum I & II Mid-Term I Status Winter 2013

Project Charter Winter OMSE 555/556 Software Engineering Practicum To develop an software system that will interface with the open source collaboration software (such as Assembla 1 ) to:  Gather tracking and communication data.  Analyze the data.  Display results for:  Monitoring project progress  Identifying project issues 1 Collaboration Software with capabilities for assisting distributed teams in communication, collaboration, and project management.

Mission Statement Winter OMSE 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 Methodology Winter OMSE 555/556 Software Engineering Practicum

Technical Decisions Made… Winter OMSE 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 (

Project Status Winter OMSE 555/556 Software Engineering Practicum IterationStart Date Duration (Weeks) End Date Activities Deliverables 01/31/01332/13/2013  Finalize Project Plan  Produce SRS and Concept of Operations.  Midterm presentation Software Requirements Specification (SRS) Concept of Operations (ConOps) Midterm Presentation 12/14/201322/27/2013  Iteration Planning  Development  Retrospective Build 1/prototype 22/28/1333/18/13  Iteration Planning  Development  Retrospective  Prepare end of term presentation Stories for iteration 2, Build 2, End of term PPT 34/4/1324/17/13  Iteration Planning  Development  Retrospective Build 3 44/18/1325/1/13  Iteration Planning  Development  Retrospective Build 4 55/2/201325/16/2013  Iteration Planning  Development  Retrospective Build 5 65/16/1325/29/13  Iteration Planning  Development  Retrospective Build 6 75/30/201326/10/13  Iteration Planning  Development  Retrospective Final build

Project Status (cont.) Winter OMSE 555/556 Software Engineering Practicum Software Process Step DeliverablesStatus Project PlanningProject 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 Management Winter OMSE 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. 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 Management Winter OMSE 555/556 Software Engineering Practicum Identified Risks  Time Constraint  Loss of Work  Loss of Communication  Loss of Personnel Correct Risks Identified?  Yes and Maybe  Communication outages have occurred infrequently, but have been handled.  More time needed.

Problems/Insights Winter OMSE 555/556 Software Engineering Practicum Redmine is missing some key functionality  Parent/children tasks  Notifications (Hit or miss) Diff/Merge issues with word (.docx) files. Intermittent audio issues with Collaborate. IIS Servers unavailable through CAT.

Questions? Winter OMSE 555/556 Software Engineering Practicum