Student Record-Keeping

Management System
 a. project title

Table of Contents b. ERD

c. DATABASE DEMO
d. System DEMO
e. DIVISION OF LABOR
f. Conflicts encounter
Student Record-Keeping Management
System
ERD
Entities:
1.User:
1. Attributes: UserID (PK), Username, Password, UserType
2. Relationships: Connected to Student, Administrator, and Teacher entities.
2.Student:
1. Attributes: StudentID (PK), FirstName, LastName, ContactNumber, Email, Address
2. Relationships: Connected to User, Enrollment, AcademicRecord entities.
3.Administrator:
1. Attributes: AdminID (PK), FirstName, LastName, ContactNumber, Email
2. Relationships: Connected to User entity.
4.Teacher:
1. Attributes: TeacherID (PK), FirstName, LastName, ContactNumber, Email
2. Relationships: Connected to User entity.
5.Enrollment:
1. Attributes: EnrollmentID (PK), StudentID (FK), ClassID (FK), EnrollmentDate
2. Relationships: Connected to Student, Class entities.
6.Class:
1. Attributes: ClassID (PK), ClassName
2. Relationships: Connected to Enrollment entity.
7.AcademicRecord:
1. Attributes: RecordID (PK), StudentID (FK), Subject, Grade, ExamDate
2. Relationships: Connected to Student entity.
8.Communication:
1. Attributes: MessageID (PK), SenderID (FK), ReceiverID (FK), MessageType, MessageContent, Timestamp
2. Relationships: Connected to User (Sender, Receiver) entities.
9.ExamFeePayment:
1. Attributes: PaymentID (PK), StudentID (FK), Amount, PaymentDate
2. Relationships: Connected to Student entity.
Key Points:
•The User entity is used for authentication and access control, with different user types such as Students, Administrators, and Teachers.
•Students can be enrolled in multiple classes (Enrollment) and have academic records (AcademicRecord).
•Administrators and Teachers are distinct user types with their own profiles.
•Communication allows messaging between users, and ExamFeePayment records payment details made by students.
•The simplified ERD provides a high-level view of the relationships between key entities in the system.
DATABASE DEMO
Database Schema
Tables:
1.Users Table:
1. UserID (Primary Key)
2. Username
3. Password
4. UserType (Administrator/Student)
2.Students Table:
1. StudentID (Primary Key)
2. UserID (Foreign Key referencing Users.UserID)
3. FirstName
4. LastName
5. Other personal details
3.Administrators Table:
1. AdminID (Primary Key)
2. UserID (Foreign Key referencing Users.UserID)
3. FirstName
4. LastName
5. Other personal details
4.Courses Table:
1. CourseID (Primary Key)
2. CourseName
3. Other course details
5.Enrollments Table:
1. EnrollmentID (Primary Key)
2. StudentID (Foreign Key referencing Students.StudentID)
3. Course
System DEMO
System Demo Structure:
1.Login Page:
1. Design a simple login page where users can input their credentials (username and password).
2. Add a "Forgot Password" link for password recovery.
2.Register Page:
1. Create a registration page where new users (administrators, teachers, and students) can sign up.
2. Include fields such as username, password, role, and additional details depending on the user type.
3.Dashboard Page:
1. Develop a dynamic dashboard that changes based on the user's role (admin, teacher, student).
2. Include key information such as recent activities, notifications, and quick links to important features.
4.User Profile Page:
1. Allow users to view and edit their profiles.
2. Include fields like name, contact details, and other relevant information.
5.Main System Features:
1. Student Record Management:
1. Develop a section where administrators can manage student records.
2. Teachers and students should have access to their own records.
2. Communication Tools:
1. Create a messaging system for communication between educators, students, and parents.
2. Implement notifications for important updates.
3. Data Analytics and Insights:
1. Develop a section where administrators can access data analytics and insights.
2. Provide visual representations of student performance and trends.
4. System Security:
1. Implement user authentication and access controls based on roles.
2. Ensure data privacy and compliance with data protection regulations.
5. Flowchart Integration:
1. Consider integrating the flowchart elements into the system to showcase the processes involved in student administration.
6. DFD Integration:
1. Implement the DFD elements to show the flow of data within the system.
6.Prototype Website:
1. Host the prototype on a platform like GitHub Pages or a similar service for easy access.
7.Interactive Elements:
1. Add interactive elements to simulate user actions.
2. Utilize sample data to showcase how the system responds to different inputs.
Login Page
Register Page
Dashboard Page
User Profile Page
DIVISION OF LABOR
Team Member

Keanu Leo N. Nedruda Aikon Delos Reyes John Christian Valdez Dylan Lacson
Conflict Encounters
Conflicts Encounter Scenario:
Setting: A team meeting during the development phase of the "Student Record-Keeping Management System.“

Characters:
1.Keanu Leo N. Nedruda (Developer): Leads the software development team.
2.Aikon Delos Reyes (Database Specialist): Manages database-related tasks.
3.John Christian Valdez (Project Manager): Oversees the project and ensures alignment with goals.
4.Dylan Lacson (Marketing Lead): Responsible for promoting the system.

Conflict: The team is facing a conflict regarding the prioritization of features in the upcoming release. Keanu, the lead developer, is pushing for the inclusion of advanced
data analytics features, emphasizing their potential to provide valuable insights. Aikon, the database specialist, is concerned about the additional workload and complexity
this may introduce, suggesting a phased implementation approach. John, the project manager, is focused on meeting the project timeline and is worried about potential
delays. Dylan, the marketing lead, is eager to start promoting the system and is concerned that delays might impact the marketing strategy.

Tensions:
•Technical vs. Timeline Concerns: Keanu and Aikon are at odds regarding the technical feasibility and potential delays associated with implementing advanced analytics.
•Project Goals vs. Marketing Strategy: John and Dylan have differing perspectives on whether prioritizing advanced features aligns with the project's overall goals or
impacts the marketing strategy.
Resolution Steps:

1.Clarify Goals: John facilitates a discussion to ensure everyone is aligned with the project's overarching goals. This helps in understanding whether advanced analytics
aligns with the project's primary objectives.
2.Technical Feasibility Discussion: Keanu and Aikon discuss the technical feasibility of the proposed features, exploring options for phased implementation to manage
workload concerns.
3.Timeline Assessment: John works with the team to reassess the project timeline, considering both technical complexities and marketing strategies.
4.Prioritization Exercise: The team collectively prioritizes features based on their impact on project goals and marketing objectives.
5.Compromise: The team reaches a compromise by agreeing to include a scaled-down version of the advanced analytics features in the upcoming release, with a
commitment to revisit and expand on them in future updates.

Outcome: The conflict resolution process results in a balanced approach that aligns with both technical considerations and project timelines. The compromise satisfies the
team's varying concerns and ensures the development and promotion of the "Student Record-Keeping Management System" stay on track.