RS002: Telemetry Support (In-app logging)

[emilio-aburto]

Description: The "Concept Location", "Impact Analysis" and "Change Propagation" process must be registered with the corresponding data: Timestamp (day & hour), process phase (CL, IA or CP), action taken and marked entity (class, method, variable). The logging data must be exported as a CSV files with columns corresponding to timestamp, phase, action and entity. A basic replay mode must be supported, showing a time-ordered table contained in the CSV file.

Source: Team / Teacher Priority: High Stability: Non-Negotiable Last Update: 2017-01-26 State: Finished Increment: 7 Type: Functional Associated user: End-User Associated User Requirements:

• RU004: Telemetria (Emilio)

Software Change Process:

• [X] Initialization
• [x] Concept Location
• [x] Impact Analysis
• [x] Prefactoring
• [x] Actualization
• [x] Postfactoring
• [x] Conclusion

[emilio-aburto]

Concept Location

Significant Concepts: Concept Location, Analysis, Change Propagation, Search, Mouse Concept to be implemented: Telemetry, Phase, Entity Relevant matched classes:

• "Concept location": JSwingRipplesApplication, StartAnalysisDialog.
• "Analysis": JSwingRipplesApplication, StartAnalysisDialog, StartAnalysisAction.
• "Change propagation": StartAnalysisDialog.
• "Search": JSwingRipplesApplication, SearchMenu, Searcher, StartSearchWorker
• "Mouse": HierarchicalView, ProjectsView, ProjectsViewMouseEvent, ProjectsViewMouseListener.

[emilio-aburto]

The issue was big enough to be split in 2 independent issues: this and #6.

[emilio-aburto]

Impact Analysis

• From JSwingRipplesApplication: new variable logger and getter method getLogger()
• From SearchMenu: SearchMenu() constructor
• From StartAnalysisDialog: beginConceptLocation(), createChangePropagationCallback(), createImpactAnalysisCallback().

[emilio-aburto]

Prefactoring, Actualization, Postfactoring & Conclusion

In-app logging is ready and working