Sprint 1 User Stories

Evan Vander Hoeven

As a programmer, we need to setup a minimal Android Studio project so we have a good starting point.

Hours: 2

Acceptance Criteria:

• there is a .gitignore
• the app can be built and run on a tablet, even if the app does nothing

As a professor, I need a list of every user story and acceptance criteria in a sprint log connected to each user for the first sprint so that the professor can print and read the information easily.

Hours: 1

Acceptance criteria:

• All of the user stories for the first sprint are listed
• All of the user stories for the first sprint are grouped by developer
• All of the user stories have their acceptance criteria listed.

As law abiding citizen, I need to make sure that we are aware of all potential legal issues that we might encounter in developing a peer-to-peer chat application so we don't break any laws.

Hours: 13

Acceptance criteria:

• have a list of relevant laws documented in the wiki
• the documentation must include links to the laws, if applicable.
• the research must include countries other than the united states.
  • country related research must create a whitelist of countries where this app can be released.
  • the whitelist must research applicability in the United States, Canada, and the European Union
• the documentation must consider if not include a terms of service and a privacy policy

As a programmer, I need a framework for communicating with WI-FI direct so that we can figure out P2P communication between devices.

Hours: 21

Acceptance criteria:

• documentation on the wiki, including links to sources, must be written
• the documentation must include:
  • how to interact with wi-fi direct
  • the limitations of wi-fi direct
  • any device / hardware limitations
  • data formats for communication
• a minimum viable prototype, demonstrating that we can send signals peer to peer, between two devices.

Nicholas La Belle

As a programmer, I need to research if there is a standard format for android chat applications, and how our app can use it to build the actual GUI faster.

Hours: 21

Acceptance criteria:

• a wiki page describing a android standard chat system, if any, including links to the original documentation
• the documentation shall include any relevant data models used by chat applications, and list pros and cons for each type of data model
• the documentation shall include user experience design flaws encountered in other popular chat applications, so that we can avoid potential pitfalls

As a programmer, I need to research how we can integrate with other Android applications, such as Android photos, to allow us to expand functionality.

Hours: 13

Acceptance criteria:

• have a list of potential applications we can integrate with, elaborating on how we would integrate with each
• a page is in the wiki describing how we can integrate our app with the android OS, including links to the documentation where the research was gathered.

Nick Zolondek

As a programmer, we need a UI design prototype so we can agree on how the app will look and feel before implementation

Hours: 8

Acceptance Criteria:

• the entire group has weighed in on the design and agrees
• the design has a consistent look and feel
• the design encompasses the entire known scope of the app
• The design prototype must either be placed in the wiki, or a file format must be included in a separate branch where anyone can see it.

As a programmer, I need a set of style standards to keep code neat and well documented

Hours: 2

Acceptance Criteria:

• There is a page on the repository wiki with a style guide
• All style criteria are agreed upon by members of the project

As a man who lives for the aesthetic, I need an app icon so that our app looks good from the homescreen

Acceptance Criteria:

• Everyone needs to agree on design.
• When app is built through Android Studio the app's default icon should be replaced with the new icon

As an imperfect programmer we need a java linter configured and added to the project to enforce style guidlines so we make fewer silly style mistakes

Hours: 21 acceptance criteria:

• a linter configuration file is added to the android studio project, and can be added to each member's project
• the linter shall enforce inline code documentation
• the linter shall enforce all code styles on our wiki
• the assignee must demonstrate that the linter is able to catch mistakes by creating a temporary bad file to show that the linter works. (This bad file must be deleted before merging with master)

Austin Scott

As a programmer, I need the user stories imported into the github repository as issues so we can better collaborate online.

Hours: 2

Acceptance Criteria

• A framework which accommodates the requirements of the Software Engineering Practicum course is in place
• the github respository has tools which will enable us to rapidly create new user stores / issues as they are discovered
• a series of custom labels are created, which include a description, and are understood by the entire group

As a QA tester, I want to research a testing framework so that the entire team can work together to test the app

Hours: 21

Acceptance Criteria:

• documentation must include how to write a test, including style standards
• links to the original documentation must be included in the wiki
• any tools, extensions, or dependencies needed for the testing framework shall be installed into Android Studio, or a guide detailing how to install them must be written.
• a demonstration test must be written proving that the testing framework is working

As a programmer, we need a method of generating a GUID for each installation, so the app can connect to a specific user.

Hours: 8

Acceptance Criteria:

• The app must be able to generate a identifier that is universally unique.
• The generation must not only be based on system time.
• Unit tests must be written for all functions that can be tested.