Professional Documents
Culture Documents
Entrega Final
Entrega Final
Entry and Exit: Must be able to efficiently record vehi- H. Non functional Requierment 8
cle entry and exit, whether through key cards, license plate
Energy Efficiency:If applicable, the system should mini-
recognition, or other methods.
mize the energy consumption of the devices used.
C. functional Requierment 3
I. Non functional Requierment 9
Access control: It must ensure that only authorized users
have access to the parking facilities, using secure methods Legal Compliance: The system must comply with local
such as access cards. laws and regulations related to parking and personal data
management.
D. functional Requierment 4
Availability management: It should maintain a real-time J. Non functional Requierment 10
record of available parking spaces and display this information Data Backup: Regular data backups should be performed
to users. to prevent the loss of important information.
VIII. U SE CASE D IAGRAM X. S ECUENCE D IAGRAM
A. Diagram
A. Diagram
B. Description
The employee hands over the access card to the guard,
and the guard checks in the system whether it’s valid in the
database. The system returns the data and either accepts or
B. Description
denies access, informing the guard. The guard then informs
In the first scenario, the employee requests registration, pro- the employee whether entry has been accepted or not.
vides personal information and vehicle details to be registered XI. ACTIVITY D IAGRAM
in their name. Security records it in the database and assigns
a parking space, allowing entry to the parking area. A. Diagram
In the second scenario, the employee requests access, pro-
vides an access card, waits for confirmation from security,
accepts entry, and proceeds to the parking area to their
assigned parking space. In the third scenario, the employee
hands over the access card, security records the exit, and the
employee exits the parking area.
E. Rol
B. Main Screen
Incidents: There were no incidents with this screen.
F. Exit
Incidents: The only issue here is that the buttons aren’t fully
displayed depending on the screen resolution where it’s
running. This is resolved by changing the project’s geometry. :
There were no incidents with this screen.
C. Access
G. Continuous Improvement
Lessons Learned: Reflection on incidents and challenges,
extracting key lessons for future projects. Best Practices:
Identification and documentation of successful strategies and
practices employed during development. Feedback Mecha-
nisms: Establishing feedback loops for team members to share
insights, suggestions, and critiques. Design Decisions: Details
on the decisions made during the planning phase regarding the
integration of a database and the overall program architecture.
Database Integration: A step-by-step account of integrating
the database into the application, addressing challenges, and
Incidents: An issue we have here is that when we enter the implementing best practices. User Training: Strategies for user
data in the text boxes and click the register button, it still training to adapt to changes introduced by the integrated
doesn’t show in the viewer we have below the text boxes. We database and refined program design.
XVIII. DATA BASE B. Menu
A. Collection
Buttons for the new screens were added in this screen, as,
according to the requirements, more functional screens were
incorporated. Each button directs to its respective screen.
The rest of us decided to use mongoDB since it has Data
Schema Flexibility which means that it does not require a
fixed schema like relational databases. This provides flexibility
C. Register
to adapt to changes in project requirements without needing to
modify the database structure. Another important point why
we selected MongoDB is that it offers a complete set of fea-
tures, such as automatic replication, partitioning, and disaster
recovery, which are essential for client-server environments
seeking high availability and reliability.
D. Access
G. Rol
This will send you to the menu where you can choose which
screen to go to, choose the one you prefer or the one you
need.
C. Register
H. Employee
I. Vehicular count
For this screen, the fields are filled out for an event that takes
place in the company, for example an audit.
G. Rol
For this screen, the role that the employee will have and their
permissions are recorded.
H. Employee
The new user is registered with their personal data and the
role they will have.
I. Vehicular count