SCAG

Grupo: SCAG

Integrantes:

• German Andrade
• Antonio de la Vega
• Carlos Gonzalez
• Esneider Velandia

Contrato:
El contrato del grupo lo puede encontrar aquí y el formato de lanzamientos y compromisos aquí.

Problemas a solucionar:

• Queremos solucionar la experiencia de los usuarios cuando van a mercar, específicamente minimizar el tiempo de pago. Los almacenes de cadena por lo general son altamente frecuentados en épocas de pagos, es decir, a inicio o final de mes.  Esto genera largas filas para hacer el pago y que los productos se agoten rápidamente. Este evento que se genera cada 15 días es un problema para todos sus usuarios. Una posible solución es desarrollar una aplicación móvil que permita al usuario realizar la factura de los productos que va a llevar mientras los esta escogiendo. El usuario debe escanear el código de barras de cada producto con su celular usando la cámara y cuando ya desee pagar, la aplicación le asigna una caja disponible para que realice únicamente realice el pago, ademas se desea desarrollar un motor de sugerencias de productos asociados a los que lleva.

• La idea principal detrás de la solución es tener una aplicación para la cámara que ayuda a los turistas con la señalización y las reseñas de restaurantes. La aplicación usaría la cámara para superponer componentes AR a la imagen que está viendo el usuario. De esta forma, podemos agregar señalización al área y superponer las reseñas en la parte superior del restaurante al que el usuario apunta su cámara. También es posible usar otros sensores para ayudar al usuario a navegar por el área / restaurantes. Por ejemplo, podríamos usar audio + micrófono para ayudar al usuario a navegar por el área sin usar la cámara. Por supuesto, los servicios de localización se usarían activamente en esta solución. De esta forma, sabemos dónde está nuestro usuario, qué restaurantes están cerca de él, qué caminos debe recorrer y hacia dónde apunta el celular.

App Restaurants

Problem: Pedestrians that explore tourist zones with many restaurants have no idea which one to
pick.It is really hard to make up your mind due to the sheer amount of restaurants in the area. It is
also difficult to look at ratings for all of them. Specially when looking through Google Maps. Since
these tourist areas tend to be so big, they are not fully explored by tourists / pedestrians since its
not clear where it ends.

Solution

The main idea behind the solution is having a camera-first app that helps tourists with both signalization
and restaurant reviews. The app would use the camera to overlay AR components to the image the user is seeing. This way, we can add signalization to the area and overlay the reviews on top of the restaurant the user is pointing its camera at. It is also possible to use other sensors to help the user navigate the area / restaurants. For example, we could use audio + microphone to help the user navigate the area without using the camera. Of course, location services would be actively used in this solution. This way we know where our user is, what restaurants are near him, which roads he should go through, and where is the smartphone pointing to.

Personas

1.

Persona: Foreigner visiting Colombia

Fictional name: Bob McDonald

Demographics: 29 year old, single man with no children. Has a bachelor's degree from a
foreign university. Currently in vacation.

Motivations: He is very hungry and wants to eat a good meal fast. He expects the app to
help him find a good restaurant in an easy manner given the large number of options available.
He also doesn't speak Spanish, however, he does speak English. He is a pedestrian.

Technical ability: He is very comfortable using smartphones, smart watches, etc.

Devices: He has a latest generation smartphone (iPhone 8 or iPhone X OS 11, Google Pixel 2
on Android Oreo).

2.

Persona: Local with poor sense of location

Fictional name: Alicia Gomez

Demographics: 40 year old, married woman with 1 child. Has a bachelor's degree and
works as an accountant for a national firm.

Motivations: She lives in Bogota but suffers from poor orientation/location. She wants
to explore the area in its entirety but she doesn't really know how to get around. The poor
signalization in the area affects her ability to move! She is a pedestrian.

Technical ability: She is only comfortable using smartphones for simple purposes
(no complicated menus, features that can only be accessed after several touches).
Anything else will frustrate her.

Devices: She only has a smartphone with her. It is a old iPhone or Android
(iPhone 6 on iOS 10, mid-tier Android device with Marshmallow version).

3.

Persona: Young person that tends to visit the area in a group.

Fictional name: Juliana Casas

Demographics: 21 year old, single woman with no children. Currently pursuing a
bachelor's degree from a local university. Has many friends of her same age & demographics.

