Development of an Automated Solution for Su Ying's Noodle Bar

PART A: Journal entry
S.No. Date Activity Explanation Status
1. 21st May 2018 Project planning In this activity, I
gained understanding
of the project working
i.e. how many phases
are there in developing
a project. Then I
consulted my friend
who guided me to visit
a real case on the same
lines of Noodle Bar.
There I studied the
interfaces of the
restaurant and how
they dealt with manual
issues
Completed
2. 23rd May 2018 Software
development plan
In this activity, I
studied the phases of
software development
i.e. how a product is
developed. Then I
discussed the same
with my class mate.
We came to this
conclusion that there
are many life cycles
which can be followed
but the simplest of all
is waterfall lifecycle
but it is very costly.
Then I move ahead and
Completed

found that agile is
complex but beneficial.
3. 23rd May 2018 Team member
allocation
Resources are assigned
their roles but before
that I had to figure out
the responsibilities and
roles.
Completed.
4. 25th May 2018 Design tools
discussion
In this activity, we
tried various mock-up
tools and finally
decided to use
balshmiq wireframe
tools (Filippo &
Filippo, 2000)
Completed.

Task 2.01 Work Breakdown Structure
In this task, work breakdown structure for the proposed system is done where in all tasks are
broken down into small and manageable units of work.
1.0 Project planning
1.1 Requirement validation
1.2 Project plan
1.2.1 Project scope
1.2.2 Project Schedule
1.2.3 Budgeting
2.0 Designing and development
2.1 Designing
2.1.1 Design selection
2.1.1.1 Interfaces
2.1.1.2 Modules
2.1.2 Design documentation
2.2 Development of solution
2.2.1. Coding
2.2.1 Integration
4.0 Testing & Backup
4.1 Testing plan
4.2 Testing
4.2.1 System Testing
4.2.2 User acceptance testing
4.2.3 Functional testing
4.3 Code Backup
5.0 Training
5.1 Prepare material
5.2 Hire trainers
5.2 Conduct training
7.0 Project closure
7.1 Release resources
7.2 Client acceptance
7.3 Project learning document
7.4 Project sign off

Task 2.02 “To-be” design – activity diagram
To-Be design defines how the new system would work. The new system that is proposed in
the software development project has following entities:
Sales Assistant: The sales assistant is given an interface where a complete list of all the
orders being received and processed is listed. Based on the same, the sales representative
would pass on this information to the cook. The order once received is tracked on the menu,
the customization, quantity, taste preferences and delivery notes are taken down into the
system respectively. The sales representative would re-check the order as soon as he receives
it and then passes on this information to the cook. As soon as the cook is informed the
delivery agent is also notified as soon that order would be made available for delivery to the
respective address mentioned in the order.
Cook:
The cook receives the complete information from the sales assistant. This information is
received as soon as it’s received and validated by the sales representative. The cook would
match this information with the respective recipe for the said item and would then start
preparing the items based on the quantities, customization and taste preferences as mentioned
by the customer.
Delivery agent: As soon as the cook finishes cooking, he would inform the delivery agent.
The delivery agent would receive the completed product in appropriate manner properly
categorized and divided as mentioned by the customer and he would then locate the address
provided by the customer and begin the delivering process (Anthem , 2014).