The product backlog is made up of three epics and a total of 18 user stories. Plan the release in a hy
id manner using that
product backlog by first assigning stories to sprints. Use the following premises: (1) Up to ten ideal developer days of work can
e completed by the team in a sprint. (2) EPIC2 is given top priority, followed by EPIC1 and EPIC3. (3) Make sure the MH
stories are written first in an epic, followed by SH, then NH. (4) "Promote" the lower priority na
ative if it is necessary for the
creation of the MH tale but has a lower priority than the MH story.
A) Fill in the numbers of the planned sprints for each story: (1, 2, 3, etc.) in the column labeled "Sprint" that is cu
B) Indicate how many ideal days are expected to be completed for each sprint.
C) Create a flight or agile release plan.
D) If all stories are finished, how many sprints will be needed to finish this product backlog?
E) In how many sprints will this product backlog be finished if just the MH stories are finished?
A busy university campus cafeteria that offers university dining services would like to improve its service and help customers
who want to buy meals online or through a mobile app so they don't have to stand in line while their food is made. The app will
e used by dining service customers on their own. It applies to the cafeteria's sushi, grilled meals, sandwiches, and salad stations.
After placing her order, the customer is supposed to be able to pick up her lunch from the cafeteria at a specific time without
having to wait. The feasting administration needs to utilize the framework to upgrade client assistance and make the most ideal
client experience. As a result, there are a lot of aspects of the food service process that the application could improve.
A) Create a "casual" use case story for this circumstance.
B) The informal use case na
ative from A) should be transformed into a "fully dressed" use case na
ative with at least
three extensions that are in line with your description. Make use of the fully dressed Larman use case.
C) There are undoubtedly a variety of other goals that the university cafeteria service system might assist. The technology
may make it feasible to administer a payment system unique to the institution, control client preferences, provide
management and staff with feedback, promote special offers, particularly for loyal customers, provide dietary advice,
and other things. Make a use case diagram that shows how the system as a whole is related to the use case na
was produced in stages A) and B). Feel free to utilize your imagination and add whatever additional functionality you
elieve would be valuable to such a framework.
The class textbook's system-sequence diagram from figure 5
A) Define the distinction between a design sequence diagram and a system sequence diagram in less than 100 words.
B) Make the design sequence diagram "initiatePickUp(orderN
)" for the message in figure 5. Show the system's reaction
when an order is not yet prepared. Determine the display layer, the business logic layer, and the data layer in you
C) Make a design sequence diagram for the "enterQty(qty)" message in Figure 5 that starts with the cu
esponse. Add all classes in this message and use your understanding of loops to show how the system reacts when the
quantity entered exceeds the upccode's quantity threshold. The classes that make up the display layer, business logic
layer, and data layer should all be indicated on your diagram.
A UML class diagram for an online restaurant ordering system
A) When overlaying packages on the class diagram, choose classes that are logically connected to one another. Choose the
amount of packages that interact with one another the least.
B) Create a UML package diagram that describes the online restaurant ordering system using the packets you found in A).
C) Decide which package the "Customer" class is in. The relational database table classes for this package should be
drawn, with each table's necessary properties clearly indicated. Make that the required characteristics are included in
the abstract classes.
D) Now, in your diagram from C, add the data access and manipulation (DAM) classes to the relational database table