Skip to content

Latest commit

 

History

History
438 lines (215 loc) · 18.1 KB

sprintDoc.md

File metadata and controls

438 lines (215 loc) · 18.1 KB
Raw

#Sprint Documentation

Below are links to respective sprint directories, which contain all documents relevant to that sprint. Each sprint also has a sprint document, specifically over viewing that sprint and the process of its completion. Further, there is a log specifically dedicated to the original break down of the tasks, and recording any change of task delegation.

General Workflow for each sprint

Each sprint can be broken down into a few parts:

  • a sprint meeting, which allows for discussion of upcoming tasks, organization of questions and requirements for the sprint

  • development, which includes all formal task completion and submission to the project repository

  • documentation, which includes documenting the completion of each task, summary and description where appropriate, and organizing the sprint document to provide easy access to the TAs and Professor to relevant information and code

##Link to Repository on github

Group 7 Repo

##Sprint 1

###Task breakdown

  • Create wiki page link

    Member: Jared

    • Create general wiki page for the project, which details at a high level the sprints, requirements, and work flow

  • Sprint Documentation

    Member: Jared

    • Sprint document created in this commit

    • Many more commits related to this task, as group members updated the sprint document as they worked throughout the sprint

  • Set up deployment

    Member: Zach

    link to example page for proof of successful deployment

  • Data base creation

    relevant commit

    This page https://mizzou.tech/view.php shows a successful query to our database to show that it exists and has some data.

    Just for proof, the code for that page can be found here:

    link

    The page shows a valid query that is run when the page is loaded, verifying and displaying our data.

    Further, here is a link to the script that was used to create our tables:

    link

    And here is a link to a png file showing the tables in mysql:

    link

    Member: Geoff

  • ERD finish

    commit link

    link to ERD diagram for reference

    Member: Geoff

    Reviewer: Andrew

  • organize repo

    Member: Jared

    • Created some new folders to organize the repo.

    • Created directory for requirements and related docs

    • created directory for currents print

      commits:

      commit 1

      commit 2

  • drill down into UI functionality

    Began initial page design. Outlined each page in php file with general flow and text descriptions for each page that display when viewing the page. Mostly an outline for each page for implementation when the time comes.

    Members: Liz

  • create page design document for details on current design decisions

    commit for adding page desing document

    adding some small display functionality for searches and displaying user's manifests

    Link to document itself

  • begin thinking about UNIT tests?

    Member: Andrew

    Unit Testing Doc

    Commit

  • organize links to various documents needed for the sprint

    Jared

##Sprint 2

link to sprint 2 wikipage detailing our sprint2 meeting.

###Task discussion from sprint meeting:

  • Requirements analysis fixes

  • Have all insert, update, delete queries (should be separate files in directory called DML)

  • stub calls for all interactive UI elements

    • outline our UI skeleton so to speak; not actual implementation just ensure the plan for its eventual implementation

  • Begin UI elements for organizations

    • document and explain how UI elements will be organized for pages

  • Management of users/roles

    • Detail what each user can do based on role

  • link to sprint 1 information

    • finish requirements analysis

In case there is any confusion about where each piece of the sprint is present, here is a list, taken from the sprint document itself, of what is being asked for and where the work associated is within the task list. There is a level of interpretation, so this is an attempt to demonstrate how we interpreted the requirements and tried to fill them to the best of our ability.

###Breakdown of Sprint requirements and their respective tasks for clarity

  • Have all insert, update and delete queries required for your application written. They should be separate files in your github REPO under a directory called "DML"

    We have tasks for each query below,

    We have a task dedicated to creating the directory asked for.

  • Stub calls for all elements of UI

    According to what we were told in class when we asked, this task equivalent for this year's project is to simply create the skeleton for each page and have a place for where the eventual UI elements will go. We have a task for that, called stub calls.

  • Begin UI elements for organization

    This task seems very similar to what we were told to do with stub calls, however, we still have a separate task for it and details with it, based on our interpretation on what might be different from stub calls

  • Management of Users / Roles

    Task for this as well, manage users/roles

  • Link to Sprint 1 information

    I am not sure what sprint 1 information was exactly asked for, but we have a task for fixing our requirements analysis and we also have a link to the feedback that we were given from sprint 1, converted to a markdown format for reference.

    We also have an area detailing tasks that we addressed in fixing sprint 1 issues that we were given feedback on, titled backlog for sprint 2.

###Sprint 2 Tasks

###Sprint 2 Backlog From previous sprints:

This section is dedicated to the tasks that were inherited from the previous sprint. These tasks were addressed this sprint in order to maintain the project and address the areas that were lacking from the preceding sprints.

####Tasks

##Sprint 3

###Sprint Kickoff meeting:

link to wikipage for our sprint 3 meeting

###Task List

###Sprint 3 Backlog Tasks

  • Fix testing based on feedback from sprint 2 (see tasks)

##Sprint 4

meeting details

###Tasks for sprint 4

  • Need a way to create account without logging in (Geoff)

Link commit 1

Link commit 2

  • View manifest/edit manifest

  • begin feature Download files after they have been uploaded (Geoff) * Currently in progress, although not working in it's entirety * commit (geoffbranch commit)

  • add feature Generate a manifest file/upload manifest file (Liz branch)

    • commit

    • commit

    • Create form, include searchable terms

    • Write to file to create basic manifest in JSON format

  • upload manifest and dataset to server (Liz)

    • commit

    • Insert files into tables

  • search (Jared)

  • Finish User Documentation (Jared)

Link to user documentation

  • Finish Up testing document (Jared)

link to testing document

link to testing workflow (this is the actual tests)

###Sprint 4 backlog tasks:

  • Fix issues from sprint 3 feedback

  • Account information page (Part of UI and Query tasks, but just to be clear so we don't forget)(Andrew)