SE 430: Object-Oriented Modeling

SE 430: Object-Oriented Modeling Mid-term Study Guide

Introduction The mid-term will include material covered during the first five lectures, covering the analysis phase of development and the transition to design. The mid-term will include a variety of different problem types, chosen from the following list: • Matching terms, definitions, and examples. • True/false. • Multiple-choice. • Fill-in. • Short answers. • Word problems with multiple parts. • Identify parts of a diagram. Important disclaimer: This guide is simply a means of giving you some help in studying for the mid- term exam. It is not intended as a comprehensive inventory of every topic discussed in class nor that might be included on the exam. It is the student’s responsibility to be familiar with all the material covered through the fifth lecture and in the homework assignments.

Topics for Study Be sure you understand the material in the following list. Be able to define and give examples for terms and concepts. For techniques, be sure you know the essential steps and their significance. For artifacts, be sure you understand the techniques with which they are associated, their notation, and be able to produce the artifact, if requested. • Types. • Polymorphism—what aspects of typing lead • Classes. to polymorphism. • Objects. • Analysis—general definition. • Abstraction. • Design—general definition. • Encapsulation. • Iterative and incremental approach to software development—benefits and • Hierarchy. advantages over ‘traditional’ approaches. • Typing. • Features of iterative and incremental • Modularity. development—how is it accomplished? • Entity-level abstraction vs. coincidental • Requirements levels—names and usefulness abstraction—characteristics and examples. of each. • Interplay of abstraction and encapsulation. • Techniques and artifacts of requirements • Generalization/specialization. capture. • Aggregation. • Scope – what it is and what it should • Strong and weak typing. contain. • Static and dynamic binding.

of 3 Rev: 5-Oct-16 SE 430: Object-Oriented Modeling Mid-term Study Guide

• Understand what a use case is and how it is • Types of abstractions uncovered in analysis captured. and design phases. Limitations on • Sources of use cases. abstractions in the analysis phase. • User goals and system interactions. • Difference between domain model and domain diagram. • Use cases and scenarios. • Elements of the domain model. • How user goals lead to use cases. • Domain objects/conceptual classes. • Basic use case format: its parts and the purpose and definition of each part. • Class associations. • Primary vs. alternate scenarios. • Class attributes. • Use-case workflow, including techniques • UML class diagram notation and artifacts. o Use of compartments • Actors and types of actors. o Fundamental type vs. associations for • The types of use case formats and their attribute proper roles in the Unified Process. • Draw a domain model diagram with • Difference between use-case model and associations and attributes based on a prose use-case diagram. description. • Components of the use-case model. • Define and give examples of different class • Use-case diagram, including its essential categories. (Note: You need not memorize components. Larman’s conceptual class categories list!) • System boundary: definition and what is • Define and give examples of different class inside and outside of it. association categories. (Note: You need not memorize Larman’s class associations list!) • You should be able to take a prose description of a user/system interaction and • Definition of software architecture. produce a detailed use case with primary • Why software architecture is important. and alternate scenarios. • Definition, elements of, and an example of • Understand the relationship between a an architectural pattern. system sequence diagram and a use-case. • Architectural baseline and architectural • Define the components of system sequence releases, including how they are diagrams. determined. • Draw a system sequence diagram from a • Definition and use of design scenarios detailed use case. (general). • How use case diagrams and system • CRC (Class, Responsibility, Collaborator) sequence diagrams are similar and how they cards—what they are, what they capture, differ. and how they are used. • Decomposition—the types of • Function-Class Decomposition—basics of decomposition and how they compare and the method and what it accomplishes. relate. • Robustness Diagram and its contents and rules

of 3 Rev: 5-Oct-16 SE 430: Object-Oriented Modeling Mid-term Study Guide

of 3 Rev: 5-Oct-16