develop 2 textual use cases.

Abstract............................................................. 3

1. Introduction......................................................... 4

1.1. Purpose of System.............................................. 4

1.2. Scope of System................................................ 4

1.3. Development Methodology........................................ 5

1.4. Definitions, Acronyms, and Abbreviations....................... 5

1.5. Overview of Document........................................... 6

2. Project Plan......................................................... 7

2.1. Project Organization........................................... 7

2.2. Software and Hardware Requirements............................. 7

2.3. Work Breakdown................................................. 7

3. Requirements of System............................................... 10

3.1. Functional and Nonfunctional Requirements...................... 10

3.2. IDENTIFY Personas.............................................. 11

3.3. Use Case Diagram............................................... 12

The city of Flint, Michigan has a lot to offer its residents and visitors in the form of beautiful art spread all around its bustling streets. In an attempt to get more people out and exploring Flint, this document proposes a smartphone game that will prompt players to travel around Flint and collect pictures of the art monuments around the city in the form of a virtual scrapbook. Their progress will be tracked and rewarded in the form of in-game medals to show off to their friends and new accessories for their scrapbooks. This document will provide detailed documentation, modeling, and prototyping for easy implementation when the torch is passed onto the development team.

In this chapter we will introduce the motivation for building the system.

The purpose of the Flint Art Scrapbook is to get people of all ages out and exploring the town of Flint. It will provide people with an easy way to get to know the city of Flint through exploration of the various art pieces throughout the city. The Flint Art Scrapbook will allow users to document their adventures in Flint by encouraging photography and collecting pictures taken in a digital Scrapbook. As the user visits art pieces, the user’s scrapbooks will increasingly fill out with the pictures he takes. It will also give users the opportunity to meet each other while exploring. User’s who meet can add each other as friends to view and comment on each other’s Scrapbooks.

The Flint Art Scrapbook will be a digital collection of user captured photos of the different art pieces and monuments around Flint. It will be a cell phone application with video game elements. Android is the target operating system, but we may bring it to iOS at a later date. Each user’s scrapbook will include temporary preview pictures that will be replaced as the user visits art monuments and takes pictures of them, thus filling out their Scrapbook. At the moment we do not have any plans to include cities or towns outside of Flint.

People will be able to add friends as they meet others while out and about. Friends can view and comment on each other’s Scrapbooks and see what art they’ve visited around the city. To populate the pages we will first either find an existing database of art around flint and use this to populate the pages or perform a survey to get a general consensus of what the must-see art of Flint is. After the initial launch, we will allow people to submit their own art findings around the city to keep things fresh. We will have medals for various things such as making a certain amount of friends, seeing a certain number of monuments, etc. As you unlock medals you will unlock new things in the game like book designs, colors, etc.

When choosing an art monument to visit, the app will open the phone’s GPS app to give directions to a monument. We do not have any plans to have an on screen map to guide players (e.g. Pokemon GO). The app will also track the user’s location to keep track of distance traveled for medals. The user will have to create an account with their email address and will have the option of linking their social media accounts such as Instagram, Facebook and Twitter so that photos can be cross-posted to various sites.

There will also be special users that have the Administrator privilege, allowing them to accept regular users’ submissions to add art to the system, delete inappropriate pictures that people may upload, ban users for repeated offenses, and delete inactive accounts.

The top priority of Team X is simple and that is to do what we believe is best for the customer. Without the customer there is no Team X. So, when deciding on what decision to make, the question we will ask is: “How does this benefit the customer?” Also at Team X, we believe in a fast process and will make sure our product is done in an adequate amount of time. We are also believe in face to face communication with each other leading to more efficient cooperation.

The first thing we will do is gather all the information and requirements to determine what we will need to achieve our goals. After the initial information gathering is done we will begin development following the agile development principles which we feel are best practice. Our development process is a living and breathing approach where coding, testing, and implementation happen simultaneously. To accomplish this, the system will be built using as modules that as small and self sufficient as possible. What modules will be required and how they will be tested will be established before the code is written.

· User - The person that will download and use the Application

· Administrator - The person in charge of all support after deployment

· Mapping Application - The user’s preferred application for GPS mapping

· Smartphone Camera - The camera built in to the user’s device

· External Art Database - Where the application gets the bulk of its information

· Monument - Art exhibit or structure

· Scrapbook - The interface of the application, pictures will rest on an actual scrapbook

· Medals - Awards for finding art exhibits and taking pictures of them

What follows is a detailed outline of a path to successfully and efficiently completing and implementing the Flint Art Scrapbook system. Our team and each individual’s responsibility therein is outlined in section 3. The various requirements of the system and their accompanying use cases are outlined in section 4. Sections 5 and 6 cover technical details of the systems programmatic structure and that of it’s subsystems. Section 7 will cover system and project testing. The glossary can be found in section 8 and the appendix makes up section 9.

Client: Android based cell phone, Qualcomm Snapdragon 600 8974 CPU or better, 2GB RAM or more, 300MB free space or more, Internet connection

Infrastructure: 100TB storage, Intel Xeon E3-1225 v5 CPU or equivalent, 64GB RAM or more

Client: Android 5.0 or above

Infrastructure: MS SQL Lite, Windows Server 2019, IIS webserver for Windows, T1 fiber internet connection

The system we are proposing

· List art monuments on pages of the book

· Be able to search for a specific piece of art

· Let the user adjust their settings (i.e. book color, design, manage friends, etc.)

· Have the option to add friends and view their books/activity

· Use the user’s preferred maps app to get directions to a given monument

· Allow the user to take a picture of the art monument when they visit it and update their book with the taken picture

· Have badges/goals to work towards, like visit X monuments, etc. (Possibly have them unlock the different book designs)

· Have the user set up an account with their email/password and username for keeping track of their book

· Get data from a database or collect data to make one with information (descriptions, locations, preview pictures, etc.) on the art monuments

· Allow users to add art monuments themselves if they know a piece that is not yet in the system

· Have an Administrator role that is allowed to approve requests to add a monument to the database, delete inappropriate pictures, and ban players for breaking the rules

· List developer credits, etc. on back cover page

· Allow the users to set a favorite monument on their profile

· Track user location to see how far they’ve traveled for trophies/medals

· Give the option to share a photo taken of an art monument to preferred social media sites

· Be able to jump pages/sort art by a given criteria