Quiz 3

Question 1

Data Flow Diagrams

Answer 1

• Nodes represent processing units
• Demonstrate the flow of data via use cases

Question 2

State Transition Diagrams

Answer 2

• States are defined based on system requirements
• Demonstrate the transition between system states based on system events

Question 3

High-level Requirements

Answer 3

• Describe the purpose of an application and its intended functionality
• Describe major functions

Question 4

Concept of operations / Application Model

Answer 4

Vision of how the application will operate

Question 5

3 Types of interview questions

Answer 5

Close-ended, open-ended, and probing

Question 6

Overview

Answer 6

A section in the requirements analysis document that helps the reader quickly understand the main purpose of the intended application

Question 7

Use Cases

Answer 7

Describe the typical sequence of interactions between users of an application and the application itself, and provide a narrative of how the application is used

Question 8

Scenario

Answer 8

Interaction between the user and system

Question 9

User Stories

Answer 9

• As <role> I want <feature> so that I can accomplish <task></task></feature></role>
• Must be discrete, estimable, testable, and prioritized

Question 10

A common way to analyze stakeholder requirements is to

Answer 10

Interview stakeholders face-to-face

Question 10

Ensuring the application is compliant with the HIPAA privacy act, is an example of

Answer 10

A security requirement

Question 11

Within agile projects, the description of user actions through the application is called

Answer 11

User stories

Question 12

Stakeholders

Answer 12

People who have some interest in the outcome of the product

Question 12

The SCRUM agile process insists that the customer community supply how many stakeholders?

Answer 12

A single stakeholder

Question 12

A data flow diagram describes

Answer 12

The flow of data through the application

Question 13

Changing from one GUI state to another is called a

Answer 13

Transition

Question 13

Audit trails are an example of what type of requirement

Answer 13

Security

Question 14

Detailed Requirements

Answer 14

Complete list of specific properties and functionality that the application must possess in complete detail

Question 15

What ways can functional requirements be classified?

Answer 15

By feature, Use case, GUI, state, and class

Question 16

Organizing DR by feature

Answer 16

• Simple
• Inaccessible, lack of traceability
• Arrange them by hierarchy

Question 17

Organizing DR by use case

Answer 17

• takes advantage of operational sequences
• favored by UP

Question 18

Organizing DR by GUI

Answer 18

• direct connection with use of the application
• good traceability
• often fails to cover all requirements

Question 19

Organizing DR by state

Answer 19

• appropriate when requirements for each state are distinct
• events that affect the application while in a certain state are listed

Question 20

Organizing DR by class

Answer 20

• categorization first by selecting classes, then placing requirements on the classes
• promotes one-to-one traceability
• changing classes can break the connection between requirements and design

Question 21

Security Requirements

Answer 21

1) User ID capabilities 2) Person or entity authentication capabilities 3) Security logoff 4) Audit-trails for security related events 5) Password specifications 6) Controls to ensure data integrity 7) Retrievable record of encryption methods 8) Info on security attributes of the system

Question 22

Traceability of detailed requirements means

Answer 22

Trace the requirement through the design to the implementation

Question 23

Test driven development is when

Answer 23

tests are written before code is implemented

Question 24

Comprehensive requirements means

Answer 24

the extent to which the customer’s wants and needs are included

Question 25

A set of requirements is self complete if

Answer 25

it contains every part whose inclusion is necessitated by parts already present

Question 26

In order to validate a requirement it must be

Answer 26

Testable

Question 27

A requirement is considered to be traceable if

Answer 27

it maps back to the design, implementation and test

Question 28

Requirements should be

Answer 28

Accessible, Comprehensive, Understandable, consistent, secure, self-complete, testable, traceable, and effectively prioritized

Question 29

Target values

Answer 29

Numerical goals set in the project relative to various metrics

Question 30

At the requirements level, behavior is described in

Answer 30

use cases only

Question 31

What linguistic test can be used to determine if something is a feature of the system (or one of functional requirements)?

Answer 31

The system does .