System Analysis and Design Exam! Hardest Trivia Quiz

An external agent refers to an outside person, unit, system, or organization that interacts with a system. This can include individuals or entities that provide input, receive output, or perform actions within the system. External agents play a crucial role in the functioning of a system as they contribute to its overall operation and may influence its behavior or outcomes.

Decomposition is the act of breaking a system into sub-components. This process involves dividing a complex system into smaller, more manageable parts, which can then be analyzed, designed, and implemented separately. Decomposition helps to simplify the system and allows for better understanding and control of its components. It is an essential step in system design as it enables the identification of individual elements and their relationships within the system. Feasibility analysis, data conservation, and system design are not directly related to the act of breaking a system into sub-components.

Decomposition refers to the act of breaking down a system into its component subsystems, processes, and subprocesses. This process helps in understanding the system better and analyzing its functionality at a granular level. By decomposing a system, we can identify the different parts and their relationships, which ultimately aids in designing and managing complex systems effectively.

account transactions is a data store, monthly account statements is also a data store and payment is a data flow

An event handler is a process that handles a given event in the event response list. It is responsible for executing the necessary actions or functions when a specific event occurs. It is commonly used in programming and software development to define the behavior or response to events such as button clicks, mouse movements, or keyboard inputs. The event handler receives the event as input and performs the desired actions or invokes the appropriate functions to respond to that event.

A data flow diagram is a tool that visually represents the flow of data through a system and the processing or work performed by that system. It uses various symbols to depict the different components and processes involved in the system, such as data sources, processes, data stores, and data flows. This diagram helps to understand how data moves within a system, identify potential bottlenecks or inefficiencies, and analyze the overall flow of information. It is commonly used in system analysis and design to model and document the data flow within a system.

An entity refers to a class of persons, places, objects, events, or concepts about which we need to capture and store data. This definition implies that entities are the fundamental building blocks of a data model, representing the various categories or types of information that we want to track and manage. By capturing and storing data about these entities, we can organize and analyze information in a structured manner, enabling effective data management and decision-making processes.

An entity can refer to a person, place, object, or event, as these are all tangible or observable entities. However, relationships are not physical entities themselves but rather the connections or associations between entities. Therefore, relationships are not considered as one of the possible options for an entity.

A context diagram is a diagram that is used to document the scope for a system. It provides a high-level overview of the system and its surrounding environment, showing the interactions between the system and external entities. It helps to define the boundaries and interfaces of the system, allowing stakeholders to understand the context in which the system operates. This diagram does not provide detailed information about the system's design or implementation, but rather focuses on capturing the overall scope and context of the system.

Rounded rectangles in data flow diagrams represent processes. Processes are the activities or transformations that occur within a system. They can be manual or automated and are responsible for taking inputs, performing actions, and producing outputs. The rounded rectangle shape is used to visually represent these processes in the diagram.

When data is at "rest," it refers to the state where the data is not being actively processed or transmitted. In this state, the data is typically stored in a data store, such as a database or a file system. A data store is specifically designed to securely store and manage data, making it the most suitable option for data at rest. Therefore, the correct answer is data store.

Converging data flow refers to the process of merging multiple data flows into a single data flow. It involves bringing together different streams of data or information into one unified pathway. This can be beneficial in situations where data from various sources needs to be combined and processed together for analysis or decision-making purposes. By converging the data flows, it becomes easier to manage and manipulate the information effectively.

A diverging data flow is a type of data flow that splits into multiple data flows. This means that a single input or process is divided into multiple outputs or paths, allowing data to flow in different directions. This can occur when there are multiple branches or decision points in a system or process, and the data needs to be distributed or processed differently based on certain conditions or criteria.

Structured English is a language syntax used to specify the logic of a process. It is a method of writing software specifications using natural language statements that are structured in a way that resembles programming language syntax. This allows for clear and unambiguous communication of the process logic, making it easier to understand and implement. It is commonly used in software development to describe the steps and conditions of a process in a more human-readable format.

A composite data flow refers to a data flow that is composed of multiple other data flows. This means that it is a higher-level data flow that includes or combines several smaller data flows within it. It can be seen as a way to organize and structure data flows, making them more manageable and understandable. By breaking down complex processes into smaller, interconnected data flows, it becomes easier to analyze and design systems. This definition emphasizes the composition aspect of composite data flows, highlighting their hierarchical nature.

An iteration structure in Structured English is best defined as a set of steps that should be repeated based on a stated condition. This means that the structure allows for the repetition of a specific set of steps until a certain condition is met. It provides a way to automate repetitive tasks and streamline processes by defining the conditions under which the steps should be repeated.

An event handler is a process that is responsible for handling a given event. It is the component that receives and processes events triggered by user actions or system events. The event handler is designed to perform specific actions or tasks in response to the event, such as updating data, displaying information, or executing a function. It is an essential part of event-driven programming and allows for the execution of code based on specific events occurring.

