CISC 475/675
Object-Oriented Software Engineering

Spring 2003
221 Smith, MW 1730--1845

This is the Web page for CISC475/675, "Object-Oriented Software Engineering". It will contain announcements, policies, and other pertinent material for the course. The page will be updated frequently---plan on checking for new or updated material at least once a week.

About the course
Textbook
Schedule
Semester project
Grading
Policies
Resources

This course presents an introduction to object-oriented software engineering concepts, methodologies and tools. It covers the analysis, specification, design, and implementation of software systems using object-oriented development processes including the Unified Process and UML. The course includes a semester-long team development project using the techniques discussed in class.

Prerequisites: A minimum grade of C− in CISC280 (Program Development Techniques) and Senior status. CISC361 (Operating Systems) is recommended.

Applying UML and Patterns:
An Introduction to
Object-Oriented Analysis and Design
and the Unified Process
2nd Edition
Craig Larman
ISBN: 0130925691

A major part of the course will consist of a semester-long team project. Each team will analyze, design, and build a significant software system using the Unified Process, and will deliver a complete set of UP artifacts (use cases, domain model, sequence diagrams, operation contracts, and so forth). Projects will be implemented in Java (preferably) or C++.

Some possible project ideas are:

• E-dating service
• Customer relationship management (CRM) system
• Class scheduling system
• Online auction site
• CASE tool for CISC475/675 semester projects :-)

Each team will consist of five students, organized along the following lines:

• Team leader -- coordinates activities, leads design and implementation efforts
• Configuration manager -- documents the development process, develops deliverables with a consistent look and feel
• Lead developer -- codes core classes, oversees work of other coders
• Coders

You will present your progress to the class at four points through the semester. At the third presentation, you will be expected to demo major parts of your application. At the fourth presentation, you will demonstrate your complete application, and allow the instructor to "test drive" its functionality. The deliverables at each presentation are:

1. Requirements and Use Cases document
2. Specification documents (domain model, system sequence diagrams, operation contracts, collaboration diagrams)
3. Design documents (design class diagrams, class descriptions, system architecture, user interface)
4. Project source code, .class files, javadoc files, installation scripts, installation instructions, help files, test scaffolding, etc.

To prevent "scope creep", each project should be held to the following limits:

1. Approximately 7 (± 2, max 10) use cases.
2. A maximum of 20 concepts in the concept diagram.
3. A maximum of two or three design patterns.

You may use third-party code (e.g., the Tomcat servlet container) as discrete components in your project, but the code and documentation your team develops in this course must be the work of the project team members.

I've put up a page containing everything I've been told about the project teams.

Final project presentations will be on Monday, May 19th from 1730 to 1900 and on Wednesday, May 21st from 1730 to 2030. Two teams will present on Monday; the other four will present on Wednesday. Both sessions will be in 102 Gore Hall. The room will be open starting at 1700 to allow you to set up for the presentation.

Final project submissions are due at the beginning of class on 5/21 for ALL teams. The submission will consist of a printed portion (all project artifacts plus a table of contents) and a machine-readable portion (all of the above, plus source code, Javadocs, and build and test scripts) on CD (preferred) or floppy. Include a README file describing where you've put things. Do not include source or Javadoc printouts in the printed submission; there's no need to kill more trees.

There will be NO Internet connection available in 102 Gore, so bring all of the hardware you need for your presentation (except that the instructor will provide a power strip, a network hub, and several network cables). The instructor may connect a laptop to your server and test-drive your system, so make sure that your network drivers are up and that any firewall permissions are set to permit this.

Each member of each team should be introduced, and should make some part of the presentation. I may take a picture of each team.

Each presentation should take about 35–45 minutes, including setup/teardown and question/answer. Do at least one dress rehearsal of your presentation to make sure that everyone knows his part and that it will take about that amount of time.

Here are some examples of the things your presentation should cover:

• System overview: Describe what the system is, and why you think it's a good idea.
• System functionality: Demonstrate all of the main Use Cases for your system.
• Pattern usage: Describe which design patterns you used in your code.
• Error handling: Describe how you handle common errors.
• Infrastructure: Show off your source code, build scripts, and CVS.
• Automated testing: This will be especially impressive.
• Lessons learned: What went wrong during the project, and how would you prevent it next time?

You can't cover all of these areas thoroughly in 40 minutes, so you'll have to choose the areas to emphasize that are most likely to impress the instructor and TA.

Grades for the semester will be based on:

Exams: The course will include two exams (but no final). The lectures may introduce material not covered in the book. This additional material will be on the tests.

Late assignments: There are no homework assignments (other than the project) in this course. There are four delivery milestones for components of the project, which must be met. No credit will be given for project materials turned in late.

Academic integrity: You will be expected to conform to the University's policy on academic integrity.

• ArgoUML, a free UML-based CASE tool
• Violet, a simple open-source UML drawing tool
• UMLet, another UML drawing tool (closed-source, but free for educational use)
• UseModWiki, a simple, flexible Wiki implementation
• Apache Ant, a Java-based build system
• usecases.org has use case templates, tutorials, and more.
• Visual Paradigm offers a 'community edition' of their UML modelling tool.
• The periodic table of design patterns.

Last modified: Tuesday, 13 May 2003