search

CS2103-AY1819S2-T12-3 / main

MediTabs: Medicine Stock Taking Application
https://cs2103-ay1819s2-t12-3.github.io/main/
MIT License
2 stars 4 forks source link

Project Milestone v2.0 Project Requirements Documentation #10

Closed JonathanLeeWH closed 5 years ago

JonathanLeeWH commented 5 years ago

As required by CS2103T module AY1819S2

The following requirements are based on the project scope and constraints highlighted by CS2103T module requirements with some slight modifications to the phrasing hence, credits goes to: https://nus-cs2103-ay1819s2.github.io/cs2103-website/admin/project-constraints.html https://nus-cs2103-ay1819s2.github.io/cs2103-website/admin/project-scope.html

User constraints:

  1. The product should be mainly focus on catering towards users with higher preference towards typing commands rather than using other forms of interaction such as mouse. GUI interaction is allowed though main focus should be on command line interface inputs.

  2. The product should only be for a single user, in other words, any features for example switching of profiles for different users which involves multi user support should be avoided.

Data requirements:

  1. The data that is stored locally should be editable by user. In other words, expert users can open the file without using the application and edit it for his or her liking.

  2. The use of MySQL database management systems or similar database management systems are not allowed.

Environment requirements:

  1. The product should work on all platforms mainly Windows, Linux and MacOS platforms.

2.The product should not connect to any personal remote server though connecting of reliable public APIs like Google API are allowed but fallback system should be implemented such as a backup if connection to public APIs does not work during test.

Portability requirements:

  1. The software should not require any installer, in other words, should be able to run without installing any additional softwares. In this case, we have to use .jar when releasing the product.

Testability requirements:

  1. Avoid implementing features that are hard to test both manual and automated testing. In other words, avoid depending heavily on remote APIs as they may not work and usually out of our control.
  2. No audio related features due to project constraints. Possibly avoid features that uses sounds as indicators such as notification sounds.

Notes about project scope:

The target user should be very specific. In this case, we have decided on Pharmacists who usually in charge of medicine inventory/stock taking.

Optimised the product to suit the target user, in this case, Pharmacists in charge of medicine inventory and stock taking. In other words, add features that are applicable to them or unique to them and attractive to them. As the product will be graded on its ability to meet the needs of the target user (Pharmacist in charge of medicine inventory or stock taking) and the features should complement each other.

JonathanLeeWH commented 5 years ago

We have submitted this v2.0 Project Requirement as part of our v2.0 UserGuide documentation on LumiNUS. I will close this issue.