The correct answer is "data type." In programming, a data type refers to the classification of data that determines the type of values it can hold and the operations that can be performed on it. It defines the size and format of the data stored in an attribute. Different data types include integers, floating-point numbers, strings, booleans, etc. By specifying the data type of an attribute, we can ensure that only compatible values are stored in it and perform appropriate operations on the data.

Structured English is a language syntax used to specify the logical flow of a process. It is a method of writing pseudocode that follows a set of rules resembling the English language. It allows programmers to describe the steps and logic of a program in a more structured and readable manner, making it easier to understand and follow. By using structured English, programmers can effectively communicate and document the intended behavior of a process, facilitating collaboration and maintenance of the code.

An alternate key is a candidate key that is not selected to become the primary key. It is an alternative option for the primary key and can uniquely identify records in a database table. While the primary key is chosen as the main identifier for a table, an alternate key can also serve as a unique identifier if needed.

Gender is not considered a compound attribute because it represents a single characteristic or property of an entity. Compound attributes are composed of multiple sub-attributes that provide more detailed information. In this case, both name and address can have multiple sub-attributes such as street, city, and state, while phone number can have sub-attributes like country code and area code. However, gender does not have any sub-attributes and is therefore not considered a compound attribute.

A decision table is a tabular form of presentation that specifies a set of conditions and their corresponding actions. It is commonly used in decision-making processes to systematically analyze different combinations of conditions and determine the appropriate actions to be taken. This table helps in organizing complex logic and simplifying the decision-making process by providing a clear and structured representation of all possible scenarios and their outcomes.

An entity relationship diagram is a data model that utilizes several notations to depict data in terms of the entities and relationships described by that data. It is a visual representation that shows how different entities are related to each other in a database. This diagram helps to understand the structure of the database and the relationships between entities, making it easier to design and manage the database effectively.

The acronym CASE stands for Computer Aided System Engineering. This term refers to the use of computer-based tools and techniques to assist in the development, analysis, and maintenance of software systems. CASE tools provide support for various activities in the software development life cycle, such as requirements gathering, design, coding, testing, and documentation. These tools help improve productivity, quality, and consistency in software development processes by automating tasks, facilitating collaboration, and providing a structured approach to system engineering.

The term "attribute" refers to a characteristic or quality of something. Out of the options provided, "child" does not directly relate to this definition. In the context of data or programming, "element," "property," and "field" can all be used synonymously with "attribute" to describe different aspects or features of an object or entity. However, "child" typically refers to a subordinate or dependent element within a hierarchical structure, rather than a synonym for "attribute."

A data attribute is a term that describes the smallest piece of data that has meaning to the users and the business. It refers to a specific characteristic or property of a data entity that provides information and context. Data attributes are essential for organizing and categorizing data, allowing users and businesses to understand and interpret the information effectively.

A data flow diagram (DFD) is a tool used to illustrate how data moves through a system and the processing or work performed by that system. It is considered a process model because it focuses on the flow of data and the processes involved in a system. Therefore, the correct answer is "a & b."

In use cases, actors, events, inputs, and outputs are all commonly found elements. Actors refer to the individuals or systems interacting with the system being described in the use case. Events represent the actions or triggers that occur within the system. Inputs are the data or information provided to the system, while outputs are the results or responses produced by the system. However, "members" is not typically included in use cases as it does not directly relate to the interactions or functionality of the system.

The correct answer is "create, read, update, delete". The acronym CRUD stands for these four basic operations that can be performed on data in a database or any other storage system. "Create" refers to the action of adding new data, "read" is about retrieving or viewing existing data, "update" involves modifying or changing the existing data, and "delete" is the process of removing or deleting data from the system. These operations are fundamental for managing data and maintaining its integrity and usability.

Data flows can be described in terms of a sequence or group of data attributes that occur one after another, the selection of one or more attributes from a set of attributes, and the repetition of one or more attributes. However, the absence of one or more attributes does not describe a data structure in data flows.

A decision table is a tabular presentation that specifies a set of conditions and their corresponding actions. It is used to represent complex business rules or logic in a structured and organized manner. The table consists of rows representing different combinations of conditions and columns representing the corresponding actions to be taken. This format allows for easy understanding and analysis of the decision-making process, making it a valuable tool for designing and implementing systems or processes.

A "logical model" refers to a representation of a system or concept that focuses on the logical relationships and structure. The term "conceptual model" also refers to a representation of a system or concept, but it emphasizes the overall concepts and ideas rather than the specific implementation details. Therefore, "conceptual model" is a synonym for "logical model" as both terms describe a high-level representation of a system or concept.

The "=" symbol in data structures represents the relationship of "consists of" or "is composed of". It signifies that one element is made up of or includes another element.

The attribute that assumes a unique value for each entity instance is called a key. A key is used to uniquely identify each entity in a database table. It ensures that no two entities have the same value for the key attribute, allowing for efficient retrieval and manipulation of data.

