DRAFT

Session 1 (AUTUMN)

Total Marks: 20 marks

Project Diary:.

minutes of meetings, records of milestones, client interactions, work done, etc.

Week 6 and 12 of Session I.

The document should be submitted to the supervisor. Refer to point (e) for further information.

Preliminary Project Documents.

Preliminary User Manual and Preliminary Technical Design Manual

Week 11 of Session I.

The document should be submitted to the supervisor. Refer to point (f) and (i) for further information.

Project Website.

With online preliminary manuals in HTML or PDF.

Week 13 of Session I.

Students should advise the supervisor of the page. Refer to point (g) for further information.

Session 2 (SPRING)

Total Marks: 80

Project Diary.

Minutes of meetings, records of milestone, etc.

Week 6 and 12 of Session II.

The document should be submitted to the supervisor. Refer to point (e) for further information.

Prototype and Demonstration.

Must demonstrate to the supervisor.

Week 8 of Session II.

Groups are to demonstrate to the project supervisor the initial version of their project. Refer to point (h) for further information.

Final Product.

Code and Documentation to be submitted to both assessor and supervisor.

20 marks for Code

25 marks for Documentation

Week 12 of Session II.

Students should provide both the supervisor and assessor with a hard copy of the code and project documentation including diaries. Refer to point (i) for further information.

Project Web Site.

Week 12 of Session II.

The supervisor should be advised of the location of the final website. Refer to point (g) for further information.

Trade Show and Assessor/ Supervisor Discussions.

Week 13 of Session II.

Refer to points (j) and (k) for further information.

Notes on Assessment

Weightings shown in brackets are subject to variation and intended mainly as a guide for assessing the final result. Each student’s final result will be evaluated on his or her individual efforts and contributions.

a) Groups seeking an extension past the due date for the submission of required assessment items should consult the Guide for Student’s document (see link below). This also specifies the penalties imposed for the late submission of assessment items, copying and plagiarism. Further information can be found at: http://www.uow.edu.au/student/calendar/rules/plagiarism.html

b) Failure to complete assessable tasks may result in a FAIL grade being recorded.

c) All assessable documents must be submitted according to the format specified in lectures.

d) Feedback on submitted assessable items will be provided through your supervisor in meetings.

e) Project diaries are due in Week 6 and 12 of Sessions 1 and 2. The diaries should contain minutes from all meetings along with a description of activities performed by member. It is recommended that students use a weblog (blog) to store diaries. Diaries should be submitted to the supervisor in hardcopy form on the due dates.

f) Preliminary project documentation is due Week 11 of Session 1. The documentation should consist of a technical manual containing architectural and design aspects of the project. In addition to this a preliminary user manual should be provided. The user manual should outline what the functionality of the software is and how a user may interact with it. It should be noted that this documentation is to be submitted to the supervisor in hardcopy form. A softcopy should be placed on your website.

g) Each project group will be allocated a website by the school. If a group requires additional resources e.g. storage they should advise the 321 Project coordinators. Students should provide their supervisor with a link to a functional version of the website by Week 13 of Session 1 (if not earlier). This site should be maintained for the duration of the project. Information regarding projects as a collective can be found at http://www.itacs.uow.edu.au/tradeshow.

h) Students should demonstrate an initial version of their software by Week 8 of Session 2 to the supervisor. The supervisor should provide feedback to the students on where things should be changed/ improved. A similar meeting is held in Week 13 of Session 1 (naturally there would be no demonstration of software at that stage) – this meeting only occurs with your supervisor.

i) Final project documentation is due week 12 of session 2 . Final documentation should be accompanied with the programs code and binaries. All documentation should be submitted in hardcopy form to both the supervisor and assessor. A copy of all documentation should be made available on the project site in PDF or Postscript formats. ALL group members must contribute a reasonable amount determined by the supervisor to the implementation i.e. code of the project and documentation. Failure to do so may result in a FAIL grade being assigned to students who do not comply.

j) All groups and members are expected to participate in the tradeshow. The date for the tradeshow will be announced shortly. Your participation in the tradeshow and discussion with supervisor and assessor will be assessed. It is expected that groups coordinate with their supervisor and assessor to demonstrate their final product during the tradeshow (an alternative time may be arranged if necessary).

k) After the project each group member will be required to review other group members performance. This information is used to be supervisor and assessor to get an idea of individual participation and contribution towards the project.

l) The above points should be read in conjunction with the sections below.

Project Activities and Milestones

You should plan to spend about 12 hours per week during each session working on the project. Reports from previous years indicate that this is in fact about the average time committed by students. However, all too often the time distribution is badly skewed with 6 hours per week in session 1 and 18 hours per week in session 2 being the apparent norm. To avoid this it is highly recommended the following schedule be adhered to.

