It is the flow of transactions done by the Actors on accomplishing their goals. Elements in Use Casesġ) Brief description: A brief description explaining the case.Ģ) Actor: Users that are involved in Use Cases Actions.ģ) Precondition: Conditions to be Satisfied before the case begins.Ĥ) Basic Flow: ‘Basic Flow’ or ‘Main Scenario’ is the normal workflow in the system. We can seek the help of Stakeholders and product managers to prioritize the cases. The priority of such cases will come after the ‘Sunny Use Cases’. These can be defined as the list of edge cases. Once we have completed the cases, we give it to the project team for review and ensure that we have covered all the required cases. These are given high priority than the other cases. They are the primary cases that are most likely to happen when everything does well. Business stakeholders use the document for understanding the software requirements.Testers use them for creating the test cases.Developers use the documents for implementing the code and designing it.This documentation can be used by Software developers, software testers as well as Stakeholders. Better documentation can help to identify the requirement for a software system in a much easier way. This documentation gives a complete overview of the distinct ways in which the user interacts with a system to achieve the goal. In a case the capital Letter ‘A’ denotes ‘Actor’, the letter ‘S’ denotes ‘System’. For creating these, we need to have a development team assembled and the team should be highly aware of the project concepts.Īfter implementing the case, the document is tested, and the behavior of the System is checked accordingly. Use case writer, Team members, and the Customers will contribute towards the creation of these cases. The development team needs to write the ‘Use Cases’, as the development phase highly depends on them. It is not ‘system-oriented’: We will not specify ‘What are the input given to the system?’ and ‘What are the output produced by the system?’. It is ‘user-oriented’: We will specify ‘what are the actions done by the user?’ and ‘What the Actors see in a system?’. It is ‘user-oriented’ not ‘system-oriented’. In Use Case, we will describe ‘How a System will respond to a given Scenario?’. Use Cases may or may not result in achieving a goal by the ‘Actor/User’ on interactions with the system. It is the documentation of the ‘Actions’ performed by the Actor/User and the corresponding ‘Behaviour’ of the System to the User ‘Actions’. Use Case depends on ‘User Actions’ and ‘Response of System’ to the User Actions. Use case plays a significant role in the distinct phases of the Software Development Life Cycle.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |