Developing An Essay For A Restaurant Software Project.

Develop a project journal (a log of YOUR OWN real activities in doing Assignment 2). Use a table with columns with number, date, activ

Work Breakdown Structure

Before you start on the tasks in Assignment 2 do a one-page Work Breakdown Structure showing activities and duration (examples in Satzinger and on-line).

“To-be” design – activity diagram

Provide the “TO-BE” core business process for your new system (BPMN or UML)

Organisational change

Compare your As is and To be diagrams to assess the impact of the new system on previous pre-automation processes and prepare a briefing note for the Organisational change and Training Team on the anticipated business impact of the system. You should make recommendations on how these can be managed.

Screen design

Develop screen designs for two MUST stories, identify business rules; justify your design

Acceptance Criteria

Write all acceptance criteria for these two stories to be done

Applications Architecture

Draw an applications architecture diagram showing interfaces for all systems in the Case Study that will be operating at the client site and their connections to your new system.

Report to Client

Presume you have completed a “waterfall method” processes of RFT, evaluation of tenders and selection of a solution/supplier. Write the executive summary of the Report to client where you explain the processes undertaken and recommend a preferred supplier.

Task 2.01: Work Breakdown Structure

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 found that agile is complex but beneficial.	Completed
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).

Task 2.03 Organizational change 

As-Is Process	To-Be Process
The sales representative manually takes the order of the customer on phone, manually notes it down and even manually enters the quantity and prepares order summary	The sales representative would receive the completed order digitally which would be selected by the customer in the first place. All the essential details needed for the order such as customization option, taste preferences, delivery location etc would have been already mentioned in the order details.  (Townsville-Mackay, 2012).
The sales representative then manually provides the order summary to the cook with given customization options, the total quantity as well as the taste preferences of the customer.	The sales representative would then validate the information, which can be done quickly and then simply click a button to pass on the same information to the cook.
The sales representative also manually provides the order summary to the delivery agent who would then proceed to note it down manually. He would then proceed to standby and await further instructions which again is sent manually by the cook (Larman, 2010).	As soon as the sales representative takes down the order, validates and pass it on to the cook all through a click of a button, the delivery agent is also notified for the same. The system would automatically calculate all the pending orders in line and estimate the time required and would accordingly mention him when the order would be due for delivery.
The cook would manually take the order from the sales representative, then proceed to note it down manually on to his notebook and then start preparing the order by manually locating the recipe for the same. The cook would manually tag the order with appropriate customer name, location, number and other details and pass the same to the delivery agent.	The cook would receive all the order details on his system and as mentioned previously would also receive the estimated time it would take to receive the completed item.
The delivery agent would match the data sent by the sales representative and the cook and then accordingly would proceed to the destination to deliver the order.	The delivery agent would receive the final prepared item with a machine printed label that he would have to verify via QR code to essentially validate that it’s the right match. Once this is done, the respective address and the number of the customer will be displayed on his system.

Task 2.04 Screen design

The selected user stories of the proposed application are as follows:

User story 1: Order listing - In the first, user story the administrator can see the order list which the status of each order and other details such as – order type, creation date, special notes and total price. In the screen, only required details are shown. For instance: order details are shown next to each order number and order number text is highlighted.

User story 2: Order form – This screen is used by all the customers to place an order. In this screen, the details of products are given along with a button to add it in the cart. There is an option to depict the type of user.  Depending on it, the next payment screen will be decided.

Task 2.02: To-Be Design - Activity Diagram

Task 2.05 Acceptance Criteria

Following is the acceptance criteria in which listing of orders for the staff will be tested:

• Does the screen show the status of the order i.e. whether is pending, take-away or cancelled?
• Does the screen capture the details of the order?
• Does the screen correctly depict the order details?

Following is the acceptance criteria in which the user story order creation will be tested:

• Does the screen depict the kind of user placing order?
• Does the screen provide an option to add/delete the product from the order?
• Does the screen provide sum total of order amount?

Task 2.06 Applications Architecture

In this task, application architecture for the proposed system. It is an enterprise architecture consisting of more than three tiers: Client tier – This tier consists of interface side of the application i.e. interface using which client interacts with the system; Application tier in which application components are built; middle tier for business logic and database tier.

Task 2.07 Report to Client

