The following user stories are completed according to acceptance criteria:
- Application asks user if they want to delete a reference.
- Application deletes the reference from db.
- Application asks user if they want to put all references into a file.
- All data goes from db to a .bib file.
- Application asks user if they want to search references with a tag.
- Application fetches the references by tag if found.
The completion of user stories is verified through extensive unit testing across the program. The user story 'As a user I can add tags to references' is also system tested according to acceptance criteria. The program is continuosly integrated. Program releases contain a high unit testing coverage with fully passing unit and system tests.
The following user stories are completed according to acceptance criteria:
- Application asks user if they want to put all references into a file.
- All data goes from db to a .bib file
- Printing to terminal prints in a human readable form, rather than BibTeX.
- Application has an option for inputting a doi references.
- Application fetches a reference by doi and saves it to the database.
- Inproceedings references are saved in inproceedings form.
- Phdthesis references are save in phdthesis form.
The completion of user stories is verified through extensive unit testing across the program, and by system testing each added story according to acceptance criteria. The program is continuosly integrated. Program releases contain a high unit testing coverage with fully passing unit and system tests.
The following user stories are completed according to acceptance criteria:
- Inputted data is saved locally.
- Program writes and reads into a SQLite database.
- Application asks user for a reference type for input.
- Book references are saved in book type bibtex format.
- Application form has optional fields, which are clearly annotated.
- A reference with invalid mandatory fields is not accepted.
- Optional fields can be left empty.
The completion of user stories is verified through extensive unit testing across the program, and system testing is begun during this sprint. The program is continuosly integrated, with test coverage and passing kept high throughout development.
The following user stories are completed according to acceptance criteria:
- Application asks user if they want to input data.
- Input form asks user for values required for an article reference.
- Inputted data is kept as long as the program is open.
- Application asks user if they want to print all references inputted.
- References are printed to terminal in BibTeX form.
The completion of user stories is verified through unit testing across non-IO layers of the program. In addition, the program is continuosly integrated, with test coverage and passing kept high throughout development.