Object-Oriented Analysis & Design
handouts are located here. Students must sign in with their Evergreen account. If prompted, the domain is AC_COMPUTING
Those whose main exposure to writing software has been with once-written, once-read, once-executed programs according to an academician's specification often find surprising how little time, comparatively speaking, is spent coding during the "real" software development process. Furthermore, most (and most egregious) errors in large-scale systems can be traced back, not to coding, but to requirements specification and design. Applying project management and systems engineering best practices within each phase of software development provides a disciplined approach to developing large-scale systems that, we hope, avoids such errors. Student Originated Software introduces software engineering principles by applying and integrating the following skills to software development: requirements definition, preliminary and detailed design, programming, project management, and software testing and integration.
The main objective of this part of the program is to learn concepts of the software engineering process, to gain the ability to apply software development methods, specifically UML, and to gain some working knowledge of modern tools, specifically Rose. We will use an object modeling language "Unified Modeling Language" (UML) to draw diagrams of object-oriented designs. We will also explore the Rational Rose modeling tool.
Expectations and Requirements: To earn credit, students must attend lectures, complete the reading assignments, weekly workshops and assignments, and perform satisfactorily on two exams.
Students will be evaluated on the basis of their understanding of the software development process and methods, as reflected in their ability to explain key concepts through participation in discussions, pop quizzes, workshops and exams. They will also be evaluated on the basis of their ability to apply these basic concepts in weekly assignments.
Our primary text is Stevens' Using UML.
- Typical Week:
- 11 - 12 (LH5) - Lecture: covering new material
- 1 - 3 (LIB 3500) - Workshop: example exercises from EU-Bid
Previous week's Assignment returned and critiqued
- Reading assignments generally due (unless otherwise stated)
- 11:30 - 1 (LH1) Lecture: covering new material
- 5:00 PM Current week's assignment (EU-Lease) due.
The Case Study: Students will further apply and integrate their understanding of OOAD and OOP concepts and their new found analysis and programming abilities in a case study project where they will revise their Case Study Notebook: EU-Lease system and implement that specification and design in Java. (see Case Study Syllabus).