CS 3371: Overview

• Using UML: Software Engineering with Objects and Components, 2nd ed., Pooley & Stevens
• Software Project Survival Guide, Steve McConnell

• For the texts:
• Survival Guide
• Using UML
• Other sites:
• NASA Software Engineering Laboratory
• AmbySoft
• Unified Process
• Usability Heuristics
• Ask Tog
• WebReview

• To produce these artifacts for a moderately complex software system:
• A software development plan.
• A requirements definition, including
• Use case diagrams.
• System behavior contracts.
• A user interface style guide and prototype.
• A user manual.
• An analysis model, including
• Class diagrams.
• Use case realizations.
• A detailed design, including
• Design-model class diagrams.
• Interaction (collaboration and sequence) diagrams.
• State and activity diagrams.
• Use case realizations.
• An implementation model, including
• Component diagrams.
• Deployment diagrams.
• A staged delivery plan.

• To define, illustrate and discuss software engineering concepts, including:
• The software life cycle.
• Top-down functional decomposition.
• Object-oriented analysis and design.
• Abstraction.
• Encapsulation.
• Component.
• Inheritance.
• Polymorphism.
• Aggregation.
• Model.
• Pattern.
• CMM.

3371 home