Motivation
The database system is built due to the inconvenience of accessing data of different programs related to EAC. Since EAC is a non-profit organization, we design this database system to help them save the cost for database system for other meaningful uses. In addition, we will also design the database system to tailor the needs of EAC for an easy-access and useful database.
Users
The users of the application would be the administrators of EAC, which they will use the database to access necessary data of different programs and to create necessary reports. The users would likely only have basic experience with computer such as Excel and Words, thus we would design the database system to be as easy to navigate as possible.
Feature
Besides the database system would be easy to navigate, some features we have is that we allow the admins to edit the attributes of the database. In addition, we also allow the admins to easily generate a report for the data of each program.
Constraints
Some constraints that we have are that the lack of professional development skills our team might have. We might take a longer period to develop the application and have it to be functional. In addition, we do not have a budget, therefore we are only limited to basic development tools.
Use Cases
Use Case 1: Login
Primary Actor: EAC Administrators
Stakeholders: EAC Administrators – Login is needed to access the database system
Preconditions: N/A
Post Conditions: After login, administrator would be able to view and access the interface of the database.
Main Success Scenario: Allowed to access the database.
Extensions and alternative Flows: Wrong login information leading to failed logins, thus no access to the database.
Open Issue: N/A
Use case 2: Editing attributes of data base
Primary Actor: EAC Administrators
Stakeholders: EAC Administrators – To edit the database/data.
Preconditions: Use Case 1
Post Conditions: Data tables would have a new attributes or less attributes depending if the admin was to add to delete an attribute.
Main Success Scenario: Data table is changed to way needed.
Extensions and Alternative Flows: Attributes are deleted or added by accident.
Open Issue: N/A
Use case 3: Report generation
Primary Actor: EAC Administrators
Stakeholders: EAC Administrators – To generate reports based on the data. Boards – Interested in the performance of the programs.
Preconditions: Use Case 1
Post Conditions: A report would be generated as a file in the purpose needed.
Main Success Scenario: A report is generated.
Extensions and Alternative Flows: Unable to generate a report.
Open Issue: What is the format of the report?