Masters of Science in Software & Information Systems



Similar documents
BCS Certificate in Systems Modelling Techniques Syllabus

Object-Oriented Systems Analysis and Design

Object-oriented design methodologies

In this Lecture you will Learn: Systems Development Methodologies. Why Methodology? Why Methodology?

Object-Oriented Design Guidelines

Software Design Models, Tools & Processes *

Karunya University Dept. of Information Technology

3C05: Unified Software Development Process

Software Engineering. System Models. Based on Software Engineering, 7 th Edition by Ian Sommerville

(BA122) Software Engineer s Workshop (SEW)

Announcements. SE 1: Software Requirements Specification and Analysis. Review: Use Case Descriptions

What is a life cycle model?

Object Oriented Design

A UML Introduction Tutorial

Assuming the Role of Systems Analyst & Analysis Alternatives

Questions? Assignment. Techniques for Gathering Requirements. Gathering and Analysing Requirements

Contents. Introduction and System Engineering 1. Introduction 2. Software Process and Methodology 16. System Engineering 53

Decomposition into Parts. Software Engineering, Lecture 4. Data and Function Cohesion. Allocation of Functions and Data. Component Interfaces

Object Oriented Analysis and Design and Software Development Process Phases

Object-Oriented Modeling and Design

Software Design Document (SDD) Template

GUJARAT TECHNOLOGICAL UNIVERSITY, AHMEDABAD, GUJARAT. COURSE CURRICULUM COURSE TITLE: FUNDAMENTALS OF SOFTWARE DEVELOPMENT (Code: )

Designing Real-Time and Embedded Systems with the COMET/UML method

Lecture Overview. Object-Oriented Software Engineering: Using UML, Patterns, Java, and Software Development Processes. Prof. Dr.

Software Engineering

PROJECT MANAGEMENT METHODOLOGY OF OBJECT- ORIENTED SOFTWARE DEVELOPMENT

Information systems modelling UML and service description languages

ISSUES OF STRUCTURED VS. OBJECT-ORIENTED METHODOLOGY OF SYSTEMS ANALYSIS AND DESIGN

PROGRAMME SPECIFICATION POSTGRADUATE PROGRAMME

Chapter 8 Approaches to System Development

Department of Information Technology ENTD311: Analysis and Design of Information Systems 3 Credit Hours 8 Weeks Prerequisite(s): None

1. Software Engineering Overview

Unit 1 Learning Objectives

The Unified Software Development Process

Fundamentals of Information Systems, Fifth Edition. Chapter 8 Systems Development

A Comparison of SOA Methodologies Analysis & Design Phases

Communication Diagrams

RUP Design. Purpose of Analysis & Design. Analysis & Design Workflow. Define Candidate Architecture. Create Initial Architecture Sketch

UML SUPPORTED SOFTWARE DESIGN

Unit I Page No. 1 System Development Object Basics Development Life Cycle Methodologies Patterns Frameworks Unified Approach UML

Basic Unified Process: A Process for Small and Agile Projects

IST639 Enterprise Technologies Course Syllabus Spring 2014

Use Cases. Massimo Felici. Massimo Felici Use Cases c

LONDON SCHOOL OF COMMERCE. Programme Specification for the. Cardiff Metropolitan University. BSc (Hons) in Computing

Object Oriented Programming. Risk Management

CS 389 Software Engineering. Lecture 2 Chapter 2 Software Processes. Adapted from: Chap 1. Sommerville 9 th ed. Chap 1. Pressman 6 th ed.

Software Specification and Architecture 2IW80

System Modeling / Class Diagra Diagr m a Week 6

Adapted for a textbook by Blaha M. and Rumbaugh J. Object Oriented Modeling and Design Pearson Prentice Hall, 2005.

Chap 1. Introduction to Software Architecture

4. Multiagent Sys stems Design. Part 2: The PROMETHEUS methodology.

UML: Unified Modeling Language

SOFTWARE PROCESS MODELS

Aspect Oriented Strategy to model the Examination Management Systems

Digital Industries Trailblazer Apprenticeship. Software Developer - Occupational Brief

Incorporating Aspects into the UML

Modellistica Medica. Maria Grazia Pia, INFN Genova. Scuola di Specializzazione in Fisica Sanitaria Genova Anno Accademico

Component Based Development in Software Engineering

How To Understand The Software Development Lifecycle

A Proposal for Constructing Relational Database from Class Diagram

Programme Study Plan