Time	Activity or Milestone
Session 1,Week 1	Start group formation (groups of 4-6) & Select Topic
Week 2	Finalise groups and topics
Week 3	Commence design, prototyping and web site
Week 6	Submission of project diary.
Week 11	Submit preliminary technical manual and user manual. Look at finalizing aspects of the systems design.
Week 12	Start coding the final product, submit diary.
Week 13	Demo project web site with product description and documentation to supervisor. Once this is done you can finalise your design of the system.
Session 2, Week 6	Submission of project diary.
Week 8	Demonstrate first round working system.
Week 11	Refine product and submit final documentation.
Week 12	Finalise the project web site, submit diary and advise supervisor.
Week 13	Trade Show.

It should be noted that not all assessment tasks are defined in the above schedule. The schedule is just to give you a rough idea what you should be doing when.

Meetings & Resources

The supervisor's job is mainly to describe the product at a high level, resolve design issues and assess the work. The supervisor can be asked for advice; however the supervisor should not be expected to do any substantial part of the design or implementation. Each group should run its own meetings. It is advised that groups meet weekly. Minutes of each meeting should be recorded. As suggested previously a Weblog may be used to hold minutes of meetings with supervisors and other members. The Weblog should be accessible from the projects site.

The needs of different groups and supervisors may vary. So if any special needs are identified, which require special software or hardware, a request must be made to one of the subject coordinators to determine if the request can be fulfilled. The subject coordinators will liaise with groups on this matter during the first semester (by the end of week 5 with infrastructure/ software arriving a few weeks later)

Group Project Web Sites

Each group will be provided with a website for portraying information on their project. The project web site need not be sophisticated. However, it should promote a “corporate” image and product to its intended customers, including:

a) home page with project name, group members & their tasks, supervisor, assessor and date last modified

b) product description page(s)

c) documentation page (including user manual and technical manual links)

d) an MPEG video demonstration of the project

e) contact us page, FAQ page, etc

The MPEG video should basically provide a demonstration of your product and its functionality. It is common practice to integrate a PowerPoint Presentation into the video. Further information on how to create such a video will be provided during the semester. Some project groups may opt to put their project diaries up on the site (a weblog so to speak).

Documentation

The precise format and content of the final project documentation may vary from project to project. Consequently, the requirements of documentation should be discussed in detail with your supervisor. The final submitted project must include the following items (at least) to achieve a pass grade or better:

a) a user manual

b) a technical report (including minutes of meetings)

c) the source code

d) the web site

These documents are to be submitted to the supervisor in hardcopy and on CD ROM. An additional copy should be provided to the assessor where appropriate. Where the source code or web site is considered too large to be printed, these items may be submitted on CD only. A copy of the CD must also be submitted to the coordinator for archives. Students should also advise the supervisor and assessor as to the URL of the website.

Tradeshow & Final Assessment

The product must be demonstrated to both the supervisor and assessor either at the tradeshow or at a suitable time. In Weeks 11/12 of session 2, each group will be given a roster to pack up their computer in the project lab (exceptions may apply). These machines will then be stored and next used at the tradeshow. It is the responsibility of each group to install and configure the machine appropriately (the school will provide a basic machine with an operating system and tools). It is each group’s responsibility to backup their work, in the case of emergency, (the project lab machines are not in the backup cycle).

All software that resides on the project lab’s machines must be deleted after the tradeshow.

Prior to the tradeshow each group will be requested to provide a list of resources needed for the day. Each group will typically receive a desk with two GPO’s (General Power Outlets). The school, upon the advice of students, will provide computers and network connectivity. Students may bring in there own hardware for the tradeshow, but the hardware must be approved the technical staff before the tradeshow. Details will be provided via SOLS message when necessary.

Each group should have at least one person at the assigned booth during the event. Students should arrive prior to the tradeshow to set up their booth. After the tradeshow students will need to pack up any resources provided by the school. Students MUST have a poster for their project on display, where the poster must be displayed on the day of the tradeshow. Students will be assessed for their efforts on the day of the tradeshow. As expressed earlier in this document, all students must participate in the tradeshow.

Students will be expected to be present during the Trade Show and to remain in the vicinity of their booth to answer questions about their project.. In addition to this, groups will be assigned a small budget for the purpose of the tradeshow. It is a requirement that all project groups have an A2 sized poster advertising their product at the tradeshow. A date will be formalized in the coming months for submission of such a poster. The 321 coordinators will advise students as to any organizational changes with the 321 Tradeshow if need be.

In addition to this a number of project groups will be selected by the 321 Coordinators to provide a seminar during the tradeshow. This will be done at random with the groups being advised early in the semester. Just like last year there will be an award for the best project.

Prior to the tradeshow all projects groups will be required to submit 5 - 8 power point slides detailing the project and product. These will be displayed on the day.

Project Support & Student Contact

The following staff members are available for assistance:

