LEADER 04614nam 2200577 a 450 001 9910787696903321 005 20230801231213.0 010 $a3-95489-539-0 035 $a(CKB)2670000000406202 035 $a(EBL)1324008 035 $a(OCoLC)854977182 035 $a(SSID)ssj0001152910 035 $a(PQKBManifestationID)11749594 035 $a(PQKBTitleCode)TC0001152910 035 $a(PQKBWorkID)11148818 035 $a(PQKB)10846986 035 $a(MiAaPQ)EBC1324008 035 $a(Au-PeEL)EBL1324008 035 $a(CaPaEBR)ebr10735114 035 $a(EXLCZ)992670000000406202 100 $a20130729d2012 uy 0 101 0 $aeng 135 $aur|n|---||||| 181 $ctxt 182 $cc 183 $acr 200 10$aAspect-oriented programming evaluated$b[electronic resource] $ea study on the impact that aspect-oriented programming can have on software development productivity /$fSebastian Kleinschmager 210 $aHamburg $cAnchor Academic Pub.$d2012 215 $a1 online resource (96 p.) 300 $a"Disseminate knowledge"--Cover. 311 $a3-95489-039-9 320 $aIncludes bibliographical references. 327 $aAspect-Oriented Programming evaluated: A Study on the Impact that Aspect-Oriented Programming can have on Software Development Productivity; Abstract; Directory of Figures; Directory of Tables; Directory of Listings; Table of Contents; 1. Introduction; 2. Motivation and Problem Description; 3. Experiment Background; 3.1. A short summary on Empiricism and Experimentation; 3.1.1. What is meant by Empiricism?; 3.1.2. Research and Experimentation methods; 3.1.2.1. Case Studies or Benchmarks; 3.1.2.2. Field Studies; 3.1.2.3. Controlled Experiments; 3.1.2.4. Polls; 3.1.2.5. Meta-Studies 327 $a3.1.3. Empirical research in Software Engineering - Specifics and Dangers3.2. Aspect-Oriented Programming; 3.2.1. Aspect-Orientation in General; 3.2.2. AspectJ - a short Introduction; 4. The Experiment; 4.1. Experiment Buildup; 4.1.1. The planned Course of the Experiment; 4.1.2. The Questionnaire; 4.1.3. The Hard- and Software used in the Experiment; 4.1.3.1. The Application used for Editing; 4.1.3.2. The Development Environment and Hardware; 4.1.4. The Tasks; 4.1.4.1. Task1: The Logging Task; 4.1.4.2. Task2: The Parameter Null Task; 4.1.4.3. Task3: The Synchronization Task 327 $a4.1.4.4. Task4: The Check Player Argument Task4.1.4.5. Task5: The Notify Observers Task; 4.1.4.6. Task6: The Observers Null Check Task; 4.1.4.7. Task7: The Refresh Constraint Task; 4.1.4.8. Task8: The Label Value Check Task; 4.1.4.9. Task9: The Current Level Check Task; 4.2. Implementation of the Experiment; 5. Experiment Analysis and Results; 5.1. Data Processing and Preparation; 5.2. Data analysis and presentation; 5.2.1. The Logging Task; 5.2.2. The Parameter Null Task; 5.2.3. The Synchronization Task; 5.2.4. The Player Check Task; 5.2.5. The Notify Observers Task 327 $a5.2.6. The Observers Null Task5.2.7. The Refresh Constraint Task; 5.2.8. The Label Value Check Task; 5.2.9. The Level Check Task; 5.2.10. Results of the Development Times and Descriptive Statistics; 5.2.11. Statistical Tests on the Results; 5.2.12. Doing a Break-Even Analysis; 5.2.13. Participant Grouping; 6. Discussion; 6.1. Thoughts on Validity; 6.1.1. Internal Validity; 6.2. General Discussion; 7. Related Work; 8. Conclusion; 9. Appendix; 9.1. The questionnaire (German); 9.2. The aspect-oriented task descriptions (German); 10. References 330 $aHauptbeschreibung Aspect-oriented-programming is a relatively new technique that has evolved on top of the already well-established approach of object-oriented programming. When it is used correctly, it promises to remove many redundant parts of a code that appear repeatedly in an application, essentially untangling the original code. Thus, it can lead to a cleaner, more separated software design, to greater modularity and maintainability. Time-savings in software engineering can also be huge cost-savings, and anything that increases software quality is a welcome sight in an industry that in p 606 $aAspect-oriented programming 606 $aComputer software$xDevelopment 615 0$aAspect-oriented programming. 615 0$aComputer software$xDevelopment. 676 $a005.1/17 676 $a005.117 700 $aKleinschmager$b Sebastian$01466421 801 0$bMiAaPQ 801 1$bMiAaPQ 801 2$bMiAaPQ 906 $aBOOK 912 $a9910787696903321 996 $aAspect-oriented programming evaluated$93676895 997 $aUNINA