System Design & Input/Output Form Design

0.0(0)
Studied by 0 people
call kaiCall Kai
learnLearn
examPractice Test
spaced repetitionSpaced Repetition
heart puzzleMatch
flashcardsFlashcards
GameKnowt Play
Card Sorting

1/49

flashcard set

Earn XP

Description and Tags

Comprehensive vocabulary flashcards covering the core concepts, file structures, documentation types, design strategies, and coupling/cohesion metrics of System Design.

50 Terms

1
New cards

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?").

2
New cards

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.

3
New cards

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.

4
New cards

Architectural Design

High-level design focusing on system architecture, describing the structure and behavior of the system and the relationships between various development modules.

5
New cards

Detailed Design

The phase that follows architectural design and focuses specifically on the development of each individual module.

6
New cards

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.

7
New cards

Entity Relationship Model

A technique used in database design that helps describe the relationships between various entities of an organization.

8
New cards

Entity

A concept in an E-R model that specifies distinct real-world items in an application (e.g., vendor, item, student, course, teacher).

9
New cards

Relationship

The meaningful dependencies between entities in an E-R model (e.g., vendor supplies items, teacher teaches courses).

10
New cards

Attributes

Properties that specify details of entities or relationships in an E-R model (e.g., vendor code, student name).

11
New cards

Serial File Organization

A file organization method where records are stored in chronological order (in the order as they are input or occur).

12
New cards

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.

13
New cards

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.

14
New cards

Indexed File Organization

A file organization method where records can be processed both sequentially and non-sequentially using indexes.

15
New cards

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.

16
New cards

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.

17
New cards

Master File

A type of file that contains current information for a system (e.g., customer file, student file, telephone directory).

18
New cards

Table File

A type of master file that changes infrequently and is stored in a tabular format (e.g., storing Zipcodes).

19
New cards

Transaction File

A file containing day-to-day information generated from business activities, used to update or process a master file.

20
New cards

Mirror File

Exact duplicates of other files that help minimize the risk of downtime when the original file becomes unusable.

21
New cards

Log Files

Files containing copies of master and transaction records to chronicle changes, facilitate auditing, and provide recovery mechanisms in case of system failure.

22
New cards

Archive Files

Backup files that contain historical versions of other files.

23
New cards

Documentation

The process of recording information for reference or operational purposes, assisting users, managers, and IT staff.

24
New cards

Program Documentation

Documentation describing inputs, outputs, and processing logic for all program modules to guide programmers in constructing and maintaining code.

25
New cards

Operations Documentation

Documentation containing all information needed for processing and distributing online and printed output, including scheduling, file sources/destinations, and restart procedures.

26
New cards

User Documentation

Documentation providing instructions and information (such as user manuals, help guides, and tutorials) for users who interact with the system.

27
New cards

System Documentation

Documentation serving as the technical specifications for an information system (IS), detailing how objectives are accomplished and providing a basis for modifications.

28
New cards

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.

29
New cards

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.

30
New cards

Structured Design

A data-flow based methodology that helps identify system inputs and outputs to minimize complexity and increase program modularity.

31
New cards

Modularization

The technique of partitioning a program into small, independent modules organized top-down with bottom details to manage complexity.

32
New cards

Structure Charts

A recommended graphical tool for designing modular, top-down systems that defines system modules and their interrelationships using boxes and connecting lines.

33
New cards

Control Module

A higher-level module in a structure chart that directs lower-level subordinate modules.

34
New cards

Library Module

A reusable module in a structure chart that can be invoked from more than one point in the chart.

35
New cards

Transform-Centered Structure Charts

A structure chart design approach used when all transactions follow the exact same path.

36
New cards

Transaction-Centered Structure Charts

A structure chart design approach used when transactions do not all follow the same path.

37
New cards

Coupling

A measure of the independence of components that defines the degree of dependency of each development module on other modules.

38
New cards

High Coupling

A system state where program units are strongly interdependent, meaning changes to one subsystem lead to high impact on others.

39
New cards

Low Coupling

A system state where components are independent or almost independent, ensuring a change in one subsystem does not affect others.

40
New cards

Content Coupling

A form of coupling where one component actually modifies another, making the modified component completely dependent on the modifying one.

41
New cards

Common Coupling

A form of coupling where components are organized so that data is shared and accessible from a common data store.

42
New cards

Control Coupling

A form of coupling where one component passes parameters to explicitly control the activity of another component.

43
New cards

Stamp Coupling

A form of coupling where complete data structures are passed to communicate information between components.

44
New cards

Data Coupling

A form of coupling where components are connected purely by passing simple, individual data elements.

45
New cards

Cohesion

A measure of the closeness of the relationship between elements within a component, defining their degree of mutual dependency.

46
New cards

Coincidental Cohesion

The worst degree of cohesion, found in a component whose parts are completely unrelated to one another.

47
New cards

Logical Cohesion

A type of cohesion where several logically related functions or data elements are placed together inside the same component.

48
New cards

Temporal Cohesion

A type of cohesion where functions performed in sequence during system initialization or variable setting are related only by the timing involved.

49
New cards

Procedural Cohesion

A type of cohesion where functions are grouped together in a single component solely to ensure a specific execution order.

50
New cards

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.