1.

Software Development Methodology:

Considering the characteristics of the project, such as a short development time, evolving requirements, and the
need for flexibility, an Agile development methodology would be suitable. Specifically, Scrum could be a good fit.
Scrum allows for iterative and incremental development, ensuring that the product evolves with feedback from
stakeholders. Given the evolving nature of the project, Scrum's adaptability to changes would be valuable. Daily
stand-up meetings can keep the team aligned, and the short sprint cycles align with the leadership's expectation of
the first version within 3 months and complete project within 9 months.

2. Testing Strategy:
 Unit Testing: Developers should perform unit testing to ensure individual components work as intended.
 Integration Testing: Performed by both developers and a dedicated integration testing team to ensure
components work together.
 System Testing: Conducted by a dedicated testing team to verify the entire system against the specified
requirements.
 User Acceptance Testing (UAT): Involving lecturers, students, and academic staff to ensure the system
meets their needs and expectations.

3. Requirements:
Functional Requirements:
Lecturer Management:
1. Import student lists from PAP system or Excel.
2. Assign presentation and review groups.
3. Create reports on student activities.

Student Management:
1. View constructive questions.
2. Provide critical opinions on questions.
3. Evaluate (vote) presentations of other members or groups.

Academic Staff Functions:

1. Statistics on class hours using constructivist methods.
2. Monitor students' feedback during the learning process.

Non-functional Requirements:

1. Security: Ensure information security when logging in with FU's email accounts on the Gmail platform.
2. Performance and Reliability: The system should guarantee high performance and reliability.

5. Functional Test Cases:

1. Test Case: Import Student Lists
 Validate successful import from FAP system.
 Confirm successful import from an Excel file.
  Ensure proper handling of duplicate entries.

2. Test Case: Assign Presentation and Review Groups

 Verify the lecturer can assign groups accurately.
 Confirm the system prevents invalid group assignments.
 Check if reports are updated after group assignments.

3. Test Case: View Constructive Questions

 Ensure students can view questions relevant to their group.
 Validate proper sorting and filtering options.
 Confirm the display of critical opinions.

4. Test Case: Evaluate (Vote) Presentations

 Check if students can submit votes accurately.
 Validate the system's calculation of presentation scores.
 Confirm the proper display of evaluation results.

6. User Stories:
1 As a Lecturer:

I want to efficiently import student lists from various sources, assign presentation and review groups, and generate
insightful reports on student activities.

2 As a Student:

I want to easily view and provide critical opinions on constructive questions, as well as evaluate presentations of
other members or groups.