In Homework 1, you created the Specification for DoMore Software’s “Dolendar” pr

In Homework 1, you created the Specification for DoMore Software’s “Dolendar” product. However, for that assignment, you skipped the “heart” of the specification: the Functional Requirements section. In this assignment, you will complete the previous document by providing the Functional Requirements section.
Your Functional Requirements section should include:
A description of all of the functionality described by the customer that they want to be part of the contracted software product (i.e., not future directions). You can decompose these functionalities in multiple ways, but just be sure to describe all of the functionality that the customer decided that they wanted in the end.
Two use cases. Both of these should at least include the basic flow. These are textual descriptions with a user goal and a series of steps that make up the “flow”.One of these use cases should involve only the primary actor and the system. It should include a basic flow, an alternative flow, and an exception flow.
One of these use cases should involve a primary actor (i.e., the actor who has the “goal” of the use case), another actor, and the system. This one may only include a basic flow. In other words, I am not requiring an alternative flow nor exception flow for this one.
A use case diagram. This use case diagram should include all actors (again, make sure you learn about use cases from the slides and lecture videos) and a comprehensive list of use cases (or at least, as comprehensive as you can readily think of) and make sure that they include the two above use cases.
Notes:
– I have attached a transcript of Dolenar’s customer interview
– I have attached my initial requirements document
Scoring Breakdown
Functional Requirements section: 100 pointsFunctional Requirements: 50 points
Use Case 1: 20 points
Use Case 2: 10 points
Use Case Diagram: 20 points