3 hours

Familiarity with a software process

Knowledge of object-oriented programming concepts, such as encapsulation and inheritance, and of software engineering principles, while not essential, would be an advantage

After this course the student should be able to:
1. distinguish between analysis and design
2. explain the importance of having a software life-cycle process
3. list the advantages of using object orientation
4. describe the role of the UML in analysis and design

3 hours

The course OOAD with the UML: Fundamentals; an understanding of basic software life-cycle principles

To explain how to capture a system's requirements with use cases

After this course the student should be able to:
1. explain what a use case is
2. explain what an actor is
3. describe the process of exploring system behavior through the systematic identification of use cases and actors
4. outline the purpose of problem statements
5. illustrate use cases and actors in use-case models using UML notation

4 hours

Previous courses in the curriculum OOAD with the UML

To outline techniques for finding classes from an initial set of system requirements

After this course the student should be able to:
1. distinguish between objects and classes
2. list the characteristics of a good class
3. identify candidate classes from a use-case flow of events
4. describe boundary, entity, and control class stereotypes
5. group classes into boundary, entity, or control stereotypes
6. draw simple class diagrams in the UML

4 hours

Previous courses in the curriculum OOAD with the UML; a good understanding of object-oriented principles and the role of use-case and object models

To show how to specify object interaction in the UML and to identify associations and inheritance between classes

After this course the student should be able to:
1. describe how to discover object interaction
2. understand how to interpret sequence and collaboration diagrams in the UML
3. describe the types of relationship that can exist between classes
4. add names, roles, and navigation to associations in class diagrams
5. add multiplicity
6. describe how to discover inheritance relationships between classes

4 hours

Previous courses in the curriculum OOAD with the UML

To introduce operations and attributes, state and activity diagrams, and to show the importance of a review of the class model

After this course the student should be able to:
1. find and document operations and attributes for classes
2. describe the purpose of state and activity diagrams
3. read and interpret state diagrams in the UML
4. read and interpret activity diagrams in the UML

3 hours

Previous courses in the curriculum OOAD with the UML

To introduce architectural analysis and design, and the role of key mechanisms

After this course the student should be able to:
1. discuss the importance of a system architecture
2. list the elements of the 4+1 architecture model
3. use component and deployment diagrams

3 hours

Previous courses in the curriculum OOAD with the UML; a good understanding of OOAD; a knowledge of OO programming considerations

To describe the main principles of designing and implementing an object-oriented model

After this course the student should be able to:
1. list the characteristics of well-designed classes
2. discuss the issues relating to designing relationships, attributes, operations, and inheritance
3. specify attribute and operation design details in the UML

4 hours

Previous courses in the OOAD with the UML curriculum; a firm understanding of the UML and object-oriented analysis and design principles

To show the main features of Rational Rose 98 and how to create and maintain use-case, class, and interaction diagrams

After this course the student should be able to:
1. list the main features of the Rational Rose 98 tool
2. use the user-interface, and set options
3. create, update, and save use-case diagrams
4. create, update, and save class diagrams
5. add operations and attribute details to class diagrams

4 hours

Previous courses in the OOAD with the UML curriculum; a firm understanding of the UML and object-oriented analysis and design principles

To show some enhanced features of the Rational Rose 98 tool, including team development

After this course the student should be able to:
1. create, update, and save state transition diagrams
2. manipulate packages
3. create, update, and save component and deployment diagrams
4. understand the principles of team development in Rational Rose 98