Aspect-oriented programming evaluated [[electronic resource] ] : a study on the impact that aspect-oriented programming can have on software development productivity / / Sebastian Kleinschmager |
Autore | Kleinschmager Sebastian |
Pubbl/distr/stampa | Hamburg, : Anchor Academic Pub., 2012 |
Descrizione fisica | 1 online resource (96 p.) |
Disciplina |
005.1/17
005.117 |
Soggetto topico |
Aspect-oriented programming
Computer software - Development |
Soggetto genere / forma | Electronic books. |
ISBN | 3-95489-539-0 |
Formato | Materiale a stampa |
Livello bibliografico | Monografia |
Lingua di pubblicazione | eng |
Nota di contenuto |
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
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 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 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 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 |
Record Nr. | UNINA-9910463296203321 |
Kleinschmager Sebastian | ||
Hamburg, : Anchor Academic Pub., 2012 | ||
Materiale a stampa | ||
Lo trovi qui: Univ. Federico II | ||
|
Aspect-oriented programming evaluated [[electronic resource] ] : a study on the impact that aspect-oriented programming can have on software development productivity / / Sebastian Kleinschmager |
Autore | Kleinschmager Sebastian |
Pubbl/distr/stampa | Hamburg, : Anchor Academic Pub., 2012 |
Descrizione fisica | 1 online resource (96 p.) |
Disciplina |
005.1/17
005.117 |
Soggetto topico |
Aspect-oriented programming
Computer software - Development |
ISBN | 3-95489-539-0 |
Formato | Materiale a stampa |
Livello bibliografico | Monografia |
Lingua di pubblicazione | eng |
Nota di contenuto |
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
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 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 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 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 |
Record Nr. | UNINA-9910787696903321 |
Kleinschmager Sebastian | ||
Hamburg, : Anchor Academic Pub., 2012 | ||
Materiale a stampa | ||
Lo trovi qui: Univ. Federico II | ||
|
Aspect-oriented programming evaluated : a study on the impact that aspect-oriented programming can have on software development productivity / / Sebastian Kleinschmager |
Autore | Kleinschmager Sebastian |
Edizione | [1st ed.] |
Pubbl/distr/stampa | Hamburg, : Anchor Academic Pub., 2012 |
Descrizione fisica | 1 online resource (96 p.) |
Disciplina |
005.1/17
005.117 |
Soggetto topico |
Aspect-oriented programming
Computer software - Development |
ISBN | 3-95489-539-0 |
Formato | Materiale a stampa |
Livello bibliografico | Monografia |
Lingua di pubblicazione | eng |
Nota di contenuto |
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
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 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 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 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 |
Record Nr. | UNINA-9910812966503321 |
Kleinschmager Sebastian | ||
Hamburg, : Anchor Academic Pub., 2012 | ||
Materiale a stampa | ||
Lo trovi qui: Univ. Federico II | ||
|
Can static type systems speed up programming? [[electronic resource] ] : an experimental evaluation of static and dynamic type systems / / Sebastian Kleinschmager |
Autore | Kleinschmager Sebastian |
Pubbl/distr/stampa | Hamburg, : Anchor Academic Pub., 2013 |
Descrizione fisica | 1 online resource (114 p.) |
Disciplina | 006.22 |
Soggetto topico |
Computer programming
Application software |
Soggetto genere / forma | Electronic books. |
ISBN | 3-95489-540-4 |
Formato | Materiale a stampa |
Livello bibliografico | Monografia |
Lingua di pubblicazione | eng |
Nota di contenuto |
Can static type systems speed up programming? An experimental evaluation of static and dynamic type systems; Abstract; Zusammenfassung (German Abstract); Table of Contents; Directory of Figures; Directory of Tables; Directory of Listings; 1. Introduction; 2. Motivation & Background; 2.1 Motivation; 2.2 Maintenance and Debugging; 2.2.1 Maintenance in a Nutshell; 2.2.2 Debugging in a Nutshell; 2.3 Documentation and APIs; 2.3.1 Documentation of Software Systems; 2.3.2 APIs and Application of their Design Principles in General Programming; 2.4 Type Systems
2.5 Empirical Research in Software Engineering2.5.1 On Empirical Research; 2.5.2 Controlled Experiments; 2.5.3 Current State of Empirical Research in Software Engineering; 3. Related Work; 3.1 Gannon (1977); 3.2 Prechelt and Tichy (1998); 3.3 Daly, Sazawal and Foster (2009); 3.4 Hanenberg (2010); 3.5 Steinberg, Mayer, Stuchlik and Hanenberg - A running Experiment series; 3.5.1 Steinberg (2011); 3.5.2 Mayer (2011); 3.5.3 Stuchlik and Hanenberg (2011); 4. The Experiment; 4.1 The Research Question; 4.2 Experiment Overview; 4.2.1 Initial Considerations 4.2.2 Further Considerations: Studies on Using Students as Subjects4.2.3 Design of the Experiment; 4.3 Questionnaire; 4.4 Hard- and Software Environment; 4.4.1 Environment; 4.4.2 Programming Languages; 4.4.2.1 Java; 4.4.2.2 Groovy; 4.5 Workspace Applications and Tasks; 4.5.1 The Java Application - A Labyrinth Game; 4.5.2 The Groovy Application - A simple Mail Viewer; 4.5.3 Important Changes made to both Parts; 4.5.4 The Tasks; 4.5.4.1 The Task Types; 4.5.4.2 Tasks 1 and 10 - 2 Types to identify; 4.5.4.3 Tasks 2 and 11 - 4 Types to identify; 4.5.4.4 Tasks 4 and 13 - Semantic Error 4.5.4.5 Tasks 5 and 14 - Semantic Error4.5.4.6 Tasks 6 and 15 - 8 Types to identify; 4.5.4.7 Tasks 7 and 16 - Stack size 2 and branch size 3; 4.5.4.8 Tasks 8 and 17 - 12 types to identify; 4.5.4.9 Tasks 9 and 18 - Stack size 2 and branch size 5; 4.5.4.10 Summary of Variables and Mapping of Tasks to Hypotheses; 4.6 Experiment Implementation; 5. Threats to Validity; 5.1 Internal Validity; 5.2 External Validity; 6. Analysis and Results; 6.1 General Descriptive Statistics; 6.2 Statistical Tests and Analysis; 6.2.1 Within-Subject Analysis on the complete data 6.2.2 Analysis for residual effects between the two ParticipantGroups6.2.3 Within-Subject Analysis on the two Participant Groups; 6.2.3.1 Participants that started with Groovy; 6.2.3.2 Participants that started with Java; 6.2.4 Exploratory Analysis of the Results based on Participants' Performance; 6.2.4.1 Participants that started with Groovy; 6.2.4.2 Participants that started with Java; 6.2.5 Hypotheses and Task based Analysis; 6.2.5.1 Tasks 1, 2, 3, 6 and 8; 6.2.5.2 Hypothesis 2-1 and Tasks 7 and 9; 6.2.5.3 Hypothesis 2-2 and Tasks 4 and 5; 7. Summary and Discussion; 7.1 Final Remarks 7.2 Result Summary |
Record Nr. | UNINA-9910463118803321 |
Kleinschmager Sebastian | ||
Hamburg, : Anchor Academic Pub., 2013 | ||
Materiale a stampa | ||
Lo trovi qui: Univ. Federico II | ||
|
Can static type systems speed up programming? [[electronic resource] ] : an experimental evaluation of static and dynamic type systems / / Sebastian Kleinschmager |
Autore | Kleinschmager Sebastian |
Pubbl/distr/stampa | Hamburg, : Anchor Academic Pub., 2013 |
Descrizione fisica | 1 online resource (114 p.) |
Disciplina | 006.22 |
Soggetto topico |
Computer programming
Application software |
ISBN | 3-95489-540-4 |
Formato | Materiale a stampa |
Livello bibliografico | Monografia |
Lingua di pubblicazione | eng |
Nota di contenuto |
Can static type systems speed up programming? An experimental evaluation of static and dynamic type systems; Abstract; Zusammenfassung (German Abstract); Table of Contents; Directory of Figures; Directory of Tables; Directory of Listings; 1. Introduction; 2. Motivation & Background; 2.1 Motivation; 2.2 Maintenance and Debugging; 2.2.1 Maintenance in a Nutshell; 2.2.2 Debugging in a Nutshell; 2.3 Documentation and APIs; 2.3.1 Documentation of Software Systems; 2.3.2 APIs and Application of their Design Principles in General Programming; 2.4 Type Systems
2.5 Empirical Research in Software Engineering2.5.1 On Empirical Research; 2.5.2 Controlled Experiments; 2.5.3 Current State of Empirical Research in Software Engineering; 3. Related Work; 3.1 Gannon (1977); 3.2 Prechelt and Tichy (1998); 3.3 Daly, Sazawal and Foster (2009); 3.4 Hanenberg (2010); 3.5 Steinberg, Mayer, Stuchlik and Hanenberg - A running Experiment series; 3.5.1 Steinberg (2011); 3.5.2 Mayer (2011); 3.5.3 Stuchlik and Hanenberg (2011); 4. The Experiment; 4.1 The Research Question; 4.2 Experiment Overview; 4.2.1 Initial Considerations 4.2.2 Further Considerations: Studies on Using Students as Subjects4.2.3 Design of the Experiment; 4.3 Questionnaire; 4.4 Hard- and Software Environment; 4.4.1 Environment; 4.4.2 Programming Languages; 4.4.2.1 Java; 4.4.2.2 Groovy; 4.5 Workspace Applications and Tasks; 4.5.1 The Java Application - A Labyrinth Game; 4.5.2 The Groovy Application - A simple Mail Viewer; 4.5.3 Important Changes made to both Parts; 4.5.4 The Tasks; 4.5.4.1 The Task Types; 4.5.4.2 Tasks 1 and 10 - 2 Types to identify; 4.5.4.3 Tasks 2 and 11 - 4 Types to identify; 4.5.4.4 Tasks 4 and 13 - Semantic Error 4.5.4.5 Tasks 5 and 14 - Semantic Error4.5.4.6 Tasks 6 and 15 - 8 Types to identify; 4.5.4.7 Tasks 7 and 16 - Stack size 2 and branch size 3; 4.5.4.8 Tasks 8 and 17 - 12 types to identify; 4.5.4.9 Tasks 9 and 18 - Stack size 2 and branch size 5; 4.5.4.10 Summary of Variables and Mapping of Tasks to Hypotheses; 4.6 Experiment Implementation; 5. Threats to Validity; 5.1 Internal Validity; 5.2 External Validity; 6. Analysis and Results; 6.1 General Descriptive Statistics; 6.2 Statistical Tests and Analysis; 6.2.1 Within-Subject Analysis on the complete data 6.2.2 Analysis for residual effects between the two ParticipantGroups6.2.3 Within-Subject Analysis on the two Participant Groups; 6.2.3.1 Participants that started with Groovy; 6.2.3.2 Participants that started with Java; 6.2.4 Exploratory Analysis of the Results based on Participants' Performance; 6.2.4.1 Participants that started with Groovy; 6.2.4.2 Participants that started with Java; 6.2.5 Hypotheses and Task based Analysis; 6.2.5.1 Tasks 1, 2, 3, 6 and 8; 6.2.5.2 Hypothesis 2-1 and Tasks 7 and 9; 6.2.5.3 Hypothesis 2-2 and Tasks 4 and 5; 7. Summary and Discussion; 7.1 Final Remarks 7.2 Result Summary |
Record Nr. | UNINA-9910787798603321 |
Kleinschmager Sebastian | ||
Hamburg, : Anchor Academic Pub., 2013 | ||
Materiale a stampa | ||
Lo trovi qui: Univ. Federico II | ||
|
Can static type systems speed up programming? : an experimental evaluation of static and dynamic type systems / / Sebastian Kleinschmager |
Autore | Kleinschmager Sebastian |
Edizione | [1st ed.] |
Pubbl/distr/stampa | Hamburg, : Anchor Academic Pub., 2013 |
Descrizione fisica | 1 online resource (114 p.) |
Disciplina | 006.22 |
Soggetto topico |
Computer programming
Application software |
ISBN | 3-95489-540-4 |
Formato | Materiale a stampa |
Livello bibliografico | Monografia |
Lingua di pubblicazione | eng |
Nota di contenuto |
Can static type systems speed up programming? An experimental evaluation of static and dynamic type systems; Abstract; Zusammenfassung (German Abstract); Table of Contents; Directory of Figures; Directory of Tables; Directory of Listings; 1. Introduction; 2. Motivation & Background; 2.1 Motivation; 2.2 Maintenance and Debugging; 2.2.1 Maintenance in a Nutshell; 2.2.2 Debugging in a Nutshell; 2.3 Documentation and APIs; 2.3.1 Documentation of Software Systems; 2.3.2 APIs and Application of their Design Principles in General Programming; 2.4 Type Systems
2.5 Empirical Research in Software Engineering2.5.1 On Empirical Research; 2.5.2 Controlled Experiments; 2.5.3 Current State of Empirical Research in Software Engineering; 3. Related Work; 3.1 Gannon (1977); 3.2 Prechelt and Tichy (1998); 3.3 Daly, Sazawal and Foster (2009); 3.4 Hanenberg (2010); 3.5 Steinberg, Mayer, Stuchlik and Hanenberg - A running Experiment series; 3.5.1 Steinberg (2011); 3.5.2 Mayer (2011); 3.5.3 Stuchlik and Hanenberg (2011); 4. The Experiment; 4.1 The Research Question; 4.2 Experiment Overview; 4.2.1 Initial Considerations 4.2.2 Further Considerations: Studies on Using Students as Subjects4.2.3 Design of the Experiment; 4.3 Questionnaire; 4.4 Hard- and Software Environment; 4.4.1 Environment; 4.4.2 Programming Languages; 4.4.2.1 Java; 4.4.2.2 Groovy; 4.5 Workspace Applications and Tasks; 4.5.1 The Java Application - A Labyrinth Game; 4.5.2 The Groovy Application - A simple Mail Viewer; 4.5.3 Important Changes made to both Parts; 4.5.4 The Tasks; 4.5.4.1 The Task Types; 4.5.4.2 Tasks 1 and 10 - 2 Types to identify; 4.5.4.3 Tasks 2 and 11 - 4 Types to identify; 4.5.4.4 Tasks 4 and 13 - Semantic Error 4.5.4.5 Tasks 5 and 14 - Semantic Error4.5.4.6 Tasks 6 and 15 - 8 Types to identify; 4.5.4.7 Tasks 7 and 16 - Stack size 2 and branch size 3; 4.5.4.8 Tasks 8 and 17 - 12 types to identify; 4.5.4.9 Tasks 9 and 18 - Stack size 2 and branch size 5; 4.5.4.10 Summary of Variables and Mapping of Tasks to Hypotheses; 4.6 Experiment Implementation; 5. Threats to Validity; 5.1 Internal Validity; 5.2 External Validity; 6. Analysis and Results; 6.1 General Descriptive Statistics; 6.2 Statistical Tests and Analysis; 6.2.1 Within-Subject Analysis on the complete data 6.2.2 Analysis for residual effects between the two ParticipantGroups6.2.3 Within-Subject Analysis on the two Participant Groups; 6.2.3.1 Participants that started with Groovy; 6.2.3.2 Participants that started with Java; 6.2.4 Exploratory Analysis of the Results based on Participants' Performance; 6.2.4.1 Participants that started with Groovy; 6.2.4.2 Participants that started with Java; 6.2.5 Hypotheses and Task based Analysis; 6.2.5.1 Tasks 1, 2, 3, 6 and 8; 6.2.5.2 Hypothesis 2-1 and Tasks 7 and 9; 6.2.5.3 Hypothesis 2-2 and Tasks 4 and 5; 7. Summary and Discussion; 7.1 Final Remarks 7.2 Result Summary |
Record Nr. | UNINA-9910827906003321 |
Kleinschmager Sebastian | ||
Hamburg, : Anchor Academic Pub., 2013 | ||
Materiale a stampa | ||
Lo trovi qui: Univ. Federico II | ||
|