Exploring Software Engineering Concepts

What are the main phases of the Software Development Life Cycle?

• Deployment, Testing, Feedback, Release

• Planning, Requirements Analysis, Design, Implementation, Testing, Deployment, Maintenance

• Planning, Design, Testing, Review

• Analysis, Implementation, Support, Maintenance

Describe the Agile methodology and its key principles.

• Agile methodology is primarily concerned with maximizing individual performance over team collaboration.

• Agile emphasizes long-term planning and minimal customer interaction.

• Agile methodology is a linear approach focused on strict planning and documentation.

• Agile methodology is an iterative approach to project management that emphasizes flexibility, collaboration, and customer satisfaction, guided by principles such as customer satisfaction, embracing change, frequent delivery, collaboration, motivated individuals, face-to-face communication, working software, sustainable development, technical excellence, simplicity, and self-organizing teams.

What is requirements elicitation and why is it important?

• Requirements elicitation is only about documenting existing features.

• Requirements elicitation is the process of gathering and defining stakeholder needs, and it is important for ensuring project success and alignment with user expectations.

• It is a process that focuses solely on technical specifications.

• Requirements elicitation is unnecessary for small projects.

List three techniques used for requirements elicitation.

• Prototyping techniques

• Brainstorming sessions

• Focus groups

• Interviews, surveys, workshops

Differentiate between functional and non-functional requirements.

• Functional requirements are only about user interface design.

• Non-functional requirements are always related to user roles.

• Functional requirements do not impact system performance.

• Functional requirements describe specific behaviors and functions, while non-functional requirements address system performance and quality attributes.

Provide an example of a functional requirement.

• The system shall allow users to change their profile picture.

• The system shall send an email notification to users.

• The system shall allow users to log in using their email and password.

• The system shall display the current weather.

Provide an example of a non-functional requirement.

• The system shall have a user-friendly interface.

• The system shall be compatible with all browsers.

• The system shall store user data securely.

• The system shall respond to user queries within 2 seconds.

What is stakeholder analysis and its significance in software projects?

• Stakeholder analysis is a method to evaluate software bugs.

• Stakeholder analysis focuses solely on financial outcomes.

• Stakeholder analysis is only relevant for marketing projects.

• Stakeholder analysis is crucial in software projects as it helps identify key stakeholders, understand their needs, and manage their expectations, leading to improved project outcomes.

Identify key stakeholders in a software development project.

• Graphic designers

• Project manager, software developers, quality assurance testers, product owners, end-users, business analysts.

• System administrators

• Marketing team members

How does Agile methodology handle changes in requirements?

• Agile methodology requires all changes to be documented and approved by a committee.

• Agile methodology handles changes in requirements by allowing flexibility and encouraging iterative development.

• Agile methodology strictly prohibits any changes to requirements once the project starts.

• Agile methodology ignores changes in requirements to maintain a fixed scope.