Team SHARPFebruary 10, 2009

Sponsor◦Dr. Will Tracz

Faculty Coach◦Robert Kuehl

Members◦Samuel Goshen◦Leo Torbochkin◦Dan Edenhofer◦Dominic Holt◦Nicholas Sabocheck

Overview Requirements Design

◦Process◦Current State

Implementation◦Technologies◦Current State

Project Risks Project Process Project Schedule & Estimation Metrics Reflection Future Endeavors

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.

Process◦ Investigation of Historical Artifacts◦ Communication with Project Stakeholders◦ Internal Team Review

Stability & Volatility◦ Ambiguous Initial Requirements◦ Feature Creep

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.

Incremental Approach◦ Phase I

Construct Essential Infrastructure◦ Phase II

Newsletter Skeleton Metadata Extraction

◦ Phase III Complete Construction of Newsletter Notification Scheduling

Evolvability

equals(Object o)equals(User u)

-username-password-affiliation-isAdmin

User

create()get()update()delete()

SQLWizard

establishConnection()closeConnection()

DBConnection

#processRequest()

LoginServlet

#processRequest()

CreateUserServlet

commitToDatabase()requestFromDatabase()

DocumentManager

#processRequest()

DocumentServletupdateUser()createUser()authenticate()resetUserPwd()getUser()deleteUser()

UserManager

#processRequest()

NotificationServlet

parseDocument()

-submitter-filename-filepath-docID

Document

parseDocument()

WordDocument

parseDocument()

PDFDocument

parseDocument()

LatexDocument

create()get()update()delete()

Abstract Manager

sendMail()

Mailer

#processRequest()

ReviewServlet

accept()reject()

Decider

#processRequest()

PasswordResetServlet

parseDocument()

TextDocument

#procesRequest()

UpdateUserServlet

getTitles()getAuthors()

-HashMap<String Title, List<String> Authors>

Extractor

buildTOP()buildTOA()

-title : String-author : String-paperID : String

TableGenerator

aggregateTables()decorateWordFile()createWordFile()

-TOP : String-TOA : String

IssueCreator

#processRequest()

GenerationServlet

Technologies◦ J2EE◦ MySQL◦ Tomcat◦ TinyMCE

Current State◦ Phase I Completion

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

Iterative & Incremental◦ Responsive to Change◦ Deliver Working Increments of Software◦ Increase Customer Collaboration◦ Three Phases

Requirements Architecture & Design Implementation Testing

12/1/2008 5/15/2009

1/1/2009 2/1/2009 3/1/2009 4/1/2009 5/1/2009

Project Timeline

3/28/2009Release Phase 2

1/11/2009Preview Phase1

12/1/2008 - 2/6/2009Phase 1

3/27/2009 - 5/15/2009Phase 3

2/6/2009 - 3/27/2009Phase 2

5/1/2009Release Phase 3

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.

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

Phase II◦ Requirements◦ Implementation◦ Testing

Phase III◦ Requirements ◦ Architecture◦ Implementation◦ Testing