Brainscape's Knowledge GenomeTM

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


See full index

2nd year, 2nd Sem > Soft Eng | 2nd Quiz > Flashcards

Soft Eng | 2nd Quiz Flashcards

1
Q

an evolutionary software process model that couples the iterative nature of prototyping with the controlled and systematic aspects of the waterfall model

A

spiral model

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

spiral process model was originally proposed by

A

barry boehm

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

it provides the potential for rapid development of increasingly more complete versions of the software

A

spiral model

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

a risk-driven process model generator that is used to guide multi- stakeholder concurrent engineering of software intensive systems

A

spiral development model

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

two main distinguishing features of spiral model

A

cyclic approach and set of anchor point milestones

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

it is for incrementally growing a system’s degree of definition and implementation while decreasing its degree of risk

A

cyclic approach

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

it is for ensuring stakeholder commitment to feasible and mutually satisfactory system solutions

A

set of anchor point milestones

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

concurrent development model is sometimes called

A

concurrent engineering

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

it allows a software team to represent iterative and concurrent elements of any of the process models

A

concurrent development model

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

this activity may be in any one of the states noted at any given time

A

modeling

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

is dynamic, content specific, aggressively change embracing, and growth oriented

A

agility

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

it encourages team structures and attitudes that make communication more simplistic

A

agility

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

it emphasizes rapid delivery of operational software and de-emphasizes the importance of intermediate work products

A

agility

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

it can be applied to any software process

A

agility

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

it is most widely used agile process model

A

extreme programming

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

it uses an object-oriented approach as its preferred development paradigm

A

extreme programming

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

four (4) framework activities of extreme programming

A

planning, design, coding, and testing

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

a design prototype

A

spike solutions

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

an iterative refinement of the internal program design

A

refactoring

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

occurs both before and after coding commences

A

design

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

developers work in pairs, checking each other’s work and providing the support to always do a good job

A

pair programming

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

this framework activity of XP, stores user stories, values, acceptance test criteria, and iteration plan

A

planning

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

it defines four (4) framework activities: Planning, Design, Coding, and Testing

A

extreme programming

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

this phase of adaptive software development incorporates adaptive cycle planning, mission statement, project constraints, basic requirements, and time-boxed release plan

A

speculation

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

a technique for building complex software and systems

A

adaptive software development

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

focus on human collaboration and team self-organization

A

adaptive software development

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

it incorporates three phases: Speculation, Collaboration, and Learning

A

adaptive software development

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

refers to the planning paradox—outcomes are unpredictable, therefore, endless suppositions on a product’s look and feel are not likely to lead to any business value

A

speculate

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

in this mindset, planning is to speculation as intention is to need

A

adaptive software development

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

it represents a balance between managing the doing and creating and maintaining the collaborative environment

A

collaboration

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

it challenges all stakeholders and project team members

A

learning

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

an agile software development approach that provides a framework for building and maintaining systems which meet tight time constraints through the use of incremental prototyping in a controlled project environment

A

dynamic systems development method

33
Q

an iterative software process in which each iteration follows the 80 percent rule

A

dynamic systems development method

34
Q

it establishes the basic business requirements and constraints associated with the application to be built

A

feasibility study

35
Q

it establishes the functional and information requirements that will allow the application to provide business value

A

business study

36
Q

produces a set of incremental prototypes that demonstrate functionality for the customer

A

functional model iteration

37
Q

revisits prototypes built during functional model iteration to ensure that each has been engineered in a manner that will enable it to provide operational business value for end users

A

design and build iteration

38
Q

it places the latest software increment into the operational environment

A

implementation

39
Q

can be combined with XP to provide a combination approach that defines a solid process model

A

dynamic systems development method

40
Q

they are consistent with the agile manifesto and are used to guide development activities within a process that incorporates the five framework activities: requirements, analysis, design, evolution, and delivery

A

scrum principles

41
Q

within each framework activity, work tasks occur within a process pattern called

A

sprint

42
Q

emphasizes the use of a set of software process patterns that have proven effective for projects with tight timelines, changing requirements, and business criticality

