Project Organization - CSC 4700 Software Engineering
Spring 2006, Dr. Joyce
NOTE: Also see the
Writing Requirements page for information
about the content and format of some project documentation.
- Class 1: Project related questions included in course questionnaire
- Class 3: Teams identified
- Class 4: Open team meeting time
- Class 5: Proposals due - At the beginning of class each team
should hand in a Proposal Report. This report should include
Be ready to describe your proposals to the class (no
- The team name
- The team members' names
- Three project proposals. Each should be 100 to 500 words.
Rank them in order of preference.
- A brief description of how each team member contributed to the
proposal identification, documentation, and/or presentation.
- Class 9: By this class your group should have a "live"
Project web site. The site should
- identify the name of your group
- include a list of group members
- provide a group email link that allows me to mail the entire
group with the click of a button
- your project proposal
- include a section of links to class deliverables
- could include a short "plan" describing roles of group members,
communication plans, a projected schedule, and so on
- an up-to-date "diary" where you describe what the group
has done and upcoming plans
- an up-to-date time tracker where you describe who has done
what and for how long, in an organized fashion
- a set of questions and answers about your project; these,
along with your project proposal, will form the basis
for a more formal requirements specification; I may
provide some questions, either verbally or through e-mail;
you should have at least 20 Q/As
- eventually will include requirements documents, user-interface
design, and possible a software design
- End of Semester Presentation: Each team will give a
25 minute presentation on Monday, May 8th. Most of the time
should be spent instructing the class on your research topic.
Teach us - make it interesting.
You can/should also remind us what your project was about, briefly
show off your web site, tell us how far you got with the
project, and your future plans for it.
- Team Binders: At the presentation session each group must
hand in a project binder. This binder should provide a well
organized history of the project. It could include the following
(* = required):
- a Table of Contents
- an "intro"/"overview"
- * the diary/blog
- * the time tracker
- * both Requirements versions
- a sampling of your Project web site
- slides from your presentations
- * a short (4-10 page) research report
- relevant documentation of communication with the customer
and/or meetings with the "manager"
- suggestions of how to continue the project
- * a Team Post Mortem with
- what went well
- what you would do differently
- what you learned, as a team