User story #182
Updated by Ivan Herrero over 9 years ago
As a developer I want to be able to write log messages at every level of the framework. The logging mechanism shall be interrupt-safe.
This would satisfy requirements:
* MARTe-EX-F-3.1.1: The framework shall offer developers an interrupt-safe logging mechanism.
* MARTe-EX-F-3.1.2: The framework shall automatically include in the log message the absolute time of the message.
* MARTe-NE-F-3.1.3: The framework shall automatically include in the log message the source file line number.
* MARTe-NE-F-3.1.4: The framework shall automatically include in the log message the source filename.
* MARTe-NE-F-3.1.7: The framework shall automatically include in the log message the identifier of the thread from which the message is triggered from.
* MARTe-NE-F-3.1.8: The framework shall allow developers to specify the severity of the log message.
h1. Source code files modified
* SourceCore/L0Portbility/ -Logger.h- ErrorManagement.h SourceCore/L0Portbility/Logger.h
* SourceCore/L0Portbility/ -Logger.cpp- ErrorManagement.cpp SourceCore/L0Portbility/Logger.cpp
* SourceCore/L0Portbility/ -LogInformation.h- ErrorManagenement.h SourceCore/L0Portbility/LogInformation.h
h1. Architecture & design review
*Date of the review:* 31/07/2015
*Person who did the review:* Andre' Neto
*Version of architecture & design document:* N/A. As per the original MARTe implementation, this is a support function and does not require formal design in UML.
*Result of review:* N/A
*List of non-conformities:* N/A
h1. Code and documentation review
*Date of the review:* 31/08/2015 23/08/2015
*Person who did the review:* Ivan Herrero Andre' Neto
*Result of review:* PASS TO BE DISCUSSED.
*List of non-conformities:* N/A
*Note:* There is an open discussion about if these classes/namespaces must be named
* I believe we should rename all the Error infrastructure or to Log infrastructure, because we otherwise it will lead to confusion. We log a lot of Information and Debug which by definition are not errors.
h1. Unit test review
*Date of the review:* --/--/2015
*Person who did the review:* -----
*Result of coverage tests review:* [PASS/FAIL]
*Result of functional tests review:* [PASS/FAIL]
*Result of review:* [PASS/FAIL]
*List of non-conformities:*
This would satisfy requirements:
* MARTe-EX-F-3.1.1: The framework shall offer developers an interrupt-safe logging mechanism.
* MARTe-EX-F-3.1.2: The framework shall automatically include in the log message the absolute time of the message.
* MARTe-NE-F-3.1.3: The framework shall automatically include in the log message the source file line number.
* MARTe-NE-F-3.1.4: The framework shall automatically include in the log message the source filename.
* MARTe-NE-F-3.1.7: The framework shall automatically include in the log message the identifier of the thread from which the message is triggered from.
* MARTe-NE-F-3.1.8: The framework shall allow developers to specify the severity of the log message.
h1. Source code files modified
* SourceCore/L0Portbility/ -Logger.h- ErrorManagement.h SourceCore/L0Portbility/Logger.h
* SourceCore/L0Portbility/ -Logger.cpp- ErrorManagement.cpp SourceCore/L0Portbility/Logger.cpp
* SourceCore/L0Portbility/ -LogInformation.h- ErrorManagenement.h SourceCore/L0Portbility/LogInformation.h
h1. Architecture & design review
*Date of the review:* 31/07/2015
*Person who did the review:* Andre' Neto
*Version of architecture & design document:* N/A. As per the original MARTe implementation, this is a support function and does not require formal design in UML.
*Result of review:* N/A
*List of non-conformities:* N/A
h1. Code and documentation review
*Date of the review:* 31/08/2015 23/08/2015
*Person who did the review:* Ivan Herrero Andre' Neto
*Result of review:* PASS TO BE DISCUSSED.
*List of non-conformities:* N/A
*Note:* There is an open discussion about if these classes/namespaces must be named
* I believe we should rename all the Error infrastructure or to Log infrastructure, because we otherwise it will lead to confusion. We log a lot of Information and Debug which by definition are not errors.
h1. Unit test review
*Date of the review:* --/--/2015
*Person who did the review:* -----
*Result of coverage tests review:* [PASS/FAIL]
*Result of functional tests review:* [PASS/FAIL]
*Result of review:* [PASS/FAIL]
*List of non-conformities:*