Content deleted Content added
Astute geek (talk | contribs) m Grammar changes |
Citation bot (talk | contribs) Add: s2cid, authors 1-1. Removed parameters. Some additions/deletions were parameter name changes. | Use this bot. Report bugs. | Suggested by Abductive | #UCB_toolbar |
||
Line 1:
{{Expert needed|Software|reason=it appears to misrepresent the history of software analytics|date=December 2014}}
'''Software analytics''' is the [[analytics]] specific to the ___domain of [[software system]]s taking into account [[source code]], static and dynamic characteristics (e.g., [[software metric]]s) as well as related processes of their [[software development|development]] and [[software evolution|evolution]]. It aims at describing, monitoring, predicting, and improving the efficiency and effectiveness of [[software engineering]] throughout the [[software lifecycle]], in particular during [[software development]] and [[software maintenance]]. The data collection is typically done by mining [[software repository|software repositories]], but can also be achieved by collecting user actions or production data. One avenue for using the collected data is to augment the [[integrated development environment]]s (IDEs) with data-driven features.<ref name="Bruch2010">{{cite journal|last1=Bruch|first1=Marcel|last2=Bodden|first2=Eric|last3=Monperrus|first3=Martin|last4=Mezini|first4=Mira|title=IDE 2.0: Collective Intelligence in Software Development|year=2010|url=https://hal.archives-ouvertes.fr/hal-01575346/document|doi=10.1145/1882362.1882374|s2cid=7637561 }}</ref>
== Definitions ==
Line 19:
Core data sources include [[source code]], "check-ins, work items, bug reports and test executions [...] recorded in software repositories such as CVS, Subversion, GIT, and Bugzilla."<ref>Harald Gall, Tim Menzies, [[Laurie Williams (software engineer)|Laurie Williams]], and Thomas Zimmerman. "Software Development Analytics". Dagstuhl Reports, Vol. 4, Issue 6, pp. 64-83.</ref> [[telemetry | Telemetry data]] as well as execution traces or logs can also be taken into account.
Automated analysis, massive data, and systematic reasoning support decision-making at almost all levels. In general, key technologies employed by software analytics include analytical technologies such as [[machine learning]], [[data mining]], [[statistics]], [[pattern recognition]], [[information visualization]] as well as large-scale data computing & processing. For example, software analytics tools allow users to map derived analysis results by means of [[software map]]s, which support interactively exploring system artifacts and correlated software metrics. There are also software analytics tools using analytical technologies on top of [[software quality]] models in [[agile software development]] companies, which support assessing software qualities (e.g., reliability), and deriving actions for their improvement.<ref>{{Cite journal|
== History ==
| |||