Software Development Process & Requirements - Lecture Review

0.0(0)
studied byStudied by 0 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/29

flashcard set

Earn XP

Description and Tags

Question-and-answer flashcards covering SDLC phases, Waterfall vs Agile, Agile Manifesto, requirement analysis importance, types and properties of requirements, requirement-gathering activities and techniques, and related key concepts.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

30 Terms

1
New cards

What does SDLC stand for and what is its main aim?

Software Development Life Cycle; a systematic process to produce high-quality software that meets or exceeds customer expectations within time and cost estimates.

2
New cards

In SDLC, what is the objective of the Planning phase?

Identify project scope and feasibility, then create a schedule, resource plan, and budget.

3
New cards

What is accomplished during the Analysis phase of SDLC?

Detailed understanding and documentation of business needs and processing requirements.

4
New cards

What is the goal of the Design phase in SDLC?

Create the technical solution based on requirements and analysis decisions.

5
New cards

What happens in the Implementation phase of SDLC?

The software solution is built (coded) to satisfy business needs.

6
New cards

Why is Testing performed in SDLC?

To verify the system meets specified requirements and validate that it solves the intended problem.

7
New cards

What is Deployment in the SDLC context?

Making the developed software available in its operational environment.

8
New cards

What is the objective of the Maintenance phase?

Ensure the solution continues to address the problem during operation and manage its eventual decommissioning.

9
New cards

What is a software development methodology?

A predefined set of deliverables, artifacts, and processes used by a team to develop or maintain software.

10
New cards

When is the Waterfall model most suitable?

When requirements are clear and fixed, technology is stable, and the project is short.

11
New cards

Give one benefit of the Waterfall model.

It is simple to understand and manage because each phase has specific deliverables and review processes.

12
New cards

Give one drawback of the Waterfall model.

No working software is produced until late in the life cycle, making it hard to detect issues early.

13
New cards

What is Agile software development?

A lightweight framework promoting iterative development, close collaboration, and adaptive planning to handle changing requirements.

14
New cards

Agile value comparison: Which is valued more—individuals and interactions or processes and tools?

Individuals and interactions.

15
New cards

Name the four core values of the Agile Manifesto.

1) Individuals & interactions, 2) Working software, 3) Customer collaboration, 4) Responding to change.

16
New cards

Which Agile principle identifies the primary measure of progress?

Working software is the primary measure of progress.

17
New cards

Provide one example of an Agile methodology.

Scrum (others: Kanban, XP, Lean, FDD, DSDM).

18
New cards

State one benefit of Agile development.

Customers receive working software at the end of each iteration, providing continuous feedback and visibility.

19
New cards

State one drawback of Agile development.

Heavily depends on active customer interaction; unclear customer input can misdirect the team.

20
New cards

Why is requirement analysis critical in software development?

It ensures the right product is built to meet client and end-user needs and guides planning, design, implementation, and testing.

21
New cards

Define a functional requirement and give an example.

A capability the system must provide; e.g., "ATM system shall dispense money."

22
New cards

Define a non-functional requirement and give an example.

A constraint or quality attribute the system must meet; e.g., "Saving an order must complete in under 5 seconds."

23
New cards

List two properties of a good requirement.

Unambiguous and verifiable (also: consistent, comprehensive, prioritised).

24
New cards

What are the four main activities in requirement analysis?

Eliciting, analysing, modelling, and review & retrospective.

25
New cards

What is scope creep and how does it affect projects?

Uncontrolled growth of requirements, leading to cost overruns and schedule delays.

26
New cards

Name three common techniques for requirement gathering.

Interviews, questionnaires, observation of business processes (others: document review, prototyping, vendor research).

27
New cards

During an interview for requirements, what mix of questions is typically used?

A mixture of open-ended and closed-ended questions.

28
New cards

What is a prototype in requirement gathering?

An initial model (discovery, evolving, or mock-up) used to verify concepts and gather feedback, sometimes evolving into the final system.

29
New cards

What does the activity "Prioritise requirements" involve?

Ranking requirements by importance, urgency, complexity, and effort to balance user needs against limited resources.

30
New cards

In testing, how does verification differ from validation?

Verification checks the product meets specified requirements; validation ensures the product actually solves the intended problem.