Software use case examples




















But when a user adds friend then it must that user should first search the friend included. You need to develop a web-based application with the following functionalities; Users can buy products online by placing the online order. The user can pay the bill by credit card or through Paypal. This diagram represents inheritance among use cases. Place an order is the parent use case and pay through PayPal and pay through a credit card are child use cases. It means that some of the variables, functions are something else is inherited from parent to child.

Variables, functional and all kinds of data etc, that is set as protected, can be accessed from parent to child use case. For example, here anything can be inherited from place order use case to pay through pay and pay through credit card.

Variables, functional and all kinds of data, etc that are set as protected, can be accessed from parent to child use case. For example, here anything can be inherited from authentication use case to authentication by fingerprints and authentication info. Suppose you need to make a software in which when the user confirms order and confirmation need the confirmation depends upon the product selection, calculation of price with tax and payment.

Payment can be through PayPal or credit card. The basic flow, or main success scenario, is a use case that works perfectly and as fully intended, with no exceptions or errors in the run. They often serve as a foundation to create alternative options. Understanding how a normal scenario works can help you implement correct code or find alternative flows. An alternative path, or alternative flow, is a variation of the main success scenario.

It typically shows when an error happens at the system level. You often include the most likely or most significant alternatives an actor might make an exception for in this portion of the use case. In the e-commerce example, some alternative flows might include:. A session time-out when the customer is placing the order. A failed credit or debit card payment authorization. In this use case example, an international airline wants to refresh its online booking system, offering more complex fare options and ancillary revenue options and additional optional services, like curbside check-in.

UpCloud Airways software engineers design a branded and refreshed fare booking page, complete with tiered fare selection, add-on options like lounge access, free flight change or cancel abilities and complimentary checked bags. It also allows account holders to pay in credit, debit, online payment platforms or by UpCloud loyalty program miles.

The software engineers conduct several use cases to establish how the booking flow works and identify potential concerns. They run cases that include:. A customer browsing flight schedules and prices. A customer selecting a flight date and time. A customer adding on lounge access and free checked bags.

A customer paying with a personal credit card. A customer paying with UpCloud loyalty miles. Through the various use cases, the engineering team identifies a malfunction with the optional add-ons prompting unless the user has a previously established account. The team rectifies the issue before launching the refreshed booking system and the airline sees improved customer satisfaction ratings and increased revenue within the first week of the new platform.

In this use case scenario, a food delivery mobile application wants to expand to include more food and drink establishments, even if some locations have a limited menu. Deliver the Good Eats, a food delivery service, wants to grow the number of offered establishments and aims to include coffee shops and convenience stores.

The software developers need to determine how the newly featured establishments benefit from current software parameters and what user thresholds might prompt the software through to the next stage. The team runs use cases like:.

A customer searching for a specific name brand item not found in the area or chosen establishment. A customer with a low dollar amount total prompting for a minimum purchase message. A feature to allow customers to click "Order again," getting a previously purchased selection delivered again with quick user interaction. In this use case example, a ticket sales platform wants to streamline its functionality and make it more intuitive for customers. Ticket King sells concert and sporting event admissions tickets across the country at venues of all sizes, seat types and price points.

The company received feedback from customers saying the user interface was challenging, which served as a trigger for use cases. User, user, user, user, user, user. It really dials you into, as a businessperson, what the system is doing to support you and what those requirements actually are of the system that you might not see otherwise. User, user, user, user. You want the requirements. Not how the system is doing all that. Otherwise, you really have a different kind of document, not a use case.

Then, alternate flows and exception flows. These are the variant paths. You can do different things. You might have—Sometimes it might not fit within the scope of that use case but all the different things you can do. An exception flow might be: what happens if your Internet connection cuts out and the stream ends?

How does that get presented to the user? Things that go wrong and keep people from, stopping reaching the end goal or the end of the use case. Post-conditions are what are true after the use case is over. How do I communicate with developers, and how do I do things like requirements? What do I see the system doing for me? Then, the user fills in the order form; the user submits the order form, the shopping cart checks credit card details.

How does that actually happen? That would be really important, the user information from one system to the other, so we can automate that setup and get people their course registration details as quickly as possible.

That is the kind of thing where you would see the gap. We see this thing happening here. We have this thing happening here. Where does it come from, and how does it get there?



0コメント

  • 1000 / 1000