1 / 11

OMSE-555/556 Software Engineering Practicum I & II Mid-Term I Status Winter 2013

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.

gilead
Download Presentation

OMSE-555/556 Software Engineering Practicum I & II Mid-Term I Status Winter 2013

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

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

  2. Project Charter 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. OMSE 555/556 Software Engineering Practicum

  3. Mission Statement 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.” OMSE 555/556 Software Engineering Practicum

  4. Process Methodology OMSE 555/556 Software Engineering Practicum

  5. Technical Decisions Made… • 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) OMSE 555/556 Software Engineering Practicum

  6. Project Status OMSE 555/556 Software Engineering Practicum

  7. Project Status (cont.) OMSE 555/556 Software Engineering Practicum

  8. Project Management • 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. OMSE 555/556 Software Engineering Practicum

  9. Risk Management • 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. OMSE 555/556 Software Engineering Practicum Winter 2013 9

  10. Problems/Insights • 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. OMSE 555/556 Software Engineering Practicum

  11. Questions? OMSE 555/556 Software Engineering Practicum

More Related