Project Delivery 2

Really about this project, we take so serious and we try to do a lot of things but in this partial was a little difficult because we have a lot of things to do, so we have to do it simple but efficiently that is why we just answer the questions about the project, we did an interview with the head coach of the team of League of Legends and we decide to add this audio to the blog and maybe transcript the important parts on it.

so here’s the question first, later the interview and some changes that we decide to make in the use cases.

What did you learn about the project with these interviews?

At first, our idea was to have a complex web application with multiple interactions by every user that uses it. But when doing the interview we discovered that the stakeholders wanted more simple features but more complex analysis of data, so we changed the way of modeling the software into a much more easy and intuitive interactions with more complex process of data.

The regular player can check his or her stats at any time and make leagues to make small competitions between friends or other people. Those are the only interactions because for the stakeholders it is only important to have a good analysis of data so decisions can me made to recruit new representative players and to analyze the ones that are part of the team already.

From the interviews we also learnt that our focus need to be on the web application and later on the mobile app. This is because our main stakeholders which are the headhunters and administrators made very clear that the project needs to be done in a web application first so when the mobile app is done, the final clients or players will not have a problem using it and its database. Also, in that time the web application is going to be more structured and polished to be able to process big data.

Photo by Arielle Lilley

What did you learn about the process of interviewing?

Before starting the interview, we had our questions ready, and in the process of making them we tried to focus on finding out the necessity of our potential stakeholder. In the process of doing the interview we also learnt that some new questions needed to be asked based of the previous answer.

It was not that hard to understand what the stakeholder wanted because of the experience the whole team has in that area. The real challenge was to even though the stakeholder did not have a big necessity of the case, we needed to be persuasive to make the necessity real for the stakeholder.

Photo by Learn – Stock Photo

What do your use cases look like now? Did you have to remove some, change some, add some?

We removed the client stakeholder because now everyone is a player at first, with the main privileges so there was no reason to have a client stakeholder in place. We also changed the administrator to have now two more functions which are the ability to delete leagues and the permission to ban players. The term “ban” refers to block or eliminate the player, it is used for control and security. 

Design Museum, London.

If you have any work on class diagrams or database ER diagrams, include those as well.

Use cases

Diagram

Publicado por Masharelli

-Estudiante del Tecnologico de Monterrey -Ingenieria en Sistemas Computacionales -Geek -Catador de Tacos

Deja un comentario

Introduce tus datos o haz clic en un icono para iniciar sesión:

Logo de WordPress.com

Estás comentando usando tu cuenta de WordPress.com. Cerrar sesión /  Cambiar )

Google photo

Estás comentando usando tu cuenta de Google. Cerrar sesión /  Cambiar )

Imagen de Twitter

Estás comentando usando tu cuenta de Twitter. Cerrar sesión /  Cambiar )

Foto de Facebook

Estás comentando usando tu cuenta de Facebook. Cerrar sesión /  Cambiar )

Conectando a %s

Crea tu página web en WordPress.com
Empieza ahora
A %d blogueros les gusta esto: