The project aims to design and develop a prototype to accurately record entries and exits in the Computer Lab. The system will capture biometric data, link it to each person and store the information on a remote server. It will also have a simple web page for administrators.
Project Objective
The primary objective of this project is to design and develop a prototype of a system that will allow monitoring the entrances and exits of staff in the Computer Laboratory facilities through biometric data.
Team Structure
Project Leader
Name: @GabrielEValenzuela
Role: Responsible for overseeing the prototype development, coordinating the team, ensuring the project meets its objectives, solving technical issues, and maintaining adherence to the timeline.
Sr. Engineers
Name: @francobottini99 @valentinrb1
Role: Senior engineer providing first response and technical support. Currently active in research at the Computer Laboratory, responsible for guiding the technical aspects of the project.
Team Members
Name: @solnou @Jorgear27
Role: Developer
Responsibilities: Responsible for designing, developing, and testing the project, ensuring alignment with project specifications and standards.
Stakeholders
School of Computer Engineering, UNC: Interested in showcasing the laboratory’s work, facilitating student and faculty engagement, and supporting ongoing research and collaboration.
Laboratory Director: Provides oversight and ensures that the project aligns with the laboratory’s strategic goals and objectives.
Milestone 7: Complete Back-End Development - Due: [Date]
Milestone 8: Complete Integration of Back-End with Hardware Interface - Due: [Date]
Milestone 9: Complete Integration of Back-End with Front-End - Due: [Date]
Milestone 10: Complete Integration - Due: [Date]
Milestone 11: Complete Testing - Due: [Date]
Milestone 12: Complete Deployment and Launch System - Due: [Date]
Project Schedule
Timeline
Start Date: [Date]
End Date: [Date]
Key Phases:
Phase 1: Planning and Design (Start Date - [Design Completion Date])
Phase 2: Development (Start Date - [Development Completion Date])
Phase 3: Testing and Launch (Start Date - [Launch Date])
Gantt Chart
(Optional) [Insert Gantt Chart]
Resource Allocation
Budget
Budget Not Applicable
Resource Requirements
Hosting Provider: Laboratory Servers
Development Tools: Visual Studio Code, PlatformIO, GitHub, etc.
Testing Tools: Choose.
Risk Management
Risk Identification
Risk 1: Hardware Component Failure
Description: During prototyping or even in production, components such as the fingerprint sensor, microcontroller, or real-time clock (RTC) may fail due to manufacturing defects, connection errors, or wear and tear.
Risk 2: Security Breach
Description: Since the system handles sensitive biometric data, there is a risk of a security breach in data storage or transmission, potentially leading to unauthorized access or data theft.
Risk 3: Integration Issues
Description: The integration of hardware with the back-end and the back-end with the front-end may present compatibility issues, requiring significant rework to resolve.
Risk 4: Delays in Development
Description: Delays in hardware implementation or software development may occur due to inadequate planning, technical issues, or lack of resources.
Risk 5: Limited Team Experience with Chosen Technologies
Description: If the team has limited experience with some of the technologies chosen for back-end or front-end development, it could lead to delays or the need for additional training.
Risk Mitigation Strategies
Risk 1 Mitigation:
Use high-quality components and conduct regular stress testing during the development phase. Have spare components available and clearly document hardware configurations and connections.
Risk 2 Mitigation:
Implement robust security measures such as data encryption at rest and in transit, multi-factor authentication for administrative access, and conduct regular security audits.
Risk 3 Mitigation:
Create a detailed integration plan and perform early and frequent integration tests to identify issues as soon as possible. Use simulations and isolated test environments.
Risk 4 Mitigation:
Establish a realistic timeline with well-defined intermediate milestones. Conduct periodic schedule reviews and re-plan as needed.
Risk 5 Mitigation:
Provide training sessions and create a collaborative environment where team members can share knowledge and resources. Assign mentors with experience to guide less experienced members.
Quality Assurance
Quality Standards
Standard 1: Code Quality and Documentation
Description: All code must adhere to project-specific coding standards and be fully documented. This includes the use of comments, function documentation, and code maintainability.
Standard 2: Data Privacy and Security
Description: Data privacy and security standards must be met according to industry best practices. This includes encryption, access policies, and compliance with applicable regulations.
Standard 3: Performance and Scalability
Description: The system must be capable of handling the expected workload efficiently and be scalable to accommodate future growth. Performance testing should be conducted to identify potential bottlenecks.
Testing and Validation
Unit Testing:
Validate that individual components (functions, classes, modules) function as expected. This will include simulating hardware failures to verify robustness.
Integration Testing:
Ensure that the interaction between system components (hardware, back-end, front-end) is seamless and that integration does not introduce errors.
User Acceptance Testing (UAT):
Conduct tests with end users (laboratory administrators) to verify that the system meets their expectations and requirements.
Communication Plan
Reporting
Weekly Reports: The project manager and senior engineers will provide updates on progress, address risks, and outline upcoming milestones.
Meetings
Team Meetings: Weekly, to review progress, discuss challenges, and ensure alignment across the team.
Approval
Project Approval
Approval Status: Approved
Approved By: Alejandro Amborisini
Approval Date: [Date]
Additional Notes
Include any other information that may be relevant to the project or its management.
GabrielEValenzuela
commented
6 hours ago
Project Overview
Project Name
Prototype of a Staff Access Monitoring System
Project Summary
The project aims to design and develop a prototype to accurately record entries and exits in the Computer Lab. The system will capture biometric data, link it to each person and store the information on a remote server. It will also have a simple web page for administrators.
Project Objective
The primary objective of this project is to design and develop a prototype of a system that will allow monitoring the entrances and exits of staff in the Computer Laboratory facilities through biometric data.
Team Structure
Project Leader
Sr. Engineers
Team Members
Stakeholders
Work Breakdown Structure (WBS)
Major Deliverables
Work Packages
Milestones
Project Schedule
Timeline
Gantt Chart
(Optional) [Insert Gantt Chart]
Resource Allocation
Budget
Resource Requirements
Risk Management
Risk Identification
Risk Mitigation Strategies
Quality Assurance
Quality Standards
Testing and Validation
Communication Plan
Reporting
Meetings
Approval
Project Approval
Additional Notes
Include any other information that may be relevant to the project or its management.