System Analysis Presentation

System Analysis Presentation:

slides:

Recorded videos:

LoFi Prototypes

LoFi Prototypes

1. home page for order management.

2. check information of an order.

3. Add new Order.

   

4. Edit & delete order.

Three Use Cases

Activity Diagram

Discussion and Interview Agenda

Setting

Objective of interview

   Determine process of making orders and how orders are scheduled.

Data, Time, and Location

October 15, 2013 at 12:00 PM in the restaurant.

User participants

   John Whilser, vice president of the restaurant, Raymond Fong, Service department manager, and Tim Tabasuki, Manager of production

Project Team Participants

   Yan

Interview/ Discussion

1. Who is eligible to make orders?

Waiters and manager.

2. Who is eligible to modify orders?

Waiters and manager.

3. What information must be in an order?

Table number, name of person who made the order, type of order delivery(take out or not?), number of customers of each order, menu names, size of each menu(small, medium, and large), and number of orders of each menu.

4. How do customers respond to waiting time of orders?

customers who have already served some food is more tolerant of delay than those who have nothing on the table. Some customers is likely to cancel those unserved food or just leave if delay is over 20 minutes.

5. What are the expectations for the order sub-system?

A. Order can be made through  mobile devices.

B. Order information can be shared to casher in case customers want to verify what they have eaten when making payment.

C. Order information should contain all the details of any update(add or remove menus after the order is made).

D. the system can inform the waiters when an order is not available due to some reasons (not enough inventory etc.)

E. the system will automatically disable those unavailable menus so that waiters would know the information in advance.

6. Who make the decision to pick which order to product of a list of orders?

Only the chief chef.

7. How to decide the schedule of a set of orders to be produced?

First in first serve strategy. In addition, They group menus from a sequence of orders base on the first one.

8. What constraints  affect the decision of scheduling?

A. order of the incoming food orders.

B. capacity of the oven

C. whether sequence of menu of an order is important or not.

9. What to do if there was unexpected events such as no inventories or defective products.

if there were no inventories, the menu should be disable in the system.

if there were defective products, stop process of all food of the same type of defective products until problem is solved.

10. What are the expectations for the auto scheduling algorithm?

the system can handle the constraint of 8.c above.

orders can be decomposed into suborder for different ovens in the kitchen so that chef would get the right orders.

Follow-Up

Date and time of next meeting or follow-up session

   October 20, 2013, at 12:00 PM

Activity Diagram

Discussion and Interview Agenda

The following is an interview session agenda with follow-up information regarding Restaurant Order Scheduling. 

Discussion and Interview Agenda

Setting
Objective of interview
    Determine process of making orders and how orders are scheduled.

Data, Time, and Location
October 15, 2013 at 12:00 PM in the restaurant.

User participants
    John Whilser, vice president of the restaurant, Raymond Fong, Service department manager, and Tim Tabasuki, Manager of production

Project Team Participants
    Yan

Interview/ Discussion
1. Who is eligible to make orders?
2. Who is eligible to modify orders?
3. What information must be in an order?
4. How do customers respond to waiting time of orders?
5. What are the exceptions for the order sub-system?
6. Who make the decision to pick which order to product of a list of orders?
7. How to decide the schedule of a set of orders to be produced?
8. What constraints  affect the decision of scheduling?
9. What to do if there was unexpected events such as no inventories or defective products.
9. What are the exceptions for the auto scheduling algorithm?

Follow-Up

Date and time of next meeting or follow-up session
    October 20, 2013, at 12:00 PM

Reaching Out

Talking with manger of the restaurant about project "Restaurant Order Scheduling".

1. Self introduction: "Hi, I am Yan, a student from computer science department of Hawaii Pacific University."

2. Project introduction: "I am doing a project of the System Analysis class. For the project, we are looking to help an organization analyze some of its IT issues. Is there any IT issues that we would help?"

3. Investigating issues if the manager accepts my request, otherwise, say "Thank you for your time."

         3.1 Ask current system "How is the current order scheduling procedures working?"

                  3.11 Ask ” what are the order scheduling processes?”

                  3.12 Ask ” how are the processes performed?”

                  3.13 Ask “ what information is required?”

         3.2 Ask issues "What is the problem with the current order scheduling"

         3.3 Ask the expectation for the solution "What is your expectation to the solution?"

        

4. Define Requirements

         4.1 Ask functional requirement “what are the functional requirements, that is, what does the new system must perform. In other words, what tasks is the order scheduling system designed for?”

         4.2  Ask non-functional requirement “Rather than perform required tasks, what other requirements does the system must provide, for example, requirements of performance, integration with other system, reliability, etc..? ”

5. Define Stakeholders: Ask “who are related to the new system if it success, that is, who will be benefit from the system from internal and external perspective?”

6. Ask for contacts for further detailed requirements information including users and stakeholders.

7. "Thanks for your time, see you later!"

The Stakeholders

Stakeholders are those who have interest in the successful implementation of the system (Satzinger, Jackson and Burd 2012). Thus, they are the most important people as information supplier for the analysis and design of the system.
For the system "Open House Route for Multiple Location", the stakeholders include:
1. Customers
2. Agents
3. Managers
4. Corporate partners
5. Navigation providers
6. Map providers

For the system "Restaurant order scheduling", the stakeholders include:
1. All works in the kitchen
2. Managers
3. Staffs from inventory department
4. Food suppliers
5. Works who communicate with customers from  services department
6. Clerks
7. Customers

For the system "ABC Inventory Management System (basic functions)", the stakeholders include:
1. Sale order clerks
2. Marketing, sales, accounting, and financial mangers
3. Manufactures and parts suppliers
4. Warehouse and shipping personnel
5. Customers
6. External shippers
7. Partners
8. Senior executives

Open House Route for Multiple Location

Problem Description: Real estate companies provide an information system for their customers to find for sell houses. However, the system do not provide multiple location route in its map. As open house session comes, customers will visit multiple house at one time. It is so inconvenience for them to input every destinations to their navigators each time. In addition, customers would only approximate a better route since it is not easy to calculate multiple destinations. It is recommend that the existing information system would have the ability to calculate an optimize route for multiple location with the integration of Google Maps.

System Capacities:
1. Use Google Maps service.
2. Show desire location of the existing information system on the map.
3. Calculate and show the route for those desire location.
4. Output route to portable devices.

Business Benefits:
1. Save customers' time in locating multiple houses.
2. customers would easily compare destination of those desire location.
3. customers would make decision quicker.

ABC Inventory Management System (basic functions)

Problem Description: ABC construction equipment LLC believes that constructors do not earn money by owning tools; they make money by using tools as efficiently as possible.  ABC company try to change its business model to help constructors get the job done by leasing tools instead of selling them. The company will provide the best tools at the right time, and quickly finished tool repair, replacement, and upgrade.  To delivery those service, ABC company needs an inventory management system with the basic functions to manage its large arsenals of tools more inexpensively and effectively than it's  customers had.

System Capacities:
1. Minimizing the unnecessary tools and parts in storage while have enough stock to meet the demand.
2. Optimize warehouse inventories, that is, to effectively allocate inventory to different warehouse so that tools can be delivery to constructors quickly.
3. be able to track all tools and parts.

Business Benefits:
1. Cost saving. Since unnecessary tools in the storage is removed, company would save a lot of investment.
2. Increase timely delivery of tools to customers.
3. Increase customer value since there are more type of tools available for their projects so that they can easily scale their projects.

Restaurant Order Scheduing

Problem Description: customers desire good quality and tasted food. However, the quality and taste of food has a negative relationship with its storage time.  The longer the food is storaged the less the quality and taste of the food is. Thus, the quality and taste of the food is the best as it is just finished cooking from the kitchen. However, there is a time constrain for the cooking procedure, and customers' satisfaction will decrease as their waiting time increase. It is hard for a restaurant to hire new chiefs since the size of the kitchen is fixed. As holiday and weekend come, the expected waiting time will be much greater than weekdays.
It is recommend that the new system will be deployed so the schedule of each cooking order is optimized, that is, giving a tolerant waiting time of an order, the chiefs would cook as many orders as possible.

System Capabilities: 
1. Collect order information from the existing order subsystem 
2. Exchange information with the inventory subsystem.
3. schedule orders.
4. inform clients (system who place orders) as orders are not available.

Business Benefits: 
1. Increase customers' satisfaction since waiting time for food is decreased under the schedule system.
2. Decrease waiting time for those who wait for an available table since waiting time for food is decreased that customers would finished their food early.
3. Increase timely response to client who make orders that when an  order is not available due to some unexpected reasons.

Cloud computing are becoming new platforms for enterprise and personal computing as it is better in software delivery and pricing than the traditional platforms. The development of cloud computing technology has speeding up the SaaS since it provides a lower barrier for company with less budget for their information system infrastructure.

SaaS is a method of software delivery that allows data to be accessed from any device with an Internet connection and web browser . In fact, SaaS is an interface liked concept in OOP, which provides a method of function delivery that allows data to be accessed from other classes.  One of the big difference between them are the clients who use it (locally or through network). However, SaaS is not RPC or CORBA architecture (programming language dependent).

Currently, There are two approach for the implementation of SaaS as API, which are RESTful and SOAP. REST uses HTTP/HTTPS  with the standard GET, PUT, POST, and DELETE verbs, in contrast, SOAP can use XML to address  almost any transport to send the request. I personally prefer the RESTful approach since it is much simpler than the SOAP approach.

The following video shows the difference between RESTful and SOAP.

Test Post

Test post