|
|
Project Instructions
Team allocation
Each team will have 6 students. Students are free to choose their own
team, subject to the following.
- Teams are optionally self selected and will be organized in
Lecture 1. One person from each
self selected team must mail the details of the team members to
admin3200@csse.uwa.edu.au, DEADLINE 9am Tuesday of week 1. The mail
should state the student number, UWA email name and full name of each
person in the group, one per line, separated by commas.
Only complete teams of 6 people may be self selected.
- Those not in self selected teams will be put into Allocated
Teams by me and the list will be published by 8:30am Wednesday of
week 1.
- Once the teams are allocated, all teams may email
admin3200@csse.uwa.edu.au their three most preferred projects in
order, DEADLINE 4pm Thursday of week 1. (Some projects are very
popular, so a list of three
covering a wide range is helpful.)
Project Selection
Projects will be assigned to each team. There is no guarantee that
choices can be met, but priority will go to the Allocated Teams.
Project allocations will be announced by Friday 1pm. Once assigned, you
can opt to swap a project with another team if they are
willing. Please inform me of the swap. Once assigned you can visit the
client to introduce yourselves and set up times for meetings, etc.
Doing the Project
You should commence the project as soon as the project
is allocated to you. Your first Deliverable, A, is due in
week 3, so time is of the essence. The unit homepage will contain
full details of the deliverables, updated as the semester progresses.
Here are some issues you will need to address.
- The most difficult hurdle will be scheduling meetings
between yourselves. Fix a regular weekly meeting time and place early
and hand in a meeting schedule with Deliverable A.
- Keep minutes of each scheduled meeting - they will be
marked.
- Make your first meeting a warm up session. Suggested goals
are:
- Get to know each other
- Establish a decision-making process
- Set operating guidelines: attendance, timeliness, time
and place, basic courtesies, breaks, interruptions, guidelines for
unexpected happenings and various behaviours
- Consider allocation of duties, the team should be
organized around the roles of developers, testers and program manager.
You may all attend the client meetings or you may elect that the
program manager and one or two others attend.
- Expect to learn new things, you are responsible for your
learning. Allocate time for learning. In particular those who have not
taken SED, CITS2220, should allocate time to read up on software
process and testing.
- Work out a plan and keep revising it
- Learn to motivate each other, and develop strategies for
developing appropriate trust in each other's ability, or lack of it, to
meet deadlines.
- Consult your Client regularly - keeping this person
informed is crucial. Expect the Client's requirements to change. You
may decide only to have one or two people interacting with the Client
rather than the whole team.
- Keep a record of the hours spent on the project each week,
by each person and what they worked on. This will be required for
Deliverables C, D and the individual summary report.
- Fill out the weekly TimeSheet, updating your team's copy of
the spreadsheet each week. Submit
the TimeSheet as an xls file via cssubmit by 5pm Friday of
weeks 2-11.
The Deliverables
A brief outline of the deliverables follows. This will be expanded on
the project page.
- Deliverable A, 5% overall mark, comprising a list of
requirements in rank order of value/estimate ratio plus screen mockups.
A schedule of meeting date/times and places is required. (Purpose is to
act as an ice breaker and to get you thinking about the specification.)
- Deliverable B, 18% overall mark, comprising a project plan,
more
detailed requirements, some design docs such as class models, a set
of acceptance tests, revised ratios and rankings.
- Deliverable C, 29% overall mark, comprising full
implementation, code, build, testing, meeting minutes, analysis of time
taken in hours. Use of CVS/Subversion and Trac (replacing Bugzilla) will be graded here.
- Deliverable D, 10% overall mark, consisting of a
presentation of
your project post mortem.
Individual Summary Report: 10% overall mark - this is a report produced
by every student which describes their personal experience of the
project. It will include a timesheet of all activities undertaken in
the project, description and analysis of the project, meetings,
process, etc. Finally, it will include details
of the actual work that the student contributed to the project.
Mentors
Mentoring is being performed by members of staff from Thales and perhaps other
industrial partners. Mentors will
provide
general advice and feedback on process and team issues.
The project schedule lists the weeks in which mentoring weeks should occur.
A specific timetable of meetings will be provided nearer the day.
These meetings are mandatory and discussion of the meetings
may be appropriate in the individual summary report.
There will be a mark of 1% for each meeting that you attend
precisely on time, maximum 3 in total. Marks are binary: either you are
on time or you are not.
Computing Resources and Labs
Normally the Department's Linux or Windows systems
will be used in the labs on the third floor. There are no scheduled
labs or lab sheets, rather machines may be used on a first come first
served basis outside booked periods.
A server, cits3200.csse.uwa.edu.au, is available to those teams that require
servlets, php and other server-side facilities. Occasionally some
projects may require other resources that belong to the Client
Access to Trac and Subversion will be on the projects server. You
are strongly urged to
use both for stages B, C and D of the project. Try using Trac in
Deliverable A to record
Client reactions to your RAD.
Submissions
All submissions will be done via cssubmit and via hard copy to the CSSE
Administrator in 1.31A prior to the deadline. If you have multiple
files, please submit as a zip or tar.gz file.
Documents will be accepted preferrably in pdf.
Ensure documents, folders, archives etc have the Team name clearly
visible on them, perhaps in a header or footer.
|
