Your company is a 4-year-old startup called XYZ Software Enterprises. XYZ produces a point of sale system and was awarded a Proof of Concept (POC) to one of the largest and oldest restaurants in the industry (you know, the ones in the commercials all the time). The restaurant wants XYZ to prove that the software will do what the sales people said it could do.

Your Proof of Concept will include four parts:

• Part 1: Gantt Chart
• Part 2: Testing and User Acceptance Report
• Part 3: Use Case Diagram
• Part 4: Activity Diagram

There are two diagrams needed for this assignment and the information for the diagrams is supplied so you do not need to make things up or find it anywhere but in the assignment information

Please see attachments for important details

Systems Analysis and Design in a Chaning World Technical Paper

Today: Initial Meeting

 

 

 

1 week: Select teams to participate in project

 

 

 

2 weeks: System configurations based on information gathering methods

 

 

 

2 days: Create activity chart based on information gathering

 

 

 

1 day: Create use case diagram based on information gathering

 

 

 

1 day: Show the finished configurations to the team and get feedback

 

 

 

3 days: Make changes based on feedback

 

 

 

2 days: Install the system in the test store

 

 

 

1 day: Train staff

 

 

 

2 weeks: Run a live test of POC

 

Additional tasks:

 

 

 

 

 

1. Research information gathering methods (1 week)

 

 

 

2. Select information gathering methods (1 day)

 

 

 

3. Implement information gathering methods (1 week)

 

 

 

4. Analyze information gathered (1 day)

 

 

 

5. Present findings to team (1 day)

 

 

Explanation:

Today is the first scheduled meeting.

 

 

1 week to choose teams that will take part in the project.

 

 

 

System configurations depending on information gathering methodologies, to be completed in two weeks

 

 

 

Two days: construct an activity chart based on the information that was gathered.

 

 

 

Use case diagram based on information gathered must be created within 24 hours.

 

 

 

1 day: Present the completed configurations to the group and solicit feedback from them.

 

 

 

3 days: Make adjustments based on the comments you receive.

 

 

 

Install the system in the demo store, which will take 2 days.

 

 

 

Training of personnel for one day

 

 

 

2 weeks: Conduct a real proof-of-concept test

 

 

 

Additional tasks:

 

 

 

1. Conduct research on the various information collection methods (1 week)

 

 

 

2. Determine the means of information collection (1 day)

 

 

 

3. Put in place procedures for the collection of information (1 week)

 

 

 

4. Perform an analysis on the data that was gathered (1 day)

 

 

 

5. Make your findings known to the team (1 day)

Your company is a 4-year-old startup called XYZ Software Enterprises. XYZ produces a point-of-sale system and was awarded a Proof of Concept (POC) to one of the largest and oldest restaurants in the industry. The restaurant wants XYZ to prove that the software will do what the salespeople said it could do.

Create a Gantt chart for the entire process of the Proof of Concept. There is a two-month deadline from today to complete the POC. Your Gantt chart must include the following:

Today as the initial meeting.

It should appear as the first line.

Select teams to participate in the project (1 week).

Information gathering (add the information gathering methods you will use and how long each will take).

System configurations based on information gathering methods (2 weeks).

Create activity chart based on information gathering (information to create chart supplied; 2 days).

Create use case diagram based on information gathering (information to create chart supplied; 1 day).

Show the finished configurations to the team and get feedback (1 day).

Make changes based on feedback (3 days).

Install the system in the test store (2 days).

Train staff (1 day).

Run a live test of POC (2 weeks).

Five more tasks from the concepts learned in this course.

The additional tasks can be subtasks for information-gathering methods and other subtasks or major tasks not listed above.

Remember that events in a Gantt chart can happen simultaneously with other events. Some items also cannot start until others are completed. Everything has an estimated time frame, and it is displayed in the chart.

Today: Initial Meeting

 

 

 

1 week: Select teams to participate in project

 

 

 

2 weeks: System configurations based on information gathering methods

 

 

 

2 days: Create activity chart based on information gathering

 

 

 

1 day: Create use case diagram based on information gathering

 

 

 

1 day: Show the finished configurations to the team and get feedback

 

 

 

3 days: Make changes based on feedback

 

 

 

2 days: Install the system in the test store

 

 

 

1 day: Train staff

 

 

 

2 weeks: Run a live test of POC

 

Additional tasks:

 

 

 

 

 

1. Research information gathering methods (1 week)

 

 

 

2. Select information gathering methods (1 day)

 

 

 

3. Implement information gathering methods (1 week)

 

 

 

4. Analyze information gathered (1 day)

 

 

 

5. Present findings to team (1 day)

 

 

Explanation:

Today is the first scheduled meeting.

 

 

1 week to choose teams that will take part in the project.

 

 

 

System configurations depending on information gathering methodologies, to be completed in two weeks

 

 

 

Two days: construct an activity chart based on the information that was gathered.

 

 

 

Use case diagram based on information gathered must be created within 24 hours.

 

 

 

1 day: Present the completed configurations to the group and solicit feedback from them.

 

 

 

