Class project website design homework help
A local entrepreneur is partnering with a bakery to produce a website that customers can use to order custom cakes. The customer will use a web browser to access a website, and from there may specify the type of cake (white, chocolate, or marble, perhaps more options in the future), color of frosting picked from a list the bakery carries, and provide a custom message. Further the customer may select a cake that is themed to currently popular childrenâ€™s television shows or recent cartoon movies.
Once an order is paid, the order will be routed to the bakery so they can produce it. Typically the bakery will hold the order for pickup; however the entrepreneur wants to offer a service where the cake can be delivered for an additional fee. Further the entrepreneur wants to give the customer the option to select common extras at the same time they purchase the cake. Right now he has a deal to provide balloons for purchase and possible delivery with the cake, but other extras may be available in the near future.
To complete this assignment, make assumptions as needed–just be sure to document any assumptions you make. Remember: “When in doubt sound convincing.”
- Identify the following information about the Custom Cake ordering application:
- Purpose or goal of the system. Please make this at least a paragraph.
- Primary user(s) of the system. This must include all users that will be referenced in your work and must also include a description of each user.
- Generate an Activity UML diagram that starts with the customer connecting with the web site and ends with the order available for pickup or delivered to a driver who would also receive the address (along with the food). I am looking for a very focused and specific UML Activity diagram here. I want the diagram to show me the process of what happens between the time that the customer connects to the website and the order is complete.
Note that the bakers will also interact with the process at some point – identify the step or steps where the baker interacts with the system. *** Number each element of the activity diagram. *** The activity diagram must contain a minimum of 10 elements.
- Using the activity diagram created for step 2, generate 15 User stories, each with 2 acceptance criteria (30 acceptance criteria total). See assignment 4.1 for details.
For each User story, identify the User (customer, baker, or driver, or as you specified in item1b above), and the element of the activity diagram you are using to generate this user story. The user stories must be of the form “As a
I need to
4.4. Convert the User stories from step 3 into User Requirements. Convert the acceptance criteria into System Requirements. NOTE: ALL REQUIREMENTS MUST BEGIN WITH “The system shall…”. See assignment 5.2 for details.
- Produce a Use Case UML diagram that contains a minimum of the Customer, the Baker, and the Driver. Review the User stories from step 3 for ideas as to the features to include in the Use Case diagram, but all features need not be included.
- Using the system requirements from step 4, produce 20 system tests. (See assignment 8.3).
- Identify whether a plan-driven “waterfall” software development approach or an agile framework or methodology might be more suitable for this software development project. Explain your recommendation.
- Identify at least five evolution and maintenance related items that should be considered when planning to develop the Custom Cake ordering software application.
- Identify ten or more SOFTWARE DEVELOPMENT risks that could develop with this project. What is the probability or likelihood that each risk might occur, and what would be the effect to your Custom Cake ordering application if it did? What is your plan to avoid, minimize or recover from (i.e., contingency plan) each of these risks if they were to occur? Present your risk analysis as a Risk Register in a tabular format, with the highest impacts/effects listed first.
- Assume that SCRUM is being used for this project. Rank your user stories from number 3 and assign them to four different two week sprints. Identify which user stories should be completed in each sprint. See assignment 4.1 for the format. If you lost points on the formatting of the sprint backlog, please figure it out now or you will lose some more for this assignment.
NOTE 2: Please see the items above that I have taken the effort to BOLD. If you ignore instructions that are BOLDED you WILL LOSE POINTS!