objectiF RM distinguishes between database administrators and project administrators.
A database administrator user can create projects and organizations and open them. He does not have to be assigned to a project as a user to configure things like the Task Manager, create employees, or open the Settings window.
A user of the project administrator type is assigned to a project and can open it, define permissions, and so on.
Availability determines how many hours the user is available for a project or activity over a certain period of time.
Relative availability is the percentage of available working time that the user has available for the project or activity. The percentage is given as a percentage.
When you create a new project with a template, the backlogs are created automatically. They are named with the domain name of your choice according to the rule Requirements <Domain name> Backlog and Use cases <Domain name> Backlog. In the tutorial project, the domain name is “Domain”.
The collection of all requirements of a domain is called a domain backlog.
The term element is also used as a synonym for entity.
An Epic is a refinement of a feature and should therefore be regarded as the more specific requirement. An Epic is in the range of a two-digit number of person days and is still too extensive for a typical sprint of 1-2 weeks. They need further refinement. The next smaller level are the user stories.
External documents are all files that are dragged and dropped into a directory.
We call the requirements at the highest professional level, which correspond to a solution component – i.e. a clearly definable characteristic of a system – features. A feature is so extensive that it must be further refined.
For most elements, an ID is automatically generated when you create them. By default, the ID consists of the short identifier of the project – U (for use case) – sequential number. You can also define your own numbering scheme for a stereotype.
Packages are structural elements within a project. They contain various project elements, such as requirements, test cases, goals, diagrams, etc., and can also be viewed as folders.
The user stories gained by refining features and Epics, which are intended for realization in a release, are stored in a central release backlog.
A user story is a requirement with a scope of approx. 1-5 person days.