Systems Analysis and Design: Chapters 4-7 Review

Comprehensive practice flashcards defining core terminology, architectural concepts, models, and controls from Chapters 4 through 7 of Systems Analysis and Design.

Problem Domain

The specific area of the users' business need that is within the scope of the new system being developed.

"Things"

Items users work with when accomplishing tasks that need to be captured and remembered by the system, modeled as domain classes in UML or data entities in database modeling.

Brainstorming Technique

A technique to identify domain classes by using a checklist of typical categories (tangible things, roles, organizational units, devices, sites, and incidents/events) to systematically question users.

Noun Technique

A systematic technique to identify problem domain classes by finding, classifying, and refining a comprehensive list of all nouns mentioned in discussions, procedures, and existing documents.

Compound Attribute

Two or more attributes combined into a single structure (such as an address consisting of street, city, state, and postal code) to simplify the data or domain model.

Multiplicity

The UML term specifying the allowable range of associated instances between classes (such as 1 to 1, zero to many, or one to many), synonymous with cardinality in ER diagrams.

Crow's Foot Cardinality Symbols

Standard graphical symbols used on Entity-Relationship Diagrams (ERDs) to depict relationship constraints: a single crossbar for mandatory one, a crossbar with a circle for optional zero or one, a crow's foot with a crossbar for mandatory one or more, and a crow's foot with a circle for optional zero or more.

Semantic Net

A graphical representation of individual data entities and their specific real-world relationship links, used to understand connections before formalizing an ERD or class diagram.

Association Class

An association treated as a class in a many-to-many relationship because it has attributes that need to be captured (such as a grade in a course enrollment).

Abstract Class

A class in an inheritance hierarchy that defines common attributes and associations for subclasses but is never directly instantiated, often styled in italics.

Concrete Class

A class within an inheritance hierarchy that can be directly instantiated into individual objects.

Aggregation

A whole-part relationship where the component part can exist separately from the whole and can be removed or replaced, represented in UML by an open diamond.

Composition

A whole-part relationship where the constituent parts cannot exist separately from the aggregate whole and cannot be detached, represented in UML by a filled diamond.

State

A condition during an object's lifecycle where it satisfies a criterion, performs an ongoing activity, or waits for an external event.

Pseudostate

The starting point symbol in a UML state machine diagram, represented graphically by a solid black circle.

Guard-Condition

A true/false test enclosed in square brackets [ ] that evaluates whether a state transition can fire or whether an SSD message is sent.

Action-Expression

A procedural action or expression preceded by a slash / in a transition label that specifies an activity that must execute when the transition fires.

Preconditions

The required state of the system and business environment that must be true before a use case can commence.

Postconditions

The state or conditions that must be established and saved in the system after a use case successfully completes.

System Sequence Diagram (SSD)

A UML sequence diagram that models input and output messaging requirements for a use case by depicting the actor interacting with a single object representing the entire automated system (:System).

Object Lifeline

A vertical dashed line extending downward beneath an actor or object in a sequence diagram that shows its sequence of existence and message exchanges from top to bottom.

CRUD Analysis

A cross-checking technique (Create, Read/Report, Update, Delete) that correlates problem domain classes with use cases to confirm all necessary lifecycle operations are fully supported.

Systems Design

The process of defining, organizing, and structuring the components of the solution system to serve as a detailed blueprint for construction and implementation.

Application Component

A well-defined unit of software that performs a cohesive set of functions, defined during design by scope, boundaries, interfaces, and programming languages.

Integrity Controls

Internal system mechanisms integrated into application code and DBMS software to maintain the accuracy, completeness, and validity of inputs, outputs, data, and programs.

Value Limit Controls

Input controls that check the numerical range or boundaries of data inputs for reasonableness to reject erroneous values.

Completeness Controls

Input validation controls designed to confirm that all required fields have had data entered before a transaction proceeds.

Field Combination Controls

Input controls that verify the logical correctness of entered data based on known relational rules between two or more interdependent fields.

Output Controls

Controls designed to guarantee that outputs arrive at their designated destination, remain visible only to authorized users, and are accurate, current, and complete.

Fraud Triangle

A conceptual model outlining the three primary drivers of internal fraud, embezzlement, and unauthorized activity: Opportunity, Motive, and Rationalization.

Separation of Duties

A fraud risk-reduction control whereby systems are built so users with custody of physical assets have limited access to records, ensuring no single individual can execute and conceal a fraud.

Authentication

The security control process of identifying and validating a user's identity before permitting access to system resources.

Authorization

The security mechanism that establishes and enforces an authenticated user's specific level of permission for accessing individual system resources, data, and applications.

Symmetric Key Encryption

A cryptographic method that uses the identical secret key to encrypt data and to decrypt the resulting ciphertext.

Asymmetric Key Encryption

An encryption method (also known as public key encryption) that employs two mathematically linked keys: a public key to encrypt data and a private key to decrypt it.

Digital Certificate

A secure digital record containing an organization's identity and public key that has been encrypted and validated by a trusted certifying authority.

Technology Architecture

The structural combination of computer hardware, communication networks, peripheral devices, and system software that forms the physical platform for an information system.

Application Architecture

The layout, organization, and functional partitioning of software programs and execution modules across an enterprise system.

Software as a Service (SaaS)

A system architecture where application software runs remotely on shared servers and is delivered over the network, requiring no application installation on client hardware.

Web Service

A modular software function accessible over standard Web protocols via a URL, accepting inputs through the URL and returning data in a standard Web format.

Three-Layer Architecture

A client/server software design pattern partitioned into a view layer (user interface), a domain/logic layer (business logic and rules), and a data layer (database access functions).

Interoperability

The operational capability of an application or software component to interact, share data, and function collaboratively with diverse software systems.

Location Diagram

An architectural diagram depicting the geographic distribution and physical placement of systems, facilities, hardware, and user groups.

Network Diagram

An architectural model showing how software systems and applications are deployed across networked hardware nodes, switches, routers, and transport layers.

Deployment Diagram

A UML diagram illustrating how software execution environments, components, and subsystems are assigned to and interconnected across physical hardware devices.

System of Record

The designated authoritative system or database that holds the master version of data and has primary responsibility for maintaining its integrity.