UMass Lowell

Computer Science Department

91.522 Object-Oriented Analysis and Design

http://www.cs.uml.edu/~lechner/91.522/99f522syl.html

INSTRUCTOR: Professor Robert J Lechner

Office: OS220B, 934-3632

Phone: (781)444-8321; email to:lechner@cs.uml.edu

 

COURSE DESCRIPTION:

REQUIRED TEXTS:

• [DMOD]: Sanders: Data Modeling (Boyd-Fraser 1995) (static information models).
• [OLC]: Shlaer & Mellor: "Object Life Cycles: Modeling the World in States" (P-H 1992): (dynamic behavior models).
• [UML]: Martin Fowler: "UML Distilled: Applying the Standard Object Modeling Language" (A-W 1997) (Recommended)
• Selected reprints and project legacy reports. (See http://www.cs.uml.edu/~lechner)

Other useful texts:

[OOSC]: Meyer: "Object-Oriented Software Construction", (2nd edition), P-H 1997 (a required text for course 91.523; the included CD-ROM contains the text and a 60-day evaluation copy of the EIFFEL language and environment.).

Gamma et al: Design Patterns: Elements of Reusable Object-Oriented Software, A-W 1995. (The first of many recent books on O-O software design Patterns)

Shlaer and Mellor: Object-Oriented Systems Analysis: Modeling the World in Data, P-H 1988. (More details on info modeling, summarized in Ch. 2 of OLC)

Kilov and Ross: Information Modeling: An Object-Oriented Approach, P-H 1994. (A rigorous intro.)

Shaw and Garlan: Software Architecture: Perspectives on an Emerging Discipline, P-H 1996. (Surveys the impact of distributed systems on software design.)

Brown: Object-Oriented Analysis: Objects in Plain Englsh, Wiley 1997. (An elementary intro.)

 

PREREQUISITES:

For a list of possible 99f523 project topics, see: http://www.cs.uml.edu/~lechner/91.523/98f523projects.html.

91.522/523 OO-CASE Tool Framework Support:

98F522 OOAD project teams are encouraged to use our locally-developed software engineering framework of portable generic tools, or another OO-CASE environment which can produce portable and maintainable design documentation. (Many tools save proprietary, non-portable formats.) 91.523 project teams are encouraged to re-engineer and enhance this framework.

This framework consists of four generic CASE tool sub-domains BDE, GEN, LCP, BDE2*, and one integrated application, JPsim, which together comprise the CASE Object-Oriented Laboratory (COOL).

1. BDE creates and maintains generic hierarchical block diagram editor for Entity-Relationship, Object Communication and State-Event models. Prototypes exist in C, C++, Visual C++ and Java. Browse or download Bde User Guide from http://www.cs.uml.edu/~lechner/bdeUG2htm/index.htm
2. GEN translates Extended ER diagrams into database support code for maintaining a memory-resident OODB of C structures or C++ classes and an interface to a persistent RDB in ASCII relational table format.
3. LCP (Life Cycle Prototyping) is an executable event-driven software prototyping architecture based on Object Life Cycles. (See hyperlink to COOL below.)
4. JPsim is a non-trivial application of LCP which simulates the Juice Plant example in the OLC text. Click here to inspect its data and state models: (Only browsable locally from Unix) http://www.cs.uml.edu/~lechner/97f522/jp2htm/ksuresh/DEMO/
5. BDE2* is a set of database converters from BDE's generic block diagrams to hyper-linked html files (bde2ht*), to database definitions for GEN (bde2sch), and to state models for LCP (bde2SM).

Click below to browse or download a PowerPoint slide presentation on COOL at htpp://cs.uml.edu/~lechner/COOL/index.htm

Weekly Topic Outline and Assignments - 99f522:

This outline specifies topics to be covered biweekly and relevant reading assignments. Handouts include reprints and project reports are to be read by the next class meeting. Many project reports are online at www.cs.uml.edu/~lechner and under the unix path $CASE = /usr/proj3/case/ in a subdirectory named {toolname/../doc or term/project/../doc}). Each 99f522 student will have a user directory under the semester home directory $CASE/98f522.

Reading assignments follow the template format < Week#: Keynote: <topic list>; Read first: <list of prior handouts and text chapter refs>; Handouts for next meeting: <list> >. The reading assignments present the authors' various perspectives on OOAD. Most differences are incidental. What is important is to understand the common basis underlying all these views and our generic tools. I expect you to peruse the reading assignments at least once before each class and to email a few questions per week to lechner@cs.uml.edu for a FAQ list.

PART I: INFORMATION MODELING CONCEPTS

1. Information Modeling (4 wks): Static and dynamic models; information modeling, cardinality or multiplicity, associative entities; Bachman Data Structure Diagrams(DSDs) and Chen Entity-Relationship Diagrams(ERDs), notational extensions for inheritance and multiplicity; network, relational and O-O databases; using BDE. Read asap: OLC Ch. 1, 2; DMOD Ch.1, 2. Handouts: Browse/download these PowerPoint presentations:

Bde Overview: http://www.cs.uml.edu/~lechner/bdeUG2htm/index.htm

Data Modeling Tutorial : http://www.cs.uml.edu/~lechner/DataModels2htm/index.html

 

Assignment 1: (a) Use bde to draw a DSD called SIS.dat for a course scheduling, student enrollment and transcript archiving database. The database relations should caoture rosters and grades of students enrolled in course sections that are scheduled in specific rooms and timeslots, and taught by faculty of academic departments over multiple semesters. 1(b): manually create a test database called Term99f.dat that could be used for demos and testing.. Due at next week's meeting (99F Week 2)

