Event Decomposition Technique Quiz
44 Questions
1 Views

Choose a study mode

Play Quiz
Study Flashcards
Spaced Repetition
Chat to Lesson

Podcast

Play an AI-generated podcast conversation about this lesson

Questions and Answers

Which type of event is triggered by some action within the system?

  • State Event (correct)
  • Temporal Event
  • External Event
  • Internal Event
  • What type of event is initiated by an action outside of the system?

  • System Event
  • External Event (correct)
  • State Event
  • Temporal Event
  • Which of the following is an example of a Temporal Event?

  • A user clicks a button on a website
  • A database record is updated
  • An external server sends a request to the system
  • A timer reaches a specific time (correct)
  • Which of these events are influenced by factors outside the system?

    <p>External Events (B)</p> Signup and view all the answers

    Which type of event occurs as a result of the system reaching a certain condition?

    <p>State Event (B)</p> Signup and view all the answers

    What is the main purpose of identifying duplicates with similar use cases?

    <p>To simplify the development of the system by identifying common functionalities. (A)</p> Signup and view all the answers

    Which of the following is NOT a step involved in the event decomposition technique?

    <p>Classify potential users by organizational level. (C)</p> Signup and view all the answers

    What is the primary purpose of identifying a list of specific goals for each user type?

    <p>To understand the different user needs and expectations from the system. (D)</p> Signup and view all the answers

    What is the definition of an event in the context of the Event Decomposition Technique?

    <p>Something that occurs at a particular time and place, can be described, and should be remembered by the system. (B)</p> Signup and view all the answers

    What is the main benefit of using the Event Decomposition Technique?

    <p>It ensures that all possible user scenarios are considered during system design. (A)</p> Signup and view all the answers

    What is the key characteristic of an external event?

    <p>It involves data coming from an outside source. (C)</p> Signup and view all the answers

    Which of the following scenarios would be considered an external event?

    <p>A customer requesting an update to a previous order. (C)</p> Signup and view all the answers

    Which of the following is NOT an example of an external output needed at points in time?

    <p>An internal memo summarizing project progress. (A)</p> Signup and view all the answers

    Which of these is an example of an external event that results in a transaction?

    <p>A customer making a purchase through an online store. (C)</p> Signup and view all the answers

    What is the main purpose of tracing a sequence of transactions?

    <p>To understand the flow of data within the system. (B)</p> Signup and view all the answers

    Which of the following situations would require a Temporal Event Checklist?

    <p>A monthly management report needs to be generated on the 15th of each month. (B)</p> Signup and view all the answers

    What is the difference between an external event and a temporal event?

    <p>External events occur randomly, while temporal events happen at pre-determined times. (D)</p> Signup and view all the answers

    Why is it important to identify the actual event that affects a system?

    <p>To determine the appropriate response for the system to execute. (B)</p> Signup and view all the answers

    What is the primary focus of the Event Decomposition Technique?

    <p>Breaking down system functionality into smaller, manageable units. (C)</p> Signup and view all the answers

    Why is it important to consider temporal events in the Event Decomposition Technique?

    <p>They can trigger user interface updates in real-time systems. (A)</p> Signup and view all the answers

    What is the role of the "perfect technology assumption" in the Event Decomposition Technique?

    <p>It simplifies the design process by assuming that all events can be handled flawlessly. (A)</p> Signup and view all the answers

    Why are system controls like login, logout, and password changes usually excluded from the initial event decomposition?

    <p>They are addressed in later stages of the system design process. (D)</p> Signup and view all the answers

    How does the Event Decomposition Technique differ from traditional system analysis methods?

    <p>It emphasizes the relationship between system events and functionalities rather than data structures. (B)</p> Signup and view all the answers

    What is the main purpose of identifying state events in the Event Decomposition Technique?

    <p>To ensure that the system can handle changes in its internal state effectively. (A)</p> Signup and view all the answers

    How does the Event Decomposition Technique contribute to the system design process?

    <p>It facilitates the creation of a detailed functional specification for the system. (B)</p> Signup and view all the answers

    Which of these is NOT a step involved in the Event Decomposition Technique?

    <p>Defining the specific user interface elements. (A)</p> Signup and view all the answers

    What is an advantage of the Event Decomposition Technique?

    <p>It helps break down complex processes into smaller, manageable steps, simplifying the analysis process. (B)</p> Signup and view all the answers

    What is a key advantage of using the Event Decomposition Technique to analyze system requirements?

    <p>It simplifies the analysis process by focusing on user requirements and business goals. (C)</p> Signup and view all the answers

    What does the term 'elementary business process' (EBP) refer to in the context of Event Decomposition?

    <p>A fundamental process that is executed by one person in a single location in response to a business event. (A)</p> Signup and view all the answers

    What is a potential drawback of using the Event Decomposition Technique?

    <p>It can focus too heavily on user-specific requirements, neglecting the broader needs of the business. (B)</p> Signup and view all the answers

    Which of the following is NOT a benefit of using the Event Decomposition Technique?

    <p>It provides a framework for identifying all possible system functionalities, including those not directly related to user actions. (D)</p> Signup and view all the answers

    How does the Event Decomposition Technique help decompose system requirements at the right level of analysis?

    <p>By breaking down complex processes into smaller, more manageable steps or elementary business processes (EBPs). (D)</p> Signup and view all the answers

    Why is it important for the system to be able to 'update vacancies'?

    <p>To ensure that the system accurately reflects the current job opportunities available. (A)</p> Signup and view all the answers

    What is the primary function of the 'Count Applications' functionality?

    <p>To track the number of applications received for each vacancy, providing insights into the hiring process. (B)</p> Signup and view all the answers

    What is the main purpose of the 'Filter Applications' functionality?

    <p>To categorize applications according to specific criteria, such as qualifications or experience. (B)</p> Signup and view all the answers

    What is the key benefit of implementing the 'Forward Applications' functionality?

    <p>It allows for the automated forwarding of applications to the relevant departments, streamlining the hiring process. (C)</p> Signup and view all the answers

    What is the primary purpose of using user stories in software development?

    <p>To capture a simplified description of a software feature from an end-user perspective (D)</p> Signup and view all the answers

    Identify the three essential elements of a user story.

    <p>User type, Functionality, Acceptance Criteria (D)</p> Signup and view all the answers

    What is the purpose of 'Acceptance Criteria' in user stories?

    <p>To define the features that must be present at the completion of the user story (C)</p> Signup and view all the answers

    What is the correct template for a user story description?

    <p>As a [User type], I want to [Functionality], so that [Value] (B)</p> Signup and view all the answers

    The phrase 'As a [User type], I want to [Functionality], so that [Value]' helps define the user story. What does the 'As a [User type]' specify?

    <p>The specific user who will use the functionality (A)</p> Signup and view all the answers

    Which of the following statements accurately describes the 'Value' element in a user story?

    <p>It explains the benefits that the user will derive from the functionality (C)</p> Signup and view all the answers

    Why is it crucial to have specific acceptance criteria for a user story?

    <p>To ensure that the developed functionality will be tested and verified (B)</p> Signup and view all the answers

    What is the significance of knowing 'who' the functionality is for in a user story?

    <p>To ensure that the developed functionality is tailored to the needs of the specific user (A)</p> Signup and view all the answers

    Flashcards

    User Stories

    Descriptions of software features from an end-user’s perspective.

    Acceptance Criteria

    Features that must be present upon task completion.

    Template for User Story

    A user story is structured as: As a [type of user], I want to [functionality] so that [value].

    User Role in User Stories

    Indicates who is benefiting from a feature.

    Signup and view all the flashcards

    User Functionality

    Denotes what the user wants the software to do.

    Signup and view all the flashcards

    Value of Functionality

    Explains the benefit of the functionality to the user.

    Signup and view all the flashcards

    Event Decomposition

    Breaking down events to outline specific user actions within use cases.

    Signup and view all the flashcards

    Use Cases

    Models that capture functional requirements based on user interactions.

    Signup and view all the flashcards

    External Event

    An event initiated by an external agent outside the system.

    Signup and view all the flashcards

    Temporal Event

    An event that occurs at a specific point in time.

    Signup and view all the flashcards

    State Event

    An event triggered by something happening within the system.

    Signup and view all the flashcards

    Event Types

    Categories distinguishing events based on their origin and nature.

    Signup and view all the flashcards

    Trigger Process

    The action initiated by an event resulting in a process change.

    Signup and view all the flashcards

    User Classification

    Organizing potential users by their roles and levels in the organization.

    Signup and view all the flashcards

    User Goals

    Specific aims users have when interacting with a new system.

    Signup and view all the flashcards

    Stakeholder Review

    Discussing system requirements with users and stakeholders to ensure alignment.

    Signup and view all the flashcards

    External Agent Transaction

    An external actor initiates a transaction, such as a purchase.

    Signup and view all the flashcards

    Information Request

    An external agent seeks information about a product or service.

    Signup and view all the flashcards

    Data Update Requirement

    Changes in external data that require updates in the system.

    Signup and view all the flashcards

    Management Information Needs

    Higher management requests specific information for decision making.

    Signup and view all the flashcards

    Internal Outputs

    Reports needed internally at specific times, like management reports.

    Signup and view all the flashcards

    External Outputs

    Documents needed outside the organization like bills or reminders.

    Signup and view all the flashcards

    Transactional Sequence

    The process of tracing a series of transactions resulting in events.

    Signup and view all the flashcards

    Event Identification

    Finding the actual event that affects the system's functionality.

    Signup and view all the flashcards

    Event Decomposition Technique

    A process for breaking down events to identify system responses.

    Signup and view all the flashcards

    Use Case Identification

    The process of naming and defining use cases for events.

    Signup and view all the flashcards

    Perfect Technology Assumption

    A principle to determine if identified events are realistic and necessary.

    Signup and view all the flashcards

    Response Checklist

    A tool to help identify required responses for external events.

    Signup and view all the flashcards

    System Controls Exclusion

    Specific system controls are intentionally not included in event definitions.

    Signup and view all the flashcards

    Job Applicant Events

    Actions triggered by an external job applicant during the application process.

    Signup and view all the flashcards

    Functionalities of the System

    Capabilities required by the system to manage job applications effectively.

    Signup and view all the flashcards

    Record Applicant Profile

    Entering and saving information about the job applicant in the system.

    Signup and view all the flashcards

    Count Applications

    The process of tallying the total number of job applications received.

    Signup and view all the flashcards

    Filter Applications

    The method of sorting applications based on specific criteria to identify qualified candidates.

    Signup and view all the flashcards

    Forward Applications

    The action of sending received applications to appropriate departments for review.

    Signup and view all the flashcards

    Produce Summary Report

    Creating a document that provides an overview of the applications received and their statuses.

    Signup and view all the flashcards

    Elementary Business Process (EBP)

    A fundamental business activity conducted by a person in response to a business event.

    Signup and view all the flashcards

    Study Notes

    Course Information

    • Course Title: Software Requirements Analysis and Design
    • Course Code: ACS2913
    • Instructor: David Tenjo
    • Semester: Fall 2022

    Chapter 3 Outline

    • User Stories and Use Cases
    • Use Cases and the User Goal Technique
    • Use Cases and Event Decomposition
    • Use Cases in the Ridgeline Mountain Outfitters Case

    Overview

    • Previous chapters covered system analysis, functional and non-functional requirements, and information gathering techniques.
    • This chapter focuses on identifying and modeling the key aspect of functional requirements: use cases.

    User Stories

    • Tools used to describe software features from an end-user perspective.
    • Describe the user type, their desired outcome, and reasoning.
    • Help create simplified requirement descriptions.
    • One-sentence descriptions of work-related user tasks to achieve a goal.
    • Acceptance criteria define necessary features at task completion.

    User Stories (Template)

    • Template: As a , I want to so that .
    • Elements are crucial: who the story is for, what functionality is needed, value derived, and priority decisions.
    • Example acceptance criteria: Given the customer has one credit account and one savings account, When they have logged in successfully, Then the two accounts are listed in account number order (Account no, Name, Balance, Available Funds).

    Sample User Story

    • Example Story: As a shipping clerk, I want to ship an order accurately and as quickly as possible once the order details are available.
    • Acceptance Criteria:
      • Available order details pop up on the screen when available.
      • Portable display/scan device speeds up.
      • Items are sorted by bin location.
      • Items not in stock are marked as backordered.
      • Shipper recommendation based on weight, size, and location.
      • Shipping label printed for selected shipper.

    User Stories (Aspects)

    • Three aspects documented in a user story:
      • Who is the function for? E.g., As a . (More specific, the better).
      • What should be created? E.g., I want to . (User should drive the goal).
      • Why is it valuable to the user? E.g., So that .
    • Understanding the Who, What, and Why is essential for proper story understanding. If these are unclear, do not proceed with development.

    Use Cases

    • A use case is an activity performed by the system, typically in response to a user request.
    • Use cases define functional requirements.
    • Analysts decompose the system into use cases (functional decomposition).
    • Techniques for identifying use cases include user goal and event decomposition techniques.
    • Use cases are named using verb-noun phrases.

    Identifying Use Cases

    • Use cases can begin with user stories or requirements.
    • Follow either the user goal technique or the event decomposition technique.

    User Goal Technique

    • Most common industry technique; simple and effective.
    • Identify all potential user categories.
    • Interview users to understand their tasks and desired functionalities.
    • This technique refines tasks into specific user goals.
    • Example of a user goal: "I need to ship items, track a shipment, create a return."

    User Goal Technique (Specific Steps)

    • List all potential system users.
    • Classify users by their roles.
    • Categorize users further by organizational level (e.g., operational, management, executive).
    • For each user type, list goals for using the system, considering new functionalities.
    • Create a list of preliminary use cases, categorized and revised for inconsistencies.
    • Determine where multiple user types need the same use cases.
    • Review the finalized use cases with the corresponding user groups and key stakeholders.

    Event Decomposition Technique

    • More comprehensive and structured approach.
    • Identify events triggering system responses.
    • For each event, name a use case describing the system's action (verb-noun).
    • Define Events as something happening at a specific time and place.

    Events and Use Cases (Examples)

    • "Customer pays bill," so the use case is "Record a payment."
    • "Time to send late notices," so the use case is "Send late notices."
    • "Customer changes address," so the use case is "Maintain customer data."

    Types of Events

    • External event: event outside the system, typically initiated by an external actor.
    • Temporal event: event occurring as a result of reaching a point in time.
    • State event: event within the system that triggers a process.

    External Event Checklist

    • External agent or actor wants something resulting from a transaction.
    • External agent or actor requires information.
    • External data changed and requires updating.
    • Management needs information.

    Temporal Event Checklist

    • Internal outputs needed at specific times (e.g., management reports, operational reports).
    • External outputs needed at specific times (e.g., statements, status reports, bills).

    Finding the Actual Event

    • Illustrations help visually identify the actual event causing a system change.

    Tracing a Transaction Sequence

    • Sequence of events leading to multiple transactions.

    Event Decomposition Technique (Specific Steps)

    • Consider external events requiring a system response.
    • For each external event, define and name a use case.
    • Consider temporal events needing a system response; define and name a use case.
    • Define the steps, events, and use cases.
    • Review for required use cases.

    Event Decomposition Example (Recruitment System)

    • Example: a job applicant triggers creation of a profile, searching for vacancies, and submitting an application. The system must handle recording applicant information, recording vacancies, and accepting applications as necessary use cases.

    Event Decomposition Technique (Benefits)

    • Events are broader than user goals.
    • Capture temporal and state events.
    • Breaks down to elementary business processes (EBPs).
    • Fundamental business process steps for one person, action triggering use cases, system event.

    Perfect Technology Assumption

    • No need to anticipate limitations in technology; consider during design phase.
    • Examples: user logging on, changing passwords, preference settings.

    Summary

    • Use cases define system functions for user requests.
    • User goal and event decomposition are techniques used for this.
    • The user goal technique identifies actors and their goals, while event decomposition analyzes system-triggering events.
    • External, temporal, and state events are system-impacting factors.

    Studying That Suits You

    Use AI to generate personalized quizzes and flashcards to suit your learning preferences.

    Quiz Team

    Related Documents

    Description

    Test your knowledge on the Event Decomposition Technique and its various types of events. This quiz covers definitions, characteristics, and the implications of different event categories within a system. Perfect for students and professionals looking to deepen their understanding of event-driven analysis.

    More Like This

    Event Management
    12 questions

    Event Management

    ExemplaryRealism avatar
    ExemplaryRealism
    System Analysis Techniques Quiz
    42 questions
    Business Process Modeling Techniques
    29 questions
    Use Quizgecko on...
    Browser
    Browser