Preview

2.1.0 Explanation Of Use Case

Better Essays
Open Document
Open Document
1925 Words
Grammar
Grammar
Plagiarism
Plagiarism
Writing
Writing
Score
Score
2.1.0 Explanation Of Use Case
1.0 Explanation of Use Case
“Use Case” is a system engineering or software term that portrays how a customer or user uses a system to complete a certain task. In other word, “Use case” is act as a software modeling method that defines the logic to be implemented and the outcome of the error in the result can be encountered earlier.

An interaction between external actors is defined by use cases to attain particular goals. Three main elements that construct a use case are:
• Actors: Actors are the type of users that have interaction with the system.
• System: Systems are the functional requirements that specify the intended behavior of the system.
• Goals: In order to reach the goal, use case is used by a user to fulfill requirement by describing
…show more content…
There the clerk confirms their membership and checks for any overdue books. The return date of the selected book has been set, the student check it and leaves with their books.”

2.0 Explanation of Use Case Diagram

Use case diagram is graphic description of the communication and interactions among the elements of a system. As mentioned before, use case is a methodology used in system to identify, clarify and organize system requirements. UML (Unified Modeling Language) is a standard notation for the modeling of real-world objects and systems and is been employed in use case diagram.

There are 4 components contained in use case diagram, there are:
• Boundary: Define the system of interest in relation to the world around it.
• Actors: Individuals or Users involved with the system that are defined depend on their roles.
• Use Case: It specific the roles played by the actors within and around the system.
• Relationships: Connection between the actors and the use cases.
Use case is similar to flowchart. They are using presentational symbols to show the system element. Below is the simple
…show more content…
Each of these quality factors is also further break down:
• Functionality: o Feature Set o Capabilities o Generality o Security
• Usability o Human factors o Aesthetics o Consistency o Documentation
• Reliability o Frequency/severity of failure o Recoverability o Predictability o Accuracy o Mean time to failure
• Performance o Speed o Efficiency o Resource consumption o Throughput o Response time
• Supportability o Testability o Extensibility o Adaptability o Maintainability o Compatibility o Configurability o Serviceability o Installability o Localizability o Portability
From the above list, we can see that hierarchical definition model. The first four quality factors (FURP) are more focus at the customer or user and operator of the software and the last factor (S) is more aimed at the system developers, programmers, testers and

