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

Project teams have been assigned in class.  There are two groups of five and there is one group of four.  Students have been assigned one of three projects.  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 work outlined on this webpage.  Completion of this work does not guarantee an A nor will minimal completion of a project.  Note that you may submit one copy of each milestone's requirements per team unless otherwise instructed.

Team members are expected to exhibit professionalism while working on group projects.  This includes but is not limited to 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 if additional expertise is needed in each of the following areas
    Documentation
    Design (including UML and MS Visio)
    Databases (MySQL, SQLite, etc.)
    UI (Static and Dynamic Webpages, Java Swing, etc.)
    Project Management (Estimated cost, Issues, Bug Tracking, Burn Down Charts, Extreme Programming, Agile Scrum, etc.)
    Various project related APIs (J2EE, OpenGL, Java Graphics, Android, iOS, etc.)

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

An in class presentation of an electronic poster will be required on the project due date.
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, working software, or testing documents.
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 0 (Due: February 7, 2014) 5 points

Submit a poster abstract to the NWMSU Celebration of Quality competition.   You must also submit proof of your submission, including your abstract, copies of emails, etc., to the Dropbox for Project 2, Milestone 0.

Milestone 1 (Due: February 14, 2014, Valentine's Day) 10 points

Begin work on a segment of your project, estimate the time for this and future segments, determine brief use cases for that portion of the project, create test cases for this segment, unit test the segment using stubs if necessary, keep a log of issues faced during this segment, update your design documents if necessary, denote any questions or concerns the team has about the project, and include any code you have completed so far (even items that do not yet compile).  More complete documentation of these requirements is included in worksheet 3.  The entire team must complete a progress report (one paragraph summation of work completed).  You are exempt from project activity logs for this milestone.  Submit these items to the eCompanion Dropbox for Project 2, Milestone 1.

Milestone 2 (Due: February 21, 2014) 10 points

Continue work on another segment of your project, estimate the time for this and future segments, determine brief use cases for that portion of the project, create test cases for this segment, unit test the segment using stubs if necessary, keep a log of issues faced during this segment, update your design documents if necessary, denote any questions or concerns the team has about the project, and include any code you have completed so far (even items that do not yet compile).  Utilize worksheet 3 as a guide to continue work on this portion of the project.  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 2, Milestone 2.

Milestone 3 (Due: March 3, 2014) 75 points

Complete an in class presentation of an electronic poster over your project.  All team members must participate in the presentation.  Your poster presentation must include an introduction and list of basic requirements/goals for your project, a brief demonstration of the working aspects of your project, a description of updates to your design, and plans for continued work on your project.  Be sure to update documentation that was not finished by the end of Milestone 2.  This may include but is not limited to requirements and specification documents, domain analysis, updated use cases, updated UML diagrams, updated ER diagrams, data dictionary, unresolved issues, and information about any additional modules you want to add to your project.  Submit your code, documentation, and electronic poster, to the eCompanion Dropbox for Project 2, Milestone 3.