Hello, dear friend, you can consult us at any time if you have any questions, add WeChat: daixieit

Faculty of Engineering, Environment and Computing

5001CEM Software Engineering

CW2 Assignment Brief Resit May/Sept 2023

Module Learning Outcomes Assessed

1. Evaluate an architectural design against accepted quality criteria.

2. Select, evaluate and use tools and techniques to successfully manage a large-scale software project, including configuration management and version control.

3. Examine software process models most suitable to develop a solution to a real-world problem.

4. Select, evaluate and apply standards, tools and techniques for assuring software quality.

5. Identify and engage with relevant social, professional, legal and ethical issues on a practical computing project.

6. Demonstrate a sound understanding of how Agile Methodologies can be used to define users’ requirements, analysis and design of information systems.

Important Notes for Resit Students

You are expected to continue your original work, consider the weaknesses of your original submission, and improve it. This may involve developing stronger code (Product), completing the development processes (Process), and raising overall quality (Project). You are not required to present the group’s artifacts,  as  you  will  be  working  individually.  However,  you  should  reflect  on  your  own  project management and how you have met the learning outcomes. A marking rubric for this resit coursework is available on Aula.

Task Overview

You will be working as a one-man team in the development of an online app as described in the case documents, which means you may need to take on four different roles at the same time to complete the project, e.g., database engineer, programmer, Product Owner, and Scrum master. You are expected to continue your original work, which is one of the study cases below. The complete description of each case is available on Aula.

BlobMaths The digital learning platform for Australian early learners

Jawara – The Manufacturing Information Systems of Tenabang accessories

You are expected to complete a full cycle of software development by adopting Scrum. However, this module   is   focused   on   the   software   engineering   aspects   of   development.   Therefore,   the construction/coding phase will have a lesser relevance to the assessment of the overall coursework. Nevertheless, you will be asked to contribute to the creation of a comprehensive project report covering three main aspects: Project, Process, and Product. Details on the structure of the report document and what should be included in its content are available at the end of this document.

As previously mentioned, you need to take on four different roles from the list below, i.e., Product Owner, Scrum Master, and any two developer roles. Each role should produce a set of artifacts listed in the table at the end of this document.

Product Owner

Scrum Master

(Developer) Database Engineer

(Developer) Full-stack Developer

(Developer) Cloud Engineer

(Developer) Web Developer

Notes

1.  You are expected to use the APA 7thEdition referencing style. For support and advice, students can contact the Centre for Academic Writing (CAW).

2.   Please notify your registry course support team and module leader for disability support.

3.  Any student requiring an extension or deferral should follow the university process. As part of the University's No Detriment policy, any request for a 2-week extension will receive automatic approval however you must complete theonline application.

4.  The University cannot take responsibility for any coursework lost or corrupted on disks, laptops or personal computers. Therefore, Students should regularly back up any work and are advised to save it on the University system.

5.   If technical or performance issues prevent students from submitting coursework through the online coursework submission system on the day of a coursework deadline, an appropriate extension to the  coursework submission deadline will  be agreed  upon. This extension will normally be 24 hours or the next working day if the deadline falls on a Friday or over the weekend period. This will be communicated via email and as a CUMoodle announcement.

6.  Assignments must be uploaded in the file format specified in the assignment brief. Submissions that are not in this format will receive a zero mark.

7.  Assignments that are more than 10% over the word limit will result in a deduction of 10% of the mark, i.e., a mark of 60% will lead to a reduction of 6% to 54%. The word limit includes quotations but excludes the bibliography, reference list and tables.

8.  You are warned to check your work and the filename before uploading to the link. You have only one chance to submit, which Turnitin will check on your Moodle Web.

9.  Collusion between students (where sections of your work are similar to the work submitted by other students in this or previous module cohorts) is taken extremely seriously and will be reported to the Academic Conduct Office. This applies to both coursework and exam answers.

10. A marked difference between your writing style, knowledge and skill level demonstrated in class discussion, and any test conditions demonstrated in a coursework assignment may result in you having to undertake a Viva Voce to prove the coursework assignment is entirely your own work.

11. If you make use of the services of a proofreader in your work, you must keep your original version and make it available as a demonstration of your written efforts.

12. You must not submit work for assessment that you have already submitted (partially or in full), either for your  current  course  or for  another  qualification  of this  university,  unless  this  is specifically provided for in your assignment brief or specific course or module information. Where earlier work by you is citable, i.e., it has already been published/submitted; you must reference it clearly. Identical pieces of work submitted concurrently will also be considered self-plagiarism.

Document Structure of Your Report

Your report should have, at least, the following components arranged in the following order.

CONTENT

DESCRIPTION

Title Page

Information about the project, including the name of the case, your full name, your student number, and date of submission.

Project Summary

Summary of the project, including its objective, the processes involved, and the outcome. You may also briefly describe the challenges you encounter whilst completing the project and other information you think the Module Leader needs to be aware of.

Table of Content

A table of content with the corresponding page.

Project Schedule

A brief description of how you manage the project, and the tasks involved. You also need to include a Gantt chart.

Product Owner artifacts

See the table below.

Scrum Master artifacts

See the table below.

Developer-1 artifacts

See the table below.

Developer-2 artifacts

See the table below.

Future Work

A detailed reflection on the challenges you have and have not overcome, as well as what you plan to do should you have an opportunity to re-visit or work on the project again in  the future.

Conclusion

Conclusion about the project, the product (online app) as the outcome of the project, and the processes involved in the project.

Required Artifacts

Your report should include the artifacts assigned to each role you take on. The list of artifacts for each of the role is available below.

DOMAIN

ROLE

PRODUCT OWNER

SCRUM MASTER

DEVELOPER

PROCESS

CONTROL

- Statement of product goal(s)

- Product backlog

- Sprint backlog

- Sprint increments

PRODUCT DEVELOPMENT

- Requirement specifications

- Test backlog

- Business process analysis

- Use case diagrams

- Data analysis

- DFDs

- ER diagrams

- Software architecture/ class diagrams

- System security design

- Test report corresponding to the test backlog

- Snapshots of codes

- Screenshots of GUI

PROJECT MANAGEMENT

- Vision statement

- Mission statement

- Statement of scope and boundaries

- Risk assessment

- Tools and access management

- Job/task management

- Project schedule