Organization. Introduction to Software Engineering

City University of Hong Kong Course Syllabus. offered by Department of Computer Science with effect from Semester A 2015/16

Menouer Boubekeur, Gregory Provan

How To Design Software

PROGRAMME SPECIFICATION POSTGRADUATE PROGRAMMES. Programme name Project Management, Finance and Risk

Design methods. List of possible design methods. Functional decomposition. Data flow design. Functional decomposition. Data Flow Design (SA/SD)

PROGRAMME SPECIFICATION POSTGRADUATE PROGRAMMES. Programme name MSc Project Management, Finance and Risk

2667A - Introduction to Programming

Software Engineering. Software Processes. Based on Software Engineering, 7 th Edition by Ian Sommerville

Tool Support for Software Variability Management and Product Derivation in Software Product Lines

User experience storyboards: Building better UIs with RUP, UML, and use cases

BCS THE CHARTERED INSTITUTE FOR IT. BCS HIGHER EDUCATION QUALIFICATIONS BCS Level 5 Diploma in IT SYSTEMS ANALYSIS & DESIGN EXAMINERS REPORT

Algorithms, Flowcharts & Program Design. ComPro

BCS Professional Certificate in Benefits Planning and Realisation Syllabus. Version 1.0 October 2015

Applying 4+1 View Architecture with UML 2. White Paper

Chapter 3 Chapter 3 Service-Oriented Computing and SOA Lecture Note

The Tropos and MaSE Agent-Oriented Software Engineering Methodologies. Msury Mahunnah, Tallinn University of Technology

Masters in Information Technology

Use Cases. Reference: Craig Larman, Applying UML and Patterns, Ch. 6

School of Computer Science

TOGAF usage in outsourcing of software development

The Business Process Model

TRADITIONAL VS MODERN SOFTWARE ENGINEERING MODELS: A REVIEW

Chapter 1 - From Beginning to End: An Overview of Systems Analysis and Design Lecture Notes

Institute of Research on Information Systems (IRIS) Course Overview

The Online Grade Book A Case Study in Learning about Object-Oriented Database Technology

City of Dublin Education & Training Board. Programme Module for. Mobile Technologies. leading to. Level 6 FETAC. Mobile Technologies 6N0734

How To Understand Software Engineering

CHAPTER_3 SOFTWARE ENGINEERING (PROCESS MODELS)

MASSEY UNIVERSITY BACHELOR OF ENGINEERING with HONOURS TELECOMMUNICATIONS AND NETWORK ENGINEERING. Major Profile Description and Competency Framework

Course Computer Science Academic year 2012/2013 Subject Software Engineering II ECTS 6

IOM433 Creative Information Systems Analysis and Design Spring 2006 T/Th 2-3:50 HOH406 (Labs meet in HOH401)

Software Requirements Specification of A University Class Scheduler

System development lifecycle waterfall model

Kentico CMS 5 Developer Training Syllabus

Transcription:

Masters of Science in Software & Information Systems To be developed and delivered in conjunction with Regis University, School for Professional Studies Object Oriented Design Table of Contents January 2009

Topic Page Number Module Details 3 Course Outline 5 Workshop 1 8 Workshop 2 10 Workshop 3 12 Workshop 4 14 Workshop 5 16 Workshop 6 18 Workshop 7 20 Workshop 8 22 Appendices 23

Section 2 Programme Title: Module Details M.Sc. in Software and Information Systems Module Name: Object Oriented Design Course Description: This module will build on the knowledge acquired by students in their software engineering module, and provide a comprehensive introduction to the field of Object Oriented Design and the Unified Modeling Language (UML). Students will be introduced to the various object oriented analysis and design techniques which have developed over time, and will learn the industry-standard notation, UML (Unified Modeling Language). This industry standard notation is covered from its original inception, through its various constituent models, and on to its practical use in systems development (Note: this module is based on UML2, the latest version of the UML notation, approved in 2004). The application of UML is explored from analysis through design and on to final system implementation, highlighting the strengths of object orientation as an approach to systems development where the one notation is used throughout. Students will develop object oriented analysis and design models using Computer Aided Software Engineering (CASE) tools, similar to those developed in the software engineering module. The challenges of progressing seamlessly from system inception, through analysis, solution design and technical implementation will be addressed, while maintaining a focus on the delivery of a quality system within timescale and budget. Prerequisites: Students taking this module will already have completed the software engineering module, and the system analysis and design techniques learned therein will provide a sound basis for the new systems development material presented in this OOD module. Some students may have already taken object oriented programming as an optional module, and this module will build on the object oriented concepts covered there, providing a broader view of the use of object orientation in the whole systems development process, as opposed to the OOP focus on code development and implementation. The object oriented programming module is not a prerequisite for this module, however, and object oriented concepts will be covered in the introductory section of this course.