Motivations: She constantly visits the area with her friends to try out trending restaurants.
She loves to eat new things. However, it has been hard for her to spot the new/flashy
restaurants. Currently she relies on word of mouth but she really wishes the process was
easier.

Technical ability: She is very comfortable using smartphones, smart watches, etc.

Devices: She has a latest generation smartphone (iPhone 8 or iPhone X OS 11,
Google Pixel 2 on Android Oreo).

4.

Persona: Data scientist interested in restaurant trends and pedestrian behavior.

Fictional name: Raul Mendoza

Demographics: 30 year old, government worker. Focused on his job, with 9am to 5pm
schedule.

Motivations: He wishes to know how many people visit areas like Zona G or Zona T on
a daily basis to provide support on decisions made on these areas (for example Zona G
pedestrian only). At the moment, he can only rely on estimations.

Technical ability: Has an advanced technical ability. He is able to use data to exploit trends.
Comfortable using web pages and dashboard-like software.

Devices: Desktop or laptop with good specs (Intel iCore 5+ processor with 8Gb of RAM
and decent graphic's card).

Context canvas

https://drive.google.com/file/d/13-1n6lOdVgFIW98QQ_0-27V94H1TNYe4/view?usp=sharing

(i) The data collected with the device/app

• User location
• User restaurants and dishes reviews
• User photos

(ii) Data that can be extracted from any other source (e.g., a government open data
service, a private web service)

• Google Maps API
• TripAdvisor Business API
• Google Places API

(iii) The knowledge/information expected to be extracted from the data.

Business questions

1. Which restaurants are trending in an area?
2. Which type of dishes do users request the most in an area?
3. Which type of dishes are best reviewed in an area?
4. Which are the top dishes of a given restaurant?
5. Which are the most economic restaurants?
6. Which dishes are best reviewed in an area?
7. Which dishes do users request the most in an area?
8. Which areas have the most congestion?
9. What is the pedestrian congestion of an area?
10. Which type of user buys the most amount of food?
11. Which type of user buys the most amount of a certain dish?
12. How does the user move around the area?
13. Which type of external restaurant decoration attracts the most amount of clients?
14. When does the area get congested the most?
15. When is the app used the most?
16. How does the location of the restaurant affects the amount of clients they get?
17. How many clients does a restaurant get by hour?
18. How many dishes does a restaurant serve by hour?
19. What ingredients make people buy the most dishes?
20. What type of clients buy the most amount of products (by nationality).
21. Why do people prefer to eat in certain places more than others.
22. Why do people refuse to use our app?
23. How does the menu affect the number of visitors a restaurant receives?
24. What factors contribute to the overall time spent by a customer at a restaurant?
25. Is the number of clients received in a restaurant correlated with the distance to the nearest parking lot?
26. Which restaurants are experiencing queues at a particular hour?
27. At what times do each restaurant experience the most user activity?
28. What is the expected number of users in a particular restaurant at a given time?
29. What dishes should a restaurant prepare beforehand to be able to cope with an imminent surge in users?
30. How many days in average do users that visit a particular restaurant take to visit it again?
31. Does the ordering of the items in the menu affect the number of times a particular dish is ordered?
32. How many days in average does a user visit any restaurant?
33. Is the number of clients received correlated to the decoration of the place?
34. Is the number of clients received correlated to the variety of the food?
35. Is selling alcoholic beverages a factor that increases the number of people who go to the restaurant?
36. In average, which are the most sold dishes according to the day of the week?
37. Does the waiting time of a dish affect the number of times this particular dish is ordered?
38. In average, which are the most sold dishes by month?
39. Which are the least ordered dishes in a particular restaurant?
40. How does the price of the dish affect the amount of time that it is ordered?

VD map

Functional scenarios

1. The user wants to create a new account. The app must register his basic information on the database, including a user name and a password, letting him enter the app and giving him access to all logged in functionalities.
2. The user wants to login, the app must verify user and password against the server.
3. The user wants to see the best restaurants near him, the application must show a list based on the restaurants with the best scores in the database that are in the same area as the user.
4. The user wants to rate a particular restaurant. The app must show him the basic information of the restaurant he wants to rate and let him add to the database a 1 to 5 star rating that adds up to the general score of the restaurant.
5. The user wants to know the information of the restaurant that is in front of him by using his camera. The app must overlay in the camera image the information of the restaurant he is pointing at.
6. The user wants to see which nearby restaurants are trending (i.e., it started becoming popular recently). The app must query the database to find which restaurants have the app’s user started visiting more often to display this information to the user by locating the trending ones in a map (adding a pin).
7. The user wants to see the pedestrian congestion of an area. The app should display a map that overlays this information using a heat map.
8. The user wants to get recommendations of restaurants he should visit. The app should retrieve a list of restaurants picked based on the user’s preferences and eating habits.
9. The user wants to search for a particular restaurant. The app should allow him to filter them by the type of food that they serve, minimum rating, minimum and maximum average price, and the area where the restaurant is located.
10. The user (pedestrian) wants to receive directions to a particular restaurant. The app should use the phone’s speaker to help the user reach his destination.

Quality scenarios

1

Scenario Name: User starts using camera to obtain restaurant information

Quality attributes involved in the scenario: Performance

App status and context: The app is currently opening the camera. It must have permissions to do so. It also must have permission to access location services. Additionall

Changes in the context (includes what the persona is doing): The camera opened, the user starts pointing the smartphone towards the restaurant he wants to get more information about. The app starts hitting the backend server to analyze what is the user seeing in order to provide useful insights.

System reaction to the changes in the context: The backend must be able to answer each user image query in less than 500ms to guarantee semi real time performance. This way the user will perceive that the information overlaid on top of the image is instant (giving a good AR experience).

2

Scenario Name: A user tries to alter the app’s database with SQL injection

Quality attributes involved in the scenario: Security

App status and context: The app is running and displaying the login/sign in screen to the user. The user is trying to use this page for malicious acts against the app’s information.

Changes in the context (includes what the persona is doing): The user start entering inputs with the intention of altering the app’s database for his own good (changing some restaurant’s score, letting him login without signing in first, etc).

System reaction to the changes in the context: The app validates all inputs for length, range, format and type using constraints and sanitizers which denies the user of doing a SQL injection to the db. It denies the user of entering this input to the system’s backend.

3

Scenario Name: The app must be able to communicate and exchange information with TripAdvisor and Google Places.

Quality attributes involved in the scenario: Interoperability

App status and context: The app is displayed a list of restaurants names to the user with no additional information. The user is contemplating which one he wishes to know more about. The user is already in an area with lots of restaurants nearby (e.g. Zona T or Zona G).

Changes in the context (includes what the persona is doing) The user tapped a restaurant that interested him. This triggers a change in the UI. Now, detailed information about the restaurant must appear.

System reaction to the changes in the context: In order to provide detailed restaurant information like rating, menus, prices, etc, we must use third-party services. Mainly, our app should be able to communicate with Google Places API and TripAdvisor API. Both APIs provide detailed information.

4

Scenario Name: The app should have an availability of 99%, i.e. it should be available 99% of the 365 days of the year.

Quality attributes involved in the scenario: Reliability

App status and context: The app is being used normally by a set of users. Everything is working as intended.

Changes in the context (includes what the persona is doing): The main backend server experienced an issue and ceased to work. The users start noticing a delay on the last request they submitted through the app. The user is running out of patience.

System reaction to the changes in the context: The applications should start to redirect requests to a backup server immediately. Pending user requests should fail fast in order for them to hit the backup server. This transition must go as smoothly as possible in the least amount of time possible to ensure an overall availability of the application of 99% throughout the year.

5

Scenario Name: The amount of users start to increase rapidly

Quality attributes involved in the scenario: Scalability, performance

App status and context: The app has a few amount of users in the beta testing phase. Users are happy with the response times of the app.

Changes in the context (includes what the persona is doing): After releasing the app and doing some publicity campaigns, the app starts getting an overwhelming amount of users, and each user is making a great amount of requests per minute.

System reaction to the changes in the context: The app must be able to handle this issues by having a scalable infrastructure that handles a large amount of requests at the same time. There should be no notable changes in the response times of the application.

6

Scenario Name: The user doesn’t have a reliable internet connection

Quality attributes involved in the scenario: Availability and performance

App status and context: The app is in use at the moment. The user is trying to find a good restaurant in the area by using the map that we have provided for him.

Changes in the context (includes what the persona is doing): The user is going through an area with low reception or with so much congestion that his network is failing. The app starts to see that the user is having unreliable external systems, failed communications and failed transactions.

System reaction to the changes in the context: The app needs to be able to handle network faults by using high performance communication between tiers. The app will be able to take the system offline but still queue pending requests. Then it will implement store and forward or cached message-based communication systems to store requests and replay them when it is online.

7

Scenario Name: Web Analytics Heat Map works as Expected.

Quality attributes involved in the scenario: Performance

App status and context: The user is logging into the web app to check what is the pedestrian congestion on certain areas in the city.

Changes in the context (includes what the persona is doing): The heat map showing the congestion of the areas just loaded. The user zoomed in on a particular area in the city (e.g. Zona T).

System reaction to the changes in the context: The system must be able to perform aggregations on all the user location data to determine what is the congestion level of the area in less than 1 second. If it takes longer, the user might close the application or grow impatient.

8

Scenario Name: User (pedestrian) is getting directions to a restaurant through the speaker.

Quality attributes involved in the scenario: Usability

App status and context: The user arrived to an area he doesn’t know well. He wishes to get to a restaurant, but doesn’t know how to get there. The app is open but the user has yet to provide an action.

Changes in the context (includes what the persona is doing): The user tapped the button that activated the feature for voice-controlled directions. The user gave the name of the place he wished to arrive to.

System reaction to the changes in the context: The app must “understand” what was it that the user said in the first try. It must also then provide TIMELY updates through the speaker that indicate to the user when to turn left, right, etc.

9

Scenario Name: The user is running low on device memory

Quality attributes involved in the scenario: Performance

App status and context: The app is running smoothly, sending and receiving requests and storing some of its data on the device temporarily.

Changes in the context (includes what the persona is doing): The user starts to save a lot of the restaurants information to his phone. The device starts to run low on memory and can’t handle any more transactions.

System reaction to the changes in the context: The system needs to be able to maintain the performance of the app, without having excessive cache misses and decreasing data store access, due to the efficient and appropriate caching strategy that we have implemented.

10

Scenario Name: There is a critical change in the OS, some functionalities stop working

Quality attributes involved in the scenario: Modifiability

App status and context: The user just updated his OS version to the latest, where there have been some library changes and some functionalities of the OS have been removed.

Changes in the context (includes what the persona is doing):  The user is trying to use some of the app’s functionalities, but they are not working quite as expected. The user reports this to the app’s creators.

System reaction to the changes in the context: The system must immediately react to the failures in the system and notify the user about the bug, letting him know that shortly there will be an update to fix this error. The system must be easy to maintain and modify when this type of things occur, so it can provide the user with an update as quickly as possible.

App: Supermarket

Problem: When a user goes to the supermarket on special dates (end of month or every 15 days; days of payment) must make long lines to make the payment of the products that they want to take, this generates annoyance in the clients because they spend more time in paying than finding your products.

Solution: Mainly we want to make a mobile application that allows the customer to make the invoice of the products that he wants to take while he is doing the tour of the supermarket, in addition, the application will allow to search for a specific product and in the screen will show the route that he must do to find the product. Finally, we want to give small announcements of the products that are in promotion and that will be of interest for the client.

Persons

• Person: Mother
• Name: Patricia Lagos
• Demographic data: Tiene 48 years old, psychologist with a Child Development Specialization, marry with two childs, works in a hospital
• Motivation: She  wants to spend less time in the payline at the supermarket. Furthermore, she wants to be notified with products that may be of their interest or that has a discount.

• Technical capability: Patricia uses his phone in average 3 hours per day.
• Dispositivos: She has a phone with android Oreo, an Ipad 3 and a Samsung Smart TV. Furthermore, she has a desktop computer with windows 10.

• Persona: GrandMother
• Nombre ficticio: Paulina Méndez
• Demographic data: Woman, 69 years old, marry and with 5 children, only has primary education, housewife and comes from Quindio.
• Motivation: She wants to be able to have a list of the products that she want to buy and get recommendations. In addition, she is interested in catch up with the technology.
• Technical capability: She is making their first steps with technology, she uses Whatsapp to communicate with their family but it's hard to her.
• Devices: She uses an mid tier android phone with Lollipop.

• Person: Hijo
• Name: Samuel Elias
• Demographic data: Young man of 21 years old, has no children, at this moment he is studying his penultimate year of design, he is single, he lives with his parents in the city of Bogotá.
• Motivation: For Samuel it is cumbersome and boring to go to the supermarket, since, he must collaborate in line while his family makes the market. In addition, he must have patience when accompanying your mother, since you must search several times for a product. For Samuel the application is useful because it decreases the time spent doing this diligence.
• Technical capability: The use of technology for Samuel is one of his main motivations, since he thinks that these tools facilitate his daily life. For this reason, it has no problems with learning a new technology.
• Devices: In addition to his Smartphone, Samuel has an iPad to carry out his books and a computer that is his main tool of work in the university.

• Persona: Commercial analytics manager
• Nombre ficticio: Hector
• Demographic data: He is an adult person of 43 years old, is married, has a university son, at this moment he is finishing his master's degree in commercial analytics and lives in the city of Bogotá.
• Motivaciones: For Hector it is an honor to work with one of the most recognized chain stores in Colombia, for this reason implementing an analytical engine in the warehouses allows us to demonstrate their skills and knowledge. With the implementation of this system Hector can suggest changes that generate an increase in revenues.
• Technical capability: The use of technologies is their specialty, since their work is based on the use of advanced software and hardware tools.
• Devices: Permanently makes use of the laptop and his cell phone, but he likes to be fashionable and has a Smart Watch.

Context canvas

(i) the data collected with the device/app

• the information of the each product.
• the georeferencing of each hall in the supermarket.
• the information of the persons.

(ii) data that can be extracted from any other source (e.g., a government open data service, a private web service)

• The weather
• The holidays
• Games matches (mainly soccer)

(iii) the knowledge/information expected to be extracted from the data.

A simple way for defining the objectives is to make a list of the questions that should be answered with the analytics engine:

Business questions

1. Which is a good recommendation of product for an user?
2. Which is the most popular zone of the market?
3. Which is the rate of increase of sales of a product in promotion?
4. What kind of users exists based on their purchases.
5. Which are the top 10 products for amount of sales?
6. Which are the top 10 products for amount of profit?
7. Which schedule is the most visited?
8. Which products tend to be sold together?
9. What are the days more popular of the week?
10. Why do users choose to go to this place and not to another?
11. Which type of products are best reviewed for each type?
12. Which are the cheapest products?
13. All user that visit this place have a phone ?
14. The products that are offered in the supermarket is the same if this place are situated in other zone in the city ?
15. What kind of products are the most profit?
16. Given the address of the store which are the most important products?
17. Are the events that trigger the sales?
18. Which are the low salest products?
19. Which are less the profitable products?
20. Who are the most important clients?
21. Why people prefer to buy here?
22. what percentage of customers use the parking
23. Which products use to lost their barcode?
24. What kind of products are used to be most returned?
25. How are our prices vs our competitors?
26. What products of the self-brand are the most sell?
27. What products of the self-brand are the less sell?
28. What products of the self-brand are the most profitable?
29. What products of the self-brand are the less profitable?
30. Who are frequent customers?
31. What kind of products buy our frequent customers?
32. What percentage of our customers buy impulse products?
33. Which is the highest sale without counting electrodomestic products?
34. What is the influence of the weather on sales?
35. What are the relations between products ? (cigarettes and gums)
36. If the supermarket have the web marketplace what is the most and less popular product ?
37. Are all product offered on the web?
38. What are the profile of user that buy in your web place? is the same that there are in the physical place?
39. Is there a possibility that some products will be stolen? how to detect this ?
40. which are the most common reason that are returned the products? and What are these?

VD map

Functional scenarios

1. The user wants to know the position of a product, the application must show him their location, the user is already in the supermarket and has internet connection.
2. The user wants to add a product to their shopping cart, the application must add the product if it does not exceed the limit, the user is already in the supermarket.
3. The user want to pay their products, the application must put him on a queue and send him a notification with the number of cashier when it's the turn of the user, he is in the supermarket.
4. The user want to get a recommended product. The application must recommends products based on the last product added, the user is in the supermarket.
5. The user wants to add a product to their reminder list, the application must show him the products related to his search and it to the list, the user does not have to be in the supermarket.
6. The user want to get a recommended product. The application must recommends products based on the last product added, does not have to be in the supermarket.
7. The user want to check their old bills. The app must store this bills in the phone (at least the last 10), not internet connection is required.
8. The user want to rate a product. The app must allow the user to rate every product that he has already buy, only internet connection is needed.
9. The user want to search a product, the app must allow him to filter by brand, price and number of starts, only internet connection is needed.
10. The user want to login, the app must verify user and password against the server, only internet connection is needed.
11. The user wants to create a new account. The app must register his basic information on the database, including a user name and a password, letting him enter the app and giving him access to all logged in functionalities.
12. The user wants to login, the app must verify user and password against the server.

Quality scenarios

1. Scenario name: The person open the app

• Quality attributes involved in the scenario:  low energy consumption
• App status and context: In this moment the app is not running, but it is installed in the device of the user.
• Changes in the context (includes what the persona is doing): The person is entering to the supermarket, take his cellphone and open the app (our solution). Automatically fill sign in(if not is the first time in the app) and then start looking for the products.
• System reaction to the changes in the context: the app start to running in the device of the user and show the products that are in promotion.

2. Scenario name: How to use

• Quality attributes involved in the scenario: Usability
• App status and context: The app in this moment is in use, but is in second “activity” view, in this frame the app show the products in promotion and provide the user means to search a specific product. Also the bluetooth of the device mobile are on, because it can define a route for each search. Finally show a button to make a scan product barcode.
• Changes in the context (includes what the persona is doing): : The user is in the first frame, they view some things that can do and chooses one. It depends on the activity that user has done. The context changes depending on the option that he choose.
• System reaction to the changes in the context: As mentioned above depends on the action the user takes. If he chose to see the discount, a list of the products in promotion is displayed, if he chose the option to search for a specific product, the application should show a route that indicates the path that the user must do and if he is scanned a barcode, simply scan the product and is open again for a new capture.

3. Scenario name: The person wants to pay his account.

• Quality attributes involved in the scenario: Interoperability
• App status and context: The application is about to finish generating the invoice, since the user gave a click in send invoice (a button), this sends the invoice to the box that has fewer users queued.
• Changes in the context: The user clicks on send invoice, later, the application returns the number of the box to which the user must go to make the payment.
• System reaction to the changes in the context: The system after generating the invoice, indicate the user where to go and the total that must be canceled. The app must return to the initial state and save (in DB) the products that have it.

4. Scenario name: The user have a different OS

• Quality attributes involved in the scenario:  Interoperability
• App status and context:In this moment the app is not running, but it is install in the device of the user.
• Changes in the context: The person is entering to the supermarket, take his cellphone and open the app (our solution). Automatically fill sign in(if not is the first time in the app) and then start looking for the products.
• System reaction to the changes in the context: Regardless of the OS, the application must have a similar physical appearance and the same functionalities when the user accesses it from his mobile device.

5. Scenario name: User actions

• Quality attributes involved in the scenario: Performance
• App status and context: The application is running, the user can be in the supermarket or not, may have internet.
• Changes in the context: The user try to make any action, like search a product or consult a bill.
• System reaction to the changes in the context: The system should respond to the user in less than a second, if the user does not have internet and tries to do an action that requires internet the app will inform him.

6. Scenario name: Amount of users increase rapidly.

• Quality attributes involved in the scenario: Scalability
• App status and context: The app has less than 100 users, they are happy with the application and it responds quickly to every request.
• Changes in the context: After a campaign the amount of users increase very fast.
• System reaction to the changes in the context: The app must be able to support these changes, without affect any user.

7. Scenario name: Personal data

• Quality attributes involved in the scenario: Security
• App status and context: The user want to add a payment method or modify/add personal information.
• Changes in the context: The stored information must be cipher and when its transmitted must follow the security protocols.
• System reaction to the changes in the context: The app should be able to process this request and guarantee the security of the information.

8. Scenario name: Normal schedule

• Quality attributes involved in the scenario: Availability
• App status and context:.The use is logged in the application.
• Changes in the context: The user wants to make an action.
• System reaction to the changes in the context: The systems make the user’s action and guarantees a disponibility of 99%.

9. Scenario name: Discount the products of an invoice in the inventory

• Quality attributes involved in the scenario: Interoperability
• App status and context: The user wants to cancel the products that he wants to take.
• Changes in the context: The user goes to the point of payment.
• System reaction to the changes in the context: The application gives the information to the user where to go, additionally the application must send this information to the accounting system. The database must be updated.

10. Scenario name: See the products in promotion

• Quality attributes involved in the scenario: Performance
• App status and context: The application is in the second frame, and offers the 3 more important options that a user can make.
• Changes in the context: The user wants to see the products in promotion. The application must show products in promotion in less than 0.2 seconds, after this, it allows to find basic information of some product (but must select it).
• System reaction to the changes in the context: When the user selects to see the products in promotion the application shows the products in an orderly manner. Each product must have a small description if the user wants to see it, the products appear with the current price and with the price in discount.