1. Presented By:

2.  Problem  Solution  Architecture ◦ What ◦ Why  Challenges  Status  Demo  Questions

3.  Current Assembly of Software Engineering Notes (SEN) Newsletter ◦ Completed Manually  Reaction to Events  Notification  Approval  Assembly & Generation of Newsletter ◦ E-mail Based ◦ Time-Consuming ◦ Hard to keep track of submissions and contacts ◦ No Accountability

4.  Central Location For: ◦ Documents ◦ Approvals ◦ Notifications ◦ Contacts ◦ Generation  Newsletter Generated Automatically  Administrative Functionality  Event Logging for Security and Accountability

5. Solves: Separation of Concerns

6. Solves: Event Driven

7. Solves: Extensibility

8.  Patterns ◦ Model View Controller ◦ Event-Driven System ◦ Pipe & Filter

9.  Word XML Specification ◦ Poorly Documented ◦ Convoluted ◦ Does not conform to standards  OpenOffice UNO Development ◦ High learning curve ◦ Limited Examples  Managing Change Requests

10.  Content Management Complete  Newsletter Generation ◦ Front Matter Complete ◦ Back Matter Complete ◦ Addition of Columns & TOC still Manual  Notifications Complete  Event Logging Complete  Administrative Functionality Complete