Course Objectives: At the end of the module, students are expected to be able to competently: Discuss and explain general concepts related to Object Orientation and particularly Object Oriented Analysis and Design. Gather a clear set of requirements from clients for a software system. Analyse a business requirements, and develop an object oriented domain model from those requirements, clearly identifying the domain classes. On further analysis, progress from the domain model to an object oriented application model for those requirements, clearly identifying the application artefacts required. Evaluate the potential for reuse in the design of a system solution: from patterns to commercially available components. Produce an object oriented design model for the proposed system solution. Prepare relevant UML implementation models for this system solution. Evaluate issues related to the implementation of the proposed system wrt resource usage, security, maintenance and performance. Compare the Unified Process with agile process approaches. Required Texts: Selected chapters and sections from the following two texts will be presented as part of the core content of this module: Object-Oriented Modeling and Design with UML, by Michael Blaha and James Rumbaugh. Second Edition, UML2 (International Edition). 2005 Pearson Prentice Hall. ISBN: 0-13-196859-9 UML 2 and the Unified Process, Second Edition Practical Object-Oriented Analysis and Design, by Jim Arlow and Ila Neustadt. 2005 Pearson Education Ltd. ISBN: 0-321032127-8 Course Emphasis on Fundamental Skills: This course emphasises the development of object oriented systems analysis and design skills, specifically UML2 techniques, by the individual student (Class Models, State Models, Interaction Models, Use Case Models, and system design

and implementation diagrams) for use throughout the Systems Development Lifecycle (SDLC). These skills are taught within the overall context of quality systems development. Students complete their lab exercises using their Citrix account in the selected Computer Aided Software Engineering (CASE) tool (most likely Rational Rose). Accounts will be assigned to all students by the facilitator at the beginning of the module. Course Assignments: Student assessment will take the form of: - Weekly assessments to be completed, sometimes in the Virtual Lab - A Final Exam consisting of both practical OOD tasks and theoretical questions Grading: The balance of these marks reflects overall degree requirements and specific workshop assignments/labs within this module. Assignment Weight Workshop Participation 15% 1-8 Final Exam 25% 8 Weekly assessments 60% 1-7 Total 100%

Course Outline: Workshop Text Reading Topics Assessments to be completed Workshop 1 Object-Oriented Modeling and Design with UML Chapters 1 and 2 Introduction to Object Oriented Design Research Assignment: Software Process Workshop 2 UML2 and The Unified Process Chapter 1 Object-Oriented Modeling and Design with UML Chapter 7, Section 7.1; Chapter 8: Section 8.1 Introduction to the Unified Modeling Language (UML) Problem Statements: Requirements Domain Analysis: Use-Case Models Assignment: Use Case Model to be completed for problem statement Workshop 3 UML2 and The Unified Process Chapters 3, 4, 5 Object-Oriented Modeling and Design with UML Sections of Chapters 3 and Chapter 4 UML Class Model Assignment: Class Modeling exercise to be completed using CASE tool Workshop 4 UML2 and The Unified Process Sections of Chapters 6, 7, 8, 9, 10 and 11 Object-Oriented Modeling and Design with UML Chapter 7: Sections 7.2 and 7.3, Chapter 8: Sections 8.2 and UML Interaction Model UML Activity Diagrams Assignment: Interaction Model to be completed for exercise using CASE tool.

8.3. Chapters 12 and 13. Workshop 5 UML2 and The Unified Process Chapter 12, and Chapter 13 Object-Oriented Modeling and Design with UML Parts of Chapters 5 and 6, Chapter 7: Section 7.3 UML State Model Analysis Case Study: Restaurant System Assignment: State Modeling assignment to be completed using CASE tool Workshop 6 Workshop 7 Workshop 8 UML2 and The Unified Process Chapter 14 Object-Oriented Modeling and Design with UML Chapter 14 UML2 and The Unified Process Chapters 16, 19 Object-Oriented Modeling and Design with UML Chapters 15, 17, 18, 19 UML 2 and The Unified Process Chapters 17, 18, 23, and 24 Object-Oriented Modeling and Design with UML Chapter 21 System Design: Architecture and Patterns System Design: HIC, TMC, DMC Detailed Class Design OO Implementation: UML implementation Diagrams Implementation: Languages and Databases Comparison of OO and other lifecycle approaches Revision Final Examination Research Assignment: Design Patterns Assignment: Create Implementation model for assignment using CASE tool. Assignment: Final Exam

