Soft Eng | 2nd Quiz

Question 1

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

Answer 1

spiral model

Question 2

spiral process model was originally proposed by

Answer 2

barry boehm

Question 3

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

Answer 3

spiral model

Question 4

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

Answer 4

spiral development model

Question 5

two main distinguishing features of spiral model

Answer 5

cyclic approach and set of anchor point milestones

Question 6

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

Answer 6

cyclic approach

Question 7

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

Answer 7

set of anchor point milestones

Question 8

concurrent development model is sometimes called

Answer 8

concurrent engineering

Question 9

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

Answer 9

concurrent development model

Question 10

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

Answer 10

modeling

Question 11

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

Answer 11

agility

Question 12

it encourages team structures and attitudes that make communication more simplistic

Answer 12

agility

Question 13

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

Answer 13

agility

Question 14

it can be applied to any software process

Answer 14

agility

Question 15

it is most widely used agile process model

Answer 15

extreme programming

Question 16

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

Answer 16

extreme programming

Question 17

four (4) framework activities of extreme programming

Answer 17

planning, design, coding, and testing

Question 18

a design prototype

Answer 18

spike solutions

Question 19

an iterative refinement of the internal program design

Answer 19

refactoring

Question 20

occurs both before and after coding commences

Answer 20

design

Question 21

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

Answer 21

pair programming

Question 22

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

Answer 22

planning

Question 23

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

Answer 23

extreme programming

Question 24

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

Answer 24

speculation

Question 25

a technique for building complex software and systems

Answer 25

adaptive software development

Question 26

focus on human collaboration and team self-organization

Answer 26

adaptive software development

Question 27

it incorporates three phases: Speculation, Collaboration, and Learning

Answer 27

adaptive software development

Question 28

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

Answer 28

speculate

Question 29

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

Answer 29

adaptive software development

Question 30

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

Answer 30

collaboration

Question 31

it challenges all stakeholders and project team members

Answer 31

learning

Question 32

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

Answer 32

dynamic systems development method

Question 33

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

Answer 33

dynamic systems development method

Question 34

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

Answer 34

feasibility study

Question 35

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

Answer 35

business study

Question 36

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

Answer 36

functional model iteration

Question 37

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

Answer 37

design and build iteration

Question 38

it places the latest software increment into the operational environment

Answer 38

implementation

Question 39

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

Answer 39

dynamic systems development method

Question 40

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

Answer 40

scrum principles

Question 41

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

Answer 41

sprint

Question 42

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

Answer 42

scrum

Question 43

items can be added to the backlog at any time

Answer 43

scrum

Question 44

five framework activities of scrum

Answer 44

requirements, analysis, design, evolution, and delivery

Question 45

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

Answer 45

backlog

Question 46

one of the most lightweight, adaptable approaches to software development

Answer 46

crystal methodology

Question 47

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

Answer 47

crystal

Question 48

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

Answer 48

crystal

Question 49

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

Answer 49

crystal family

Question 50

a model-driven, short-iteration process

Answer 50

feature driven development

Question 51

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

Answer 51

feature driven development

Question 52

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

Answer 52

feature driven development

Question 53

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

Answer 53

requirement engineering

Question 54

it builds a bridge to design and construction

Answer 54

requirement engineering

Question 55

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

Answer 55

requirement engineering

Question 56

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

Answer 56

system requirement specification

Question 57

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

Answer 57

system requirement specification

Question 58

it is also helping the clients to understand their own needs

Answer 58

system requirement specification

Question 59

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

Answer 59

requirement phase

Question 60

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

Answer 60

system requirement specification

Question 61

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

Answer 61

correct

Question 62

it is when every stated requirement has only one interpretation

Answer 62

unambiguous

Question 63

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

Answer 63

complete

Question 64

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

Answer 64

ranked for importance

Question 65

it implies the probability of changes in the requirement in future

Answer 65

stability

Question 66

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

Answer 66

modifiable

Question 67

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

Answer 67

traceable

Question 68

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

Answer 68

forward tracing

Question 69

it implies defining each requirement explicitly referencing its source

Answer 69

backward tracing

Question 70

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

Answer 70

verifiable

Question 71

it is essential for verifiability

Answer 71

unambiguity

Question 72

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

Answer 72

consistent

Question 73

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

Answer 73

functional requirements

Question 74

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

Answer 74

functional requirements

Question 75

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

Answer 75

non-functional requirements

Question 76

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

Answer 76

non-functional requirements

Question 77

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

Answer 77

product requirements

Question 78

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

Answer 78

organisational requirements

Question 79

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

Answer 79

external requirements