ASSESSMENT:
Software Architecture: Scope And Goals
Overview
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.
By successfully completing this assessment, you will demonstrate your proficiency in the following course competencies and assessment criteria:
Competency 1: Define business problems that can be solved using software architecture concepts and standards.
Define the architectural scope of the project.
Competency 2: Explain fundamental concepts and principles of software architecture.
Define the architectural principles for the project.
Competency 3: Create a software and data architecture for an organization.
Create a UMLUse Case diagram.
Competency 4: Apply collaboration strategies in the software architecture process.
Create stakeholder questions. Explain project constraints.
Describe team member roles.
Competency 5: Communicate effectively.
Communicate in a manner that is scholarly, professional, and consistent with expectations for members of professional communities
Context
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.
Questions to Consider
To deepen your understanding, you are encouraged to consider the questions below and discuss them with a fellow learner, a work associate, an interested friend, or a member of the business community.
How have you determined project scope in your current profession?
What constraints should a software architect consider to determine project goals?
Resources
Required Resources
The following resources are required to complete the assessment.
Capella Multimedia
Click the links provided below to view the following multimedia pieces:
Project Stakeholders | T ranscript- http://media.capella.edu/CourseMedia/IT3345/ProjectStakeholders/projectStakeholders.asp
Conversation About Goals | T ranscript- http://media.capella.edu/CourseMedia/IT4710/convoGoals/wrapper.asp
Conversation About Constraints and Scope | T ranscript- http://media.capella.edu/CourseMedia/IT4710/convoScope/wrapper.asp
Suggested Resources
The following optional resources are provided to support you in completing the assessment or to provide a helpful context. For additional resources, refer to the Research Resources and Supplemental Resources in the left navigation menu of your courseroom.
Course Library Guide
A Capella University library guide has been created specifically for your use in this course. You are encouraged to refer to the resources in the I TFP3345 - Fundamentals of Software
Architecture Library Guide to help direct your research.
Pluralsight Videos
Instructional videos from Pluralsight are provided for your use in this course. You may access the videos via the Pluralsight resources in this assessment.
Internet Resources
Access the following resources by clicking the links provided. Please note that URLs change frequently. Permissions for the following links have been either granted or deemed appropriate for educational use at the time of course publication.
Chitnis, M., Tiwari, P., & Ananthamurthy, L. (2005). T utorials: Discover UML. Retrieved from http://www.developer.com/design/article.php/3500181
Miller, R. (2007). P ractical UML: A handson introduction for developers. Retrieved from http://dn.codegear.com/article/31863
Pay special attention to the part on Class Diagrams.
Bookstore Resources
The resources listed below are relevant to the topics and assessments in this course and are not required. Unless noted otherwise, these materials are available for purchase from the C apella
University Bookstore. When searching the bookstore, be sure to look for the Course ID with the specific -FP (FlexPath) course designation.
Qian, K., Fu, X., Tao, L., Xu, C., & DiazHerrera, J. L. (2010). Software architecture and design illuminated. Sudbury, Mass: Jones and Bartlett Publishers. ISBN: 9780763754204.
Video Resource: Visio 2013 Fundamentals For Bus.
Click the linked title next to the arrow in the heading above to access an optional Pluralsight video titled Introduction to UML.
For help using Pluralsight, see P luralsight User Guide and Technical Support.
Assessment Instructions
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, userrank functionality, and highscore 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-4page 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 highlevel 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.