The web-based application would required to be developed as separate interfaces each for the sales agent, the cook and the delivery agent. Also, at the back-end, the codes would need to be developed for different modules including matching the order with the item, generation of a smart label with QR code, the estimation module, order management module and a customer history maintenance module. Also, for the same the system would need to be connected to all different devices being used by all the parties involved so that it could effectively update all at once. The system would also need a front-end which would be with the customer from which the order would be placed. The system would also need to communicate between all the systems so that everything is automated, connected to one another and can appropriately generate notifications after one another.

The system would require appropriate IT infrastructure hardware that would effectively make the entire system possible. These systems includes a web-server which would contain the bulk of the front-end and the back-end system. The same web-server would contain the application with the bulk of the programming logic. Another server would be needed which is the database server which would take care of the entire database. Finally, another server is needed which would handle the communication’s aspect such as triggering notifications on each of the systems or allowing to pass on the details to one another.

The system would also have to be connected via digital printer which would be installed in the kitchen allowing for printing of smart-labels that would then be read by the smart reader with the delivery agent. The system would be developed with appropriate web-coding standards that ensures a quality product with highest level of security possible. The system would also be unit tested to phase out any bugs and inconsistencies that may be present in the system.

Task 2.08 Agile and Waterfall differences

For the development of the said system, there needs to be a proper software development methodology. Among the most used methodologies for software development are the Waterfall and Agile methodologies. In the case of Waterfall methodology, it takes the approach of phase wise development. It’s the simplest of the two models. In this case, the project is divided in several phases and one phase cannot begin unless the previous phase is completed. The benefit of this methodology is that the development are sequential and thus development are phase. This methodology however does not allow for any interim modifications, iterations and testing. If at all the project requires changes in the middle, the system would need to be re-done which increases the cost significantly (WHO, 2010).

Organisational Change

On the other hand, the Agile model is a type of development methodology which aims at rapid development of the system in short iterations. The team does not full clarity of the system requirements before-hand and the requirements are delivered in bits as the system development progress. The project is completed with phases that has bare minimum application features and each of the features as and when they are completed are tested. Agile methodology has higher level of flexibility and can accommodate project requirement changes in any phase of development. This methodology also allows for delivering of the system in bare-bones to the client and thereafter inputs can be taken from the client for making any changes into the software (Anthem, 2014)).

The testing is carried out in every single iteration and thus the final output is something which is readily tested and mostly free of any bugs. The risks are overall much lower in Agile development methodology. Although there are mostly up-sides to Agile, the major downside is that it’s suitable for projects that may change over time as the project progresses. Also, the team must be highly efficient in this type of development and tends to be more expensive as it requires frequent interaction with the client. This will be the ideal choice of development methodology of the two.

Task 2.09 Speech

I was appointed as the by the <your name> Technology Consulting to come up with the automated solution which can minimize the issues arising from the present manual process of Su Ying’s Noodle bar. In order to come up with an efficient solution, first of all, I identified the users of the system. It resulted into three main types of users: customer, staff and management team. The proposed solution will be used by the customers to place orders, make payment and cancel orders. The staff uses the system to track orders and check the order details. Management use the solution to generate reports such as number of orders cancelled in a month, total salary of the staff, etc. Since the last report, I have figured out the architecture i.e. the multi-tier architecture. The development of project will take around 6 weeks. It will consist of phases: Requirement analysis, design, coding, testing and maintenance. The three modules will be developed are order management, employee management and payment management. The modules will be developed by different team members. Since, Agile methodology will be used to develop the system, all above mentioned phases will be executed in iterations. Each iteration will provide feedback which will be incorporated in next iterations. Once the project was completed, the next step was to close the project. The closure will include framing learning document, release resources and also document any changes in the project. Also, a training module will also be created to train the users of the system (ACRRM, s2013).

References

ACRRM. (2013). GUIDELINES FOR TELEHEALTH ON-LINE VIDEO CONSULTATION FUNDED THROUGH MEDICARE. Australian Government Department of Health and Ageing.

Anthem . (2014). Anthem Blue Cross Telehealth Program Provider Manual. Anthem .

Filippo, R. D., & Filippo, D. D. (2000). The Six-Phase Comprehensive Project Life Cycle Model Including the Project Incubation/Feasibility Phase and the Post-Project Evaluation Phase . IIL.

Larman, C. (2010). Applying UML and Patterns. University of Dallas.

Townsville-Mackay. (2012). Telehealth Support Program – Connecting Health Services with the Future. TMML.

WHO. (2010). TELEMEDICINE Opportunities and developments in Member States. WHO