Brainscape's Knowledge GenomeTM

Browse over 1 million classes created by top students, professors, publishers, and experts.


See full index

HCI- FINALAS > Lesson 11 > Flashcards

Lesson 11 Flashcards

1
Q

The Four values of Agile

A

Individuals and Interactions
Working software
Customer Collaboration
Responding to change

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

The Agile software development Lifecycle

A

Meet
Plan
Design
Develop
Test
Evaluate

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

The Six phases of the Agile life cycle

A

Concept
Inception
Iteration or Construction
Release
Production
Retirement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Envision and prioritize projects.

A

Concept

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Identify team members, appointment of funds, and discussion of initial environments and requirements.

A

Inception

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

The development team works to deliver working software based on iteration requirements and feedback

A

Iteration or Construction

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Quality assurance (QA) testing, internal and external training, documentation development, and the iteration is put into production.

A

Release

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

Ongoing software support.

A

Production

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

End-of-life activities, including customer notification and migration.

A

Retirement

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

The Agile iteration workflow

A

Plan requirements
Develop product
Test software
Deliver iteration
Incorporate feedback

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Types of Agile methodologies

A

Scrum
Lean software development
The extreme programming (XP)
Crystal
Kanban

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Is a lightweight Agile framework that can be used by project managers to control all types of iterative and incremental projects.

A

Scrum

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

is another iterative method that places a focus on using effective value stream mapping to ensure the team delivers value to the customer.

A

Lean software development

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

Method is a disciplined approach that focuses on speed and continuous delivery.

A

The extreme programming (XP)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

is the most lightweight and adaptable methodology. It focuses on people and the interactions that occur while working on an Agile project as well as business-criticality and priority of the system under development.

A

Crystal

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

uses a highly visual workflow management method that allows teams to actively manage product creation – emphasizing continuous delivery – without creating more stress in the software development lifecycle (SDLC).

A

Kanban

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
17
Q

The Lean method uses the following primary principles:

A

Increasing learning
Empowering the team
Fostering integrity
Removing waste
Understanding the whole
Making decisions as late as possible
Delivering the product as fast as possible

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
18
Q

Types of Agile methodologies 2

A

The dynamic systems development method (DSDM)
feature-driven development (FDD)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
19
Q

is a response to the need for a common industry framework for rapid software delivery.

A

The dynamic systems development method (DSDM)

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
20
Q

blends software engineering best practices – such as developing by feature, code ownership and domain object modeling – to create a cohesive, model-driven, short-iteration process.

A

feature-driven development (FDD)

21
Q

The_ is an approach to continuously improving a concept, design, or product. Creators produce a prototype, test it, tweak it, and repeat the cycle with the goal of getting closer to the solution.
Iterative model is an alternative to the Waterfall approach, which relies on sequential steps.

A

Iterative process

22
Q

The iterative process refines a product through repeated adjustment cycles. In math, an _ identifies the solution to a problem based on an initial guess. Then, you introduce a sequence of algorithms to find the answer.

A

Iterative Procedure

23
Q

Here are some of the specific benefits of Iterative Process:

A

It’s efficient
It’s timely
It’s cost-effective
It’s collaborative
It improves usability
It eliminates confusion
It’s easier to manage risk
It offers continual improvement

24
Q

You can build your product step-by-step, rather than having to rework an entire plan as changes occur. In addition, the workload of the team is spread out more effectively throughout the project’s development lifecycle.

A

It’s efficient

25
Q

The first iteration allows you to develop the top priority in functionality. Each iteration is based on any improvements identified in the past cycle, and continual testing gives you a clear picture of the status of your project. You can see the results early and often because each iteration is a managed milestone.

A

It’s timely

26
Q

Any changes to the project’s scope or requirements, which are common in most projects, are less costly than with a Waterfall approach.

A

It’s cost-effective

27
Q

