Supporting agile software development through active documentation

Agile development processes are adaptive rather than predictive. Therefore, agile processes emphasize operational system code rather than its documentation. To overcome the absence of comprehensive documentation artifacts, agile methods require constant interaction between the system stakeholders. Ironically, however, some traditional documentation artifacts come to support this kind of interaction. In this study, we examine the relationship between software and documentation. We develop an approach that enables incorporating domain documentation to agile development, while keeping the processes adaptive. We also provide a system design that actively uses domain knowledge documentation. These ideas have been applied through the implementation and use of agile documentation support components.

[1]  Michael Uschold,et al.  The Enterprise Ontology , 1998, The Knowledge Engineering Review.

[2]  Kari Laitinen Document classification for software quality systems , 1992, SOEN.

[3]  Martin Fowler,et al.  The new methodology , 2001, Wuhan University Journal of Natural Sciences.

[4]  Julio Cesar Sampaio do Prado Leite,et al.  On Non-Functional Requirements in Software Engineering , 2009, Conceptual Modeling: Foundations and Applications.

[5]  Edward Yourdon,et al.  Object-oriented analysis , 2012 .

[6]  David Harel,et al.  Statecharts: A Visual Formalism for Complex Systems , 1987, Sci. Comput. Program..

[7]  Graham Beech,et al.  Software engineering with ada , 1983 .

[8]  Jacquie Barker,et al.  Beginning C# Objects , 2004, Apress.

[9]  Russ Abbott,et al.  Knowledge abstraction , 1987, CACM.

[10]  Pär J. Ågerfalk,et al.  Session details: Flexible and distributed software processes: old petunias in new bowls? , 2006 .

[11]  Alan M. Davis A taxonomy for the early stages of the software development life cycle , 1988, J. Syst. Softw..

[12]  Stephen J. Mellor,et al.  Object lifecycles: modeling the world in states , 1992 .

[13]  Audris Mockus,et al.  An Empirical Study of Speed and Communication in Globally Distributed Software Development , 2003, IEEE Trans. Software Eng..

[14]  Helen M. Edwards,et al.  Problem frames: analyzing and structuring software development problems , 2002, Softw. Test. Verification Reliab..

[15]  Vladan Devedzic,et al.  Understanding ontological engineering , 2002, CACM.

[16]  John Mylopoulos,et al.  Representing Software Engineering Knowledge , 1997, Automated Software Engineering.

[17]  Peter Wegner,et al.  Principles of problem solving , 2006, CACM.

[18]  Stephen Fickas,et al.  Goal-Directed Requirements Acquisition , 1993, Sci. Comput. Program..

[19]  Peter Bernus,et al.  Handbook on Architectures of Information Systems , 1999 .

[20]  Michael Jackson,et al.  Four dark corners of requirements engineering , 1997, TSEM.

[21]  Hermann Kaindl,et al.  Difficulties in the Transition from OO Analysis to Design , 1999, IEEE Softw..

[22]  Pericles Loucopoulos,et al.  Goal driven requirements engineering: Evaluation of current methods. , 2003 .

