Home - LittleBo22/-CS690-finalproject GitHub Wiki
Welcome to my CS690-finalproject home page!
Scenario: A Day in the Life of Ahmed Morning
Ahmed glances at the community board in his apartment lobby. A few notices are pinned up—one about a bake sale, another for a lost dog, and a flyer about a neighborhood cleanup. “It’s hard to keep track of everything going on,” he thinks, wishing there was a better way to stay informed.
Late Morning
While out for a walk, Ahmed sees a neighbor fixing their fence and stops to chat. They mention needing help painting their shed this weekend. Ahmed offers to lend a hand, but by the time he gets home, he realizes he’s already made plans for that day. “If I had a way to organize my commitments, I wouldn’t double-book myself,” he mutters.
Lunch
During lunch, Ahmed recalls a conversation with another neighbor about setting up a carpool for school drop-offs. “That would be great,” he thinks, “but how do we coordinate schedules and decide who drives when?”
Afternoon
Back home, Ahmed receives a message from the apartment manager about water maintenance scheduled for the next day. “I should share this with the other residents,” he thinks, but he doesn’t know the best way to spread the word efficiently.
Evening
As Ahmed reflects on his day, he realizes how much potential his neighborhood has for collaboration and support. “If we had a way to connect and organize these ideas, we could accomplish so much more together,” he resolves.
Actors:
Apartment Manager/ Residents
Business Requirement:
BR1: To create software that efficiently allows apartment management and residents to organize events through the use of a calendar.
Use Cases:
Use Case 1: User Logs into the system
- ID: UC1
- Actor: user
- Flow: enter user ID to log in and view calendar. User ID consists of first two letters of first and last name and apartment number for residents. Admin login is admin + first two letters of first and last name.
Use Case 2: making changes to the calendar
- ID: UC2
- Actor: user
- Flow: user can add, edit or delete items to the calendar or they can exit back to login screen
Functional Requirements:
Functional requirements for UC1
Functional requirements for UC2
- FR1: User selects if they want to add, edit or delete from the calendar
- FR2: Adding an item to the calendar.
- FR3: Deleting an item from the calendar
- FR4: Editing an item on the calendar
- FR5: System saves changes made to the calendar
- FR6: Exit returns the user back to login screen