You can present the results of each iteration to stakeholders and clients. They can see the evolution of the project and ensure that you are meeting their requirements.

A

It’s collaborative

28
Q

Testing and debugging are easier with smaller iterations, as you can identify defects early in the process and users and customers are involved with each iteration.

A

It improves usability

29
Q

You can detect inconsistencies or flaws in requirements, design, code, and other implementations with each iteration, so you can avoid misunderstandings.

A

It eliminates confusion

30
Q

You tackle the high-risk portions of a project first, and every iteration lets you identify and resolve risks.

A

It’s easier to manage risk

31
Q

Each iteration allows the team to easily incorporate any lessons learned from previous runs and continually improve the development process.

A

It offers continual improvement

32
Q

How Does the Iterative Process Work?

A

Step One: Planning and Requirements
Step Two: Analysis and Design
Step Three: Implementation
Step Four: Testing
Step Five: Evaluation and review

32
Q

In this stage, map out the initial
requirements, gather the related documents, and create a plan and timeline for the first iterative cycle.

A

Step One: Planning and Requirements

33
Q

Finalize the business needs, database models, and technical requirements based on the plan. Create a working architecture, schematic, or algorithm that satisfies your requirements.

A

Step Two: Analysis and Design

34
Q

Develop the functionality and design required to meet the specifications.

A

Step Three: Implementation

35
Q

Identify and locate what’s not working or performing to expectations. Stakeholders, users, and product testers weigh in with their experience.

A

Step Four: Testing

36
Q

Compare this iteration with the requirements and expectations.

A

Step Five: Evaluation and Review

37
Q

Iterative Development Process

A

Step One: Requirements
Step Two: Analysis
Step Three: Design
Step Four: Coding

38
Q

Because you are working on one section — or iteration — of the product, you need to identify the software or hardware requirements for this section. Be clear about who is going to use the system and how will they use it. Identify the objective or task of the product you’re developing, especially if you are working from a project control list. Define what qualifies as a successful outcome for this new section of software.

A

Step One: Requirements

39
Q

Review the requirements to identify and resolve any incomplete, ambiguous, or contradictory expectations. Know what data you should include to produce the software and what data the software will output.

A

Step Two: Analysis

40
Q

Use the final requirement specifications to design the software. Construct the schematics that describe the software behavior, business process, interface layout, and functionality.

A

Step Three: Design

41
Q

Using the software design documents, produce the code that creates the output you identified in the requirements and analysis.

A

Step Four: Coding

42
Q

Iterative Design Process

A

Step One: User Observation and Research.
Step Two: Ideate.
Step Three: Prototype.
Step Four: Analyze.

43
Q

The first question designers ask: “What is the problem we are trying to solve?” You must understand users and analyze their habits to know what you will design and develop.

A

Step One: User Observation and Research

44
Q

In this phase, you and your team can start generating ideas that address the problem you identified through your research.

A

Step Two: Ideate

45
Q

In this “build” phase, your team creates an early example of your product. You will use this to test concepts or systems that you are considering for the final design.

A

Step Three: Prototype

46
Q

It’s time to gather feedback about your design. Ask users to test the prototype, gather feedback on what works and what doesn’t, and evaluate how well your assumptions met their needs.

A

Step Four: Analyze

47
Q

Many software and web applications rely on the iterative _ process because it gives developers more flexibility. Typically, the system development life cycle (SDLC) uses iterative development alongside incremental development. As the system is developed, SDLC becomes increasingly complex.

A

Iterative Development Process

48
Q

A variation of the iterative model, the iterative _ process allows designers to create, test, analyze, and refine ideas quickly during any phase of the design process.
This process, called rapid prototyping or spiral prototyping, allows designers to find success more quickly and involve stakeholders and clients more effectively.

A

Iterative Design Process

HCI- FINALAS (3 decks)

Brainscape helps you reach your goals faster, through stronger study habits.
© 2025 Bold Learning Solutions. Terms and Conditions