Applications Development Theory 3 - ADT372S
DEPARTMENT OF INFORMATION TECHNOLOGY
APPLICATIONS DEVELOPMENT THEORY 3
(ADTS372S)
Assignment 1
Due dates:-
Blackboard
6/3/2019
Demo
13/3/2019
This is a group assessment which has 2 deliverables – a) a Blackboard submission and b) a prototype
demonstration which will take place during the practical class.
Project Rules regarding group work:






Each group will consist of a maximum of 3 members.
Students are expected to establish and manage their groups themselves. Exception cases will be mediated by
the lecturer
You may choose to do this project on your own, but remember the outcomes and expectations remain the
same as if you worked in a group.
You will need to submit part of your solution via Blackboard and your prototype will be demonstrated during
class.
All group members need to be present and contributing during the demonstration.
A demonstration schedule will be made available during class for students to select their preferred demo slots.
Any groups not meeting the schedule selection deadline will be assigned a demo slot.
The Scenario:
You are the software manager of a consultancy and are responsible for the following software project. The owners of a
small family-owned restaurant have approached you to develop a system for their changing situation. The first
restaurant has become hugely popular and the company is in the process of opening up 2 more restaurants to cope
with demand. Due to resource-constraints the first restaurant operated in a basic, non-automated and paper-based
way. While some of the “old fashioned” aspects will remain (such as greeting customers at the door) others, such as
the tracking and updating of tables physically on a chalkboard diagram and taking orders with pen and paper needs to
go. Similarly, the delivery of paper orders to the kitchen for food preparation by waiters is out of date. Once the food is
done, the piece of paper is saved for “proper” record keeping by the management. While this system worked in a
single small restaurant with a capacity for 30 diners, it yielded a large amount of receipts, wasted a lot of time and is
out-of-date for the 2 new and much larger restaurants which can accommodate 60 diners at a time.
This project aims to automate many of the restaurant operations so that all information pertaining to customer orders
and staff activity will be conveniently shared and stored over the restaurants’ intranet. Hosts will be able to view table
status with a click of a button and the wait staff will be able to enter the customer’s orders quickly and efficiently and
then have it delivered to the kitchen electronically. The kitchen staff will be able to view the incoming orders and notify
the proper wait staff when the food is ready. Bus boys will be able to view the real-time floor status allowing them to
know which tables are clean, dirty, or occupied. Most importantly, all of the restaurant information will be organized and
saved in the database for the management viewing and archival. Since all data will be collected and processed
automatically up-to-the-minute analysis will be available on




revenue and revenue percentages per menu item
Personnel efficiency
Average turnaround time (how long customers spend in the restaurant)
Average preparation time (time from when the order is placed to when it is ready)and management will be able
to focus on analyzing the data rather than calculating it.
Cape Peninsula university of Technology -Assessments 2019
Applications Development Theory 3 - ADT372S
Domain Fieldwork
You are required to visit local restaurant(s) and interview personnel to understand the current practice and identify the
opportunities where introducing automation can help improve productivity and reduce errors. It is a great advantage if
some of the team members have experience working in restaurants. (If you are currently working in a restaurant, then
you should also interview your colleagues at work and quote their opinions in your reports.) When writing your project
reports, you should use your own experience, or that of others working in restaurants when describing and justifying
your design decisions. In software engineering, personal familiarity with the problem domain is one of the greatest
assets, and you should show it explicitly in your reports. You will also need to perform an economic study to find the
optimal kind of devices to be used by the restaurant personnel. On the one hand, waiters could have handheld PDAs
to avoid re-typing the order. On the other hand, fewer fixed computers on the restaurant floor can be used by multiple
waiters. Additionally, the possibility of loss and damage, particularly for handheld devices needs to be considered.
Your solution should include the following:-
Assignment Deliverables:
A feasibility report explaining the technical and financial feasibility considerations needed
1
for your proposed solution.
The stakeholder list
2
3
Collect the requirements for the system from software engineers and external stakeholders
and specify the user requirements as well as the following initial system design
requirements: - architectural, database, interface and component.
One software development approach not suitable for this system. Why not?
4
Use case diagram
5
Design a storyboard for your proposed solution indicating the most important
6
functionality
Write one suitable user story then develop it by
7
Creating its wireframe/design prototype
7.1
Developing a software prototype and QR code using Marvel
7.2
Develop a software prototype for a different user story using a scripting language of your
8.1
choice.
8.2
Peer test of your prototype
9
To reduce costs and the environmental impact of commuting, your company decides to
close a number of offices and to provide support for staff to work from home. However, the
senior management who introduce the policy are unaware that software is developed using
agile methods, which rely on close team working and pair programming. Discuss the
difficulties that this new policy might cause and how you might get around these problems.
Marks
5
5
15
5
10
10
10
15
15
5
5
The Rubric:
Assignment deliverables
1. Feasibility Report
2. Stakeholder list
3. User and
System design requirements including architectural, database, interface and component
design
4. Software development approach
5. Use case diagram
6. Storyboard
7. User story (Suitability, task cards)
7.1 Wireframe/Design Prototype (Content and layout)
7.2 Software Prototype and QR code
8. Second Software Prototype
8.1
Database population
User interface
Connecting to database and functionality
8.2 Peer testing
9. Team programming
Cape Peninsula university of Technology -Assessments 2019
Marks
5
5
3
12
5
10
10
5
5
15
5
5
5
5
5
Applications Development Theory 3 - ADT372S
Total
Cape Peninsula university of Technology -Assessments 2019
100