MS466 Exam 2

alias

term used in data dictionaries to indicate an alternate name used to describe the same data element

black box

metaphor for a process or an action that produces results in a non transparent manner

black hole

a process that has no output

business logic

rules to determine how a system handles data and produces useful information, reflecting the operational requirements of the business

child diagram

the lower-level diagram in an exploded DFD

context diagram

a top-level view of an information system that shows the boundaries and scope

control structure

serve as building blocks for a process; have one entry and exit point; AKA logical structure

data dictionary

a central storehouse of information about a system’s data

data element

a single characteristic or fact about an entity; smallest piece of data that has meaning within an information system; AKA data item, attribute, or field

data flow

a path for data to move from one part of the information system to another

data flow diagram (DFD)

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

data repository

a symbol used in in DFDs to represent a situation in which a system must retain data because one or more processes need to use that stored data at a later time; AKA data store

data structure

a meaningful combination of related data elements that are included in a data flow or retained in a data store; a framework for organizing and storing data

decision table

a table that shows a logical structure, with all possible combinations of conditions and resulting actions

decision tree

a graphical representation of the conditions, actions, and rules found in a decision table

decomposing

another way of conveying a process or system that has been broken down from a general, top-level view to more detail; exploded or partitioned can also be used

diagram 0

a diagram depicting the first level of detail below the initial context diagram; zooms in on the context diagram and shows major processes, data flows and data stores, as well as repeating the external entities and data flows that appear in the context diagram

diverging data flow

a data flow in which the same data travels to two or more different locations

domain

the set of values permitted for a data element

entity

a person, place, thing, or event for which data is collected and maintained

field

a single characteristic or fact about an entity; AKA data element, data item

four-model approach

a physical model of the current system, a logical model of the current system, a logical model of the new system, a physical model of the new system are all developed

functional primitive

a single function that is not exploded further; logic for this is documented in a data dictionary process description

Gane and Sarson

a popular symbol set used in DFDs. Processes, data flows, data stores, and external entities all have unique symbols

gray hole

a process with an input obviously insufficient to generate the shown output

iteration

the completion of a process step that is repeated until a specific condition changes

leveling

the process of drawing a series of increasingly detailed diagrams to reach the desired level of detail

logical model

shows what a system must do, regardless of how it will be implemented physically

looping

refers to a process step that is repeated until a specific condition changes

modular design

a design that can be broken down into logical blocks; AKA partitioning or top-down design

parent diagram

the higher or more top-level diagram in an exploded DFD

partitioning

the breaking down of overall objectives into subsystems and modules

physical model

a model that describes how a system will be constructed

process

procedure or task that users, managers, and IT staff members perform

process 0

in a DFD, represents the entire information system but does not show the internal workings

process description

a documentation of a functional primitive’s details

pseudocode

a technique for representing program logic

record

a set of related fields that describe one instance, or member of an entity; AKA tuple

selection

a control structure in modular design, it is the completion of two or more process steps based on the results of a test or condition

sequence

the completion of steps in sequential order, one after another

sink

an external entity that receives data from an information system

source

an external entity that supplies data to an information system

spontaneous generation

an unexplained generation of data or information

structured English

a subset of standard English that describes logical processes clearly and accurately

terminator

a DFD symbol that indicates a data origin or final destination; AKA external entity

validity rules

checks that are applied to data elements when data is entered to ensure that the value entered is valid

Yourdon

a type of symbol set that is used in DFDs

actor

an external entity with a specific role; used to model interaction with the system

business process model (BPM)

graphical representation of one or more business processes

closed-ended questions

queries that limit or restrict the range of responses

construction phase

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

cutover phase

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

data flow diagram (DFD)

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

document review

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

engaged listening

ability to concentrate on what someone is saying rather than hearing what is expected

epic

in agile, a simple, high-level statement of a requirement; AKA feature

fact-finding

the process of gathering requirements; AKA requirements elicitation

functional decomposition diagram (FDF)

a top-down representation of business functions and processes; AKA structure chart

functional requirement

a statement of the services a system provides

Hawthorne effect

a phenomenon where employees who know they are being observed are more productive

informal structure

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

joint application development (JAD)

a system 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

leading questions

queries that suggest or favor a particular reply

non-functional requirements

a statement of operational system constraints; AKA quality attributes

observation

a fact-finding technique where an analyst sees a system in action; allows verification of statements made in interviews

open-ended questions

queries that allow for a range of answers

personal information manager (PIM)

a tool that helps manage tasks and schedules; included in many handheld devices

pool

the overall diagram in BPMN

productivity software

applications such as word processing, spreadsheet, database management, and presentation graphics programs

rapid application development (RAD)

a team-based technique that speeds up information systems development and produces a functioning information system; similar to JAD but goes further by including all phases of SDLC

requirements definitions

description of the system requirements from the user’s point of view

requirements engineering

used in the systems planning phase of the SDLC; involves fact finding to describe the current system and identify the requirements for the new system

requirements planning phase

phase that combines elements of the systems planning and systems analysis phase of the SDLC

requirements specifications

description of the system requirements from the analyst or engineering team’s point of view

scalability

a characteristic of a system, implying that the system can be expanded, modified, or downsized easily to meet the rapidly changing needs of a business enterprise

scenarios

in agile, a real-world example of how users will interact with the system

sequence diagram

a UML diagram that shows the timing of transactions between objects as they occur during system execution

stratified sample

a set metric is collected across functional areas

storyboard

in agile, a simple graphic organizer that helps systems analysts visualize the status of a project

swim lanes

in a business process diagram, the overall diagram is called a pool and the designated customer areas are called __

system requirement

a characteristic or feature that must be included in an information system to satisfy business requirements and be acceptable to users

systematic sample

a sample that occurs at a predetermined periodicity

total cost of ownership (TCO)

a number used in assessing costs, which includes ongoing support and maintenance costs as well as acquisition costs

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

use case diagram

a visual representation that represents the interaction between users and the information system in UML

user design phase

in this phase, users interact with systems analysts and develop models and prototypes that represent all system processes, outputs, and inputs

user stories

in agile, a set of more refined requirements derived from features (epics)

activity diagram

diagram that resembles a horizontal flow chart that shows the actions and events as they occur; show order in which activities take place and identify the outcome

object-oriented analysis

describes an information system by identifying things called objects

object model

A visual representation of the various components in an information system

method

defines specific tasks that an object must perform; describes what and how an object does something

message

an object-oriented command that tells an object to perform a certain method

attribute

polymorphism

the concept that a message gives different meanings to different objects

encapsulation

the idea that all data and methods are self-contained, as in a black box

class

a term used in object-oriented modeling to indicate a collection of similar objects

instance

a specific member of a class

subclass

a further division of objects in a class; more specific categories within a class

superclass

a more generalized category to which objects may belong

inheritance

a type of object relationship; an object derives one or more of its attributes from another object