Target release0.1
Epic

LL-1 - Getting issue details... STATUS

Document status
DRAFT
Document owner
Designer
Developers
QA

Note: Contributors can sign up by making a comment to this page requesting contribution to a role (i.e. software development, QA, project management, etc.).

Goals

  • Display the current day's leased mileage based upon hard coded lease information.
  • Utilize distributed software revision control to enable contributors
  • Create living documents that model various components (e.g. system, application, etc.) to clarify communication about the product and environment and help on-board contributors.

Background and strategic fit

In March of 2016, Ralph A. Navarro Jr. wrote a LeaseLine application to help his wife, Joy, predict if her car's usage was at risk of going over the allowed mileage usage on her lease.  The application was submitted to a private git repository.  This project is to revive the original project within full SDLC processes and tools for the purposes of tracking work and making it easier to on-board contributors.  The initial release of the application will have the same minimal functionality while laying the groundwork for adding customer identifiable features.

Assumptions

  • Hard coded simulated lease information will be utilized by the application on this first draft revision.
  • This Lease Line page in Confluence will be used for knowledge management.
  • Project Management (i.e. issues, feature specifications) will be done in the Lease Line project in Jira.
  • Private Git Server will be used for source control.

Requirements

#TitleUser StoryImportanceNotes
1
2    

User interaction and design

Questions

Below is a list of questions to be addressed as a result of this requirements document:

QuestionOutcome

Not Doing

  • Updating lease information will be addressed in a future release.
  • Online user registration will be addressed in a future release.
  • Storing lease information online will be addressed in a future release.
  • Adding advertisements will be discussed in future release (i.e. implement or not).
  • Capturing user data will be discussed in future release (i.e. legality, how much, permission, etc.).