Complete your PGI and documentation by making sure all parts connect clearly and make sense.
1. Problem Statement
- Show real evidence: Make sure your problem is clear and real. Use data, examples, or facts to prove that the problem exists and needs solving.
2. Objectives
- Solve the problem: Your objectives should directly solve the problem you identified. Each objective should help reach a solution and be simple, clear, and possible to achieve.
3. Project Features
- Keep features realistic: Every feature in your project should be tied to your objectives. Don’t promise more than what you can do. Make sure the features are realistic and can be done within your timeline.
4. Use Case with Admin and User Roles
- Identify user roles: In your project, clearly define roles like admin and other users. The admin role should be able to manage the system, while regular users should perform actions based on the system’s features. Make sure these roles match what your system needs.
5. Create ERD in Lucidchart
-
Move your ERD to Lucidchart: Use Lucidchart to create your Entity Relationship Diagram (ERD), which shows how data will be connected to your system. The ERD should match the features and objectives of your project.
-
Example Lucidchart: Click here for example.
-
Once done, generate a shareable link to your Lucidchart document that can be viewed by the IT4B (System Administrator). Make sure the permissions are set to "viewable" so they can access your diagram.
Make sure your Project General Information (PGI) and your documentation are consistent with each other. Everything should match up: the problem, the objectives, the features, and your diagrams. This will make your project clear and easy to understand.
-
Submit Documentation Links:
-
Make sure to send the link of your documentation repository to svfc portal (assumed to be on your GitHub organization) by Tuesday, October 1, 11:59 PM. This is a mandatory requirement for all group members.
-
All members must submit the link to ensure proper collaboration and version control of your project documentation.
-
-
Collaboration Opportunities:
-
The first three groups with well-organized and complete documentation will have a chance to collaborate with 3rd-year students from BSIT 3A (Event-Driven Programming). These students are tasked with creating an Android app based on your system.
-
The first six groups with well-organized documentation will have the opportunity to work with 4th-year students from BSIT 4B (System Integration). These students will:
-
Create a Python Flask back-end for your system.
-
Set up the database and handle the deployment in production using AWS EC2 and a testing environment such as PythonAnywhere or Render.com.
-
-
All groups must collaborate with 2nd-year BSIT 2A students (Platform Technology). Their role is to assist with the following:
-
Mid Fidelity, and High Fidelity design prototypes.
-
Conduct User Research and User Acceptance Testing (dates for collaboration to be announced).
-
-