3 days: Make adjustments based on the comments you receive.

 

 

 

Install the system in the demo store, which will take 2 days.

 

 

 

Training of personnel for one day

 

 

 

2 weeks: Conduct a real proof-of-concept test

 

 

 

Additional tasks:

 

 

 

1. Conduct research on the various information collection methods (1 week)

 

 

 

2. Determine the means of information collection (1 day)

 

 

 

3. Put in place procedures for the collection of information (1 week)

 

 

 

4. Perform an analysis on the data that was gathered (1 day)

 

 

 

5. Make your findings known to the team (1 day)

Technical Paper: Proof of Concept (POC)

Due Week 10 and worth 230 points

Your company is a 4-year-old startup called XYZ Software Enterprises. XYZ produces a point of sale system and was awarded a Proof of Concept (POC) to one of the largest and oldest restaurants in the industry (you know, the ones in the commercials all the time). The restaurant wants XYZ to prove that the software will do what the sales people said it could do.

Your Proof of Concept will include four parts:

· Part 1: Gantt Chart

· Part 2: Testing and User Acceptance Report

· Part 3: Use Case Diagram

· Part 4: Activity Diagram

Part 1: Gantt Chart

A Gantt Chart (see page 353 Figure 11-18) needs to be created for the entire process of the Proof of Concept. There is a two-month deadline from today to complete the POC.

Using Visio or Excel, create a Gantt Chart that includes all of the items listed below and adds five more tasks minimum from the concepts learned from the course:

· The initial meeting — today.

· Should appear as the first line.

· Teams selected to participate in the project (1 week).

· Information gathering (add the information gathering methods you will use and how long each will take).

· System configurations based on information gathering methods (2 weeks).

· Create Activity Chart based on information gathering (info to create chart supplied).

· Create Use Case Diagram based on information gathering (info to create chart supplied).

· Show the finished configurations to the team and get feedback (1 day).

· Make changes based on feedback (3 days).

· Install the system in the test store (2 days).

· Train staff (1 day).

· Run a live test of POC (2 weeks).

NOTE:

· The five or more additional tasks can be subtasks for information gathering methods as well some other subtask or major task not in the initial list.

· You may add items from the SDLC, specific item(s) on testing, or any other concept you think should be part of the POC process learned in the course of this semester.

NOTE: Remember that events in a Gantt chart can happen at the same time as other events. Some items also cannot start until others are completed. Everything has an estimated timeframe and it is displayed in the chart.

 

Part 2: Testing and User Acceptance Report

As part of the expected documentation in the POC, XYZ wants a report on Testing and User Acceptance.

Your manager is asking you to research the testing criteria they listed in the POC documents.

The POC document states that they are looking for:

1. System and Stress Testing

2. User Acceptance Testing (UAT)

For both categories, research and report on:

1. What these tests are.

2. Why the industry leader would want these particular tests.

3. The best ways, in detail, to accomplish the tests so that your company meets the criteria they are looking for.

· These items can be added to your Gantt Chart (Part 1)

Part 3: Use Case Diagram

The restaurant, as part of the information gathering, outlined a use case in a chart (below).

Your manager assigned you to create the Use Case Diagram using Visio, MS Word, or any other software. (See the diagrams on Page 84 and 85 of the textbook.)

· Paste the diagram into the created report.

USE CASE	ACTOR
Order Food	Waiter, Patron, Chef
Serve Food	Waiter
Cook Food	Chef
Pay for food	Waiter, Patron
Eat Food	Patron

 

Part 4: Activity Diagram

As a part of the information gathering process, a chart of items was provided by XYZ.

Your manager has asked that you use Visio, MS Word, or any other software with which you are familiar to create the Activity Diagram (see pages 138 Figure 5-5 and 139 Figure 5-6 in the textbook.)

· Paste the diagram into the created report.

POS SALES PROCESS

Activity Diagram

Host/Hostess seats patron

Server takes drink order

Server opens order for table in POS system

Server places drink order in the POS system

System sends drink order to the Bar

Bar makes drinks

Server brings drinks to table

Server takes food order

Server adds food order in the POS system

Order goes to kitchen

Chef and staff cook the order

Food Runner brings food to table

Server takes dessert order

Server adds dessert order to POS

Chef and Staff create desserts

Food Runner brings desserts to table

Server creates check in POS

Server collects payment and enters it in POS

Server adds tipped amount to POS

Server closes table in POS

Additionally you must:

· Use at least 3 quality resources. NOTE: Wikipedia and similar websites do not qualify as quality resources.

Your assignment must follow these formatting requirements:

· Be typed, double spaced, using Times New Roman font (size 12), with one-inch margins on all sides; citations and references must follow APA or school-specific format. Check with your professor for any additional instructions.

· Include a cover page containing the title of the assignment, your name, the professor’s name, the course title, and the date. The cover page and the reference page are not included in the required assignment page length.

· Include charts or diagrams created in Visio, Word, or an open source alternative. The completed diagrams/charts must be imported into the Word document before the paper is submitted.