CS 562
Software Engineering II
Group Project 4 (100 points)
Due: April 25, 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 the three following 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 work together. The instructor
reserves the right to directly assign work to individuals that are
not
appropriately contributing to their respective teams or not
working
together.
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 expertise 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, 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 will be required on the project due
date.
Presentations should last 12 minutes with 3 minutes for questions
and
answers.
Presentations must include both powerpoint equivalent slides and a
project demonstration
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 1 (Due: April 18, 2014) 10 points
Continue and complete all coding, testing, and documentation for
your
project.
Be sure to complete your existing work before moving on to new segments of your project. It is highly recommended that you start documenting your progress now. Refer to worksheet 5 and complete any necessary for information on the detailed requirements for this iteration. Each team must still complete a progress report (one paragraph summation of work completed). For this milestone, it is recommended but not required that your team keep a burndown chart. Teams should also complete their usability studies by the due date above. Submit these items including those listed on the worksheet to the eCompanion Dropbox for Project 4, Milestone 1.
Milestone 2 (Due: April 25, 2014) 90 points
Complete all coding, testing, usability studies, and documentation
for your
project.
Complete your existing work and clean up any issues you have or haven't logged. It is expected that your code will be thoroughly documented, you will have an installation guide (yes, this includes how to install your server), and a user manual. You may create a video using screen capture software to describe how to use your product. You must complete an in class PowerPoint or similar presentation as described above, over your project. Refer back to worksheet 5 and complete any items from that worksheet that are currently incomplete. The entire team must complete a progress report (one paragraph summation of work completed). For this milestone, you must document any remaining issues in your project and explain why they are incomplete. You must also submit an assessment of your teammates as provided at the following link. Submit these items including those listed on the worksheet to the eCompanion Dropbox for Project 4, Milestone 2.