You are currently viewing Fundamentals of Software Architecture: Fantasy Games Scope and Requirements

Fundamentals of Software Architecture: Fantasy Games Scope and Requirements

Scope and Requirements

Architectural Scope

One of the first steps in the process is to identify the architectural scope. According to Rozanski & Woods, the scope definition should define both the broad functional aspects, and the external interfaces of the new systems. The scope should also identify any systems that will be decommissioned or modified during the integration process, and all data that will be utilized by the new system. (Rozanski & Woods, 2005)

Fantasy Games is looking to update their outdated website in order to provide an improved online experience for their clientele. Game technology has advanced tremendously since the original site was launched 10 years ago, and gamers are demanding advanced features that are currently unavailable at Fantasy Games. After much deliberation, Fantasy Games has decided that the updated system will provide online technical support, gamer-to-gamer communications, online gaming, and an improved purchasing process.


Common requirements throughout the site include compliance with IEEE Standard 1471, security features to protect customer and product data, and multi-language support. Technical support will require an extensive searchable database of game information including FAQ’s and technical information to improve or repair game play. Gamer-to-gamer communications will need to allow players to communicate with each other via instant messaging, forums, and blogs. For online gaming, a secure login process is required for subscribers along with additional server space and bandwidth to handle increased demands. The improved purchasing process will utilize an outside CC validation system with additional in-house security to protect sensitive information.

Business Goals

  1. Create an online community where gamers can get technical support and communicate with other players.
  2. Establish online gaming using several Fantasy Games titles and genres.
  3. Establish a secure, easy to use storefront.
  4. Comply with IEEE standard 1471.

Context Diagram

Architectural Principles

“An architectural principle is a fundamental statement of belief, approach, or intent...” (Rozanski & Woods, 2005). Good principles are constructive, well reasoned, articulate, testable, and significant to the case at hand. Principles for this project include:

  • Online game playing will be monitored 24/7.
  • Forums and blogs will be regularly monitored for content. IM communications are available through 3rd party software, and will not be monitored by Fantasy Games.
  • Customer information will be securely maintained in one place for easy updating.
  • Fantasy Games business information will be maintained in a separate location in order to maintain security.
  • Technical support and FAQ’s for all games will be available through the website.
  • E-Commerce will expand to support the sale of subscriptions to online games, hard-copy games, and downloadable games.
  • Fantasy Games will continue to provide a secure, family oriented, gaming experience.

Architectural Constraints

Constraints are the “standards, guidelines, strategies, and policies” that limit architectural choices. (Rozanski & Woods, 2005) Constraints for this project include:

  • Architecture must comply with the standards set forth in IEEE 1471.
  • The website must perform with 99.9% uptime.
  • The website must provide a gaming experience that is fun, safe, and secure.
    • 24/7 game site monitoring
    • SSL will be used to protect sensitive data.
  • The website must be secure for online purchasing.
  • The new website must be compatible with existing framework to allow for simple migration from one system to the other.

Architectural Team

The architectural team will consist of the following members:

  • Lorrie Syms, Software Architect – Responsible for overseeing the project from start to finish in compliance with goals set forth by Fantasy Games.
  • Robert Walling, CEO and Jack Burns, CIO – Chief acquirers responsible for setting goals and assisting SA in defining architecture.
  • Dave Erwert, Fantasy Games Legal Department, is the Assessor and is responsible for guaranteeing compliance with legal regulations and standards compliance.
  • Dawn Sullivan, Tracy Posey, and Ken Murray are the developers in charge of constructing the system according to the specifications.
  • Kye Phillips and Jody Jones are user/testers who will assess the system for usability and performance.
  • Kathy Strenge, Sharon Paschke, and Louise Johnson will provide maintenance, support, and administrative services once the system is up and running.


Fantasy Games must keep scope and requirements in mind while creating the software architecture for their new interactive website. Business goals, architectural principles, and architectural constraints will all play a role in creating an architecture that will meet the needs of the stakeholders. With this section, a path to follow has been set, the main players have been identified, and the architecture is ready to move forward to the next step.


Rozanski, N., & Woods, E. (2005). Software Systems Architecture. Upper Saddle River: Pearson Education, Inc.