CS-319 Object Oriented Analysis and Design - Lecture 12

1
Chapter 20Mapping Designs to Code

• Beware of bugs in the above code I have only
  proved it correct, not tried it. - Donald Knuth

• Objectives
• Map design artifacts to code in an
  object-oriented language.

2
Introduction

• With the completion of interaction diagrams and
  DCDs for the current iteration of the case
  studies, there is more than enough thought and
  detail to cut some code for the domain layer of
  objects.
• The UML artifacts created during design work will
  be used as inpit to the code generation process.
• UP Implementation Model is all the implementation
  artifacts, such as source code, database
  definitions, JSP/XML/HTML pages, and so forth.
• Implementation in an O-O Language requires
  writing source code fo
• Class and interface definitions
• Method definitions.

3
Defining a Class with Method Signatures and
Attributes
Fig. 20.1 SalesLineItem in Java.
4
Creating Methods from Interaction Diagrams
Fig. 20.2 The enterItem interaction diagram.
5
Fig. 20.3 The Register class.
6
Fig. 20.4 The enterItem method.
7
Collection Classes in Code
Fig. 20.5 Adding a collection.
8
Fig. 20.6 Sale.makeLineItem method.
9
Order of Implementation
Fig. 20.7 Possible order of class implementation
and testing.