Staff is going to be a tool to monitor and analyse a company's staff structure by storing skills and relationships of staff members and providing visualizations and queries on that.
As a staff manager
I want my basic data to come from a configuration LDAP service
to make use of this existing database and to avoid managing facts in two places.
Requirements
at least email address, first- and last name should be used
LDAP configuration should stored in a properties file at /etc/staff/application.properties to make it manageable via provisioning
Remarks
Spring LDAP sounds like a good choice for the implementation.
As a staff member
I want to see a workplace location on a colleague's profile
to be able to find that colleague within the office.
As a staff manager
I want staff members to be able to add a workspace location to their profiles
in order to have a self organizing workplace location database.
Requirements
the location should be given as a simple string
RESTful POST and PUT interfaces to add or update a workspace location is sufficient
As a staff manager
I want members to be able to add skills to their profile data to their own profiles
to have a self organizing and therefore scaling skill database.
Requirements
skills should be a simple list of keywords to enable members to make relevant skills that I have not thought of
RESTful POST and DELETE interface + display of skills in the existing profile (see #1) is sufficient