1. Dr. Kivanc DincerCS319 Week 11 - Nov.21,20051 Chapter 20 Mapping Designs to Code Objectives Map design artifacts to code in an object-oriented language. “ Beware of bugs in the above code; I have only proved it correct, not tried it.” - Donald Knuth

2. Dr. Kivanc DincerCS319 Week 11 - Nov.21,20052 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 inpıt 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. Dr. Kivanc DincerCS319 Week 11 - Nov.21,20053 Defining a Class with Method Signatures and Attributes Fig. 20.1 SalesLineItem in Java.

4. Dr. Kivanc DincerCS319 Week 11 - Nov.21,20054 Creating Methods from Interaction Diagrams Fig. 20.2 The enterItem interaction diagram.

5. Dr. Kivanc DincerCS319 Week 11 - Nov.21,20055 Fig. 20.3 The Register class.

6. Dr. Kivanc DincerCS319 Week 11 - Nov.21,20056 Fig. 20.4 The enterItem method.

7. Dr. Kivanc DincerCS319 Week 11 - Nov.21,20057 Fig. 20.5 Adding a collection. Collection Classes in Code

8. Dr. Kivanc DincerCS319 Week 11 - Nov.21,20058 Fig. 20.6 Sale.makeLineItem method.

9. Dr. Kivanc DincerCS319 Week 11 - Nov.21,20059 Order of Implementation Fig. 20.7 Possible order of class implementation and testing.