Those who fail to learn from history are doomed to repeat it Herez Moise Kattan - PhD Student in computer science (email:
[email protected]) Researches are dreams coming true, a series of thoughts that with work metamorphose in real and useful things ...
I argue that TI Bimodal in the short term would be one first step to unify of software development process again, because the union could make us strongest than separate. I would like in middle term, reduce the gap between software developers and academic researchers, thus, produce more ready to use knowledge. Toward to do this, I proposed one new approach called Illuminated Arrow. The Illuminated Arrow proposed application examples to deepen impartially the initial work of an action research, supported by systematic and tertiary revisions. The reason to start with an action research is to fix the initial mistakes of the research and to be sure about the benefits and limitations of it. If the result of the initial work, is considered positive, the next step suggest by the Illuminated Arrow is systematically review the literature, making it easier to audit. The interpretation made in an interpretive case study is frequently impossible to be auditing posteriorly, and is very difficult to conduct controlled experiments. For this reason, it’s suggested to conduct application examples to produce raw data. After, to analysis this data, recommend the use of the Grounded Theory techniques, to looking for one auditable Theory to explain the findings. There are no silver bullets, but maybe together we could create illuminated arrows that somehow inspire the correct path to innovators. I see one future in long term with more consistent software engineering research methods and integrated databases among ACM, IEEE, SBC, Agile Alliance and many others smaller but integrated. Like Sir Isaac Newton said: ”If I have seen further than others, it is by standing upon the shoulders of giants”. As a more concrete outcome, I cite my recent research on the improvement of pair programming using aspects of Concurrent Engineering[6]. The most important is the Continuous Improvement because while some techniques will fly toward the forgetfulness, the research process still conquer continuously the wonderful blue sky of knowledge.
Illuminated Arrow
We could create illuminated arrows that somehow inspire the correct path to innovators. Figure at the left side illustrates the phases of this new research method, that reduces the gap between software developers and academic researchers, thus, produce more ready to use knowledge.
There are no silver bullets [5], but maybe together we could create illuminated arrows that somehow inspire the correct path to innovators.
Programming and review simultaneous in Pairs:
a pair programming extension[6]
The one who seeks finds The illuminated arrow is a research method [1]. In Software Engineering it is very difficult to conduct controlled experiments or make convincing Double Blinding. Furthermore, human expertise and human subjectivity interfere with the result of experiments [2]. The research on software engineering are much more similar to Social Sciences. This similarity is due to experimental practice, subjectivity and Blinding Procedures [3]. The types of software are very different, each software is different software, it depends on the problem it solves, so is different from medical research, where every human being has blood, lung, heart, brain, etc. Therefore, the illuminated arrow would be a auditable, easier way compared to controlled experiments in the area of software engineering. The Illuminated Arrow [1] proposed application examples to deepen impartially the initial work of an action research, supported by systematic and tertiary revisions [3]. The reason to start with an action research is to fix the initial mistakes of the research and to be sure about the benefits and limitations of it. If the result of the initial work, is considered positive, the next step suggest by the Illuminated Arrow is systematicly review the literature, making it easier to audit. The interpretation made in an interpretive case study is frequently impossible to be auditing posteriorly, and is very difficult to conduct controlled experiments. For this reason, Kattan [1] suggests to conduct application examples to produce raw data. After, to analysis this data, is suggested the use of the Grounded Theory techniques, to looking for one auditable Theory to explain the findings [4]. The use of grounded theory is founded on the premise that the generation of theory at various levels is indispensable for a deep understanding of social phenomena [8] [7].
References References [1] Kattan, H. M.: Illuminated Arrow: a research method to software engineering based on action research, systematic review and grounded theory. In: CONTECSI - International Conference on Information Systems and Technology Management 2016: pages 1971-1978. DOI: 10.5748/9788599693124-13CONTECSI/PS-3926 - Paper submission: 1 Dec 2015 - Presented at Session 4A – AUD Systems Auditing and IT Governance 02/Jun/16-15H30 (2016). [2] Budgen, D., Charters, S.; Turner, M.; Brereton, P.; Kitchenham, B.; Linkman, S: Investigating the Applicability of the Evidence-Based Paradigm to Software Engineering, In: Proceedings of WISER Workshop, ICSE 2006, ACM Press, 7-13, May (2006). [3] Kitchenham, B.; Charters, S.; Budgen, D; Brereton, P; Turner; M; Linkman, S; JØrgensen, M.; Mendes, E. Guidelines for performing Systematic Literature Reviews in Software Engineering. Version 2.3. EBSE Technical Report EBSE-2007-01 Software Engineering Group School of Computer Science and Mathematics Keele University Keele, Staffs ST5 5BG, UK and Department of Computer Science University of Durham Durham, UK 9 July, (2007). [4] Allan, G. The Legitimacy of Grounded Theory Proc. Fifth European Conf. Business Research Methods, pp. 1-8, (2006). [5] Brooks, F. The Mythical Man-Month: Essays on Software Engineering, 20th Anniversary Edition. Reading, MA: Addison-Wesley, 322 pages, (1995). [6] Kattan, H. M.: Programming and review simultaneous in Pairs: a pair programming extension. Master dissertation. In: Institute for Technological Research of the Sa˜o Paulo State. (2015). http://aleph.ipt.br/F. Or ’ipt.br’, click on: Online Consultations, then click on: Library. DOI: 10.13140/RG.2.2.15831.68004 [7] E.G. Glaser, ”Advances in the Methodology of Grounded Theory: Theoretical Sensitivity”, Sociology press, Mill Valley, California - USA, (1978). [8] E.G. Glaser, and A.L. Strauss, ”The Discovery of Grounded Theory: Strategies for Qualitative Research”, (1967).
LATEX Tik Zposter
