1/49
Comprehensive vocabulary flashcards covering the core concepts, file structures, documentation types, design strategies, and coupling/cohesion metrics of System Design.
System Design
The phase that bridges the gap between the problem domain and the existing system in a manageable way, focusing on the solution domain ("how to implement?").
Logical Design
An abstract representation of the data flow, inputs, and outputs of the system, describing sources, destinations, data stores, and procedures in a format that meets user requirements.
Physical Design
The design phase that relates to actual input and output processes, focusing on how data is entered, verified, processed, and displayed as output to produce a working system.
Architectural Design
High-level design focusing on system architecture, describing the structure and behavior of the system and the relationships between various development modules.
Detailed Design
The phase that follows architectural design and focuses specifically on the development of each individual module.
Conceptual Data Modeling
The representation of organizational data that includes all major entities and relationships, aiming to capture as much meaning of the data as possible.
Entity Relationship Model
A technique used in database design that helps describe the relationships between various entities of an organization.
Entity
A concept in an E-R model that specifies distinct real-world items in an application (e.g., vendor, item, student, course, teacher).
Relationship
The meaningful dependencies between entities in an E-R model (e.g., vendor supplies items, teacher teaches courses).
Attributes
Properties that specify details of entities or relationships in an E-R model (e.g., vendor code, student name).
Serial File Organization
A file organization method where records are stored in chronological order (in the order as they are input or occur).
Sequential File Organization
A file organization method where records are stored in order based on a key field containing a value that uniquely identifies each record.
Direct (Relative) File Organization
A file organization method where each record is stored based on a physical address or device location calculated from the key field via a randomizing routine or hashing algorithm.
Indexed File Organization
A file organization method where records can be processed both sequentially and non-sequentially using indexes.
Sequential Access
A file access method where every record on the file is processed starting with the first record until the End of File (EOF) is reached.
Direct (Random) Access
A file access method where records are located by knowing their physical locations or device addresses rather than their positions relative to other records.
Master File
A type of file that contains current information for a system (e.g., customer file, student file, telephone directory).
Table File
A type of master file that changes infrequently and is stored in a tabular format (e.g., storing Zipcodes).
Transaction File
A file containing day-to-day information generated from business activities, used to update or process a master file.
Mirror File
Exact duplicates of other files that help minimize the risk of downtime when the original file becomes unusable.
Log Files
Files containing copies of master and transaction records to chronicle changes, facilitate auditing, and provide recovery mechanisms in case of system failure.
Archive Files
Backup files that contain historical versions of other files.
Documentation
The process of recording information for reference or operational purposes, assisting users, managers, and IT staff.
Program Documentation
Documentation describing inputs, outputs, and processing logic for all program modules to guide programmers in constructing and maintaining code.
Operations Documentation
Documentation containing all information needed for processing and distributing online and printed output, including scheduling, file sources/destinations, and restart procedures.
User Documentation
Documentation providing instructions and information (such as user manuals, help guides, and tutorials) for users who interact with the system.
System Documentation
Documentation serving as the technical specifications for an information system (IS), detailing how objectives are accomplished and providing a basis for modifications.
Top-Down Strategy
A modular design approach that starts from the highest-level module and subdivides downward into simpler submodules until the lowest-level modules are reached.
Bottom-Up Strategy
A modular design approach that starts from the bottom or most basic level modules and moves upward toward the highest-level modules.
Structured Design
A data-flow based methodology that helps identify system inputs and outputs to minimize complexity and increase program modularity.
Modularization
The technique of partitioning a program into small, independent modules organized top-down with bottom details to manage complexity.
Structure Charts
A recommended graphical tool for designing modular, top-down systems that defines system modules and their interrelationships using boxes and connecting lines.
Control Module
A higher-level module in a structure chart that directs lower-level subordinate modules.
Library Module
A reusable module in a structure chart that can be invoked from more than one point in the chart.
Transform-Centered Structure Charts
A structure chart design approach used when all transactions follow the exact same path.
Transaction-Centered Structure Charts
A structure chart design approach used when transactions do not all follow the same path.
Coupling
A measure of the independence of components that defines the degree of dependency of each development module on other modules.
High Coupling
A system state where program units are strongly interdependent, meaning changes to one subsystem lead to high impact on others.
Low Coupling
A system state where components are independent or almost independent, ensuring a change in one subsystem does not affect others.
Content Coupling
A form of coupling where one component actually modifies another, making the modified component completely dependent on the modifying one.
Common Coupling
A form of coupling where components are organized so that data is shared and accessible from a common data store.
Control Coupling
A form of coupling where one component passes parameters to explicitly control the activity of another component.
Stamp Coupling
A form of coupling where complete data structures are passed to communicate information between components.
Data Coupling
A form of coupling where components are connected purely by passing simple, individual data elements.
Cohesion
A measure of the closeness of the relationship between elements within a component, defining their degree of mutual dependency.
Coincidental Cohesion
The worst degree of cohesion, found in a component whose parts are completely unrelated to one another.
Logical Cohesion
A type of cohesion where several logically related functions or data elements are placed together inside the same component.
Temporal Cohesion
A type of cohesion where functions performed in sequence during system initialization or variable setting are related only by the timing involved.
Procedural Cohesion
A type of cohesion where functions are grouped together in a single component solely to ensure a specific execution order.
Sequential Cohesion
A type of cohesion where the output produced from one part of a component acts directly as the input to the next part.