Functional Specification and Management Plan - Executive Summary

Introduction

The Functional Specification and Management Plan document outlines WinterSoft's proposal for the Project Atlantis student registration system that we will be constructing for the University of Atlantis. We are explaining our plans to create the best system possible for this institution. This document is a brief summary of pertinent information from that document.

Document Summary

Introduction

This section gives some context. The University of Atlantis needs a new scheduling system for its students, and WinterSoft is just the software developer to build it for them!
Key points:

• Our company explains what WinterSoft is all about
• Products defines our commitment to quality in all of our software
• Our commitment to our customers is discussed in "our customers" and our explanation of our warranty
• The section concludes with a discussion of Project Atlantis, our current software project

User Interaction

The User Interaction section of the document explains how users will interact with the system. The purpose of this section is to help our customers better understand the system, which will allow them to give us better feedback, so that the system can be implemented efficiently and effectively.
Key points:

• 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

Management Plan

This section is a bit of a "crystal ball". The goal is to explain WinterSoft's plans for developing the system, and to summarize the system's key functions.
Key points:

• Features outlines the key features of the system
• The classes of functions section explains further how the functionality of the system will be divided into two parts
• Component interaction explains how the two different classes of users will interact
• The discussion of system implementation and data structures gives some preliminary ideas of how the design might be approached
• The minimal system section explains what capabilities the system must have to be successful
• Possible enchancements is a list of capabilities we would like to provide, but are not key to the system's success
• The section concludes with an explanation of WinterSoft's internal organization, and a summary of what we want to deliver to the University of Atlantis

Glossary

Finally, a brief glossary is included to help clear up any inconsistencies or misunderstandings.

Conclusion

We look forward to working with the University of Atlantis on this project, and we believe that we will be able to meet all of their expectations with the Project Atlantis registration system.