Which phase of the Software Development Life Cycle (SDLC) involves gathering and inspecting requirements?

What is the purpose of creating a Requirements Specification Document (RSD)?

Which of the following is NOT a phase in the Software Development Life Cycle?

What is the significance of project objectives according to the lecture?

How do project objectives assist in risk identification?

What is a critical skill for a developer in the Requirements Management Process?

Which role is responsible for ensuring that user needs are met during software development?

What does the term 'verification' refer to in the SDLC?

What is the main focus of the 'Maintenance/Evaluation' phase in the SDLC?

Which of the following best describes the role of a business analyst?

What is the first step in the Requirements Management Process?

Why is it important for objectives to be written in business terms?

What is a key outcome of the Requirements/Analysis phase?

Which role is primarily responsible for delivering data-driven recommendations?

What does the acronym SDLC stand for?

What is the role of a Tester in the SDLC?

What is the purpose of conducting research and analysis in the Requirements Management Process?

What is the main focus of the 'Design' phase in the SDLC?

What is a key factor in determining the success of a project according to the text?

Which of the following is a responsibility of a software developer?

What is the significance of stakeholder involvement in the Requirements Management Process?

What is the role of documentation in the project life cycle?

Which phase of the SDLC focuses on the actual coding and execution of the software?

What is the primary goal of the 'Verification/Testing' phase?

What is a common challenge faced during the change management process?

This stage is where you GATHER all the specific details required for a new system. This is also where you determine the first ideas for prototypes.

"Just because you're FINISHED, doesn't mean you can rest easy. There is still the __________."

Theoretically, this stage means that the software or product is READY for market and can now be provided to any end-users.

Developer 1 = "There are a lot of BUGS in this software."

Developer 2 = "How did you know?"

Developer 1 = "Because we went through the ___________."

How many steps are in the systems development life cycle (SDLC)?

Focused on timeline, budget, scope, and making sure people actually do the thing they promised.

Focused on knowledge of how the business currently works and what it really needs.

Deep domain expertise, providing requirements from a business-user perspective, calling out nonsense when others suggest impossible solutions.

The translator between business and tech.

Gathering, analyzing, and documenting requirements, then turning them into something developers/designers can actually use.

Helping people actually adopt the new process/system: training, communication, and minimizing resistance.

Writes the code, builds the features, makes the thing actually work.

Creates how the product looks and feels, ensuring it’s usable and appealing.

Ensures the product works as intended and doesn’t break when users touch it.

During the requirements gathering phase of the SDLC, the enablers like the business analyst uses a prototype (usually simple for non-tech clients) to demonstrate how a proposed system will function.

In the implementation phase, developers write the actual code for the software application.

In the implementation phase, the software is deployed to the production environment, and end-users begin using it.

While some older SDLC models like the Waterfall model are more linear, many modern methodologies, such as Agile, are iterative and allow for cycles of development, testing, and feedback, often returning to previous stages to refine requirements or design.

User feedback is crucial and is sought throughout the SDLC, especially during requirements gathering, prototyping, and testing, to ensure the final product meets their needs.

A system's architecture, including its hardware and software components, is defined during the design phase.

Prototyping in SDLC is an effective technique used in the requirements gathering phase to visualize and confirm the user's needs and expectations for the system's interface and functionality.

The testing phase of the SDLC is primarily concerned with finding and fixing bugs after the software has been released to the public.

In a typical SDLC, the user's feedback is only considered during the final maintenance phase.

A project manager's main responsibility during the maintenance phase is to continuously develop new, major features for the software.