Conceptual Design Document - Executive Summary

Introduction

The Conceptual Design document outlines Wintersoft's design plans for theProject Atlantis Student Registration system. This document providesan overview of Wintersoft's design ideas through the use of diagrams anddescriptions. It is our goal to provide the University of Atlantis with aclear understanding of the system we will develop. We are confident that it willmeet the requirements set forth by the University of Atlantis.

Document Summary

Introduction

This design document was created to ensure a complete understanding ofProject Atlantis. It expands on our previous communications, providing moredetail on some aspects of the system. Wintersoft is moving closer to the deadlinefor this project so it is important that we have enough information to proceed.

• Outline and purpose of the document
• Goals of the document

Management Plan

This section outlines the plans for the development of the system.Without going into technical details, it mentions the components of thesystem and the relationships between them. As well, it provides a timeline,which will allow the University of Atlantis to monitor our progress.

• The system will have two unique users: general users, and administrators (staff)
• The general functionality and features are discussed, including descriptions of how they will work
• Administrator functionality explains special capabilities which staff at the University of Atlantis will have
• A summary of the section explains the security and maintenance advantages of the two-tiered system

Context Diagrams

Provides an overview of how the two different types of users interact withthe system. The top-level diagrams show the functionality of the userswithout specifying the flow of data.

• Student interaction with the system is explained
• Administrator interaction is explained

Entity Relationship Diagrams

Until now we have referred to those that interact with the system asusers. In this section, we refer to the user as an entity and displayit's interaction with the system. This interaction shows how much each entityinteracts with another.

• Overview
• Administrators interacting with courses
• Administrators interacting with students
• Students interacting with courses
• Students interacting with themselves (i.e. modifying personal information.)

Data Dictionary

To help clarify the previous section, the Data Dictionary gives a clearexplanation of what attributes each entity has.

• Student attributes
• Administrator attributes
• Course attributes

Data Flow Diagrams (DFDs)

Displays the flow of data between processes. This is the next level inthe design phase and shows explicit interaction between users and thesystem. It shows the flow of data from the users and databases and howthis data is handled by the system. It considers:

• The general system (login)
• The student system
• The administrator system

Graphical User Interfaces (GUIs)

Prototypes of the system layout are important to give an early indicationof the system's proposed appearance and usage. These images, along withexplanations, address concerns that may have been missed in the earlierdescriptions. They provide an easy understanding of how the registrationsystem will be used. It also explains where Wintersoft expects tohandle incorrect input.

• Login, Logout and Change Password functions are described
• Student interfaces are described
• Administrator interfaces are described

Walkthroughs

This section takes the reader on an imaginary "trip" through the system,referring to the interfaces described in the last section. It is useful tounderstand how users will interact with the proposed system, so that we candevise the best solutions.

• Walkthrough for a student
• Walkthrough for an administrator

Conclusion

Wintersoft is happy with the progress we are making with this system andlook forward to the continued input from the University of Atlantis. We aremoving towards the implementation phase of this system so we at Wintersoftare very excited to move forward.