1271
Comment: Move to design related dicussion to Design/*
|
1321
Move to design related discussion to Design/*
|
Deletions are marked like this. | Additions are marked like this. |
Line 1: | Line 1: |
## page was renamed from FreedomBox/Requirements |
FreedomBox High Level Requirements
The Goal for generating an adequate requirements list is to be able to map to them existing tools that achieve the objective specified. Further, we can identify what changes/additions need to be made in order to support the requirement. This way, we get a clear list of work that needs to be done to accomplish the goals. It will be easier for individuals to just pick up a task and go with it from there. Finally, we need someone that takes on the role of figuring out if the proposed suite of tools can work together properly in one system (high-level system architect for the project).
All requirements must be written as:
- It must …
FreedomBox will only fulfill the vision if this requirement is met.
- It should …
- Every effort should be made to achieve this requirement.
- It may …
- If time, budget and effort permit these are highly desirable.
There is no such thing as a “hidden” requirement.
?Hardware requirements