1.
• Nature of Requirements:
1. Flexibility and Adaptability: The project involves new functionality with
initially unclear requirements, as FU has not had a similar system before. Scrum’s
iterative approach allows for ongoing adjustments based on user feedback and
evolving requirements. This ensures that the final product can adapt to changes and
meet user needs effectively.
2. Complexity: The project has both functional and non-functional requirements.
Scrum's iterative development helps manage complexity by breaking the project into
smaller, manageable increments, facilitating early detection and resolution of
issues, and minimizing the risk of disruptive changes.
• Development Team:
1. Team Composition: The team of 4-5 experienced developers, supported by
additional employees from other departments, is well-suited for Scrum. The
methodology relies on self-organizing teams that collaborate closely, which fits
the team’s structure and expertise.
2. Collaboration and Communication: Effective collaboration and communication
are crucial for Scrum. The team's shared language and strong communication skills
enhance the Scrum process, ensuring that tasks are completed efficiently and that
the team remains aligned with project goals.
3. Expertise and Adaptability: The team's high level of expertise and
adaptability aligns with Scrum’s focus on iterative progress and responsiveness to
change. This will be beneficial in addressing evolving requirements and ensuring
timely project delivery.
• User Involvement:
Engagement: The project requires significant input from users (lecturers, students,
and lecturer leaders). Scrum’s emphasis on regular user feedback through sprint
reviews ensures that user needs and preferences are continuously incorporated into
the development process. This user-centric approach is crucial for creating a
system that meets the diverse needs of its users.
• Time Constraints and Expectations:
Timeline: The project aims to deliver the first version within 3 months and
complete the full system within 8 months. Scrum’s iterative sprints (2-4 weeks)
allow for incremental delivery of working software, enabling regular progress
assessments and adjustments to meet deadlines. This approach supports the project’s
timeline by providing frequent opportunities to review and refine the product.
• Project Risks and Management:
Risk Management: Scrum’s iterative nature helps manage risks by providing regular
opportunities to identify and address potential issues early in the development
process. This proactive approach reduces the likelihood of significant problems
arising late in the project.
In conclusion, Scrum’s iterative, flexible, and collaborative approach is well-
suited to the FU-NextExam project’s requirements, team structure, and timeline. It
will facilitate effective management of evolving requirements, user involvement,
and timely delivery of the system.
2.
Testing Levels/Stages for the SBMS Project:
Unit Testing:
Tester Role: Developers
This initial testing level involves assessing individual software components to
ensure their correctness.
Integration Testing:
Tester Role: Developers or a dedicated integration testing team
Focused on testing the interaction and compatibility of individual components to
ensure seamless operation.
System Testing:
Tester Role: A dedicated team of testers
Comprehensive testing of the entire system to verify compliance with specified
requirements.
User Acceptance Testing (UAT):
Tester Role: End users, such as lecturers, students, and academic staff
The final stage involves real users testing the system to ensure it meets real-
world requirements and specifications.
Regression Testing:
Tester Role: A dedicated testing team or automated using software testing tools
Ensures that changes or enhancements to the system do not negatively impact
existing functionalities.
Performance and Load Testing:
Tester Role: Specialized testers or engineers
Essential for ensuring high performance and reliability, evaluating the system
under both normal and peak load conditions.
3.
Functional Requirements:
1. Lecturers and staff should be able to register bus routes.
2. Lecturers should be able to change bus routes
3. Lecturers should be able to view currently registered bus routes.
4. Administrative staff can synthesize weekly bus schedules of staff and
lecturers.
5. Admin manager can view bus schedules for weekly trips, approve weekly bus
schedules and view vehicle cost summaries.
Non-Functional Requirements:
1. Users should log in using their FU's email account on the Gmail platform.
2. The system must ensure high performance, robustness, and reliability.
4.
Test Case 1: Import Questions
Objective: Ensure that lecturers can import questions from an Excel file.
Steps:
Log in as a lecturer.
Navigate to the "Import Questions" section.
Upload an Excel file with questions.
Verify that the questions are correctly imported and appear in the lecturer's
question bank.
Expected Result: The questions from the Excel file are successfully imported and
displayed in the question bank.
Test Case 2: Create and Manage Exams
Objective: Verify that lecturers can create and manage exams.
Steps:
Log in as a lecturer.
Navigate to the "Create Exam" section.
Enter exam details and save.
Start the exam, then stop it and change the test time.
Verify that the exam status and time changes are reflected correctly.
Expected Result: The exam is created, and changes to the exam status and time
are correctly updated.
Test Case 3: View Test Results
Objective: Ensure that students can view their test results.
Steps:
Log in as a student.
Navigate to the "My Tests" section.
Select a completed test and view the results.
Verify the accuracy of the test results displayed.
Expected Result: The student can view accurate test results for completed tests.
5.
User Story 1: Import Questions
As a lecturer,
I want to import questions from an Excel file,
So that I can easily add new questions to my question bank.
User Story 2: Create and Manage Exams
As a lecturer,
I want to create, start, stop, and manage exams,
So that I can efficiently conduct and control the examination process.
User Story 3: View Test Results
As a student,
I want to view my test results after finishing the exam,
So that I can see how I performed and track my progress.