Task

You've just been hired to write a specification for a computer program! Fabulous $--$but now you have to write a specification. There isn't any code yet and there is no code to be written in this assignment. $($You need to write a specification document!$)$

From initial correspondence with the customer, your coworker has determined the following aspects that need in the first version of the specification document. These are described below under the headings Section I, Section II$,$ and Section III. Ensure such is in your specification document $+$ the $($three$)$ diagrams $+$ accompanying text. Your diagrams must be figures with caption text that explains what each picture $($high$-$level$)$ is without reading the text.

Section I: Use Cases

These are the use cases for this program:

Company staff need to be able to:

Search for products

Place an order

See a customer's orders and history

Customers need to be able to:

Call company staff persons on the phone for help searching $/$ ordering product

Send email to the company to order product

Call company staff persons to ask about any amounts owing.

Section II: Class Diagram

There are at least these classes with the following operations in them:

Database

Search for products function.

Place an order function

Get specific customer order function

Get all customer orders function

CompanyStaff

Search for product function

Place an order from a customer function

Get a specific customer order function

Get all customer orders function

Check emails function

All of these functions should be public. CompanyStaff is dependent on Database. The Database does not exist without the CompanyStaff. $($Hint: That means you want to use a specific kind of "arrow".$)$ There is no inheritance in this diagram.

You will need to make up suitable function names $--$don't use the text given above. Explain the names you used in the text of the specification document in this section.

Section III: Sequence Diagram

The use cases and classes object clearly have operations to be performed. Let's model one of those as a sequence diagram!

A customer triggers company staff by calling them on the phone to ask about amounts they owe $--$let's model such in a sequence diagram. Start by asking yourself which Actors are involved here, e$.$g$.,$ Customer, CompanyStaff, $--$and Database. So create a UML sequence diagram with those as the three lifeline symbols.

Now ask yourself what is involving those actors that is relevant in a sequence diagram given the aforementioned operations above. Draw such in a sequence diagram and discuss such in the body text of that section.

References, Etc.

You don't need a references section as you likely are not citing external document $/$ other's work in this assignment $--$so omit such. That said, ensure your specification has an appropriate title, date, your name as author, and sections with text and diagrams per the above.

Remember: Specification documents are NOT code $--$they are documents to help others understand how something is supposed to be$,$ to work, and to help implement such!