A

scrum

43
Q

items can be added to the backlog at any time

A

scrum

44
Q

five framework activities of scrum

A

requirements, analysis, design, evolution, and delivery

45
Q

a prioritized list of project requirements or features that provide business value for the customer

A

backlog

46
Q

one of the most lightweight, adaptable approaches to software development

A

crystal methodology

47
Q

it is actually comprised of a family of agile methodologies such as Crystal Clear, Crystal Yellow, Crystal Orange and others, whose unique characteristics are driven by several factors such as team size, system criticality, and project priorities

A

crystal

48
Q

it promotes early, frequent delivery of working software, high user involvement, adaptability, and the removal of bureaucracy or distractions

A

crystal

49
Q

it addresses the realization that each project may require a slightly tailored set of policies, practices, and processes in order to meet the project‘s unique characteristics

A

crystal family

50
Q

a model-driven, short-iteration process

A

feature driven development

51
Q

it continues with a series of two-week “design by feature, build by feature”

A

feature driven development

52
Q

it features are small, “useful in the eyes of the client” results

A

feature driven development

53
Q

it means that requirements for a product are defined, managed and tested systematically

A

requirement engineering

54
Q

it builds a bridge to design and construction

A

requirement engineering

55
Q

it provides the appropriate mechanism for understanding what the customer wants, analyzing need, assessing feasibility, negotiating a reasonable solution, specifying the solution unambiguously, validating the specification, and managing the requirements as they are transformed into an operational system

A

requirement engineering

56
Q

it contains a complete information description, a detailed functional description, a representation of system behavior, an indication of performance requirements and design constraints, appropriate validation criteria, and other information pertinent to requirements

A

system requirement specification

57
Q

it is a document that completely describes what the proposed software should do without describing how software will do it

A

system requirement specification

58
Q

it is also helping the clients to understand their own needs

A

system requirement specification

59
Q

the basic goal of this phase is to produce the SRS, which describes the complete behavior of the proposed software

A

requirement phase

60
Q

it is said to be of high quality when the developer and user easily understand the prepared document

A

system requirement specification

61
Q

it is when all user requirements are stated in the requirements document

A

correct

62
Q

it is when every stated requirement has only one interpretation

A

unambiguous

63
Q

it is when the requirements clearly define what the software is required to do

A

complete

64
Q

all requirements are not equally important, hence each requirement is identified to make differences among other requirements

A

ranked for importance

65
Q

it implies the probability of changes in the requirement in future

A

stability

66
Q

the requirements of the user can change, hence requirements document should be created in such a manner that those changes can be modified easily, consistently maintaining the structure and style of the SRS

A

modifiable

67
Q

it is when the source of each requirement is clear and facilitates the reference of each requirement in future

A

traceable

68
Q

it implies that each requirement should be traceable to design and code elements

A

forward tracing

69
Q

it implies defining each requirement explicitly referencing its source

A

backward tracing

70
Q

it is when the specified requirements can be verified with a cost-effective process to check whether the final software meets those requirements

A

verifiable

71
Q

it is essential for verifiability

A

unambiguity

72
Q

it is when the subsets of individual requirements defined do not conflict with each other

A

consistent

73
Q

these are statements of services the system should provide, how the system should react to particular inputs, and how the system should behave in particular situations

A

functional requirements

74
Q

in some cases, it may also explicitly state what the system should not do

A

functional requirements

75
Q

these are constraints on the services or functions offered by the system

A

non-functional requirements

76
Q

it often applies to the system as a whole rather than individual system features or services

A

non-functional requirements

77
Q

requirements which specify that the delivered product must behave in a particular way e.g. execution speed, reliability, etc.

A

product requirements

78
Q

requirements which are a consequence of organizational policies and procedures e.g. process standards used, implementation requirements, etc.

A

organisational requirements

79
Q

requirements which arise from factors which are external to the system and its development process e.g. interoperability requirements, legislative requirements, etc.

A

external requirements

2nd year, 2nd Sem (11 decks)

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