Order from us for quality, customized work in due time of your choice.
Overview
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.
Your Proof of Concept will include four parts:
Part 1: Maintenance.
Part 2: Gantt Chart.
Part 3: Use Case Diagram.
Part 4: Activity Diagram.
Instructions
Include the following components in your Week 10 Technical Paper: Proof of Concept (POC) Assignment Template [DOCX] Download Week 10 Technical Paper: Proof of Concept (POC) Assignment Template [DOCX].
Part 1: Maintenance
Software maintenance is the process of modifying and updating the software after it has been provided to the customer. The different types of maintenance for new software include adaptive, perfective, and preventive maintenance.
Write a half-page summary of these different types of new software maintenance in which you briefly describe what each is and explain the pros and cons of each.
Use two sources to support your writing. Choose sources that are credible, relevant, and appropriate. Cite each source listed on your source page at least one time within your assignment. For help with research, writing, and citation, access the library or review library guides.
Part 2: Gantt Chart
Create a Gantt chart (see Figures 3.3 and 3.4 in your textbook) 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 an activity chart based on information gathering (information to create chart supplied; 2 days).
Create a 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.
Part 3: Use Case Diagram
The restaurant, when gathering information, outlined a definition document to be used to create the use case diagram. There are three actors: Waiter, Patron, and Chef. There are 5 use cases; these are the ovals in the example, Figure 6-15 in the textbook. In this use case, all the arrows point from the actors to the use cases.
Create a use case diagram from the chart below, including all use cases and actors.
Use Case DiagramUSE CASEACTOROrder FoodWaiter, Patron, ChefServe FoodWaiterCook FoodChefPay for foodWaiter, PatronEat FoodPatron
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 create the activity diagram. (See Figure 6-21 in the textbook.) This diagram should not be one long snake. You can order drinks and reorder more drinks at any point during the dinner service.
Create an activity diagram from the chart below, including people and systems steps and options from the supplied chart or all POS.
Activity Diagram ChartPOS SALES PROCESS
Activity Diagram
Host or Hostess seats patronServer takes drink orderServer opens order for table in POS systemServer places drink order in the POS systemSystem sends drink order to the BarBar makes drinksServer brings drinks to tableServer takes food orderServer adds food order in the POS systemOrder goes to kitchenChef and staff cook the orderFood Runner brings food to tableServer takes dessert orderServer adds dessert order to POSChef and Staff create dessertsFood Runner brings desserts to tableServer creates check in POSServer collects payment and enters it in POSServer adds tipped amount to POSServer closes table in POS
This course requires the use of Strayer Writing Standards (SWS). The library is your home for SWS assistance, including citations and formatting. Please refer to the Library site for all support. Check with your professor for any additional instructions.
The specific course learning outcome associated with this assignment is:
Develop a proof of concept of a software system for a potential customer.
Order from us for quality, customized work in due time of your choice.