Brainscape's Knowledge GenomeTM


Top Flashcards (Certified)
All Flashcards

SAD > Chapter 4 > Flashcards

Chapter 4 Flashcards

(61 cards)

Start Studying
1
Q

actor

A

An external entity with a specific role. In a use case model, actors are used to model interaction with the system

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

agile methods

A

Systems development methods that attempt to develop a system incrementally by building a series of prototypes and constantly adjusting them to user requirements. Also called adaptive methods

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

brainstorming

A

a fact-finding technique for gaining information through the use of a small group discussion of a specific problem, opportunity, or issue.

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

business process model (BPM)

A

A graphical representation of one or more business process

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

Business Processing Modeling Notation (BPMN)

A

A standard set of shapes and symbols used to represent events, processes, and workflows in computer-based modeling tools.

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

close-ended questions

A

Queries that limit or restrict the range of responses. Used in the interview process when specific information or fact verification is desired.

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

construction phase

A

A phase that focuses on program and application development tasks similar to SDLC

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

cutover phase

A

A phase that resembles the final tasks in the SDLC implementation phase, including data conversion, testing, changeover to the new system, and user training

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

data flow diagram (DFD)

A

Diagram that shows how the system stores, processes, and transforms data into useful information

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

Document Review

A

A review of baseline documentation. A useful fact-finding technique that helps an analyst understand how the current system is supposed to work.

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

Engaged listening

A

The ability to really concentrate on what someone is saying and avoid the temptation to hear what is expected. Also includes noticing nonverbal communication

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

epic

A

In an agile project, a simple, high level statement of a requirement.

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

fact-finding

A

The process of gathering requirements

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

feature

A

In an agile project, a simple, high level statement of a requirement

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

fill-in form

A

A template used to collect data on the Internet or a company interest

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

functional decomposition diagram (FDD)

A

A top-down represetnation of business functions and processes. Also called structure chart.

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

functional requirement

A

A statement of the services a system provides

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

Hawthorne Effect

A

Phenomenon where employees who know they are being observed are more productive

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

histogram

A

a common tool for showing the distribution of questionnaire or sampling results. It takes the form of a vertical bar chart

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

informal structure

A

An organization based on interpersonal relationships, which can develop from previous work assignments, physical proximity, unofficial procedures, or personal relationships

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

interview

A

A planned meeting during which information is obtained from another person

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

joint application development (JAD)

A

A systems development technique that uses a task force of users, managers, and IT professionals who work together to gather information, discuss business needs, and define the new system requirements

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

leading questions

A

Queries that suggest or favor a particular reply

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

non-functional questions

A

A statement of operational system constraints

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
25
Observaton
A fact-finding technique where an analyst sees a system in action. This allows the verification of statements made in interviews
26
open-ended questions
Queries that allow for a range of answers. They encourage spontaneous and unstructured responses and are useful in understanding a larger process.
27
personal information manager (PIM)
a tool that helps manager tasks and schedules. Many handheld devices also include this function
28
pool
Overall diagram in BPMN
29
productivity software
Applications such as processing, spreadsheet, database management, and presentation graphics program
30
questionnaire
A document containing a number of standard questions that can be sent to many individuals. Also called a survey
31
random sample
A selection taken in a random, unplanned manner.
32
range of response questions
Close ended questions that ask the person to evaluate something by providing limited answers to specific responses or on a numeric scale
33
rapid application development (RAD)
A team-based technique that speeds up information systems development and produces a functioning information system. RAD is similar concept to JAD but goes further by including all phases of the SDLC
34
requirements definition
A description of the system requirements from the user's point of view
35
requirements elicitation
The process of gathering requirements
36
requirements engineering
Used in the system's planning phase of the SDLC. It involves fact-finding to describe the current system and identify the requirements for the new system.
37
requirements planning phase
A phase that combines elements of the system planning and systems analysis phases of the SDLCr
38
requirements planning phase
A phase that combines elements of the systems planning and systems analysis phases of the SDLC
39
requirements specification
A description of the system requirements from the analyst or engineering team's point of view
40
research
Important fact-finding technique that includes the review of journals, periodicals, and books to obtain background information, technical material, and news about industry trends and developments
41
sampling
a process where an analysts collects samples of actual documents, which could include records, reports, or various forms
42
scalability
A characteristic of a system, implying that the system can be expanded, modified, or downsized easily to meet rapidly changing needs of a business enterprise
43
scenarios
In an agile project, a real-world example on how users will interact with the system
44
Scrum
A popular technique for agile project management. Derived from a rugby term. In Scrum, team members play specific roles and interact in intense sessions
45
sequence diagram
a UML diagram that shows the timing of transactions between objects as they occur during a system execution
46
site visit
A trip to the physical location to observe a system in use at another location
47
stratified sample
A set metric is collected across functional areas.
48
storyboard
In an agile project, a simple graphic organizer that helps systems analysts visualize the status of a project
49
structured brainstorming
A group discussion where each participant speaks when it is his or her turn or passes
50
survey
A document containing a number of standard questions can be sent to many individuals
51
swim lanes
In a business diagram, the overall diagram is called a pool and the designated customer areas are called swim lanes
52
SysML
A dialect of UML 2, used for representing requirements (and other things), primarily in MBSE applications
53
system requirement
A characteristic or feature that must be included in an information system to satisfy business requirements and acceptable to users
54
systematic sample
A sample that occurs at a predetermined periodicity. For example, every 10th customer record might be selected
55
total cost of ownership (TCO)
A number used in assessing costs, which includes ongoing support and maintenance costs as well as acquisition costs
56
traceability
The ability to follow a requirement backward to its origins and forward through the SDLC to link design documents, code fragments, and test artifacts
57
Unified Modeling Language (UML)
A widely used method of visualizing and documenting software systems design. UML uses object-oriented design concept, but is independent of any specific programming languages that can be used to describe business processes and requirements generally
58
unstructured brainstorming
A group discussion where any participant can speak at any time
59
use case diagram
A visual representation that represents the interaction between users and the information system in UML
60
user design phase
In this phase, users interact with system analysts and develop models and prototypes that represent all system processes, outputs, and inputs
61
user stories
In an agile project, a set of more refined requirements.

SAD (5 decks)

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