Too Tired? Too Anxious? Need More Time? We’ve got your back.
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 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.
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 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 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.
POS SALES PROCESS
Activity Diagram
Host or 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
This course requires the use of Strayer Writing Standards. For assistance and information, please refer to the Strayer Writing Standards link in the left-hand menu of your course.
The specific course learning outcome associated with this assignment is:
Develop a proof of concept of a software system for a potential customer.
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 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.
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 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 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.
POS SALES PROCESS
Activity Diagram
Host or 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
This course requires the use of Strayer Writing Standards. For assistance and information, please refer to the Strayer Writing Standards link in the left-hand menu of your course.
The specific course learning outcome associated with this assignment is:
Develop a proof of concept of a software system for a potential customer.
Too Tired? Too Anxious? Need More Time? We’ve got your back.