FEA05-Log-Management-System 1.0
Feature ID | e.g. FT0101 |
Subsystem the feature is part of | e.g. billing |
Responsible person | e.g. Mauri Myyrä |
Status | e.g. approved |
Description
Explain what the feature means and what can be done with it
Sed non nisi id ligula interdum mattis. Fusce vel ullamcorper nunc. Nulla pharetra dui ut enim semper semper. Aenean ut leo tortor. Fusce felis nibh, malesuada vitae nibh at, rhoncus feugiat leo. Nam vehicula vitae ligula vitae condimentum. Ut maximus metus nec lorem ultrices elementum.
Restrictions, requirements and use cases related to this feature
All relevant issues related to or contributing to the definition of the feature are gathered here
Use Case 1 | |
Use Case 2 | |
Requirement ReqID | |
Requirement ReqID |
Preliminary user stories
- US127 As a service provider, I would like to collect a usage log related to the use of the service, based on which possible abuses can be determined (Issue #69)
- US145 User ID, time, performed function, possible status are saved in the usage log" (Issue #88)
- US132 As a data protection officer, I would like to check, if necessary, the actions taken by an individual in the user log at a certain point in time (default 1h) (Issue #74)
- US146 As a service administrator, I want to be able to search and visualize the collected usage log" (Issue #89)
*These should be transferred to issue descriptions as soon as possible
User interface mock-up
Add a picture or a link here. The mock-up should be essentially related to the feature/functionality.
Testing / possible acceptance criteria
Write down some notions for testing
Testcase | Test source | Responsible |
---|---|---|
Testcase 1 | Requirement ID? | |
Testcase 2 | Requirement ID? | |
Testcase 3 | Requirement ID? | |
Testcase 4 | Requirement ID? | |