Software Architecture: Project Scope and Goals

REQUIRED Information is in the attachments

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

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.

For this assessment, consider the scope and the stakeholders for Fantasy Games.

Preparation

To begin, read the following Fantasy Games scenario:

Fantasy Games Scenario

The CIO of Fantasy Games has hired your consulting company to design Fantasy's software architecture. The company is adding a new game titled Asteroids to its catalog and intends to build a multiplayer environment for this new game. You must add an entirely new subcomponent to their existing Web community in order to support this game, and you must create a software architecture proposal for this new subsystem. As part of your proposal, Fantasy asks you to develop a single-player, working prototype of the game itself.

The Fantasy Games community currently has 1.2 million users, and they expect that user activity will grow tremendously with the addition of this new environment. Your design must be flexible enough to accommodate the current number of users plus all anticipated and unanticipated future growth.

The Asteroids Web component, or subsystem, for this game should include many of the same features found on other popular online gaming sites such as chat, instant messaging, user-rank functionality, and high-score display. Although Fantasy Games currently has a few other multiplayer games available within their overall community, they would like this project to set the new standards for how similar subsystems will be added in the future.

For this assessment, consider these four Fantasy Games stakeholders:

• An avid online gamer.
• The Vice President of Operations.
• The Lead Software Developer.
• The Lead Software Architect.

Consider what type of questions and facts you would ask of these stakeholders when developing the scope of the project. It will be up to you to develop all the Fantasy Games user requirements, business needs, facts, and assumptions to drive your architecture design. This assessment will include writing and using Visio to create a diagram.

In order to prepare for your assessment, view the following media pieces (linked in the Resources under the Required Resources heading).

• Project Stakeholders.
• Conversation About Goals.
• Conversation about Constraints and Scope.

Directions

Create a 3–4-page professional paper in which you complete the following:

Create a Requirements and Scope document for this development. Complete the following:

1. Determine the types of questions you would need to ask the stakeholders.
2. Determine the architectural scope of the project.
3. Create a UML use case diagram of the project that presents a high-level picture of the system's boundaries and adjacent external entities. Use Visio to complete this diagram.
4. Determine constraints on the project.
5. Determine the team necessary to work on this project and clarify the roles of each team member.