TY - GEN
T1 - Activities performed by programmers while using framework examples as a guide
AU - Boghrati, Reihane
AU - Heydarnoori, Abbas
AU - Kazemitabaar, Majeed
PY - 2014
Y1 - 2014
N2 - It is now a common approach pursued by programmers to develop new software systems using Object-Oriented Application Frameworks such as Spring, Struts and, Eclipse. This improves the quality and the maintainability of the code. Furthermore, it reduces development cost and time. However, the main problem is that these frameworks usually have a complicated Application Programming Interface (API), and typically suffer from the lack of enough documentation and appropriate user manuals. To solve these problems, programmers often refer to existing sample applications of those frameworks to learn how to implement the desired functionality in their own code. This is called the Monkey See, Monkey Do rule in software engineering literature. The aim of this paper is to investigate and analyze the activities programmers perform to achieve a successful use of this rule. The results of this analysis will help us to build automated tools which are helpful for programmers while perusing the aforementioned Monkey See, Monkey Do rule.
AB - It is now a common approach pursued by programmers to develop new software systems using Object-Oriented Application Frameworks such as Spring, Struts and, Eclipse. This improves the quality and the maintainability of the code. Furthermore, it reduces development cost and time. However, the main problem is that these frameworks usually have a complicated Application Programming Interface (API), and typically suffer from the lack of enough documentation and appropriate user manuals. To solve these problems, programmers often refer to existing sample applications of those frameworks to learn how to implement the desired functionality in their own code. This is called the Monkey See, Monkey Do rule in software engineering literature. The aim of this paper is to investigate and analyze the activities programmers perform to achieve a successful use of this rule. The results of this analysis will help us to build automated tools which are helpful for programmers while perusing the aforementioned Monkey See, Monkey Do rule.
KW - Monkey Do rule
KW - Monkey See
KW - Object-oriented application frameworks
KW - Program comprehension
UR - http://www.scopus.com/inward/record.url?scp=84905662429&partnerID=8YFLogxK
UR - http://www.scopus.com/inward/citedby.url?scp=84905662429&partnerID=8YFLogxK
U2 - 10.1145/2554850.2555016
DO - 10.1145/2554850.2555016
M3 - Conference contribution
AN - SCOPUS:84905662429
SN - 9781450324694
T3 - Proceedings of the ACM Symposium on Applied Computing
SP - 1146
EP - 1151
BT - Proceedings of the 29th Annual ACM Symposium on Applied Computing, SAC 2014
PB - Association for Computing Machinery
T2 - 29th Annual ACM Symposium on Applied Computing, SAC 2014
Y2 - 24 March 2014 through 28 March 2014
ER -