CSIT314 Project-Software Development Methodologies Solution

TASKS
Your tasks are to:
1. Carefully read this document;
2. Form and structure your group, allocating roles and responsibilities to your members. Make sure you communicate frequently and contribute significantly to your group work. If you have little contribution to your group project, your individual mark will be significantly lower than your group’s mark (or even 0 mark if you have almost no contribution).
3. Complete the development of a given software system (enclosed in this document). This should cover all software development activities from requirements elicitation and specification, design to implementation and testing. Your design must be based on the b-c-e framework discussed in the subject.
4. Choose an agile method (Scrum is highly commended) for your group to follow. Choose a tool which supports that methodology for your group to use. Taiga https://taiga.io/ for agile method is strongly recommended (choose the public option which allows multiple team members).
5. Demonstrate the practice of test-driven development and Continuous Integration/Continuous Delivery (CI/CD) in your project.
6. Produce a report detailing the group's work.
SUBMISSION
• Final report
• A 15 minute recorded video of a live demo of your product
• Source code
2. Final presentation (5 marks): The last lab session

GUIDLINES
1. The final report should cover at least the following:
• A complete list of user stories.
• For each user story, a list of complete tasks.
• A complete and detailed design including UML use case diagrams, use case descriptions, sequence diagrams, class diagrams, data persistence and user-interface aspects.
• Sufficient evidence (with screenshots and detailed text description/explanation) to demonstrate that your group has followed an agile methodology and has used a tool which supports the methodology from the beginning to the end of the project. Note: make sure that you record these evidence every week (e.g. screenshots of the product backlog, sprints, the work-in-progress software system, etc.)
• Test plans, test cases (include unit test cases), and test data that is sufficiently large enough to simulate the scale of the developed system. Details of unit testing procedures that have been conducted to clearly demonstrate (with sufficient evidence) that your group has followed test-driven development

• Sufficient evidence (with screenshots and detailed text description/explanation) to demonstrate the use of CI/CD in your project (i.e. the development and deployment of at least one feature/functionality).
• Identify and discuss ethical considerations in developing the software system in this project and how your team have addressed them.

• Identify a feature of your software application that can be developed using data-driven software development. Present a detailed plan of how this feature would be developed and integrated into your software application using the data-driven approach discussed in the subject.

• True group meeting records: agendas and meeting minutes which includes at least the following:

• Member contribution for the whole project (with each member’s signature):
o On the cover page of your progress/mid-project/final report, you need to provide rating for the contribution of each team member and a detailed explanation of what the team member did for the project to justify the rating (e.g. the roles that they filled, the tasks they completed, and the artefacts that they successfully delivered).
o Everyone in the team should sign the cover page. The individual contribution of each team member is assessed by all the other members.
o The rating scale can be a percentage number (e.g. 60%). Alternatively, the scale be in the form of
“contributed”, “very little”, and “almost no contribution”. For a team member who has

A suggested plan:
• The first week after the lectures: finalize group and start working on the project. Produce the first complete version of the requirements.
• One iteration/sprint per week until the end of project. In each iteration:
o Design, implement, and test a number of functionalities;
o Continue eliciting and clarifying further requirements.
The project description is in the next page.
Project Description

Important Notes:
• At least the backend/middleware of your software product (i.e. the main code that controls/runs all application logic and hold data in memory) needs to be object oriented.
o Full time cohort: Terence Chew (tchew@uow.edu.au) o Part time cohort: Kheng Teck Tan (ktan@uow.edu.au)

In this project, your team is asked to design and develop a contactless table ordering system for a restaurant. This system will enable the restaurant’s customers to order food and drinks from the restaurant’s digital menu and pay for them directly using the system that is running on their phone, tablet or computer. To access the system, customers can scan a QR code or enter a unique code that is placed on each table.

The system should support at least the following key aspects.
1. Support and manage different types of users and user profiles.
2. Support restaurant managers in creating/modifying menu and prices, coupon codes, etc.
3. Support restaurant staff in managing and fulfilling orders
4. Support customer in browsing menu, placing an order, and makes their payment from the table.
5. Support restaurant owners in collecting and organising data that can be used for marketing efforts. This includes customers’ behaviour and patterns such as average spend per visit, frequency/patterns of visits (or how long since they last visited) and preferences for dishes/drinks. These insights can be used for personalised marketing such as tailoring specials to specific customers.

You must create test data that is sufficiently large enough to simulate the system (e.g. 100 records to each datatype). You could write a script to generate these data randomly. In the final product demonstration, you will need to run a live demo of your product with these test data.

The marking scheme is in the next page for your reference.

Marking scheme
Component Out of Marks Comments

Final Project Presentation (Recoded demo video + Q&A session)

5




Final Deliverables

Overall quality of the Final Deliverables

2



User stories and tasks
8

Analysis and Design (use cases, detailed design models, consistency between design models, consistency between design with code, etc.)
9



Implementation (quality of code, functionalities implemented, sophistication of the solutions, consistency with design, etc.) 6

Test-driven development

CI/CD

Ethical consideration and discussions

Data-driven development

Effective use of methodologies (e.g.
evidence of the use of a methodology and tool support, true meeting records, weekly
progress as observed and noted in the labs, etc.)

2

2

2

2

2



Total 40