You May Also Find These Documents Helpful

  • Good Essays

    · Apply the tools of systems analysis to describe a work-related information system’s architecture in terms of data, processes, interfaces, and networks. Draw the physical and data flow and any other necessary diagrams.Include an explanation of eachdiagram. You may need to talk to your systems department for some help.…

    • 547 Words
    • 3 Pages
    Good Essays
  • Powerful Essays

    BIS261 Final Exam Paper

    • 1552 Words
    • 7 Pages

    ensure that the needs and wants of the client are represented correctly so that a solution can be developed and implemented by capturing and documenting the requirements needed to (design and) implement a solution…

    • 1552 Words
    • 7 Pages
    Powerful Essays
  • Good Essays

    Cis 210 Assignment 1

    • 917 Words
    • 4 Pages

    2. Why do systems analysts need to know who the stakeholders are in the organization?…

    • 917 Words
    • 4 Pages
    Good Essays
  • Powerful Essays

    Such applications of SAML are done in a particular "context of use". A particular context of…

    • 2032 Words
    • 9 Pages
    Powerful Essays
  • Powerful Essays

    Figure 11 - The Pie Chart for Failure Probability Based on the Table In The Appendix…

    • 9074 Words
    • 54 Pages
    Powerful Essays
  • Good Essays

    Reliability

    • 875 Words
    • 14 Pages

    Reliability in the design context Weibull Analysis • • • • Practical testing Trends Beta trends Real data for numerical work • Weibull examples Failure rate Early-life failure Wear out Mid-life failure Time in service Failure rate…

    • 875 Words
    • 14 Pages
    Good Essays
  • Powerful Essays

    Use Case Modeling

    • 80141 Words
    • 321 Pages

    There are still no trusted guides about how to write (or review) use cases, even though it is now nearly a decade since use cases have become the "norm" for writing functional requirements for object-oriented software systems, and are gaining acceptance for embedded software and business process reengineering work. I can say from firsthand attempts that is very difficult to articulate what makes a use case "good", let alone how to write them so they will come out being "good". This view is shared by many teachers of use case writing. The problem is that writing use cases is fundamentally an exercise in writing natural language essays, with all the difficulties in articulating "good" that comes with natural language prose writing in general. These are the guidelines I use in writing and coaching. The ideas came from listening to my on the fly inventions, describing to beginners what is going wrong, how to think and observe to get the writing to improve. This book has those guidelines, examples of use cases, variations that make sense - - and best of all, the reassurance that a use case need not be "best" to be "useful". Even mediocre use cases are useful, more useful than many of the competing requirements files being written. So relax, write something readable, and you will have done your organization a service already. Audience This book is predominantly aimed at the professional practitioners who read and study alone. For these people, the book is organized as a self-study guide. There are introductory, intermediate and advanced concepts, reminders and rules, examples, test questions with answers, and a set of discussions around frequently asked questions. The second group of people for whom this book is intended are consultants and…

    • 80141 Words
    • 321 Pages
    Powerful Essays
  • Powerful Essays

    Several recommendations were mentioned in the previous report. However, this document only focuses on providing the requirement model for the system of BasketCase Company to recruit and manage the workforce. The new system named Workforce Recruitment and Management…

    • 3552 Words
    • 15 Pages
    Powerful Essays
  • Satisfactory Essays

    Managing Project System

    • 306 Words
    • 2 Pages

    Data Flow Diagram - uses various symbols to show how the system transforms input data into useful information.…

    • 306 Words
    • 2 Pages
    Satisfactory Essays
  • Good Essays

    asdsdf sdf

    • 768 Words
    • 4 Pages

    2) Does each use case have one primary scenario, one or more variations of successful scenarios, and failure scenarios identified?…

    • 768 Words
    • 4 Pages
    Good Essays
  • Good Essays

    Case study emphasizes detailed contextual analysis of a limited numbers of events or conditions. As proposed by Eisenhardt (23), building theory from case studies is a research strategy that involves using one or more cases to create theoretical constructs, propositions and/or midrange theory from case-based, empirical evidence. Case studies are rich, empirical descriptions of particular instances of a phenomenon that are typically based on a variety of data sources (24). In this particular study, the use of of theis qualitative research method to examine contemporary operational situations and provided the basis for the application of product requirement and extension of…

    • 1198 Words
    • 5 Pages
    Good Essays
  • Good Essays

    The component diagram's main purpose is to show the structural relationships between the components of a system. In addition, component diagrams are useful communication tools for various groups. In creating a component diagram, there are different notations that can be used to show the different relationship of each component within the system. The component diagram notation set now makes it one of the easiest UML diagrams to draw:…

    • 912 Words
    • 4 Pages
    Good Essays
  • Powerful Essays

    In the study, the researchers used the Data Flow Diagram, which is a diagrammatic representation of the information flows within a system showing how information enters the system and leaves the system, what changes the information and where information is stored. Data Flow Diagrams show the passage of data through the system by using 5 basic constructs: Data Flows, Processes, Data Stores, External Entities, and Physical Resources, [Kendall, 2005]. The diagram would easily show the processes that would be done by the system and the other elements or entities that are involved.…

    • 1174 Words
    • 5 Pages
    Powerful Essays
  • Satisfactory Essays

    End users(administrator, manager, staff) can perform ordering, editing ,checking and management function insider the RAMsystem. End user can use food ordering function and food editing function only bill had been created by user. Only manager can manage the duty roaster. No one can edit the database or checks the password database execpt the administrator.…

    • 427 Words
    • 2 Pages
    Satisfactory Essays
  • Satisfactory Essays

    Marriage Failures

    • 1550 Words
    • 7 Pages

    | User Action1. Open the App2. user will select new data option3.user is going to add new mall info which includes mall name,mall address,phone no…

    • 1550 Words
    • 7 Pages
    Satisfactory Essays