Module 4: Requirements Engineering Review

0.0(0)
studied byStudied by 8 people
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
Card Sorting

1/56

encourage image

There's no tags or description

Looks like no tags are added yet.

Study Analytics
Name
Mastery
Learn
Test
Matching
Spaced

No study sessions yet.

57 Terms

1
New cards

Actor

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

2
New cards

Agile Methods

Attempt to develop a system incrementally by building a series of prototypes and adjusting them to user requirements. Developers revise, extend, and merge earlier versions into the final product. Emphasize continuous feedback. Each incremental step is affected by what was learned in the prior steps.

3
New cards

Brainstorming

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

4
New cards

Business Process Model (BPM)

Represents the people, events, and interaction in a system.

5
New cards

Business Process Model Notation (BPMN)

Includes various shapes and symbols to represent events, processes, and workflows.

6
New cards

Close-Ended Questions

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

7
New cards

Construction Phase

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

8
New cards

Cutover Phase

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

9
New cards

Data Flow Diagram (DFD)

Shows how data moves through an information system but does not show program logic or processing steps. Uses various symbols to show how the system transforms input data into useful information.

10
New cards

Document Review

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

11
New cards

Engaged Listening

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

12
New cards

Feature / Epic

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

13
New cards

Fact-Finding / Requirements Elicitation

The process of gathering requirements.

14
New cards

Fill-in Form

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

15
New cards

Functional Decomposition Diagram (FDD)

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

16
New cards

Functional Requirement

A statement of the services a system provides.

17
New cards

Hawthorne Effect

A phenomenon where employees who know they are being observed are more productive.

18
New cards

Histogram

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

19
New cards

Informal Structures

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

20
New cards

Interview

A planned meeting during which information is obtained from another person.

21
New cards

Joint Application Development (JAD)

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.

22
New cards

Leading Questions

Queries that suggest or favor a particular reply.

23
New cards

Non-Functional Requirement / Quality Attributes

A statement of operational system constraints.

24
New cards

Observation

A fact-finding technique where an analyst sees a system in action. _____ allows the verification of statements made in interviews.

25
New cards

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.

26
New cards

Personal Information Manager (PIM)

A tool that helps manage tasks and schedules. Many handheld devices also include this function.

27
New cards

Pool

The overall diagram in BPMN.

28
New cards

Productivity Software

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

29
New cards

Questionnaire / Survey

A document containing a number of standard questions that can be sent to many individuals.

30
New cards

Random Sample

A selection taken in a random, unplanned manner. For example, a ______ might be a sample that selects any 20 customers.

31
New cards

Range-of-Response Questions

Closed-ended questions that ask the person to evaluate something by providing limited answers to specific responses or on a numeric scale.

32
New cards

Rapid Application Development (RAD)

A team-based technique that speeds up information systems development and produces a functioning information system. ______ is similar in concept to JAD but goes further by including all phases of the SDLC.

33
New cards

Requirements Definitions

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

34
New cards

Requirements Engineering

  • Gathering requirements

  • Representation requirements

  • Validating and verifying requirements

35
New cards

Requirements Planning Phase

A phase that combines elements of the systems planning and systems analysis phases of the SDLC.

36
New cards

Requirements Specifications

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

37
New cards

Research

An 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.

38
New cards

Sampling

A process where an analyst collects examples of actual documents, which could include records, reports, or various forms.

39
New cards

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.

40
New cards

Scenarios

In an agile project, a real-world example of how users will interact with the system.

41
New cards

Scrum

A popular technique for agile project management. Derived from a rugby term. In _____, team members play specific roles and interact in intense sessions.

42
New cards

Sequence Diagram

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

43
New cards

Site Visit

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

44
New cards

Stratified Sample

A set metric is collected across functional areas. For example, a certain percentage of transactions from every work shift, or five customers from each of four zip codes.

45
New cards

Storyboards

In an agile project, a simple graphic organizer that helps systems analysts visualize the status of a project.

46
New cards

Structured Brainstorming

A group discussion where each participant speaks when it is his or her turn or passes.

47
New cards

Swim Lanes

In a business process diagram, the overall diagram is called a pool and the designated customer areas are called ______.

48
New cards

SysML

A dialect of UML 2, used for representing requirements (and other things), primarily in MBSE applications.

49
New cards

System Requirement

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

50
New cards

Systematic Sample

A sample that occurs at a predetermined periodicity. For example, every tenth customer record might be selected as a ___________ for review.

51
New cards

Total Cost of Ownership (TCO)

The total expenditures necessary to purchase, maintain, upgrade, and support a user’s personal computer or device over its expected useful lifetime, provides one estimate.

52
New cards

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.

53
New cards

Unified Modeling Language (UML)

A widely used method of visualizing and documenting software systems design. UML uses object-oriented design concepts, but it is independent of any specific programming language and can be used to describe business processes and requirements generally.

54
New cards

Unstructured Brainstorming

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

55
New cards

Use Case Diagram

A visual representation that illustrates the interaction between users and the information system in UML.

56
New cards

User Design Phase

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

57
New cards

User Stories

In an agile project, a set of more refined requirements derived from features.