Request Management System - Features

Global

Rich Model
The model contains all important entties of the IT project world.
Flexible Relationships
Almost all entities can be be linked together with typed relationships.
High Security
Beside the role based authorization all entities may have access control lists (ACL) to have a fine grained control over the rights to view or change those entities.
User Interface
The user interface can be switched between different locales. The desktop is web based and organized in three columns - the width of those columns can be changed. The content is displayed in cards which can be moved on the desktop. The style of the desktop and the cards can be changed, also an individual font size can be selected. Every feature except the locale can be set and stored individually.

Environment

Projects and Systems
The environment of the Tideland Request Management System is defined through projects and systems. Each one can be defined in multiple versions.
Persons, Users and Customers
The application manages persons like all other entities. The person model is specified by the RFC 2426 vCard standard. Users and customers are own entities defining accounts for application users and external clients. Through the relationship management a person can be both, user and customer.
Groups
Groups - again linked to each other in flexible ways through the relationship management - help to organize team as well as all other entities.

Requests

Use Cases
Uses cases describe on a high level how users want to handle an application or hardware system. This description is the base for the definition of requirements.
Requirements
As seen above, requirements can be defined based on use cases. The relationship management is used to add traces from these use cases to the requirements. But requirements can also be added without any dependency to a use case. The information stored inside a requirement are based on snowcards (number, type, source, description, trigger, priority, dependency, conflicts and more).
Issues
If an application or a system is allready in use and a problem occures an issue with all needed information to provide a solution can be opened.
Fit Criteria
Fit criterias can - and should - also be added and linked to requirements and issues.
Tasks
Up until now the users of the system have nothing to do. Only the responsible project manager should work. He should define the tasks to fulfill the requirements and issues and assign them to his team members. Based on an own weighting of each task and the load of the team members an optimal disposition can be found.

Administration

Authentication
The user management handles login statistics, counting of illegal login tries and account locking. Users can be members of several groups.
Authorization
The authorization is based on flexible combinations of rights and roles with parameters and time limitations for each user.
System Information
The framework provides classes for the monitoring of objects and processing times. All can be displayed to have a better view on what your application is doing.

Back ...