[{"data":1,"prerenderedAt":-1},["ShallowReactive",2],{"detail-sidebar-cat-0-en-105":3,"doc-seo-665504-105":59,"doc-detail-665504-en":130},{"code":4,"msg":5,"data":6},0,"success",[7,13,18,23,28,33,38,43,48,51,55],{"id":8,"doc_module":4,"doc_module_name":9,"category_name":10,"show_sort_weight":11,"slug":12},1,"Document","Story & Novel",90,"story-novel",{"id":14,"doc_module":4,"doc_module_name":9,"category_name":15,"show_sort_weight":16,"slug":17},2,"Literature",80,"literature",{"id":19,"doc_module":4,"doc_module_name":9,"category_name":20,"show_sort_weight":21,"slug":22},4,"Exam",70,"exam",{"id":24,"doc_module":4,"doc_module_name":9,"category_name":25,"show_sort_weight":26,"slug":27},5,"Comic",60,"comic",{"id":29,"doc_module":4,"doc_module_name":9,"category_name":30,"show_sort_weight":31,"slug":32},6,"Technology",50,"technology",{"id":34,"doc_module":4,"doc_module_name":9,"category_name":35,"show_sort_weight":36,"slug":37},7,"Healthcare",40,"healthcare",{"id":39,"doc_module":4,"doc_module_name":9,"category_name":40,"show_sort_weight":41,"slug":42},8,"Research & Report",30,"research-report",{"id":44,"doc_module":4,"doc_module_name":9,"category_name":45,"show_sort_weight":46,"slug":47},9,"Religion & Spirituality",20,"religion-spirituality",{"id":46,"doc_module":4,"doc_module_name":9,"category_name":49,"show_sort_weight":46,"slug":50},"World Cup","world-cup",{"id":52,"doc_module":4,"doc_module_name":9,"category_name":53,"show_sort_weight":52,"slug":54},10,"Lifestyle","lifestyle",{"id":56,"doc_module":4,"doc_module_name":9,"category_name":57,"show_sort_weight":24,"slug":58},19,"General","general",{"code":4,"msg":60,"data":61},"ok",{"site_id":62,"language":63,"slug":64,"title":65,"keywords":66,"description":67,"schema_data":68,"social_meta":123,"head_meta":125,"extra_data":127,"updated_unix":129},105,"en","lab-2-introduction-to-use-case-modeling","LAB 2 - Introduction to Use Case Modeling","","The document provides lab notes for “LAB 2: Introduction to Use Case Modeling,” focusing on requirements analysis using UML use case diagrams. It explains the definition and purpose of use case diagrams, outlines when use cases are typically created during project development, and introduces core UML notations. The notes cover constructs such as actors, system boundaries, and key relationships including association, generalization, include, and extend, with guidance for naming and designing actor and use case elements. It includes in-class exercise scenarios that apply these concepts.",{"@graph":69,"@context":122},[70,84,105],{"@type":71,"itemListElement":72},"BreadcrumbList",[73,77,79,82],{"item":74,"name":75,"@type":76,"position":8},"https://docshare.wps.com","Home","ListItem",{"item":78,"name":9,"@type":76,"position":14},"https://docshare.wps.com/document/",{"item":80,"name":30,"@type":76,"position":81},"https://docshare.wps.com/document/technology/",3,{"item":83,"name":65,"@type":76,"position":19},"https://docshare.wps.com/document/lab-2-introduction-to-use-case-modeling/665504/",{"url":83,"name":65,"@type":85,"image":86,"author":91,"headline":65,"publisher":94,"fileFormat":97,"inLanguage":63,"description":67,"dateModified":98,"datePublished":99,"encodingFormat":97,"isAccessibleForFree":100,"interactionStatistic":101},"DigitalDocument",{"url":87,"@type":88,"width":89,"height":90},"https://docshare.wps.com/thumbnails/lab-2-introduction-to-use-case-modeling/665504.png","ImageObject",300,407,{"name":92,"@type":93},"Ben ","Person",{"url":74,"name":95,"@type":96},"DocShare","Organization","application/pdf","2026-10-30","2026-10-29",true,{"@type":102,"interactionType":103,"userInteractionCount":14},"InteractionCounter",{"@type":104},"ViewAction",{"@type":106,"mainEntity":107},"FAQPage",[108,114,118],{"name":109,"@type":110,"acceptedAnswer":111},"What is a Use Case Diagram used for in requirements analysis?","Question",{"text":112,"@type":113},"A use case diagram represents system functionality from the user’s perspective by showing relationships among actors and use cases. It helps expose requirements and supports project planning, especially in early project stages.","Answer",{"name":115,"@type":110,"acceptedAnswer":116},"What are the main UML relationships covered in the notes?",{"text":117,"@type":113},"The notes cover association, generalization, include, and extend. Generalization captures shared behavior in a parent/child structure, while include extracts common behavior shared by multiple use cases and extend adds optional or additional behavior to a base use case.",{"name":119,"@type":110,"acceptedAnswer":120},"How should actors and use cases be designed or named?",{"text":121,"@type":113},"Actors can be human users, other systems, timers/clocks, or hardware devices. Use cases should ideally start with a verb and should not be open ended; examples show that specific forms like “Register New User” are preferred over generic wording.","https://schema.org",{"og:url":83,"og:type":124,"og:title":65,"og:site_name":95,"og:description":67},"article",{"robots":126,"canonical":83},"index,follow",{"doc_id":128,"site_id":62},665504,1793304523,{"code":4,"msg":5,"data":131},{"doc_id":128,"user_id":132,"nickname":92,"user_avatar":133,"doc_module":4,"category_id":29,"category_name":30,"doc_title":65,"doc_description":67,"doc_content":134,"file_id":135,"file_url":136,"file_type":137,"file_size":138,"view_count":14,"is_deleted":4,"is_public":8,"is_downloadable":8,"audit_status":8,"page_count":56,"language":139,"language_code":63,"site_id":62,"html_lang":63,"table_of_contents":140,"faqs":141,"seo_title":142,"seo_description":67,"update_tm":129,"read_time":143},2336478951081,"https://ap-avatar.wpscdn.com/davatar_276721f389ce27ea32af1340a28f341c","TU2943: Information Engineering Methodology Lab Notes, 2009-2010, Faculty of Technology and Information Science, Universiti Kebangsaan Malaysia  \nLAB 2 : Introduction to Use Case Modeling  \nOBJECTIVES  \n􀀁 Familiarize with the concept underlining Use Case Diagram for requirement analysis.  \n􀀁 Exposure on all elements grouped under UML Case Diagram.  \n􀀁 Analyze functional requirements and problem statements of an intended system to be able to translate into use case modeling.  \n􀀁 Be able to document use case description and specifications.  \nINTRODUCTION  \nDefinition of Use Case Diagram  \n􀀁 A Use Case is a set of scenarios describing an interaction between a user and a system.  \n􀀁 Use Case diagram displays (in symbolic form) the relationship among actor and use cases.  \n􀀁 Use case represents the system’s functionality, the requirements of the system from the user’s perspective.  \nWhen to use Use Cases  \n􀀁 Use cases are used in almost every project.  \n􀀁 Very helpful in exposing requirements and planning of project.  \n􀀁 Usually done during the early stages of project. Frequently starts by being loose in terms of connection and accuracy, but as project continues, the use cases are defined better.  \nUML Notation for Use Case Modeling  \n\n| Construct | Description | Syntax |\n| --- | --- | --- |\n| Use Case | A description of a set of sequences of actions, including variants, that system performs that yields an observable value to an actor (Booch, 1993) . | |\n| Actor | The people or system that provides or receives information from the system; called the stakeholder of the system. | |\n\n\n| System Boundary | The boundary between the physical system and the actors who interact with the physical system. | |\n| --- | --- | --- |\n| Association | The participation of an actor in a use case. | |\n| Generalization | A taxonomical relationship between a general use case and a more specific use case. | |\n| Extend | Relationship between the extension use case and the base use case. Specify how the behavior of the extension use case can be inserted into the behavior defined for the base use case. | |\n| Include | Relationship between a base use case and an inclusion use case, specifying how the behavior of the inclusion use case can be inserted into the behavior defined for the base use case. | |\n\nActor  \n􀀁 Could be human beings, other system, timers and clocks or hardware device.  \n􀀁 2 types of actor classification:  \n􀀁 Primary Actors: Actors that stimulate the system and the initiator of events.  \n􀀁 Secondary Actors: Actors that only receive stimuli from the system.  \n􀀁 Actor Designing Consideration:  \n􀀁 Who / what will be interested in the system  \n􀀁 Who / what will want to change the data in the system  \n􀀁 Who / what will want to interface with the system  \n􀀁 Who / what will want information from the system  \nUse Case  \n􀀁 Use case should ideally begin with a verb.  \n􀀁 Should not be open ended. Register, wrong. Register New User, right.  \nActor / Use Case Generalization  \n􀀁 Used when you find 2 or more use cases that have commonalities in behavior, structure and purpose.  \n􀀁 A parent use case may be specialized into 1 or more child use cases that represent more specific form of the parent.  \n􀀁 Neither parent nor child is necessarily abstract, although the parent in most cases is abstract.  \n􀀁 Children of the same parent are all specialization of the parent.  \n􀀁 For example, suppose the ATM system can be used to pay bills. Pay bills has two child use cases : Pay Credit Card Bill and Pay Utility Bill  \nInclude Relationship  \n􀀁 Used when 2 or more use cases share some common portion in a flow of events.  \n􀀁 The common portion is grouped and extracted to form an inclusion use case to be shared among the use cases related.  \n􀀁 Specifies that the source use case explicitly incorporates the behavior of another use case at a location specified by the source.  \n􀀁 For example, in the ATM system example, such as Withdraw Money, Deposit Money or Check Balance, ","cbCaipMKGnSV22s9","https://ap.wps.com/l/cbCaipMKGnSV22s9","pdf",808734,"English","# Objectives\n# Introduction\n## Definition of Use Case Diagram\n## When to use Use Cases\n# UML Notation for Use Case Modeling\n## Use Case and Actor\n## System Boundary\n## Association, Generalization, Include, Extend\n# Actor\n# Use Case\n# Actor / Use Case Generalization\n# Include Relationship\n# Extend Relationship\n# In-Class Exercises","[{\"question\":\"What is a Use Case Diagram used for in requirements analysis?\",\"answer\":\"A use case diagram represents system functionality from the user’s perspective by showing relationships among actors and use cases. It helps expose requirements and supports project planning, especially in early project stages.\"},{\"question\":\"What are the main UML relationships covered in the notes?\",\"answer\":\"The notes cover association, generalization, include, and extend. Generalization captures shared behavior in a parent/child structure, while include extracts common behavior shared by multiple use cases and extend adds optional or additional behavior to a base use case.\"},{\"question\":\"How should actors and use cases be designed or named?\",\"answer\":\"Actors can be human users, other systems, timers/clocks, or hardware devices. Use cases should ideally start with a verb and should not be open ended; examples show that specific forms like “Register New User” are preferred over generic wording.\"}]","LAB 2 - Introduction to Use Case Modeling | PDF",48]