Software Architecture (3 Parts)

REQUIRED Information for each part is in the attachments

All parts must include a Reference page with in-text citations and be double spaced Arial 12 pt. Microsoft Visio is required for the UML Diagragms


Part 1

Software Architecture: Scope And Goals


Design the software architecture for a new game. Create a requirements and scope document and consider the interests of various stakeholders in your plans.The hardest part of any system is to develop a scope of the system. The scope of the process is essentially looking at the overview of a project. If the scope isn’t followed, “scope creep” can occur. Scope creep occurs when additional requirements are added to the original project plan. Determining scope is mainly about negotiation with your customer. When determining project scope, it is necessary to consider constraints. Two common constraints are budget and schedule.

The software architect also needs to determine which stakeholders need to be selected and engaged while the architecture is being developed. Stakeholders are the interested parties in a software architecture plan. Since the architecture is ultimately designed to meet stakeholder needs, it is essential to gather their input throughout the construction process. The baseline architecture is a set of requirements agreed upon by the software architect and customers or stakeholders.

Part 2

User Stories


The Required User Story Template is included in The attachments


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.

Part 3

Data Modeling

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.



Leave a Comment

Your email address will not be published. Required fields are marked *