CIS 130 Quiz 3

Data Flow diagramming is indeed a tool used for process modeling. It helps to visually represent the flow of data within a system or process, showing how inputs are transformed into outputs through various processes. By using symbols and arrows, data flow diagrams provide a clear and concise representation of the system's functionality, making it easier to understand and analyze. Therefore, the statement "Data Flow diagramming is a tool for doing process modeling" is correct.

The major inputs and major outputs listed on the use case indeed provide a list of the sources and destinations of the inflows and outflows on the processes on a DFD. This information helps in understanding the flow of data and the interactions between different components of the system. It is important to identify these inputs and outputs accurately to ensure that the system functions correctly and meets the intended requirements.

The statement is true because use cases are a way to depict the interactions between users and a system. They describe the steps or actions that users take to accomplish a specific goal within the system. Use cases provide a clear understanding of the activities performed by the users, allowing for better design and development of the system.

Use cases and process diagrams are not the same. Use cases are a way of representing the interactions between actors and a system, while process diagrams illustrate the flow of activities or steps within a process. Therefore, the statement that "Use cases are the same as process diagrams" is false.

Use cases are diagrams that depict the interactions between users and a system. They are used to capture the functional requirements of a system by illustrating the different scenarios or use cases that can occur. Use cases typically consist of actors (users or external systems), the system under consideration, and the interactions or actions performed by the actors. They do not necessarily have three components of selection, process, and iteration. Therefore, the given statement is false.

A statement of business value is not typically a part of a Use Case. Use Cases are used to describe the interactions between a system and its users, focusing on the functionality and behavior of the system. The other options listed (Name, Number, Trigger, Major inputs) are commonly included in a Use Case as they help to identify and define the specific scenario being addressed. However, a statement of business value is more commonly associated with a Business Case, which outlines the justification and benefits of a project or initiative.

Use cases and data flow diagrams (DFDs) are both tools used by systems analysts. Use cases are developed with users to ensure that the analyst has accurately captured the processes and relationships involved in a system. On the other hand, DFDs are created based on the use cases to provide a more detailed and formal understanding of the processes. In other words, use cases serve as a foundation for building DFDs, helping analysts to further analyze and comprehend the processes involved in a system.

Data flow diagrams do not focus on the physical data in a system. Instead, they focus on the flow of information and how it moves between different processes, entities, and data stores within a system. These diagrams are used to represent the overall structure and behavior of a system, showing how data is input, processed, and outputted. Therefore, the statement that data flow diagrams focus on the physical data in a system is incorrect.

Process models are not only used to document the current system, but also to design and document future systems (the "to-be" system). By creating process models for both the current and future systems, users and stakeholders can visualize and understand the changes that will be made. This allows for effective communication, analysis, and improvement of the system. Therefore, the statement that process models are only used to document the current system is false.

Logical process models are models that describe processes without suggesting how they are conducted. This means that they provide a high-level overview of the steps involved in a process, but do not specify the exact details of how each step should be carried out. These models are useful for understanding the flow and interactions between different processes, and can be used as a basis for further analysis and improvement.

Building use cases involves analyzing major processes, external or internal triggers, and involving analysts and users. However, it is not necessary to analyze major costs when building use cases. The focus is more on understanding the processes and triggers involved in order to develop effective use cases.

A process model is a formal way of representing how a business system operates. It provides a structured and visual representation of the various processes, activities, and interactions within a business system. It helps in understanding and analyzing the flow of information, resources, and decisions in the system. By using process modeling techniques such as flowcharts or activity diagrams, stakeholders can gain insights into the system's operations, identify bottlenecks, and make improvements to enhance efficiency and effectiveness.

The given answer is correct because it states that all processes need at least one input and at least one output. This means that it is normal for a process to have two inputs and one output. It is not necessary for the number of inputs and outputs to be the same in a process.

The given answer is "Formal ways of representing how a business system interacts with its environment". This answer accurately describes what use cases are. Use cases are formal representations or models that depict how a business system interacts with its environment. They outline the various interactions and relationships between the system and its actors or users. Use cases are commonly used in software development and requirements gathering processes to understand and document the functionality and behavior of a system.

Use cases are used to more fully delineate system requirements. Use cases are a technique used in software development to capture and describe the interactions between users and a system. They outline the specific actions or tasks that users can perform and the corresponding system responses. By defining use cases, system requirements can be identified and specified in a more detailed and comprehensive manner, ensuring that the system meets the needs and expectations of its users.

Use cases are developed first and then data flow diagrams ensue because use cases provide a high-level view of the system's functionality from the user's perspective. They outline the interactions between the user and the system. Data flow diagrams, on the other hand, depict the flow of data within the system and how it is processed. Once the use cases are defined, data flow diagrams can be created to further analyze and understand the system's data flow and processes. Therefore, the development of use cases precedes the development of data flow diagrams.