[23]  Pekka Abrahamsson,et al.  A case study on the impact of customer communication on defects in agile software development , 2006, AGILE 2006 (AGILE'06).

[24]  Alistair Cockburn,et al.  Agile Software Development: The Business of Innovation , 2001, Computer.

[25]  Hitoshi Kume,et al.  A Case History Analysis of Software Error Cause-Effect Relationships , 1991, IEEE Trans. Software Eng..

[26]  Eric S. K. Yu,et al.  Towards modelling and reasoning support for early-phase requirements engineering , 1997, Proceedings of ISRE '97: 3rd IEEE International Symposium on Requirements Engineering.

[27]  James L. Peterson,et al.  Petri Nets , 1977, CSUR.

[28]  Eric Yu,et al.  From Requirements to Architectural Design –Using Goals and Scenarios , 2001 .

[29]  JaatunMartin Gilje,et al.  Agile Software Development , 2002, Comput. Sci. Educ..

[30]  Jeffrey Voas A US Government-Regulated Software Industry , 1999 .

[31]  Jacquie Barker,et al.  Beginning C# Objects: From Concepts to Code , 2004 .

[32]  Axel van Lamsweerde,et al.  Requirements engineering in the year 00: a research perspective , 2000, Proceedings of the 2000 International Conference on Software Engineering. ICSE 2000 the New Millennium.

[33]  Peng Xu,et al.  Can distributed software development be agile? , 2006, CACM.

[34]  John A. Zachman,et al.  A Framework for Information Systems Architecture , 1987, IBM Syst. J..

[35]  John Mylopoulos,et al.  Understanding "why" in software process modelling, analysis, and design , 1994, Proceedings of 16th International Conference on Software Engineering.

[36]  James D. Herbsleb,et al.  Introducing instant messaging and chat in the workplace , 2002, CHI.

[37]  Pericles Loucopoulos,et al.  Enterprise Knowledge Management and Conceptual Modelling , 1997, Conceptual Modeling.

[38]  Bashar Nuseibeh,et al.  Requirements engineering: a roadmap , 2000, ICSE '00.

[39]  Michael Jackson,et al.  Problem frame semantics for software development , 2005, Software & Systems Modeling.

[40]  Ben Kovitz,et al.  Hidden skills that support phased and agile requirements engineering , 2003, Requirements Engineering.

[41]  John Mylopoulos,et al.  Towards requirements-driven information systems engineering: the Tropos project , 2002, Inf. Syst..

[42]  Brian Henderson-Sellers,et al.  The object-oriented systems life cycle , 1990, CACM.

[43]  Kari Laitinen,et al.  Estimating understandability of software documents , 1996, SOEN.

[44]  Evangelia Kavakli,et al.  Goal-Oriented Requirements Engineering: A Unifying Framework , 2002, Requirements Engineering.

[45]  C. Petri Kommunikation mit Automaten , 1962 .

[46]  Jim Welsh,et al.  Software Documents: Concepts and Tools , 1994, Softw. Concepts Tools.

[47]  Frank Maurer,et al.  Requirements engineering and agile software development , 2003, WET ICE 2003. Proceedings. Twelfth IEEE International Workshops on Enabling Technologies: Infrastructure for Collaborative Enterprises, 2003..

[48]  E. Dubois,et al.  A knowledge representation language for requirements engineering , 1986, Proceedings of the IEEE.

[49]  Michael Grüninger,et al.  An organisation ontology for enterprise modelling: preliminary concepts for linking structure and behaviour , 1995, Proceedings 4th IEEE Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises (WET ICE '95).

[50]  Terry Halpin,et al.  Object-Role Modeling (ORM/NIAM) , 2006, Handbook on Architectures of Information Systems.

[51]  Zhi Jin,et al.  An Ontology of Problem Frames for Guiding Problem Frame Specification , 2007, KSEM.

[52]  David C. Hay,et al.  Requirements Analysis: From Business Views to Architecture , 2002 .

[53]  Axel van Lamsweerde,et al.  Goal-Oriented Requirements Engineering: A Guided Tour , 2001, RE.

[54]  J. A Turner,et al.  Understanding Elements of System Design , 1986 .

[55]  William E. Lorensen,et al.  Object-Oriented Modeling and Design , 1991, TOOLS.

[56]  Pär J. Ågerfalk,et al.  SOFTWARE PROCESSES: OLD PETUNIAS IN NEW BOWLS? , 2006 .

[57]  Mark S. Fox,et al.  An organisation ontology for enterprise modeling: preliminary concepts for linking structure and behaviour , 1996 .

[58]  Laurian M. Chirica,et al.  The entity-relationship model: toward a unified view of data , 1975, SIGF.

[59]  Siobhán Clarke,et al.  Subject-oriented design: towards improved alignment of requirements, design, and code , 1999, OOPSLA '99.

[60]  Pekka Abrahamsson,et al.  New directions on agile methods: a comparative analysis , 2003, 25th International Conference on Software Engineering, 2003. Proceedings..

[61]  Annie I. Antón,et al.  Goal-based requirements analysis , 1996, Proceedings of the Second International Conference on Requirements Engineering.

[62]  Eric S. K. Yu,et al.  Agent-Oriented Modelling: Software versus the World , 2001, AOSE.

[63]  Adam Wojciechowski,et al.  Extreme programming modified: embrace requirements engineering practices , 2002, Proceedings IEEE Joint International Conference on Requirements Engineering.

[64]  Penny Grubb,et al.  Software maintenance , 1996 .

[65]  Colette Rolland,et al.  From conceptual modelling to requirements engineering , 2000, Ann. Softw. Eng..

[66]  Colette Rolland From Conceptual Modeling to Requirements Engineering , 2006, ER.