Deliverables: (a) SIS schema definition as a Data Model Diagram and (b) a sample database called Term99f.dat. (Mandatory inclusions: required attributes and descriptive comments and accurate multiplicity annotations on relation links.

2. Object-Oriented Analysis: Relations and associations; is-part-of aggregation vs. is-a [kind-of] generalization; classes as tables; 1:M relations as foreign keys; abstract/virtual classes; extension/restriction; multiple inheritance; metadata, candidate keys, constraints. Read first: DMOD Ch. 6; OLC Ch. 1, 2; UML Ch. 1,2. Handouts: BDE User Guide, bde2sch report, $CASE/gen/ver_10log User Manual.

Assignment 2: (a) Define the chgen input schema file SIS.sch: (Either run bde2sch/b2s to convert SIS.dat to schema SIS.sch or manually define an equivalent SIS.sch with a text edtor). (b) Run 'chgen -ansi -metafile' on SIS.sch to generate SIS.h and pr*.c database support code. Due in 2 weeks (99F Week 4.)

Deliverables: result of executing this command script (the path to chgen needs to be defined). "whoami; date; pwd; echo GENPATH: $GENPATH; cat SIS.sch; $GENPATH/chgen -ansi -metafile SIS.sch ; ls -l;"

3. Database Applications: persistent data; normalization; Optional-MAX conversion of M:N relationships to associative entities; CHGEN and GENCPP operation. Read first: GENLOG User Manual, DMOD Ch. 3 and Appendix; UML Ch. 3; Handouts: TBD.

Assignment 3: Write a simple GEN-based SIS application to (a) pr_load and pr_dump Term98f.dat. (b) print a class roster (CS-->EN) and (c) print a student grade report (ST-->EN); compile and link it with SIS.h and pr_util.a; show that it operates correctly. Deliverables: source code, compile-time and run-time printouts.

4. Object-Oriented Techniques: Classes are types, runtime instances are objects; virtual classes; inheritance and type conformance; genericity and template classes; static and dynamic typing. Read first: UML Ch. 4;: None.
5. Exam 1 on Data Modeling and chgen (replaces Assignment 4). Review of Assignment 3 Solution; Handouts for next meeting: Microwave Oven, Checking Account and Tone Generator examples; Logic Simulation project report.

 

PART II: STATE-EVENT MODELING CONCEPTS

6. Dynamic behavior modeling: Object Communication models and State-Event models; messages as events; actions as methods; nested state machines; asynchronous behavior. Read first: example handouts; OLCArch User Guide.

Assignment 4: (a) Draw the state machine diagram MOC.dat for the Microwave Oven Controller from the OLC text using BDE, and (b) convert it into a State Model database MOCSM.dat using bde2sm. Deliverables: MOC.dat . Read OLC Ch. 3, 4, 5. Handouts for next meeting: JPSim reports,

7. O-O Prototype Design: OLC Architecture and Operation; specifying operations, actions and constraints. Event trace/thread of control/use case diagrams. Read first: JPsim and OLCArch handouts; OOSC Ch. 19, 20, 36. Handouts: None

Assignment 5: (a) Draw typical Use Cases and an Object Communication diagram for the microwave oven controller state machine in our Object Life Cycles text. (b) Design an OLCArch-based test driver to exercise a multi-oven simulation. Deliverables: Diagrams, test driver main program and source or pseudo-code for the oven controller classes whose instances are rows of your schema tables/

8. Design by Contract: Pre-conditions required of client/caller, post-conditions ensured by server/callee; Read first: Handouts for next meeting: OLC OPerator Class User Guide.

Assignment 6: Augment your program actions (5) and driver (6). with require and ensure assertions. Deliverables: Revised source code.

9. Executable Prototypes: State Model instantiation using Active Instances and Event Instances; Database initialization, change history and checkpointing; OPerator control over reproducible scripts. Read first: JPsim and OLCArch handouts; OLC Ch. 9. ReviewCheck out the Juice Plant data and state models at this URL: http://www.cs.uml.edu/~lechner/97f522/jp2htm/ksuresh/DEMO/index.html

Assignment 7: (a) Adapt your Oven Controller program to use the OPerator class as a simulator controller and stimulus history (script file) reader; (b) Run this program and print the FF state sequence that represents the counter's response to an input sequence of two cooking cases. Deliverables: (a) Source code and Thread of Control diagram (Use Cases), and (b) test run with operator input data and state transition history.

10. Exam 2 on State-Event modeling and OLCArchitecture; Review Assignment 7 Solution. Handouts for next class:: OLC Project docs, chgen and OLCArch reports.

PART III: O-O PROTOTYPING PROJECTS

For a list of possible 99fall project topics, see http://www.cs.uml.edu/~lechner/91.523/99f522projects.html (TBD) and its predecessor http://www.cs.uml.edu/~lechner/91.523/98f523projects.htm.

91.522 GRADING POLICY

(Fall 1999)

Two exams with a combination of in-class and take-home problems will contribute 50%;

Other assignments and two-person software projects will contribute the other 50%.

The following factors will carry approximately equal weight toward project grades:

Problem analysis: (reverse engineering, user guide & interface updates)

Project plan: (work breakdown, incremental build/test plan)

Design specs: (information, communication and state diagrams, events and actions.)

Source code: (history, source code style and robustness)

User & maintenance guides: (version tracking, readability and thoroughness)

Test reports: (specs, coverage, predicted and actual results).

 

OOAD Course BACKGROUND INFORMATION: