|
|
Project Instructions
Team allocation
Students will be randomly allocated to groups, which will have around 6 people.
The mapping of students to groups will be published by 8:30am on Tuesday of
week 1.
Once you know what group you are in, get together with the other members of
your group and make a list of your preferred projects in descending order
of preference.
One person from the group must then email the list to admin3200@csse.uwa.edu.au
by 4pm on Thursday of Week 1.
Some projects are very popular, so your list should name at least three projects -
preferably more - in case your more prefered projects are already taken.
If you wish, you can add some text with any of your project choices outlining reasons
why your group should have that project, e.g.
members of the group may have special expertise or previous experience
in the topic area.
For example, in 2008 one group which was very keen on a medical tutoring system
project included sometime med. students.
Project Selection
A project will be assigned to each team. There is no guarantee that
choices can be met, but every effort will be made to maximise overall satistifaction
based on the lists you supply, together with any additional text.
Project allocations will be announced by Friday 1pm. Once assigned, one group
can swap a project with another group if they are
willing. Please inform me of the swap. Once assigned you should contact the
client to introduce yourselves, 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 4, so time is of the essence.
The project homepage contains
full details of the deliverabless and what each is worth.
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 and D.
- Fill out the weekly TimeSheet, updating your team's copy of
the spreadsheet each week. Email the TimeSheet to admin3200@csse.uwa.edu.au
as an xls file (NOT .xlsx) 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.
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, 20% 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, detailed usage cases and/or screen
mockups (as appropriate).
- Deliverable C, 40% overall mark, comprising full
implementation, code, build, testing by the Client, analysis of time
taken in hours versus predictions. Appropriate use of CVS/Subversion and Trac
(replacing Bugzilla) and
other software engineering methodologies will be assessed here.
- Deliverable D, 10% overall mark, consists of a
presentation of your project post mortem.
Mentors
Mentoring is being performed by members of staff from Thales, IBM and other
industrial partners. Mentors
provide
general advice and feedback on process and team issues.
The project schedule lists the weeks in which mentoring weeks should occur.
It is up to each group to contact your mentor in good time to arrange
the meeting.
These meetings are mandatory (and very helpful).
Marks will be deducted for each meeting that you miss.
The decision is binary: either you are there - 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 of the major components (essay and project deliverables) 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.
|
