Apply the Scrum process to create user stories for a given scenario, including those for chat, instant messaging, user rank, and high-score functionality. In addition, create an architectural style to complete the software architecture.
Authors Nick Rozanski and Eoin Woods (2011) state, "An architectural scenario is a crisp, concise description of a situation that the system is likely to face in its production environment, along with a definition of the response required by the system" (p. 10). In UML, use cases and sequence diagrams are used to illustrate the textual scenario as a picture. You will explore the textual and graphical ways to use scenarios in a software architecture. Also, the Scrum process uses user stories; these provide a strong template in which to document the user scenarios.
A software architect explores typical architectural styles and patterns for complex enterprise software systems. Common existing architectural styles and patterns represent best practices for the design of complex software systems. Software architects should review existing architectural styles and patterns so they do not to start from the beginning each time they create a new system. Software architects should consider using common styles and patterns when applicable to the current situation. If the existing architectural style does not fit, the architect must create his or her own style.
Create a data model for the Fantasy Games scenario.
Developing a data model is an important part of the software-development process. A data model is a representation of the data you are using in your application. For example, all applications require users; therefore, you will develop a user object. Once the software architect knows the data model, the architect is better able to develop the necessary software. As a software architect, you will find yourself developing data models for each system you create.