230 likes | 360 Vues
This project outlines the creation of a comprehensive database suite for SIUC's Disability Support Services (DSS). It provides electronic bookkeeping to manage student records effectively, with administrative users granted full access and subsequent users having read-only access. The system will operate on a Windows environment utilizing MySQL for data storage, with a client program developed in C#. Key functional requirements include creating, editing, archiving, and querying student entries, as well as checking in and out equipment. This advanced suite aims to facilitate seamless record management and support for past and future students.
E N D
Project Definition: DSS Database Suite Iain Smith & Austyn Krutsinger October 23, 3008
Outline • Project Overview • Definitions • Use Cases • Functional Requirements • Non-functional Requirements
Overview • Provide electronic bookkeeping for past and future students to the Disability Support Services department of SIUC. • Allows administrative users full access • Subsequent users will have strictly read access
Environment • Hardware: • Client: Employee’s Workstation • Server: Department Server • Operation System: • Client: Window XP/Vista with .NET Framework and MySQL extension • Server: Windows Server 2000/2003/2008 with .NET Framework and MySQL • Network Connection: LAN • Code Standard: The database will be MySQL
Environment • The client program will by coded in C# using Microsoft Visual Studio 2005 • The connection to the DSS Database will be done internally with C# using the MySQL ODBC extension • Performance: The system should save and load the records in the appropriate table of the DSS Database 100% of the time
Use Cases: Iteration 1 • UC1: Create Student Entry • UC2: Edit Student Entry • UC3: Archive Student Entry • UC4: Query Student Entries
Use Cases: Iteration 2 • UC5: Check-out Equipment • UC6: Check-in Equipment
Functional Requirements • FR1: Database Access • FR2: Save Student Information • FR3: Search for Student Information
Nonfunctional Requirements • NF1: Intuitive User Interface • NF2: Program Package
System Evolution • Future Iterations • Forms • Test Scheduling • Text Book Ordering • …and anything else they want