The property of an attribute that defines what values it can legitimately take on is called the domain. The domain specifies the range or set of values that are valid for the attribute. It helps to ensure data integrity and restricts the attribute to only accept appropriate values within a specified range or set.

Balancing, in the context of data flow diagrams, refers to the concept of ensuring consistency and completeness across different levels of detail. It means that the data flow diagrams should accurately represent the flow of data and processes at various levels, without any missing or redundant information. This ensures that the diagrams are reliable and can be used effectively for analysis and design purposes.

An iteration structure in structured English is a specification that defines a set of steps to be repeated based on a stated condition. This means that the specified steps will be executed repeatedly until the condition is no longer true. It allows for the automation of repetitive tasks and provides a way to control the flow of the program based on specific conditions.

A candidate key is one of the potential choices for the primary key of an entity. It is a unique identifier that can be used to uniquely identify each record in a table. In other words, it is a column or a combination of columns that can uniquely identify a row in a table. The candidate key is chosen from a set of attributes that could potentially serve as the primary key.

The context diagram is a visual representation of a system that shows the interactions between the system and its external entities. It focuses on the inputs and outputs of the system. External events, temporal events, and state events are all types of events that can be associated with inputs on the context diagram. However, national events do not typically have a direct association with inputs on the context diagram. These events are usually broader in scope and may not directly impact the system being represented.

When mapping data requirements, it is important to ask questions related to level of access, creating instances of the entity, updating existing instances, and deleting instances. However, the question of "will we have compatibility issues" is not directly related to data requirements and therefore does not need to be asked.

A policy is a set of rules that govern how a process is to be completed. Policies provide guidelines and instructions for individuals or organizations to follow in order to achieve specific objectives or outcomes. They outline the expected behavior, procedures, and protocols that need to be followed in order to ensure consistency, efficiency, and compliance in completing a process. Policies can be implemented at various levels, such as organizational, departmental, or project-specific, and they help in maintaining order and standardization in the completion of tasks or activities.

A context data flow diagram is a process model used to document the scope for a system. It provides a high-level overview of the system and its interactions with external entities. It shows the flow of data between the system and external entities, without going into too much detail about the internal processes. This diagram helps to define the boundaries of the system and understand how it interacts with its environment.

Balancing is the concept that requires data flow diagrams at different levels of detail to reflect consistency and completeness. Balancing ensures that the inputs and outputs of a system are properly accounted for and that all data flows are balanced, meaning that no data is lost or created in the process. This concept helps to maintain the accuracy and integrity of the data flow diagrams, ensuring that they accurately represent the system being analyzed.

A use case is an analysis tool that helps in finding and identifying business events and responses. It describes the interactions between a system and its users, outlining the steps and actions required to achieve a specific goal. Use cases are commonly used in system analysis to understand the requirements and functionalities of a system and to ensure that it meets the needs of the users. They help in identifying the actors involved, the flow of events, and the expected outcomes in a business scenario.

A fully attributed data model is a data model that includes all entities, attributes, relationships, subsetting criteria, and precise cardinalities. This means that it provides a comprehensive representation of the data, including all the necessary details and specifications. It is a complete and detailed representation of the data structure, allowing for a thorough understanding and analysis of the data.

Return on investment analysis is a technique that compares the lifetime profitability of alternative solutions. It measures the return or profit generated from an investment relative to its cost. By calculating the return on investment, businesses can evaluate the financial viability of different solutions and determine which one provides the highest profitability. This analysis takes into account the time value of money and considers the cash flows generated over the entire lifespan of the investment. It is a widely used method for decision-making in business and investment scenarios.

Temporal events are triggered on the basis of time. They are events that occur at specific points in time or within a specified time frame. These events are not dependent on external factors or changes in the system's state. Instead, they are triggered solely based on the passage of time or predetermined schedules. Therefore, temporal events are the correct answer as they are specifically related to events triggered by time.

The work performed by a system in response to incoming data flows or conditions is called a process. A process refers to a series of steps or activities that are performed in order to achieve a specific goal or outcome. In this context, the system is actively processing the incoming data or conditions, which involves analyzing, transforming, or responding to them in some way. The other options, such as value stream, activity, or task, do not capture the comprehensive nature of the work performed by the system in this scenario.

The term "domain" refers to the set of permissible values that an attribute can take. In the context of this question, "domain" is the correct answer as it accurately describes the legitimate values for an attribute. The other options, such as "type," "flow," and "structure," do not specifically relate to the range of values an attribute can have.

A "logical model" refers to a representation of a system or concept that focuses on the logical relationships and structure. It is not concerned with the physical aspects or implementation details. A "physical model," on the other hand, represents the physical implementation or representation of a system. Therefore, a physical model is not a common synonym for a logical model, as it emphasizes the physical rather than the logical aspects. The other options, essential model, business model, and conceptual model, all relate to different types of logical models used in various contexts.