SE 102 - FINAL EXAMINATION

During the initial requirements gathering phase, the team realized that key stakeholders were unavailable for meetings. How should the team handle this situation?

• • a) Proceed without their input and make assumptions.

• • b) Reschedule meetings and use surveys to gather input.

• • c) Ignore their input since it’s not critical.

• d) Delay the project indefinitely until they are available.

While developing the system, the team encountered an unexpected bug that caused frequent crashes. What is the best approach to resolve this?

• • a) Ignore the bug and continue development.

• • b) Implement a quick fix without analyzing the root cause.

• • c) Pause development and perform a thorough debugging session.

• d) Revert to an earlier version of the system and start over.

Midway through the project, a major requirement change was requested by the client. How should the team respond?

• • a) Reject the change to stay on schedule.

• • b) Incorporate the change without assessing its impact.

• • c) Assess the impact on timeline and resources before deciding.

• d) Make the change immediately and inform the client of delays later.

The system's performance was suboptimal during testing. Which of the following is the best first step to address this issue?

• • a) Increase the hardware resources.

• • b) Optimize the code and database queries.

• • c) Ignore the performance issues.

• d) Blame the users for not using the system correctly.

During integration, the team found that different modules were not compatible. What should they do?

• • a) Rewrite all modules from scratch.

• • b) Use middleware to facilitate integration.

• • c) Cancel the project due to incompatibility.

• d) Assign blame to the team members responsible for the modules.

The system was deployed, but users are reporting frequent usability issues. What is the best course of action?

• • a) Tell users to adapt to the system as it is.

• • b) Collect feedback and make iterative improvements.

• • c) Ignore the feedback and focus on new features.

• d) Roll back to the previous system and abandon the new one.

A critical data migration step failed during deployment. How should the team address this?

• • a) Ignore the failure and proceed with deployment.

• • b) Perform a rollback and fix the migration script.

• • c) Manually migrate the data without fixing the script.

• d) Blame the database administrators for the failure.

One of the team members consistently misses deadlines. What is the most effective way to handle this situation?

• • a) Publicly reprimand the team member.

• • b) Understand the reasons for delays and provide support.

• • c) Assign their tasks to other team members.

• d) Ignore the delays and hope it improves.

The client requested a feature that was not in the original scope and will require significant additional work. How should the team proceed?

• 1. a) Implement the feature without discussing the impact.

• • b) Explain the impact on the timeline and budget, then decide.

• • c) Refuse to implement the feature to stay within scope.

• • d) Implement the feature and absorb the extra work within the team.

During user acceptance testing, a critical bug was found. How should the team handle this?

• • a) Delay the launch until the bug is fixed.

• • b) Launch the system with the bug and fix it later.

• • c) Ignore the bug if it affects only a few users.

• d) Remove the feature associated with the bug.