[
Software application, documentation, and testing for a fictional home rental company
Explore the docs »
Table of Contents
 |
 |
 |
Given a system requirements by the fictional OT-Bnb (air-bnb like company) we were given the task to design, implement, document and deliver a software product. All phases followed the Kanban development philosophy and practices.
Throughout this project we:
- continuously maintained test suites as requirements and quality control
- pair programed all code
- used the simplest possible solution to every problem
- continuously redesigned and re-architected
- automated testing and integration
- frequently or continuously released the software Every two weeks (or so) to deliver concrete evidence of our team’s progress as required by project phases.
This project can be broken down into the following phases:
phases
- Phase #1 Front End Requirements: Read the software requirements provided, correct any constraints in the documentation with the client, create a plan of the system from the given requirements, and finally create a set of black box tests from the requirements.
- Phase #2 Front End Rapid Prototype: Create the system's prototype using the plan created in phase #1. Find any misconceptions made in the first phase and correct them with future implementations in mind. Create and document the system's architecture.
- Phase #3 Front End Requirements Testing: Use the black box tests created in the first phase to autonomously test the prototype with bash scripts. Correct any more miscomseptions made in the previous phases for both tests and program functionality.
- Phase #4 Unit Testing: Using JUnit, create unit tests for two methods within the application, these test implement decision testing and statement coverage. Create a report for the tests.
- Phase #5 Integration and Delivery: With the provided backend, hook it up to the create front-end and test if it works as client specified.
To get started, simply pull the project from the repo and open it up using your preferred IDE. It's that simple!
File structure info here ...
Show usage?
For more examples, please refer to the Documentation
- Phase 1
- Phase 2
- Phase 3
- Nested Feature
- Phase 4
- Phase 5
See the open issues for a full list of proposed features.
Distributed under the GNU License. See LICENSE for more information.
Project Link: https://github.com/powersda/KMDLLC
David Powers: https://github.com/powersda
Mathew Migliore: https://github.com/Key-Locker
Kevin Romero: https://github.com/KevinCRR