Using the information in the original IEKS Project Vision Document, what you have learned about it for your Deliverable 1, what you have learned about it for your Deliverable 2, what you have learned about it for your Deliverable 3, any updates to the vision document, and the current IEKS Project Vision Document, and any good ideas that come to your minds, develop a list of proposed features for IEKS.
Describe each feature as a use case, i.e., give a simple imperative sentence as if when the user says the imperative sentence as a command, IEKS will obey and do the use case. From this list of features-as-use-cases, you should be able to identify IEKS use cases, as described in the lecture on Scenarios and Use Cases.
The hardest part of this exercise is coming up with a concise, consistent, and complete set of use cases that achieve the alternative ways, specified in the current IEKS Project Vision Document, to start a Prius even with a dead electronic key battery.
You do not have to develop any scenarios yet. However, your imperative sentences must be complete enough that the customer can understand what the feature does. Thus, a phrase, such as ``Facial Recognition'', does not cut the mustard because it does not explain how the driver is using facial recognition to be able to drive the Prius despite the dead electronic key battery.
Build a use case diagram that shows the system boundary, all actors, all use cases and that associates each use case with each actor that may do it. Use the notation of the use case diagram on page 22 of the slides for Classes & Concepts or on the diagram of page 61 of the slides for Scenarios & Use Cases.
You will need to submit both a hard copy AND and an electronic copy of this deliverable: