Brainscape's Knowledge GenomeTM

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


See full index

Software Engineering II > Quiz 3 > Flashcards

Quiz 3 Flashcards

1
Q

Data Flow Diagrams

A
  • Nodes represent processing units
  • Demonstrate the flow of data via use cases
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

State Transition Diagrams

A
  • States are defined based on system requirements
  • Demonstrate the transition between system states based on system events
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

High-level Requirements

A
  • Describe the purpose of an application and its intended functionality
  • Describe major functions
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Concept of operations / Application Model

A

Vision of how the application will operate

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

3 Types of interview questions

A

Close-ended, open-ended, and probing

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

Overview

A

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

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

Use Cases

A

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

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

Scenario

A

Interaction between the user and system

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

User Stories

A
  • As <role> I want <feature> so that I can accomplish <task></task></feature></role>
  • Must be discrete, estimable, testable, and prioritized
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

A common way to analyze stakeholder requirements is to

A

Interview stakeholders face-to-face

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

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

A

A security requirement

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

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

A

User stories

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

Stakeholders

A

People who have some interest in the outcome of the product

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

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

A

A single stakeholder

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

A data flow diagram describes

A

The flow of data through the application

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

Changing from one GUI state to another is called a

A

Transition

13
Q

Audit trails are an example of what type of requirement

A

Security

14
Q

Detailed Requirements

A

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

15
Q

What ways can functional requirements be classified?

A

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

16
Q

Organizing DR by feature

A
  • Simple
  • Inaccessible, lack of traceability
  • Arrange them by hierarchy
17
Q

Organizing DR by use case

A
  • takes advantage of operational sequences
  • favored by UP
18
Q

Organizing DR by GUI

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

Organizing DR by state

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

Organizing DR by class

A
  • 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
21
Q

Security Requirements

A

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

22
Q

Traceability of detailed requirements means

A

Trace the requirement through the design to the implementation

23
Q

Test driven development is when

A

tests are written before code is implemented

24
Q

Comprehensive requirements means

A

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

25
Q

A set of requirements is self complete if

A

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

26
Q

In order to validate a requirement it must be

A

Testable

27
Q

A requirement is considered to be traceable if

A

it maps back to the design, implementation and test

28
Q

Requirements should be

A

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

29
Q

Target values

A

Numerical goals set in the project relative to various metrics

30
Q

At the requirements level, behavior is described in

A

use cases only

31
Q

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

A

The system does <something>.</something>

32
Q
A

Software Engineering II (7 decks)

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