Welcome to COIT13230 Application Development Project. In this project, you will work in teams using either a plan driven or an Agile approach on the realisation of a small software development project. The following artefacts are to be submitted: 1. Artefact one Plan-driven approach: Project Plan and Requirements Specification. The project plan is to provide a description of the project scope and its schedule, risks, product quality and resources. The requirements specification is to provide a clear list of non-functional and functional requirements for the application to be developed. Agile approach: Plan and User Stories. The plan is to provide a record of discussions with the customer regarding the nature of the application that is to be developed, the number of iterations expected and the anticipated involvement of the customer. User Stories document the initial set of user stories agreed with the customer. 2. Artefact two Plan-driven approach: Design Document. The design document will follow the template provided in your pre-requisite unit, COIT12200 Software Design and Development. Agile approach: Design review. A document outlining the software architecture and the initial design approach is to be provided. 3. Artefact three – Progress Reports (two submissions) Two progress reports are to be submitted as Word documents in Week 8 and Week 10. The reports are to review progress and to review the risk plan. If Agile development is being employed, the reports are to include a review of any design refactoring that have been made. This review will be assessed as part of artefact 2. 4. Artefact four – Final Project Document and Presentation Plan-driven approach – This final submission includes three distinctive parts: The first part is a project report describing the implementation and the testing of the product (group). The second part is a project review report including peer review report (individual). The last part consists of a Power Point file (group) and an Oral in-class/online presentation (individual). Each student has to submit this final assignment individually. Agile approach – The final submission includes all the documents for the final release of the software product. It consists of the final requirements and design documents (group), the testing report (group), the project review report including peer review report (individual), the Power Point file (group) and the Oral in-class/online presentation (individual). Each student has to submit this final assignment individually. Feedback for artefacts one, two and three will be provided within two weeks after the submission. Feedback for artefact four will be available on the Certification day. If Agile approach is employed, your marks for each artefact will be assessed at the final stage. Please make sure to re-submit all your previous artefacts in the final submission. Contact time is allocated each week in the form of a workshop. During these workshops, the local lecturer/supervisor will provide teams with assistance and monitor progress. Teams will be required to give presentations for some of the above artefacts in the week that the artefact is due. For distance students, the time of the "presentation" and the technology employed for communication will be determined on an individual basis. The project itself will be concerned with the development of a 3-layered information system or an equivalent application; details will be available on the unit website. Assessment Criteria ?Artefact one (30%) - one submission per group; the team leader makes submission. Artefact two (20%) - one submission per group; the team leader makes submission. Artefact three (10%) - one submission per group; the team leader makes submission. Artefact four (40%) - individual submission; each student needs to make submission.? The detailed marking guides can be found from the weeks that the Artefact are due, that is, Week 4, Week 6, Week 8, Week 10 and Week 12.