CS 2390 Modeling and Design - Spring 1995

Information available:

• What's New
• General Information (including grading)
• Learning Objectives
• Statement of Cooperative Work and Academic Honesty
• Class Outline
• Assignments
• Labs
• Lecture Notes
• Exam Review
• Tool Usage and Supplementary Documentation

General Information (including grading):

Instructor:

Richard Billington

Office:

109 College of Computing

Phone:

854-3227

Office Hours:

Tuesday, 4:30-5:30,
Thursday 10:00-11:00

Email:

buff@cc

Newsgroup:

git.cc.class.2390

Class:

T Th 3-4:30 in CoC 17

Labs:

Wednesdays 1:30-3 (A), 3-4:30(B) in Baird Sun Lab (103 CoC)

Final Exam:

tentative Friday, 9 June 8am - 10:50am

TAs:

Lyman Taylor (lyman@cc) Office Hrs. W 4:30-6:00 Bairdsun ; or by appt.
Reza Ghorieshi (reza@cc) Office Hrs. TBD

Text:

Required: Coad and Nicola, Object-Oriented Programming

Grading:

• Midterm 25%
• Final 30%
• Design and Programming Assignments (4) 35%
• Lab Assignments (7) 10%

Final grades will be assigned on a relative scale. Incomplete will be virtually impossible.

Assuming a reasonable attempt at a program, program grades will be based 50% on design documentation and 50% on meeting project requirements. No late assignments will be accepted.

Attendance in lecture and lab sections is mandatory: Lab sections, in particular, are an excellent time to get help. HAVE AN OIT ACCOUNT BEFORE FIRST LAB!

Learning Objectives

By the end of this class, you should be able to:

• Use object-oreitned analysis (OOA) to analyze a real-world situtation.
• Use object-oreinted design (OOD) to design a model which addresses an OOA (in a language-independent fashion) with multiple classes and connections between them.
• Implement an object-oriented desing in a an object-oriented programming language (OOPL) - namely Smalltalk.
• Understand the benefits of each of the three major building blocks of the object-oriented approach to programming/problem solving: abstract data types; polymorphism ; and inheritance.
• Understand the foundations of the object-oriented paradigm to: (a) quickly learn new object-oriented programming languages (e.g. C++ ); (b) use the paradigm to improve your programming in non-OOPL's.
• Design and implemetn a graphic user-interface ( GUI) to a model or simulation
• Design and implement a simulation of a system.

Cooperative Work and Academic Honesty

People learn by doing. In this class, the doing is particularly important since the concepts are simple and the applications complex. Students are strongly encouraged to learn from one another: Form study groups, discuss programs and lab assignments, help one another debug, and tutoring (the tutor often learns as much as the student). BUT each program and lab assignment must be individual work P unless you actually do it, you can't learn from it.

• Copying another student's program and putting your name on it is plagiarism. This is a form of academic dishonest which, when detected, will be reported to the Office of Student Affairs and may result in consequences such as loss of points for the problem, loss of points for the class, or dismissal from the class.
• Copying another student's program and changing the variable names is also plagiarism.
• You are encouraged to talk to one another about your programs, even show one another your programs and get help with debugging. However, all program code must be written by the student whose name is on the program!

Class Outline (Subject to Modification):

Week	Topic							Reading
  1     Why Objects? Why model and design?           	Chapter 1, pp. 1-13;
	Object-oriented analysis vs. design            	Appendix A, p. 504-535;
          vs. programming.                             	Appendix B, p. 547 
	Notation for OOA & OOD. 	               	 HW1-> 3/30
	Introduction to Smalltalk. 

  2   	Introduction to Graphical User Interfaces.  	Chapter 1, pp. 13-26, 
	Building the Counter object.  Reuse.	                   pp. 37-63; 
								       83-86; 
							        93-95;102-108

  3     Modeling with multiple classes.  		Chapter 2, pp. 113-145;
	Interfaces with multiple views.  		 	pp. 162-169; 
	Doing a program from scratch.				pp. 176-198 
	Modeling a whole-part structure.        HW1 due 4/11 ; HW2 -> 4/11


 4	Starting a program from scratch.  
	What's a good OOA/OOD? 
	DataStructures


 5	Sales Database example 				MIDTERM April 25. 
							Chapter 3, pp. 227-240
						 HW2 due 4/25 ; HW3 -> 4/27

 6	Object-oriented analysis, design,		Chapter 3, pp. 261-284,
	programming for data				 	  pp. 317-346.
	managmenent including interfaces 		Smalltalk-80 handout


 7  	Introduction to Discrete Event & 		Chapter 4, pp. 387-343,
	Continuous Simulation.					 pp. 463-478.
	Analysis, design, and programming        HW3 due 5/11 ; HW4 -> 5/11
	of a discrete event simulation.


 8	Advanced discrete event simulation: 		Appendix A, pp. 536-545
	Probability distributions.
	Starting C++.	

 9	C++ 						 HW4 due 5/25 

10 	Advanced graphical user interfaces: 
	Alternate models.
	Research issues and future directions 
	in modeling and design. Reviewfor final.