Chapter 1: Systems Analysis and Design Overview

Vocabulary definitions from Chapter 1 regarding the Systems Development Life Cycle (SDLC), iterative development, and systems analysis and design methodologies.

Computer application (app)

A computer software program that executes on a computing device to carry out a specific set of functions.

Information system

A set of interrelated components that collects, processes, stores, and provides as output the information needed to complete business tasks; it includes a database and manual processes and is broader in scope than an app.

Systems analysis

Those activities that enable a person to understand and specify what an information system should accomplish.

Systems design

Those activities that enable a person to define and describe in detail the system that solves the business need.

System Development Life Cycle (SDLC)

The process consisting of all activities required to build, launch, and maintain an information system, consisting of six core processes.

Project

A planned undertaking that has a beginning and end and that produces some definite result.

System development process

The actual approach used to develop a particular information system, also known as a methodology (e.g., Unified Process, Extreme Programming, or Scrum).

Agile development

An information system development process that emphasizes flexibility to anticipate new requirements during development.

Iterative development

An approach to system development in which the system is "grown" piece by piece through multiple iterations.

SDLC Core Process 1

Identify the problem or need and obtain approval.

SDLC Core Process 2

Plan and monitor the project.

SDLC Core Process 3

Discover and understand the details of the problem or need.

SDLC Core Process 4

Design the system components that solve the problem.

SDLC Core Process 5

Build, test, and integrate system components.

SDLC Core Process 6

Complete system tests and then deploy the solution.

System Vision Document

A document containing the problem description, system capabilities, and business benefits; used to obtain approval for a project.

Work Breakdown Structure (WBS)

A document that describes the work to be performed for an iteration and covers core processes 3, 4, 5, and 6.

Work Sequence Draft

A document that elaborates the Work Breakdown Structure to show the order of activities.

Use case

A specific activity the system must perform, such as "Look up supplier" or "Enter/update supplier information."

Use case diagram

A visual representation showing the various use cases and how they relate to the subsystems.

Object classes

Also called domain classes; the "things" the system needs to remember and store information about.

Class diagram

A diagram used to visually represent the object classes and their associations.

Activity diagram

A workflow diagram used to document the detailed workflow of a specific use case.

Database schema

The design of the database structure, including tables and relationships.

Architectural configuration diagram

A diagram that shows the system's high-level structure, including components like browsers, windows, or smartphones.

Design class diagram

A diagram that includes View Layer Classes and Domain Layer Classes to define the software structure.

User Acceptance Testing

A testing phase where users verify the system meets their needs, performed during core process 6.