“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