Project

The project documentation should include the following sections:

Project Topic “Online Vehicle Insurance Management System”

· Title of the project (with the list of project team members);

· Executive Summary;

· Table of Contents;

· Introduction;

· Project Plan;

· Functional Specifications (including descriptions of Actors/Roles; Business Rules; Use-Case

Diagrams with Use-Case descriptions; Examples of Class Diagrams (related to particular Use

Cases); Examples of Object Diagrams [related to the selected Class Diagrams]; Examples of

Sequence Diagrams; Examples of Collaboration or Communication Diagrams; Examples of StateChart Diagrams);

· Functional Tests Plan;

· System Design Specifications (including System Architectural [Layered, “Physical”] Design Scheme selected; Package Diagram [populated with interrelated classes]; Database Tables; Entity-

Relational diagrams; Window Navigation Diagrams; Drafts of User Interfaces; and Examples of System-Response Report Forms);

· Integration Tests Plan;

· Issues to Future Studies;

· Conclusion;

· References; • Appendices (if any).

All the diagrams could be built by using Visual Paradigm, ArgoUML, MS Visio, and/or MS Word tools.

(You can use any other tools available to you, which should be specified in your project reports). Visual Paradigm Community Edition ( http://www.visual-paradigm.com/product/vpuml/communityedition.jsp ) and ArgoUML ( http://argouml.tigris.org/ ) tools are available in STH-133 and MEM-202 (or free on the Internet). All CS tools (traditionally used in particular CS courses) are available from VDI (Virtual Desktop Infrastructure) that can be reached remotely (via Horizon Clients™), (see IT Support site on VPN: https://it.rivier.edu/information-technology/vpn/ for the further instructions).