What This Document Is
This document details a software development project undertaken for the SECME (Science Engineering Communications Mathematics Enrichment) program at the University of Central Florida (EEL 5881). It represents a comprehensive project report outlining the planning, design, and anticipated implementation of a database system. The work appears to be a capstone or major assignment, demonstrating practical application of software engineering principles. It focuses on addressing a real-world need within the SECME organization – moving from a manual, paper-based system to a digital solution.
Why This Document Matters
This report is valuable for students studying software engineering, database design, or information systems. It serves as a strong example of a complete project lifecycle, from initial needs assessment to proposed system architecture and testing considerations. Individuals interested in the SECME program itself may find the overview of current challenges and proposed solutions insightful. It’s particularly useful for those learning about project management within a technical context, or those preparing for similar software development assignments.
Topics Covered
* System Requirements Gathering & Analysis
* Database Design Principles
* Software Project Management Methodologies (Waterfall Model)
* User Interface (GUI) Design Considerations
* Access Control and Security
* Testing Strategies and Quality Assurance
* Risk Assessment and Mitigation
* Team Collaboration and Organization
* Current System Analysis & Proposed Improvements
What This Document Provides
* A detailed overview of the existing SECME data management processes.
* A proposed system architecture, including technology choices (Windows-based, Access backend).
* A discussion of user roles and access levels within the new system.
* A list of key queries the system will need to support, relating to students, teachers, and schools.
* An outline of coding standards and the software lifecycle model employed.
* Identification of potential project challenges and associated risks.
* A use case diagram illustrating system interactions.
