INFT6900 Assessment Item 3

Type:                                    Final Project

Assessment Type            Team

Weighting:                         45%

Due Date:                           Week 12 Friday 12th November 2021 by 11.59pm.

Method of submission: Blackboard Assessment 3 upload link

File Names:                        teamName_project_ass3 (compressed file)

teamName_video_ass3 teamName_management_ass3 (compressed file)

Objective:

The project should be completed, or most features completed to the best of your abilities. Those features not working or not working correctly should be clearly documented in the supporting final report. If it is a coding project then it is expected to be bug free for the completed parts, proper validation and error checking, good code commenting, and good use of space and code readability. If the project does not involve application development then it is expected the deliverable meets the expectations outlined with your project sponsor, supervisor or lecturer for this course.

All expectations should also be clearly detailed, defined, and reasoned in the final project report. The focus or preference is to see a small number of things working well, instead of numerous things only partially working. As such it is expected that elements of your project should be fully functional and/or completed. If you have any further enquires or questions on the project these should have been or should be immediately clarified with the lecturer before submission.

The Assessment

This assessment will include three parts:

Part 1 Actual Project:

The team must submit all files related to the artefact deliverable you have produced for this course. It should include all data/databases, electronic files (excel, access, etc), SQL Script files for databases, all code and related project files (for example testing procedures), and any other digital files needed to evaluate your final project product.

The team testing procedures and documentation for the project will be part of this submission. This would include your working drafts if applicable. For instance, if part of the system is not working then your submission would include the drafts of that section. In essence, you are documenting what was completed and what was not completed in relation to your project proposal document.

MOST importantly your team needs to include sufficient instructions on how to view, setup, and make the product work. The video may be an additional tool to assist in this requirement.

Part 2 System Video:

Your team will create a video that demonstrates the project, this is not a sales pitch but a document that demonstrates the capabilities of your project and may include details on how to view and demo the project.

Part 3 Project Team Work:

This document/s will cover the team management part of the project.

This is a team project, as such all work should be done in a collaborative manner, with equal division of tasks among all group members.

• There will be a section that is titled “Mistakes Made and Lessons Learned – What we would do differently”
• You will be expected to highlight in a one page summary at the end of the submission document a brief accounting of each team member’s contribution to the project in general
• A full break down of group member roles and work will be documented by the Gantt chart and any other documents that your team have created.
• This will also include the weekly update you sent the

Project Submission

A three 3 ZIP file should be submitted through the Blackboard assessment link, on or before the due date. Each day late will be subjected to a 10% penalty. If the files are too large or unmanageable for submission in this manner then a USB/Thumb drive should be provided to the lecturer or online data storage (last resort).

Part 1: All files relating to the project, this includes project documentation

Part 2: Video demonstrating project

Part 3: Team Management files