Consider the following description of ReMoDD and the requirements listed below it: The ReMoDD (Repository for Model Driven Development) system will be an on-line repository for model driven development artifacts. These artifacts will include models of partial and complete systems, different types of UML models (e.g., class diagrams, sequence diagrams, and the other 9 types of diagrams), modeling patterns, descriptions of modeling notations, modeling exercises for classes, and modeling examples of both good and poor quality, source code for models, test cases for models. Artifacts may come from industry and academic organizations. The repository may be distributed across multiple sites, but all of the artifacts should be accessible via one interface. The objective of the repository is to provide a single point of access to information on Model Driven Development for researchers, industry practitioners, and students. (R1) A non-registered user must register before using the repository. (R2) A repository administrator should be able to authorize user registration. (R3) All registered users should be able to browse the repository according to categories of artifacts, where the categories could be by application domain, stage of development (e.g., requirement versus design-level model), type of artifact (e.g., model, code, test case), academic vs industrial sources. (R4) Each artifact will have a set of possible manipulations, such as viewing a model in a UML editor or image viewer, viewing source code (with keywords highlighted), etc. It is possible for a given artifact to have more than one manipulator. For example, a source code file can be opened in a programming-language specific editor or it can be printed as a PDF file. (R5) A registered user should be able to retrieve artifacts directly from the ReMoDD using one of its manipulators to access it. (R6) A registered user should be able to search for artifacts by keyword, type, and application domain. Part 1 (elicitation) Reading the description and the requirements, which information do you think is missing? Imagining you can integrate your knowledge with an interview, which questions (provide at least 3) would you ask? Part 2 (use cases) Create a use case diagram for the six requirements specified above and document each use case by instantiating the use case template provided below Use Case Template:

Use Case Template: Use Case Primary (essential) or secondan Name ofuse cases that the current use case includes (common goal shared by 2 or more ise cases Name of use cases that the current use case extends (the name of the normal scenario use case that the current use case extends Type Includes Extends Cross-refs mber of requirement that the current use case addresses Enumerate use cases that are dependent upon the current one. Use cases Use Case Template: Use Case Primary (essential) or secondan Name ofuse cases that the current use case includes (common goal shared by 2 or more ise cases Name of use cases that the current use case extends (the name of the normal scenario use case that the current use case extends Type Includes Extends Cross-refs mber of requirement that the current use case addresses Enumerate use cases that are dependent upon the current one. Use cases