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:

There is no such thing as a “hidden” requirement.


Information

Support

Work Space

Reports

Promote

Overview

Hardware

Live Help

Where To Start

Translate

Calls

Talks

Features

Vision

Q&A

Design

To Do

Metrics

Press

Download

Manual

Use cases

Code

Contributors

Releases

Blog

HELP & DISCUSSIONS: Mailing List - #freedombox irc.debian.org | CONTACT Foundation | JOIN Alioth Projects, GitHub

Next call: Saturday, December 9th at 14:00 UTC

Latest news: Stable FreedomBox images - 2017-08-05

This page is copyright its contributors and is licensed under the Creative Commons Attribution-ShareAlike 4.0 International (CC BY-SA 4.0) license.


CategoryFreedomBox