{"text_format":"5","workbook":"xls","n_sheets":1,"sheets":["report2"],"props":{"last_modified_by":"sharecat"},"not_rendered":{"external_links":1,"defined_names":1},"read":"whole","date_system":"1900","formulas":"cached_only"}

{"sheet":"report2","index":0,"n_rows":21,"n_cols":5,"rows_kept":21,"merged":[[0,2,0,3],[0,4,0,5],[1,2,1,3],[1,4,1,5],[2,2,2,3],[2,4,2,5],[3,2,3,3],[4,2,4,3],[5,2,5,3],[6,2,6,3],[8,2,8,3],[10,2,10,3],[11,2,11,3],[15,2,15,3]],"flags":["formulas_cached_only"]}
[null,"1.","Record Nr.",null,"UNINA9910787696903321"]
[null,null,"Autore",null,"Kleinschmager Sebastian"]
[null,null,"Titolo",null,"Aspect-oriented programming evaluated [[electronic resource] ] : a study on the impact that aspect-oriented programming can have on software development productivity / / Sebastian Kleinschmager"]
[null,null,"Pubbl/distr/stampa",null,"Hamburg, : Anchor Academic Pub., 2012"]
[null,null,"ISBN",null,"3-95489-539-0"]
[null,null,"Descrizione fisica",null,"1 online resource (96 p.)"]
[null,null,"Disciplina",null,"005.1/17"]
[{"$nulls":4},"005.117"]
[null,null,"Soggetti",null,"Aspect-oriented programming"]
[{"$nulls":4},"Computer software - Development"]
[null,null,"Lingua di pubblicazione",null,"Inglese"]
[null,null,"Formato",null,"Materiale a stampa"]
[{"$nulls":3},"Livello bibliografico","Monografia"]
[{"$nulls":3},"Note generali","\"Disseminate knowledge\"--Cover."]
[{"$nulls":3},"Nota di bibliografia","Includes bibliographical references."]
[null,null,"Nota di contenuto",null,"Aspect-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"]
[{"$nulls":4},"3.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"]
[{"$nulls":4},"4.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 "]
[{"$nulls":4},"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"]
[{"$nulls":4},"5.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"]
[{"$nulls":3},"Sommario/riassunto","Hauptbeschreibung 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"]