411 Test 1

Front 1

Dialogue with user or manager to obtain their requirements

Back 1

Interviewing

Front 2

conversational, questions with no specific answers in mind

Back 2

Open-Ended Interviewing

Front 3

structured, questions with limited range of possible answers

Back 3

Close-Ended Interviewing

Front 4

document for developing, planning and conducting an interview.

Back 4

Interview Guide

Front 5

Each question in an interview guide can include both ________ and __________ information

Back 5

verbal; non-verbal

Front 6

Advantages of Individual Interviews

Back 6

Easier to schedule than group interviews

Front 7

Disadvantages of Individual Interviews

Back 7

Contradictions and inconsistencies between interviewees
Follow-up discussions are time consuming

Front 8

Advantages of Group Interviews

Back 8

More effective use of time
Can hear agreements and disagreements at once
Opportunity for synergies

Front 9

Disadvantages of Group Interviews

Back 9

More difficult to schedule than individual interviews
Risk of social desirability in answers

Front 10

A facilitated process that supports idea generation by groups

Back 10

Nominal Group Technique (NGT)

Front 11

Watching users do their jobs

Back 11

Direct Observation

Front 12

Can provide more accurate information than self-reporting (like questionnaires and interviews)

Back 12

Direct Observation

Front 13

Review of existing business documents

Back 13

Document Analysis

Front 14

Can give a historical and “formal” view of system requirements

Back 14

Document Analysis

Front 15

Four types of useful documents

Back 15

Written work procedures
Business form
Report
Description of current information system

Front 16

Describes how a job is performed
Includes data and information used and created in the process of performing the job or task

Back 16

Written work procedures

Front 17

Explicitly indicate data flow in or out of a system

Back 17

Business Form

Front 18

Enables the analyst to work backwards from the report to the data that generated it

Back 18

Report

Front 19

business document that formally describes work processes, provides useful information regarding system functionality and logic.

Back 19

Written work procedure

Front 20

Potential Problems with Procedure Documents

Back 20

May involve duplication of effort
May have missing procedures
May be out of date
May contradict information obtained through interviews

Front 21

The official way a system works as described in organization’s documentation

Back 21

Formal

Front 22

The way a system actually works in practice
Interviews and observation reveal informal system

Back 22

Informal

Front 23

Brings together key users, managers, and systems analysts

Back 23

Joint Application Design (JAD)

Front 24

Facilitate sharing of ideas and voicing of opinions about system requirements
Not used by most organizations

Back 24

Group Support Systems

Front 25

Used to analyze existing systems
Help discover requirements to meet changing business conditions

Back 25

CASE tools

Front 26

Iterative development process
Rudimentary working version of system is built
Refine understanding of system requirements in concrete terms

Back 26

System prototypes

Front 27

facilitates group process

Back 27

Session Leader

Front 28

active, speaking participants

Back 28

Users

Front 29

active, speaking participants

Back 29

Managers

Front 30

high-level champion, limited participation

Back 30

Sponsor

Front 31

should mostly listen
Scribe: record session activities

Back 31

Systems Analysts

Front 32

should mostly listen

Back 32

IS Staff

Front 33

Documentation detailing existing system
Features of proposed system

Back 33

End Result

Front 34

CASE Tools During JAD

Back 34

Upper CASE tools are used
Enables analysts to enter system models directly into CASE during the JAD session
Screen designs and prototyping can be done during JAD and shown to users

Front 35

Quickly converts requirements to working version of system

Back 35

Prototyping

Front 36

Prototyping Drawbacks

Back 36

Tendency to avoid formal documentation
Difficult to adapt to more general user audience
Sharing data with other systems is often not considered
Systems Development Life Cycle (SDLC) checks are often bypassed

Front 37

Search for and implementation of radical change in business processes to achieve breakthrough improvements in products and services

Back 37

Business Process Reengineering (BPR)

Front 38

Reorganize complete flow of data in major sections of an organization
Eliminate unnecessary steps
Combine steps
Become more responsive to future change

Back 38

BPR Goals

Front 39

Technologies that enable the breaking of long-held business rules that inhibit organizations from making radical business changes

Back 39

Disruptive technologies

Front 40

Replace traditional SDLC waterfall with iterative analyze – design – code – test cycle

Back 40

Continual user involvement

Front 41

Focuses on user goals, roles, and tasks

Back 41

Agile usage-centered design

Front 42

Based on eXtreme programming
Exploration, steering, commitment

Back 42

The Planning Game

Front 43

Graphically represent the processes that capture, manipulate, store, and distribute data between a system and its environment and among system components

Back 43

Process Modeling

Front 44

Scope of system

Back 44

Context data flow diagram (DFD)

Front 45

Enables analysts to understand current system

Back 45

DFDs of current physical and logical system

Front 46

Technology independent
Show data flows, structure, and functional requirements of new system

Back 46

DFDs of new logical system

Front 47

A picture of the movement of data between external entities and the processes and data stores within a system

Back 47

Data Flow Diagram (DFD)

Front 48

depict logical data flow independent of technology

Back 48

DFDs

Front 49

depict details of physical systems

Back 49

Flowcharts

Front 50

work or actions performed on data (inside the system)

Back 50

Process DFD Symbol

Front 51

data at rest (inside the system)

Back 51

Data store DFD symbol

Front 52

external entity that is origin or destination of data (outside the system)

Back 52

Source/sink DFD symbol

Front 53

arrows depicting movement of data

Back 53

Data Flow DFD System

Front 54

No process can have only _____ or only _________ processes must have both ________ and ______________.

Back 54

outputs/inputs
(Part of DFD Diagramming Rules for *Process*)

Front 55

Process labels should be _______ phrases

Back 55

verb

(Part of DFD Diagramming Rules for *Process*)

Front 56

All flows to or from a data store must move through a _______________.

Back 56

process

DFD Diagramming Rules for *Data Store*

Front 57

Data store labels should be _________ phrases

Back 57

noun

DFD Diagramming Rules for *Data Store*

Front 58

No data moves directly between external entities without going through a ________________

Back 58

process

DFD Diagramming RulesSource/Sink

Front 59

Interactions between external entities without _________________ are outside the system and therefore not represented in the DFD.

Back 59

intervening processes

DFD Diagramming RulesSource/Sink

Front 60

Source and sink labels should be ________ phrases

Back 60

noun

DFD Diagramming RulesSource/Sink

Front 61

Bidirectional flow between process and data store is represented by ____________

Back 61

two separate arrows.

DFD Diagramming RulesData Flow

Front 62

Forked data flow must refer to __________ (not different data items) from a common location to multiple destinations.

Back 62

exact same data item

DFD Diagramming RulesData Flow

Front 63

Joined data flow must refer to ____________ (not different data items) from multiple sources to a common location.

Back 63

exact same data item

DFD Diagramming RulesData Flow (cont.)

Front 64

Data flow cannot go directly from a process to itself, must go through ______________

Back 64

intervening processes.

DFD Diagramming RulesData Flow (cont.)

Front 65

Data flow from a process to a data store means __________

Back 65

update (insert, delete or change).

DFD Diagramming RulesData Flow (cont.)

Front 66

Data flow from a data store to a process means ___________ or _____________

Back 66

retrieve or use.

DFD Diagramming RulesData Flow (cont.)

Front 67

Data flow labels should be __________ phrases.

Back 67

noun

DFD Diagramming RulesData Flow (cont.)

Front 68

An iterative process of breaking a system description down into finer and finer detail

Back 68

Functional Decomposition

Front 69

High-level processes described in terms of lower-level sub-processes

Back 69

Functional Decomposition

Front 70

Overview of the organizational system

Back 70

Context DFD (DFD Level)

Front 71

Representation of system’s major processes at high level of abstraction

Back 71

Level-0 DFD

Front 72

Results from decomposition of Level 0 diagram

Back 72

Level-1 DFD

Front 73

Results from decomposition of Level n-1 diagram

Back 73

Level-n DFD

Front 74

shows the system boundaries, external entities that interact with the system, and major information flows between entities and the system.

Back 74

Context Diagram

Front 75

shows the system’s major processes, data flows, and data stores at a high level of abstraction.

Back 75

Level-0 DFD

Front 76

shows the sub-processes of one of the processes in the Level-0 DFD.

Back 76

Level-1 DFD

Front 77

shows the sub-processes of one of the processes in the Level n-1 DFD.

Back 77

Level-n DFD

Front 78

The conservation of inputs and outputs to a data flow process when that process is decomposed to a lower level

Back 78

DFD Balancing

Front 79

the process of the context diagram has only one input but the Level-0 diagram has two inputs

Back 79

Unbalanced DFD

Front 80

the numbers of inputs and outputs of context diagram process equal the number of inputs and outputs of Level-0 diagram.

Back 80

Balanced DFD

Front 81

Four Different Types of DFD

Back 81

Current Physical
Current Logical
New Logical
New Physical

Front 82

Process labels identify technology (people or systems) used to process the data.
Data flows and data stores identify actual name of the physical media.

Back 82

Current Physical

Front 83

Physical aspects of system are removed as much as possible.
Current system is reduced to data and processes that transform them

Back 83

Current Logical

Front 84

Includes additional functions
Obsolete functions are removed
Inefficient data flows are reorganized

Back 84

New Logical

Front 85

Represents the physical implementation of the new system

Back 85

New Physical

Front 86

The process of discovering discrepancies between two or more sets of data flow diagrams or discrepancies within a single DFD

Back 86

Gap Analysis

Front 87

Depiction of a system’s behavior or functionality under various conditions as the system responds to requests from users

Back 87

Use Cases

Front 88

use case diagram symbols

Oval

Back 88

Use Case

Front 89

use case diagram symbols

stick figure

Back 89

Actor

Front 90

use case diagram symbols

Rectangle

Back 90

Boundary

Front 91

use case diagram symbols

Line

Back 91

Connection

Front 92

use case diagram symbols

Line w/ <<include>>

Back 92

Include Relationship

Front 93

use case diagram symbols

Line w/ <<extend>>

Back 93

Extend Relationship

Front 94

external entity that interacts with the system.

Back 94

Actor

Front 95

An actor is a ______, not a specific user

Back 95

role

Front 96

the dividing line between the system and its environment

Back 96

Boundary

Front 97

Use cases are ________ the boundary

Back 97

within

Front 98

Actors are __________ of the boundary

Back 98

outside

Front 99

an association between an actor and a use case

Back 99

Connection

Front 100

A connection between two use cases

Back 100

<<extend>> Relationship

<<include>> Relationship

Front 101

Document containing detailed specifications for a use case

Back 101

Written Use Cases