Hris
Part-1 THE USE CASE
1. 1. Use-CASE:
In software and systems engineering, a use case is a list of steps, typically defining interactions between a role (known in UML as an "actor") and a system, to achieve a goal. The actor can be a human or an external system.
In systems engineering, use cases are used at a higher level than within software engineering, often representing missions or stakeholder goals. The detailed requirements may then be captured in SysML or as contractual statements.
Again a use case is a software and system engineering term that describes how a user uses a system to accomplish a particular goal. A use case acts as a software modeling technique that defines the features to be implemented and the resolution of any errors that may be encountered.
A use case is a description of how users will perform tasks on your Web site/Devise/System.
A use case includes two main parts: * the steps a user will take to accomplish a particular task on system * the way the system should respond to a user 's actions
A use case begins with a user 's goal and ends when that goal is fulfilled. (Wikidipedia, 2013)
1. 2. Characteristics:
A use case (or set of use cases) has these characteristics: * Organizes functional requirements * Models the goals of system/actor (user) interactions * Records paths (called scenarios) from trigger events to goals * Describes one main flow of events (also called a basic course of action), and possibly other ones, called exceptional flows of events (also called alternate courses of action) * Is multi-level, so that one use case can use the functionality of another one.
Use cases can be employed during several stages of software development, such as planning system requirements, validating design, testing software, and creating an outline for online help and user manuals. (Rouse, 2007) |
1. 3. Coverage:
A use case describes a sequence of interactions between a user and a Web site, without specifying the user
1. 1. Use-CASE:
In software and systems engineering, a use case is a list of steps, typically defining interactions between a role (known in UML as an "actor") and a system, to achieve a goal. The actor can be a human or an external system.
In systems engineering, use cases are used at a higher level than within software engineering, often representing missions or stakeholder goals. The detailed requirements may then be captured in SysML or as contractual statements.
Again a use case is a software and system engineering term that describes how a user uses a system to accomplish a particular goal. A use case acts as a software modeling technique that defines the features to be implemented and the resolution of any errors that may be encountered.
A use case is a description of how users will perform tasks on your Web site/Devise/System.
A use case includes two main parts: * the steps a user will take to accomplish a particular task on system * the way the system should respond to a user 's actions
A use case begins with a user 's goal and ends when that goal is fulfilled. (Wikidipedia, 2013)
1. 2. Characteristics:
A use case (or set of use cases) has these characteristics: * Organizes functional requirements * Models the goals of system/actor (user) interactions * Records paths (called scenarios) from trigger events to goals * Describes one main flow of events (also called a basic course of action), and possibly other ones, called exceptional flows of events (also called alternate courses of action) * Is multi-level, so that one use case can use the functionality of another one.
Use cases can be employed during several stages of software development, such as planning system requirements, validating design, testing software, and creating an outline for online help and user manuals. (Rouse, 2007) |
1. 3. Coverage:
A use case describes a sequence of interactions between a user and a Web site, without specifying the user
Bibliography: Chitnis, M. (2013, March 14). Creating UML Use Case Diagrams. Retrieved March 28, 2013, from www.developer.com: http://www.developer.com/design/article.php/2109801/Creating-Use-Case-Diagrams.htm Rouse, M. (2007, April 07). Use-case. Retrieved March 28, 2013, from www.techtarget.com: http://searchsoftwarequality.techtarget.com/definition/use-case tutorialspoint. (2013). UML Use Case Diagram. Retrieved MARCH 28, 2013, from www.tutorialspoint.com: http://www.tutorialspoint.com/uml/uml_use_case_diagram.htm tutorialspoint. (2013). uml_use_case_diagram. Retrieved march 28, 2013, from www.tutorialspoint.com: http://www.tutorialspoint.com/uml/uml_use_case_diagram.htm uml-diagrams.org. (2013). Use Case Diagrams Examples. Retrieved March 28, 2013, from www.uml-diagrams.org: http://www.uml-diagrams.org/use-case-diagrams-examples.html uml-diagrams.org. (2013). Use Case Diagrams Examples. Retrieved March 28, 2013, from www.uml-diagrams.org: http://www.uml-diagrams.org/use-case-diagrams-examples.html Wiegers, K. E. (2013). Five-use-case-traps-to-avoid. Retrieved march 28, 2013, from www.echtarget.com: http://searchsoftwarequality.techtarget.com/tip/Software-requirements-analysis-Five-use-case-traps-to-avoid Wikidipedia. (2013). Use case. Retrieved March 28, 2013, from www.wikipedia.org/wiki/Use_case: http://en.wikipedia.org/wiki/Use_case Wikipedia. (2013). use-case. Retrieved March 28, 2013, from www.wikipedia.com: http://en.wikipedia.org/wiki/Use_case