Section 3 Workshop Syllabus Workshop One: Introduction to Object Oriented Design and UML2: Assignments/readings to be completed before Workshop 1: 1. Read Object-Oriented Modelling and Design with UML Chapters 1 and 2 UML2 and The Unified Process Chapter 1 List of topics for Workshop One: Object oriented constructs and themes. Object oriented modelling and design. Object oriented modelling history. UML and UML2. UML Common Mechanisms. The three models: class, state and interaction. The Unified Process Course objectives for Workshop One: Upon completion of this workshop students will be able to competently: 1. Define what is meant by object orientation 2. Define UML 3. Explain key concepts of object oriented approaches to systems development 4. Recognise the difference between object oriented implementation and object oriented development 5. Explain the evolution of UML 2, describing the progression from several disparate methodologies to one standard notation 6. Define each of the following models: a. Class Model b. State Model c. Interaction Model 7. Distinguish between the three different system models and recognise their overlap 8. Explain the UML s four common mechanisms 9. Describe the application of these common mechanisms throughout UML

10. Define the Unified Process 11. Describe the Unified Process and how it can be applied on a project Suggested Activities/Progress Checks/Review Questions: 1. Facilitator leads review/discussion of readings 2. Students conduct research relevant to assignment 3. Facilitator hands out assignments Lab Exercises for Workshop One: There are no lab requirements for Week one. Assignment(s) for Workshop One: 1. Research Assignment: Find out what you can about the differences between heavyweight and lightweight or agile software process methodologies, paying particular attention to the Unified Process.

Workshop Two: System Requirements and Use Case Model Assignments/readings to be completed before Workshop Two: 1. Complete Week 1 assignments 2. Read: Object-Oriented Modeling and Design with UML Chapter 7, Section 7.1; Chapter 8: Section 8.1 UML2 and The Unified Process Chapters 3, 4, 5 List of topics for Workshop Two: Requirements Analysis Requirements Analysis in UP Types of Requirements Requirements modeling Use Case Models Use Case Diagrams (UML Notation): Actors, Use Cases and Relationships Use Case Descriptions and Scenarios Use Case Modeling Process Advanced Use Case Relationships: includes, extends, and generalisation Course Objectives for Workshop Two: Upon Completion of this workshop, students are expected to competently: 1. Describe the importance of effective requirements engineering (collection and analysis) to system success 2. Identify the primary inputs and outputs of requirements analysis 3. Define the different types of system requirements 4. Compare the UML requirements model with the more traditional requirements model 5. Define use cases and use case diagrams 6. Explain the role of the use case view in the UML system architecture 7. Define scenarios and their use throughout UML modelling 8. How do you go about finding use cases? 9. Analyse problem descriptions and identify the use cases and actors therein 10. Construct UML use case diagrams 11. Create a web of scenarios for each use case

12. Identify the difference between an extend relationship and an include relationship between use cases Suggested Activities/Progress Checks/Review Questions: 1. The facilitator reviews week 1 questions with the students. 2. The facilitator leads a review of week 2 readings. 3. The facilitator hands out Week 2 assignments. 4. The students complete their assignment using their lab accounts. Lab Exercises for Workshop Two: 1.Students complete the introduction to Rational Rose tutorial using their lab accounts. 2. Students complete the models for Week two s assignment using Rational Rose. Assignment(s) for Workshop Two: 1. Complete Week 2 lab tutorial (as above). 2. Complete Week 2 assignment(s): Use Case model to be produced using Rational Rose.

Workshop Three: Class Model Assignments/readings to be completed before Workshop Three: 1. Complete Week 2 assignment 2. Read: Object-Oriented Modeling and Design with UML Chapter 3 and Chapter 4 UML2 and The Unified Process Chapter 7 and Chapter 8 List of topics for Workshop Three: Objects and Classes Class Diagrams (UML Notation) Finding Classes (CRC) Values and Attributes Operations and Methods Links and Associations Multiplicity Generalisation and Inheritance Abstract Classes Packages (Arlow and Neustadt chapter 11) Testing Course Objectives for Workshop Three: Upon completion of workshop three, students will be able to competently: 1. Define an object and class 2. Explain the representation of classes (attributes, operations and interactions) in class diagrams 3. Describe UML class diagram notation 4. Analyse problem descriptions and identify the classes and their associated attributes therein 5. Identify the operations required by these classes 6. Be able to identify the interactions between the classes and the required relationships between them 7. Construct UML class diagrams from the above 8. Create hierarchies of classes using generalisation and inheritance 9. Define UML packages

