Member Directory:2011 Fall:Requirements and Analysis Document

Non-functional requirements
Usability Reliability Performance Supportability Implementation Interface Operation Packaging Legal
 * Implementer will need a moderate level of understanding of both SQL and PHP
 * User will only need basic web browsing and data input knowledge
 * Currently there is an existing user application that sends information from a website to a database.
 * The manager of the member directory information/site will receive user and developer manuals. The actual user of the site will receive no documentation.
 * The system will be available 24/7 with no anticipated down times. Schedule site maintenance can be performed on a need to need basis. The system will carry normal web site reliability standards and the database will model the currently used database reliability model.
 * Restarting the system in the event of a failure is acceptable. Not data will be lost from the database; however, unsaved data from the site will most likely not upload or be saved to the database.
 * The database will be designed to operate independently with system backups that protect the data in the event of a system failure. The system will not have the flexibility for failure with large data loss. In the event of a system failure, the database will need to be reloaded and unsaved data will be lost.
 * The system will address data exceptions by storing the data in a file for developers to address.
 * The safety requirements will model the existing system.
 * The security requirements will model the existing system.
 * From a site users stand point the usability and responsiveness of the system will be instantaneous. From a developers stand point the system will perform as any other database managed tool. Normal responsiveness will allow the developer to perform system functions immediately. However, based on the size or complexity of the database query, the system could take time that would be comparable to the queries complexity – meaning delays should be expected.
 * Time critical user tasks from a site usability stance – the system must be able to upload user inputted data within 10 seconds (subject to change based on the users connection speed).
 * The system will be able to support multiple users. From a site standpoint – multiple users will be able to upload member data. From a database management standpoint – multiple developers will be able to access the database and manipulate data. However, the developers will not be able to make changes to the same file at the same time.
 * A data store for a similar system can easily be absorbed by a 500 gb system with room for expandability.
 * There will be no restrictions on the latency of the data fields for the developer. Users can only upload current data – past or old data will not be changeable to the user.
 * The system will allow for expandability for future expansion. At this time no planned expansions have been written into this development model.
 * The system will be maintained by system developers at NHHTC
 * No plans have been proposed to port the system to a different software platform or change the hardware platform for the system.
 * No hardware constrains have been identified in this development design model giving us full flexibility in the hardware design.
 * No constraints have been identified for the hardware team. However, normal maintenance and updates to the system should be performed at a time that allows for the least amount of system interruptions.
 * No constraints have been identified for the testing team. However, normal testing should be performed at a time that allows for the least amount of system interruptions.
 * The system has been developed to only interact with the proposed web site data fields and the SQL database for the system previously designed during the spring 2011 semester.
 * Data will be exported and imported via embedded SQL query code within the PHP script of the web page. Data will be directly sent to the database. Data is exportable via standard SQL utilities.
 * There are no system standards that have been identified for the system – therefore designers have the flexibility to create standards that follow the latest system standards described in out text book.
 * The running system will be managed by the NHHTC system manager.
 * The system will be portable and installed by the NHHTC system manager.
 * Version 1 of the system will be installed and implemented for the database. Only one installation should be needed.
 * No time constraints have been identified for the system implementation.
 * The system will be licensed as open source and therefore require no license to operate. Current open source software will be used to support the system.
 * There are no liabilities that are associated with the system.
 * There are no royalties or licensing fees associated with this system development and installation.

Implementation and target environment
All users should be be able to access to the system with a web browser with internet access, and an XAMPP installation. This implementation of this system will be described in the installation manual (insert link for this manual).

Packaging
This system will be distributed to the user from the development team via the Google Code hosting site.

Operation
This system will be used by the users NHHTC designates.

Legal issues
This software is developed and distributed under the Creative Commons Attribution 3.0 United States (CC BY 3.0) license.

Analysis class diagram

 * Class Diagram Description