DeVry University

6600 Dumbarton Circle, Fremont, California

Course Syllabus (2005 Fall Term, Nov – Feb)

Course Title: OOAD (Object Oriented Analysis and Design using UML)

Course No: CIS339 Contact Hours: 4 Credit Hours: 3

Prerequisites: CIS270 and CIS321

Course Instructor: Dr. George Lai Office Phone: 510 574-1133

E-mail Address: [email protected]

Web Site: http://eclipse.fre.devry.edu/~glai

Office Hours: Tuesdays, Wednesdays, Fridays 10:00am – 11:00am

Thursdays, 3:00pm – 4:00pm

Class Meetings: Thursdayss 1:00pm to 2:50pm Rm105

Fridays 1:00pm to 2:50pm Rm105

Course Description

Building on the foundation established in CIS-321 (Structured Analysis and Design), students will explore techniques, tools and methods used in the object-oriented approach to develop applications. Students will learn how to model and design system requirements using tools such as Unified Modeling Language (UML), use cases and scenarios, class diagrams and sequence diagrams.

Course Goals

Upon completion of this course, the student can expect to be competent concerning the following:

· Determine the difference between a procedural and an object-oriented solution,

· Articulate object-oriented concepts in the design of a solution to a problem,

· Design fundamental diagrams of UML,

· Determine the classes, attributes, and functions for an object-oriented solution,

· Prepare and present a management level report for a business system problem,

· Software skills: Microsoft Word, Microsoft Excel, OOP Using C++/C#, Microsoft PowerPoint, Microsoft Project Planner and VISIO.

Terminal Course Objectives

1. Given a case study, such as those found in a standard Systems Analysis textbook, of a system to be developed, propose a software development plan based on the Unified Process or similar RAD methodology.

2. Given a case study, such as those found in a standard Systems Analysis textbook, of a system to be developed, create a Use-Case Description and Use-case Diagram of the system.

3. Given the Use-Case Description and Diagram developed for the TCO #2, develop a class diagram that represents the classes and their relationships.

4. Given the Use-Case Description and Diagram developed for TCO #2, develop a detailed sequence diagram for each of the Use-Cases in the system.

5. Given the detailed sequence diagram developed for TCO #4, create a collaboration diagram for each of the Use-Cases in the system.

6. Given the class, sequence, and collaboration diagrams developed for the earlier CTO’s, propose how some of the Use-Cases could use some common architectural and design patterns for the Use-Case realization.

7. Given an architecturally significant Use-Case Class diagram and Interaction diagrams, implement (code) the Use-Case using an Object-Oriented programming language such as Visual Basic, C++, or Java.

8. Given the Interaction diagrams for a Use-Case that displays complex behavior, create a State Diagram for the Use-Case.

Group Project Assignment

Two or three students can form a group. Each group should submit a one-page proposal that includes name of the project and its scope of the work during Week 10. The project should employ use case diagrams, class diagrams, sequence diagrams, collaboration diagrams and state chart diagrams for implementation. The project should be completed and presented to class during Week 13 and Week 14.

Weekly Course Schedule

Week	Topics	TCO	Reading	Lab	Due
1	SDLC, Project Initiation	1	Ch 1, 2 Ref 2: Ch 1	#1a	Friday Week 2
2	Application (Using UP)	1	Ch 3, 4, Ref 1: Ch 1	# 1b	Friday Week 3
3	Use Case Diagrams	2	Ch 5, 6, Ref 1: Ch 2	# 2	Friday Week 4
4	Application (Use Case Modeling)	2	Ch 6, R1: 3, R4: 11	# 3	Friday Week 5
5	Class Diagrams	3	Ch 7	# 4	Friday Week 6
6	Application (Class Diagram)	3	Ch 7, Ch 14	# 5	Friday Week 7
7	Sequence Diagrams	4	Ch 8, Ref 1: Ch 5	# 6	Friday Week 8
8	Review and Midterm		Review and Test
9	Application (Sequence)	4	Ch 8, 9 Ref 1: Ch 5	# 7	Friday Week 10
10	Collaboration Diagrams	5	Ch 9, 10, Ref 3: Ch 5	# 8	Friday Week 11
11	State Chart Diagrams	8	Ch 11, 12, Ref 3: Ch6	# 9	Friday Week 12
12	Implementation	6, 7	Ch 15	Project
13	Project Implementation	7, 8	Ch 16	Project	Friday Week 13
14	Project Presentations	7, 8	All chapters	Project	Friday Week 14
15	Final

Tests Week 4 Test 1

Week 8 Test 2

Week 11 Test 3

Project Presentations Week 13 & 14

Make-up tests are not given.

Text Book and Materials

Systems Analysis and Design, an Object-Oriented Approach with UML

Alan Dennis, Barbara Haley Wixom, David Tegarden

John Wiley & Sons, ISBN 0-471-41387-9

You will need to use the following software: MS Word, MS EXCEL, VISIO, Microsoft Project Planner, Power Point, Microsoft Visual .NET C#, Internet/email

Reference Materials

Ref 1: The Object-Oriented Approach, Concepts, System Development, and Modeling with UML J W Sat zinger, T W Orvik, Course Technology, Thomson Learning, ISBN 0-619-03390-8

Ref 2: The Unified Software Development Process, I Jacobson, G Booch, J Rumbaugh,

Addison Wesley, ISBN 0-2-57169-2

Ref 3: Object Oriented Systems Development using the Unified Modeling Language,

Ali Bahrami, ISBN 025625348X Irwin/McGraw-Hill

Ref 4: Introduction to Object-Oriented Analysis and Design with UML and the Unified Process

Stephen Schach, ISBN 0-07-293984-2 Irwin/McGraw-Hill

Grading Policy

Tests 50%

Lab/Class Work/Homework 20%

Final 30%

A for 90% - 100%

B for 80% - 89%

C for 70% - 79%

D for 60% - 69%

F for < 60%

Attendance and Class Participation

According to DeVry policy, each student is required to attend every lecture in the course.

If a student misses a lecture, then it is the responsibility of the student to determine what work was missed.

Be aware that some exam material may come from lectures, in-class assignments, and class discussion that are not covered in your text. You are responsible for notifying your instructor of planned absences, and for fulfilling course requirements missed during an absence.

Academic Integrity

Working with your classmates to discuss and solve the homework is strongly encouraged. However, the submitted solutions must be your own work, using your own words. Academic misconduct (i.e. cheating, plagiarism, etc.) will NOT be tolerated with regards to labs, homework assignments, quizzes or exams during the course! If a student violates the academic integrity policy by gaining advantage over others through unfair means, he or she will earn a non-pass grade. All students are expected to follow the academic honesty policy.

What IS cheating?

Sending another student your entire or any portion of your source code.
Leaving your source code within an open area, or on a computer that is accessible to other students.
Showing another student your source code for the purposes of copying and/or “to see exactly how you did it”.
Receiving any portion of another student’s source code in any manner listed in (1-3).

What is NOT cheating?

Helping another student find logical and/or syntactical bugs/errors in their program (not do it for them)
Receiving help from another student by allowing that student to help you (not do it for you) find logical and/or syntactical bugs/errors in their program.

Student Academic Integrity Policy

All students are expected to follow the academic honesty. Academic honesty is violated when students gain advantage over other students through unfair means.

When students violate the academic honesty, they get a non-passed grade.

For more details, refer to DeVry Student Handbook.