UC IRVINE - ICS 125 PROJECT IN SYSTEM DESIGN
Assignment 5: Final
|
Due at the time of your demonstration during finals week, June 15-19
Assignment Requirements
This assignment consists of three parts: 1) an update to the requirements
document (see below); 2) your code and accompanying files; and 3) a demonstration
to be scheduled with Professor Redmiles and your client. The demonstrations
will be scheduled during the week of June 15-19th.
Purpose and Content
The final document will include a complete record of the requirements and
design for your project. Thus, most of the sections will be updates
of sections in your requirements and design documents. The only new
sections are the Package diagram and Deployment diagram; the testing section
will also include new material.
-
Title Page--Important: Please include the student ID of each team
member!
-
Summary
-
Use Cases
-
Class Diagrams
-
Activity Diagrams
-
The Activity diagrams should give a high-level picture of the dynamic flow
of control. They should not be a reiteration of the Use cases.
-
Package Diagram
-
If you have more than a few classes, they should be grouped together in
packages of related classes.
-
Include dashed arrows that indicate dependencies between packages.
A dependency exists between two packages if any class of one package depends
on any class in the other. One class depends on another if: it needs
to call the other class, it needs to send it a message, it uses the class
in the parameter list of one of its methods, it includes the class as part
of its data.
-
Read chapter 7 of UML Distilled for more information.
-
Deployment Diagram
-
If your project runs on more than one physical processor, you need to include
a deployment diagram that shows the physical relationship between the components
(or packages) of your system. For more information, read chapter
10 of UML Distilled.
-
Deliverables
-
List all the items you are going to give your client.
-
Make sure you mention how you are turning in your code (see below).
-
Delivery Platform
-
Development Platform
-
Milestones and Effort
-
Testing
-
Include your acceptance test plan and the results
-
Also describe what other testing you did (e.g. unit testing), and include
the test cases.
Turning in your code
If your project runs on UNIX, leave your code and other files (e.g.
README files, on-line help files, test data) in your team account and mention
in your document the top level directory for your code. Include in
each directory a README file that gives a brief description of the files
in that directory and their relation to the rest of the directories.
The README file in the top level directory should also give a brief description
of each of the sub-directories.
If your project runs only on PC's, put a copy of each of your
source files and other files (e.g. README files, on-line help files, test
data) on 1 or more floppies. Label each floppy with your team name
and floppy number, and mention in your document that you are turning in
your code on floppies and the number of floppies required.
Include in each folder a README file that gives a brief description of
the files in that folder and their relation to the rest of the folders.
The README file in the top level folder should also give a brief description
of each of the sub-folders.
Comments
ICS125
SQ98 Assignments
ICS125
SQ98
David F. Redmiles ­
Home Page
Department of Information and Computer
Science
University of California, Irvine CA 92717-3425