Report

CS 319 -
Object-Oriented Software Development

Summer 2013

Project

The project report will describe the object-oriented design for a selected relevant case. The following points need at least to be addressed. For the Analysis report System Design, Object-Design, Implementation and Testing chapters should not be included in the report. The final report should of course include all the chapters. We will try to largely follow the template as defined in the textbook:

Table of Contents

1. Introduction
Describes the context and the introduction of the project including outline of the report.

2. Case Description
What is the case about? What is the goal of the project? Textual description of the work that needs to be done.

3. Requirements Analysis
Describes the textual requirements, use cases, user interface prototype(s), etc. Including both functional and non-functional requirements.
3.1 Functional Requirements
3.2 Non-Functional Requirements
3.3 Constraints
3.4 Scenarios
3.5 Use Case Models
3.6 User Interface

4. Analysis Models
Describes the class diagram of the application domain and the related dynamic model (statecharts and sequence diagram).
4.1 Object Model
   4.1.1 Domain Lexicon
   4.1.2 Class Diagram(s)
4.2 Dynamic Models
   4.2.1 State Chart
   4.2.2 Sequence Diagram

5. System Design
Describes the design goals and the architecture with the required patterns.
5.1 Design Goals
5.2 Sub-System Decomposition \\ Define the top-level decomposition of the system
                                                \\ consisting of subsystems; package diagram
5.3 Architectural Patterns       \\ Apply at least three architectural patterns
                                                \\ to further structure the subsystems. Explain.
5.4 Hardware/Software Mapping \\ Describe deployment diagram
5.5 Persistent Data Management
5.6 Access Control and Security

6. Object-Design
6.1 Design Patterns \\ Apply at least three patterns. Explain these.
6.2 Class Interfaces \\ Describe classes and their public interfaces (visibility and type signatures)

7. Conclusion
Summary, lessons learned, obstacles, future work.
Including critical overview of adopted process.

References

Appendix
The full code should be provided in the electronic version of the document.

Example Projects

These are sample projects from past years which got a high grade. Each of these project reports are not perfect and had their own limitations. Yet, these sample projects might help you to provide insight in what is expected. In no means can these reports be used as a comparison or evaluation criteria for the final project grade.