10. Define dependencies between packages 11. Apply packages to systems analysis problems to organise the system solution 12. Test class model against user expectations 13. Navigate through Rational Rose 14. Open projects and create class diagrams in Rational Rose Suggested Activities/Progress Checks/Review Questions: 1. The facilitator reviews week 2 questions with the students. 2. The facilitator leads a review and discussion of week three s assigned readings. 3. The facilitator hands out Week 3 assignment: 4. The students complete their assignment in Rational Rose using their lab accounts. Lab Exercises for Workshop Three: 1. Complete the Class model, using Rational Rose, for week three s assigned exercise. Assignment(s) for Workshop Three: 1. Complete Week 3 assignment: Class model to be produced using Rational Rose

Workshop Four: Interaction Model Assignments/readings to be completed before Workshop Four: 1. Complete Week 3 assignments 2. Read: Object-Oriented Modeling and Design with UML Chapter 7: Sections 7.2 and 7.3, Chapter 8: Sections 8.2 and 8.3. Chapters 12 and 13. UML2 and The Unified Process Chapter 12, and Chapter 13 List of topics for Workshop Four: Application Model Modeling dynamic system behaviour Interaction Diagrams Sequence Diagrams Testing Course Objectives for Workshop Four: Upon completion of workshop five students will be able to competently: 1. Define sequence diagrams 2. Explain the use of interaction diagramming in UML 3. Describe UML sequence diagram notation 4. Identify relationship between use case diagrams and sequence diagrams 5. Construct UML sequence diagrams for each use case 6. Test interaction diagrams against user expectations 7. Create sequence diagrams in Rational Rose 8. Define activity diagrams and their role in UML 9. Define activities 10. Define the three types of node: a. action b. control and c. object

Suggested Activities/Progress Checks/Review Questions: 1. The facilitator reviews week three questions with the students. 2. The facilitator leads a review of the readings for week four. 3. The facilitator hands out week four s assignment: 4. The students complete their assignment using Rational Rose in their lab accounts. Lab Exercises for Workshop Four: 1. Complete the models, using Rational Rose, for week four s assigned exercise. Assignment(s) for Workshop Four: 1. Complete Week 4 assignment(s): Interaction model to be produced using Rational Rose.

Workshop Five: State and Activity Models Assignments/readings to be completed before Workshop Five: 1. Complete Week 4 assignments 2. Read: Object-Oriented Modelling and Design with UML Chapter 5 and Chapter 6 (leave out sections 6.3 and 6.) UML2 and The Unified Process Chapter 21 and Chapter 22 (leave out sections 22.3, 22.4 and 22.5) List of topics for Workshop Five: State Model and Object Behaviour Events and States Transitions and Conditions State Diagrams (UML Notation) Nested State Diagrams Relation of Class and State models Relation of all Analysis models Relationship among UML models System Analysis: Domain and Application Models Analysis Case Study Course Objectives for Workshop Five: Upon completion of workshop five students will be able to competently: 1. Define events and states 2. Define transitions and conditions 3. Define state diagram activities 4. Explain the integration of all above elements in state diagrams 5. Describe UML state diagram notation 6. Analyse problem descriptions and identify the various changes of state for each class with important temporal behaviour 7. Identify the events and responses to events for these state changes 8. Construct UML state diagrams for these classes 9. Create nested state diagrams

10. Test state model against user expectations 11. Create state diagrams in Rational Rose 12. Define a domain model and its associated components 13. Analyse a set of requirements and identify the key classes, and their attributes, behaviour, interactions 14. Construct a domain model for a set of re quirements 15. Construct an application model from the domain model for a set of requirements 16. Test domain and application models against user requirements Suggested Activities/Progress Checks/Review Questions: 1. The facilitator reviews week 4 questions with the students. 2. The facilitator leads a review and discussion of week five s assigned readings. 3. The facilitator hands out Week 5 assignment: State Model. 4. The students complete their assignment using Rational Rose in their lab accounts. Lab Exercises for Workshop Five: 1. Complete the models, using Rational Rose, for week four s assigned exercise. Assignment(s) for Workshop Five: 1. Complete Week 5 assignment(s): State model to be produced using Rational Rose

