Ooa - Object-Oriented Analysis CSC305 Fall 2004 Due Date Wednesday October 20th in Lab Instructor/TA Signature The object-oriented analysis

Info iconThis preview shows page 1. Sign up to view the full content.

View Full Document Right Arrow Icon
Object-Oriented Analysis CSC305 – Fall 2004 Due Date: Wednesday, October 20th, in Lab Instructor/TA Signature The object-oriented analysis document is composed of two major sections: Use Case Analysis Conceptual Class Model Use Case Analysis: Each scenario in your requirements document needs to be covered by the use case analysis. First you need to convert each scenario in your requirements document into a use case text (or make it part of an existing use case text). If your requirements document does not contain any scenarios you will need to derive use case texts from the requirements document directly. A use case text is a numbered sequence of interactions between actors and the product/system. Once you have derived the use case texts you will need to build a use case diagram for each use case text. Use the standard UML notation for use case diagrams explained in class. Your OOA document should include both the use case texts and the corresponding use case diagrams. Conceptual Class Model:
Background image of page 1
This is the end of the preview. Sign up to access the rest of the document.

This note was uploaded on 10/03/2011 for the course CSC 592 taught by Professor Staff during the Spring '11 term at Rhode Island.

Ask a homework question - tutors are online