80 likes | 261 Views
CS 383. Team Lavender Surface Presentation. Alex Cochrane, Daniel Green, David Miller, Colby Rush. Presentation Outline. Initial project assignment and Customer Agreement Demonstration of product System Hierarchy Documentation Lessons learned Sustaining Engineering.
E N D
CS 383 Team LavenderSurface Presentation Alex Cochrane, Daniel Green, David Miller, Colby Rush
Presentation Outline • Initial project assignment and Customer Agreement • Demonstration of product • System Hierarchy • Documentation • Lessons learned • Sustaining Engineering
Initial Project Assignment • Title: COE Student Advisor/Tracker • Customer: Ms. Maria Pregitzer, College of Engineering Dean's Office • Facilitator: Dr. Clint Jeffery, CS Dept. • Intent: Develop an application for the Microsoft Surface, to help with college advising and/or recruiting • Users: UI CoE general advising student services staff working with undeclared pre-engineering lower-division students, and/or general public and prospective students who are visiting the college. • Platform/Location: MS Surface, COE Think Tank • Language: MS Surface API's run in "Surface Mode" restricted to .Net "managed" virtual machine code; C# seems to be the only language MS supports on it.
System Hierarchy • Broken down into discreet components • StudentInformationCenter.exe • The surface exe, contains top level application behavior and presentation • Sic.ControlLibrary.dll • The visual controls used to present content and their associated services. • Sic.Data.dll • The data model representation and serialization tools.
Documentation Located at…………………………………..http://www2.cs.uidaho.edu/~cs383f/main.html
Lessons Learned • Document processing – XPS to .png file format • Communication between customer and team • Source Code control (TortoiseHG) • Application design patterns (MvvM) • Team Management • Documentation management • Dependency injection/resolution (IoC)
Sustaining Engineering • Refactor for loose coupling (interfaces and abstracts) • Break down service into separate single responsibilities (separation of concerns) • Refactor presentation markup for maintainability by defining resources • Continued feature development to support product life cycle (editor, AV media, etc.)