Workshop Six: System Design Assignments/readings to be completed before Workshop 6 1. Complete Week 5 assignments 2. Read: Object-Oriented Modeling and Design with UML Chapter 14 UML2 and The Unified Process Chapter 16 and Chapter 19 List of topics for Workshop Six: System Design Architecture: Packages, Subsystems Subsystems and concurrency Reuse: Frameworks, Patterns, Components Design Patterns UML Human Interaction Component UML Data Management Component UML Task Management Component System Testing Course Objectives for Workshop Six: Upon completion of this workshop students will be able to competently: 1. Define object oriented system design and distinguish it from OO analysis 2. Define frameworks and patterns 3. Create a high level strategy for solving the analysed problem the system architecture 4. Estimate system performance 5. Identify useful design patterns and describe their contribution to system design 6. Make a reuse plan 7. Organise a system solution into subsystems 8. Identify system concurrency 9. Manage data stores 10. Manage system boundaries 11. Design UI classes to handle human interaction 12. Test system design and simulate its performance

13. Identify common architectural styles and their relative merits 14. Select appropriate architectural styles for different system implementation problems Suggested Activities/Progress Checks/Review Questions: 1. Facilitator reviews questions from workshop 5 with the students. 2. Facilitator leads review/discussion of readings for week 6. 3. Facilitator hands out assignment(s) for workshop 6. 4. The students complete their research assignment for Week 6. Lab Exercises for Workshop Six: 1. There are no lab requirements for this week. Assignment(s) for Workshop Six: 1. Complete Week 6 research assignment(s) on Design Patterns.

Workshop Seven: Detailed Design and System Implementation Assignments/readings to be completed before Workshop 7 1. Complete Week 6 assignments 2. Read: Object-Oriented Modeling and Design with UML Chapters 15, 17, 18, 19 UML 2 and The Unified Process Chapters 17, 18, 23, and 24 List of topics for Workshop Seven: Class Design Realising Use Cases Refactoring and Design Optimisation Design Quality: Cohesion and Coupling Aggregation and Inheritance Implementation Diagrams Component model Deployment model System testing Course Objectives for Workshop Seven: Upon completion of this workshop students will be able to competently: 1. Complete the definition of classes and associations begun in analysis 2. Realise use cases with operations 3. Formulate algorithms for each operation 4. Refactor design model produced for a cleaner design 5. Adjust class structure to increase inheritance 6. Define system implementation 7. Define UML system implementation models 8. Construct UML deployment model for a system implementation 9. Construct UML component models for system implementation 10. Generate test data from use case scenarios: typical and exceptional 11. Unit test each class 12. Perform integration testing and analyse the system performance

Suggested Activities/Progress Checks/Review Questions: 1. Facilitator reviews questions from workshop 6 with the students. 2. Facilitator leads review/discussion of readings assigned for Week 7. 3. Facilitator hands out assignments for Week 7. 4. Students complete their assignment for week 7 in Rational Rose using their lab accounts. Lab Exercises for Workshop Seven: 1. Complete the models, using Rational Rose, for Week seven s assigned lab exercise. Assignment(s) for Workshop Seven: 1. Extend earlier Domain model with design detail using Rational Rose 2. Complete implementation model using Rational Rose

Workshop Eight: OOD in Context and Final Exam Assignments/readings to be completed before Workshop 8 1. Complete Week 7 assignment(s) 3. Read: Object-Oriented Modeling and Design with UML Chapter 21 List of topics for Workshop Eight: Final Exam Suggested Activities/Progress Checks/Review Questions: 1. Conclude all course lecture topics and conduct a final Q&A session 2. Facilitator distributes final exam. 3. Students complete the final exam 4. Student representative will distribute the Course Evaluation Forms to students and ensure that these are returned to course facilitator.

Section 4 Appendices (a) Grading Criteria for Written Submissions A standard template will be devised for this section, however if writers are using a grading template for similar courses, please include here for discussion with Faculty group. (b) Evaluation of Oral/Group Presentations (if applicable) A standard template will be devised for this section, however if writers are using a grading template for similar courses, please include here for discussion with Faculty group. (c) References Please list. (d) Information Sources Please list. (e) Guidelines for software piracy, plagiarism, using sources in academic works Standard response will be provided in each module handbook.