卡耐基.docVIP

OOA Define user roles. Write a short text or Word document that describes the different types of users and/or system agents that play a role in the operation of the software product. Create a use case diagram in UML. Using UML syntax, create a UML diagram illustrating the use cases you have identified for the software product. Write use case scenarios. Write appropriate normal and abnormal use case scenarios for each use case you identified in the use case diagram. Noun extraction: Analyze the use case scenarios that you wrote in Exercise 3, using the noun extraction technique to create a preliminary class list for the product. Preliminary class diagram in UML: Create a preliminary class diagram in UML, based on the preliminary class list. If one of the candidate classes on the list is not modeled as a class in the diagram (as per the class list refinement principles explained in 4.3.1), provide an explanation. State transition diagram in UML: Create a state transition diagram for the product, using the UML notation. OOD Sequence diagram in UML: Using UML notation, create a sequence diagram for each of the use case scenarios you created in Exercise 3. Collaboration diagram in UML: Using UML notation, create a collaboration diagram for each use case scenario you created in Exercise 3. Detailed class diagram: associate each of the messages identified in the interaction diagrams with particular classes. Update your class diagram to include this information about the messages (methods) for each class. Module interface specification: Update your class diagram to include typed arguments and a return type, where appropriate, for each of the methods you identified in Exercise 5. Skeletal class files: For each class in your class diagram, create a skeletal Java file containing the class definition, with empty signatures for the constructor(s) and method(s) in the class. Include all of the information about arguments and return types that you gathered in the module