Name	Room Number	Support
David Wilson	3.228	Unix, C,
Yuan Tian	3.2228	Unix, C
Michael Milway	3.228	PC related
Kathy Lyon	3.228A Monday-Friday 10.30 - 14.30	Tradeshow and other administrative matters.

Questions about project design should be referred to the project supervisor. Problems with team administration should be discussed first with the project supervisor. If the problem cannot be resolved at this level, it should be referred to the subject coordinator. Appointments to see the subject coordinators outside consultation times can be made via email.

Project Team Rules

The following rules apply to team members:

a) Team members will co-operate to achieve a common goal. Often, each team member will work on a different sub-problem, so that the success of the team as a whole will depend on the individual work of all of its members. Sometimes several team members will independently solve a crucially important problem, so that a "best" or "correct" solution can be established by comparison.

b) Each team will elect a leader for the project or each phase of it. The project leader will be responsible for the co-ordination of the design, programming and background reading tasks performed by members of the group and communicating instructions from the supervisor to appropriate group members.

c) Each team member will write a significant portion of the code. The code must include clear documentation about who wrote it and who modified it. This will influence your coding assessment component.

d) The team leader is to ensure that team members contribute equally to the project.

e) Any problems must be discussed with the project supervisor as soon as they arise, NOT at a later stage when the problem cannot be resolved.

f) All project team members must attend the tradeshow and project demonstrations to assessor and supervisor.

Plagiarism

When you submit an assessment task, you are declaring the following:

1. It is your own work and you did not collaborate with or copy from others.

2. You have read and understand your responsibilities under the University of Wollongong's policy on plagiarism.

3. You have not plagiarised from published work (including the internet). Where you have used the work from others, you have referenced it in the text and provided a reference list at the end ot the assignment.

4. Plagiarism will not be tolerated.

This outline should be read in conjunction with the following documents:

Code of Practice - Teaching and Assessment

http://www.uow.edu.au/handbook/codesofprac/teaching_code.html

Key Dates

http://www.uow.edu.au/student/dates.html

Code of Practice - Students

http://www.uow.edu.au/handbook/codesofprac/cop_students.html

Information Literacies Introduction Program

http://www.library.uow.edu.au/helptraining/workshops/ilip/

Acknowledgement Practice Plagiarism will not be tolerated

http://www.uow.edu.au/handbook/courserules/plagiarism.html

Student Academic Grievance Policy

http://www.uow.edu.au/handbook/codesofprac/cop_supervision.html#8

Special Consideration Policy

http://www.uow.edu.au/handbook/courserules/specialconsideration.html

Code of Practice-Honours

http://www.uow.edu.au/handbook/honourscode.html

Non-Discriminatory Language Practice and Presentation

http://staff.uow.edu.au/eeo/nondiscrimlanguage.html

Intellectual Property Policy

http://www.uow.edu.au/research/researchmanagement/1998IP.html

Occupational Health and Safety

http://staff.uow.edu.au/ohs/commitment/OHS039-ohspolicy.pdf

SCSSE Internet Access & Student Resource Centre

http://www.sitacs.uow.edu.au/info/current/internet_access_and_resource.shtml

SCSSE Computer Usage Rules

http://www.itacs.uow.edu.au/info/current/support/labs/rules.shtml

SCSSE Style Guide for Footnotes, Documentation, Essay and Report Writing

http://www.sitacs.uow.edu.au/info/current/styleguide.pdf

SCSSE Student Guide

http://www.itacs.uow.edu.au/info/current/regulations.shtml

Informatics Faculty Librarian, Ms Annette Meldrum, phone: 4221 4637,ameldrum@uow.edu.au

SCSSE Subject Outlines

http://www.itacs.uow.edu.au/info/current/subject_outlines/

Subject Coordinator/Lecturer:	Mr Daniel F. Saffioti
Telephone Number:	02 4221 4357
Email:	dfs@uow.edu.au
Location:	Building 3, Room 202

Day	Time
Monday	15:30 – 16:30
Tuesday	15:30 – 17:30
Wednesday	15:30 – 17:30

Subject Coordinator/Lecturer:	Professor John Fulcher
Telephone Number:	02 4221 4811
Email:	john@uow.edu.au
Location:	Building 3, Room 223

Subject Coordinator/Lecturer:	Professor Aditya Ghose
Telephone Number:	02 4221 4051
Email:	aditya@uow.edu.au
Location:	Building 3, Room 105

Session:	Annual, Wollongong Campus
Credit Points	12 credit points
Contact hours per week:	1 hr lecture.
Lecture Times & Location:	Lecture Wednesday 1:30 – 2:30 pm, 35.G20

SCSSE

General Information

Content

Objectives

Method of Presentation

Assessment

Notes on Assessment

Project Activities and Milestones

Additional Information

The following staff members are available for assistance: