Chapter 4 CMSC 145

Actor

An external entity with a specific role that interacts with the system in a use case model.

Agile methods

System development methods that develop a system incrementally by building prototypes and adjusting them to user requirements.

Brainstorming

A fact-finding technique that involves small group discussions to gain information about a specific problem.

Business process model (BPM)

A graphical representation of one or more business processes.

Business process modeling notation (BPMN)

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

Closed-ended questions

Queries that limit the range of responses, used to obtain specific information.

Construction phase

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

Cutover phase

A phase resembling final tasks in the SDLC implementation phase, including data conversion and user training.

Data flow diagram (DFD)

A diagram that shows how the system processes and transforms data into useful information.

Document review

A review of baseline documentation to understand how the current system is supposed to work.

Engaged listening

The ability to concentrate on what someone is saying, including nonverbal communication.

Epic

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

Fact-finding

The process of gathering requirements.

Feature

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

Fill-in form

A template used to collect data online or on an intranet.

Functional decomposition diagram (FDD)

A top-down representation of business functions and processes.

Functional requirement

A statement of the services a system provides.

Hawthorne Effect

A phenomenon where employees observed are more productive.

Histogram

A vertical bar chart showing the distribution of questionnaire or sampling results.

Informal structure

An organization based on interpersonal relationships that develop from various sources.

Interview

A planned meeting to obtain information from another person.

Joint application development (JAD)

A systems development technique using a task force of users, managers, and IT professionals.

Leading questions

Queries that suggest or favor a particular reply.

Non-functional requirements

Statements of operational system constraints.

Observation

A fact-finding technique where an analyst sees a system in action.

Open-ended questions

Queries that allow for a range of answers, encouraging spontaneous responses.

Personal information manager (PIM)

A tool that helps manage tasks and schedules.

Pool

The overall diagram in business process modeling notation (BPMN).

Productivity applications

Applications for word processing, spreadsheets, database management, and graphics.

Quality attributes

See non-functional requirements.

Questionnaire

A document with standard questions sent to many individuals.

Random sample

A selection taken in a random manner.

Range-response questions

Closed-ended questions asking for limited answers.

Rapid application development (RAD)

A team-based technique speeding up information systems development.

Requirements definitions

A description of system requirements from the user's perspective.

Requirements elicitation

The process of gathering system requirements.

Requirements engineering

Fact-finding to describe the current system and identify requirements for the new system.

Requirements planning phase

A phase combining elements of systems planning and analysis phases.

Requirements specifications

A description of system requirements from the analyst's perspective.

Research

A fact-finding technique involving the review of journals and periodicals.

Sampling

The process of collecting examples of actual documents.

Scalability

A characteristic of a system that allows easy expansion or modification.

Scenarios

Real-world examples of how users will interact with the system in an agile project.

Scrum

A popular technique for agile project management involving team roles and intense sessions.

Sequence diagram

A UML diagram that shows the timing of transactions during system execution.

Site visit

A trip to observe a system in use at another location.

Stratified sample

A sample collected across functional areas using set metrics.

Storyboard

A graphic organizer that helps visualize the status of an agile project.

Structured brainstorming

A group discussion where each participant speaks turn by turn.

Survey

A document with standard questions sent to many individuals, also called a questionnaire.

Swim lanes

Designated areas in a business process diagram for different customer areas.

SysML

A dialect of UML used for representing requirements in MBSE applications.

System requirement

A characteristic or feature that must be included in an information system.

Systematic sample

A sample selected at predetermined intervals.

Total cost of ownership (TCO)

A number used in assessing costs including ongoing support and maintenance.

Traceability

The ability to follow a requirement backward to its origins and forward through the SDLC.

Unified Modeling Language (UML)

A method of visualizing and documenting software systems design.

Unstructured brainstorming

A group discussion where any participant can speak freely at any time.

Use case diagram

A visual representation of the interaction between users and the system in UML.

User design phase

A phase where users interact with analysts to develop models and prototypes.

User stories

Refined requirements derived from features in an agile project.