1. Team SHARP February 10, 2009

2.  Sponsor ◦ Dr. Will Tracz  Faculty Coach ◦ Robert Kuehl  Members ◦ Samuel Goshen ◦ Leo Torbochkin ◦ Dan Edenhofer ◦ Dominic Holt ◦ Nicholas Sabocheck

3.  Overview  Requirements  Design ◦ Process ◦ Current State  Implementation ◦ Technologies ◦ Current State  Project Risks  Project Process  Project Schedule & Estimation  Metrics  Reflection  Future Endeavors

4. ACM SIGSOFT publishes a bi-monthly hybrid Newsletter called Software Engineering Notes (SEN). The Newsletter is manually assembled by the editor, who receives various contributions from established column editors and other contributors who submit documents in various forms and formats as part of a document workflow. The system has two main components: submission and composition. The product will support automatic composition of the various tables in the newsletter. The application will allow users of the system to submit various content. This content will be accompanied by metadata, which will be necessary to automate the construction of the newsletter. Once composed, these tables will be combined into a printable document for construction of the newsletter.

5.  Process ◦ Investigation of Historical Artifacts ◦ Communication with Project Stakeholders ◦ Internal Team Review  Stability & Volatility ◦ Ambiguous Initial Requirements ◦ Feature Creep

6.  User Registration – This feature will allow a user to register a unique identity with the system. This also encompasses role based access based on regular user, editor, or administrator status.  Administration- This feature will allow users whose role is administrator to modify, add, or remove information related to users and the system.  Document Submission- This feature will allow users to submit content to the system and edit any necessary meta-data associated with that content.  Document Review- This feature will allow a user whose role is editor to view all submitted material and review it. The editor will then be able to accept or reject the submissions.  Document Assembly- This feature will allow an editor to save time in composing an issue of “Software Engineering Notes”. It will provide tools to allow the editor to automatically generate tables which are normally more tedious to craft by hand.

7.  Incremental Approach ◦ Phase I  Construct Essential Infrastructure ◦ Phase II  Newsletter Skeleton  Metadata Extraction ◦ Phase III  Complete Construction of Newsletter  Notification Scheduling  Evolvability

12.  Technologies ◦ J2EE ◦ MySQL ◦ Tomcat ◦ TinyMCE  Current State ◦ Phase I Completion

13.  Optimistic schedules  Poorly or vaguely defined requirements  Feature Creep  Gold-plating of features during development  Availability of Sponsor  Team member unexpected unavailability  Team members do not work together efficiently Blue Highlight: Risk Occurred

14.  Iterative & Incremental ◦ Responsive to Change ◦ Deliver Working Increments of Software ◦ Increase Customer Collaboration ◦ Three Phases  Requirements  Architecture & Design  Implementation  Testing

16.  Two Progress Metrics ◦ Source Lines of Content (includes code, scripts, text)  Keep track of progress based on content.  Shows quantitative progress for the team & each team member. ◦ Slippage Chart  Keep track of progress based on meeting schedule commitments & milestones.  Shows how far ahead or behind we are on the project as a team.

21.  Consider the Project Plan as a contract between team and sponsor.  Make sure all deliverables are agreed upon beforehand, including level of detail. ◦ Software Requirements Specification ◦ Architecture ◦ User Guide ◦ Test Plan ◦ Meeting Minutes ◦ Code

22.  Phase II ◦ Requirements ◦ Implementation ◦ Testing  Phase III ◦ Requirements ◦ Architecture ◦ Implementation ◦ Testing