CS 562
Software Engineering II
Group Project 1 (100 points)
Due:  February 5, 2014 (Due dates for milestones are denoted below and will be strictly enforced)

Project teams have been assigned in class.  Students have been assigned one of three teams.  Unless there is a major issue with a project (e.g. legal, financial, etc.), groups will not be allowed to change the content of their project.  In the case that such an issue arises, groups must come to a consensus on a new or updated topic and clear it with the instructor.

General Guidelines

All teams are expected to at minimum complete the worksheets linked on this webpage.  Completion of these worksheets does not guarantee an A nor will minimal completion of a project.  Note that you may submit one copy of each worksheet per team.

Team members are expected to exhibit professionalism while working on group projects.  This includes but is not limited to completing an equal share of the work on the project, communicating with other team members, ensuring project related emails are cc'ed to other team members, attending team meetings on time, etc.  The instructor reserves the right (but is not obligated) to decrease an individual's grade on this project by half of a letter grade (5 points) for each instance failing to adhere to these standards.

Be sure to determine expertise in each of the following areas
    Documentation
    Design (including UML and MS Visio)
    Databases (ER Diagrams)
    UI (Paper Prototypes and Static Webpages)
    Project Management (Estimated cost, Issues, Bug Tracking, Burn Down Charts, etc.)
    Coding

If you have deficiencies in any of these areas, it is your responsibility to learn the material and contact me about any issues you have with that material.

Presentation requirements

Presentations should last 12 minutes with 3 minutes for questions and answers.
All team members must participate in the presentation, but the length of said participation is at the team's discretion.
Dress requirements are informal but neat.
Discuss your project, demonstrate features, discuss what you plan to do next, and describe any problems you are having.
Be prepared to answer technical questions about your project and to describe any design documents (e.g. ER or UML diagrams)
Take notes during the question and answer period.
Every team member must participate in the project.
If possible, test your equipment with the projector in the classroom at least one day in advance of the presentation.

Milestone 1 (Due: January 24, 2014) 10 points

Complete the first worksheet and update your design to fix any issues denoted last semester, include initial ER diagrams for any data that will be stored in a database, denote any questions or concerns the team has about the project, and include any code/UI design you have completed so far (even items that do not yet compile).  Each team member must complete a project activity log or similar document and the entire team must complete a progress report (one paragraph summation of work completed).  Submit these items to the eCompanion Dropbox for Project 1, Milestone 1.

Milestone 2 (Due: January 31, 2014) 10 points

Complete the second worksheet.  This includes but is not limited to design review, completion of all paper prototypes, a data dictionary, a revised ER diagram, updated use cases, and a team meeting with the course instructor regarding your project.  Submit these items to the eCompanion Dropbox for Project 1, Milestone 2.

Milestone 3 (Due: February 5, 2014) 80 points

Complete an in-class presentation over your project.  All team members must participate in the presentation.  Your presentation must include an introduction and list of basic requirements/goals for your project, description of important paper prototypes/screenshots, description of UML/ER diagrams, description of any other special tools used, any additional goals, etc.  Complete any remaining design documentation that was not finished by the end of Milestone 2.  This includes but is not limited to requirements and specification documents, domain analysis, paper prototypes/screenshots, updated use cases, updated UML diagrams, updated ER diagrams, data dictionary, and information about any additional modules you want to add to your project.  Submit all design documentation, including your presentation, to the eCompanion Dropbox for Project 1, Milestone 3.