|
| A Documented Approach in Agile Software Development
|
|
Full
text: |
 PDF(100.9KB) |
|
|
Source |
International Journal of Software Engineering (IJSE) |
|
Table of Contents |
|
|
Download
Complete Issue PDF(575.25KB) |
|
Volume: 2 Issue: 2 |
| |
Pages: NULL |
|
Publication
Date: May / June 2011 |
|
ISSN
(Online): 2180-1320 |
|
|
|
|
|
Pages |
13 - 22 |
|
Author(s) |
|
|
|
Published
Date |
31-05-2011 |
|
Publisher |
CSC
Journals, Kuala Lumpur,
Malaysia |
|
ADDITIONAL
INFORMATION |
| Keywords Abstract References Cited by Related Articles Collaborative
Colleague |
| |
|
| |
KEYWORDS: Agile Methodologies, Software Documentation, Scrum, Technical Writer |
|
|
| |
|
|
| This Manuscript is indexed in the following databases/websites:- |
|
| 1. Scribd |
| 2. Docstoc |
| |
|
| |
|
|
| Software engineers have been striving for years to improve the practice of software development and maintenance. Presently the agile approach is quickly becoming main stream in the software industry with core set of beliefs and practices called Manifesto for Agile Software Development. However, agile methods have shaken the view, arguing that more emphasis should be given on software development rather than extensive documentation. It has been observed through literature that good documentation plays a very important role in software development. It helps in increasing development speed, helping in communication and maintaining relationship among developers and other stakeholders. In this paper, a conceptual view of documentation is proposed and a technical writer is introduced along with other scrum roles. Also, the paper presents the relationship of documentation and technical writer by which we can enhance the productivity and maintainability of software. |
| |
|
| |
|
| |
| 1 |
M.F.F. Nasution and H.R. Weistroffer. “Documentation in Systems Development: A Significant Criterion for Project Success”. Proceedings of the 42nd Hawaii International Conference on System Sciences, Jan 2009, pp. 1-9.
|
|
|
| 2 |
P. McInerney and F. Maurer. “UCD in agile projects: dream team or odd couple?”. Magazine interactions, ACM, New York, USA, Volume 12 Issue 6, Nov 2005.
|
|
|
| 3 |
G. Boström et al. “Extending XP practices to support security requirements engineering”. Proceedings of the 2006 international workshop on Software engineering for secure systems, ACM New York, NY, USA, 2006.
|
|
|
| 4 |
P. Abrahamsson et al. “New directions on agile methods: a comparative analysis”. ICSE '03, Proceedings of the 25th International Conference on Software Engineering, IEEE Computer Society Washington, DC, USA, May 2003, pp. 244-254.
|
|
|
| 5 |
M. James. CollabNet Inc., “Six Pages About SCRUM”. Available: www.open.collab.net/media/pdfs/SixPagesAboutScrum.pdf [Nov. 15, 2010].
|
|
|
| 6 |
N.J. Kar. “Adopting Agile Methodologies of Software Development”. Available: www.infosys.com/Fresearch/Fpublications/FDocuments/Fadopting-agile-methodologies.pdf [Dec. 1, 2010].
|
|
|
| 7 |
M. K. Mattsson. "Problems in agile trenches". ESEM '08, Proceedings of the Second ACMIEEE international symposium on Empirical software engineering and measurement, ACM New York, NY, USA, 2008.
|
|
|
| 8 |
F. Paetsch, A. Eberlein and F. Maurer. "Requirements Engineering and Agile Software Development”. WETICE '03, Proceedings of the Twelfth International Workshop on Enabling Technologies: Infrastructure for Collaborative Enterprises, IEEE Computer Society Washington, DC, USA, 2003.
|
|
|
| 9 |
J. Baptista. “Agile Documentation with uScrum”. SIGDOC '08, Proceedings of the 26th annual ACM international conference on Design of communication, ACM, New York, NY, USA, 2008.
|
|
|
| 10 |
S.W. Ambler. “Agile/Lean Documentation: Strategies for Agile Software Development”. Available: http://www.agilemodeling.com/essays/agileDocumentation.htm [Dec. 1, 2010].
|
|
|
| 11 |
T. Clear. “Documentation and agile methods: striking a balance”. ACM SIGCSE Bulletin, Volume 35 Issue 2, ACM New York, USA, Jun. 2003.
|
|
|
| 12 |
B. Selic. “Agile Documentation Anyone?”. IEEE Software, Volume 26 Issue 6, IEEE Computer Society Press Los Alamitos, CA, USA, Nov. 2009, pp.11-12.
|
|
|
| 13 |
A. Sillitti et al. “Managing Uncertainty in Requirements: a Survey in Documentation-driven and Agile Companies”. Software Metrics, 2005. 11th IEEE International Symposium, Oct. 2005, pp. 10-17.
|
|
|
| 14 |
T.C. Lethbridge et al. “How Software Engineers Use Documentation: The State of the Practice”. IEEE Software, Volume 20 Issue 6, IEEE Computer Society Press Los Alamitos, CA, USA, Nov. 2003, pp. 35-39.
|
|
|
| 15 |
S. Bhalerao and M. Ingle. “Analyzing the modes of communication in agile practices”. 3rd IEEE International Conference on Computer Science and Information Technology (ICCSIT), Sep. 2010, pp. 391-395.
|
|
|
| 16 |
Software Design Document. Available: http://en.wikipedia.org/wiki/Software_design_document [Dec. 3, 2010].
|
|
|
| 17 |
T. Ryan. “The Anatomy of a Design Document, Part 1: Documentation Guidelines for the Game Concept and Proposal”. Available: http://www.gamasutra.com/view /feature/3384/the_anatomy_of_a_design_document_.php [Dec. 3, 2010].
|
|
|
| 18 |
R. S. Pressman. “Software Engineering: A Practitioner's Approach”. McGraw-Hill, 2000.
|
|
|
| 19 |
“Lessons Learned: Scientists, Distributed Teams, and Groupware”. Available: http://en.wikiversity.org/wiki/Lessons_Learned:_Scientists,_Distributed_Teams,_and_Grou pware [Dec. 8, 2010].
|
|
|
| 20 |
“Documenting Lessons Learned”. Available: http://pmtips.net/documenting-lessons-learned [Dec. 8, 2010].
|
|
|
| 21 |
“Document management system”. Available: http://en.wikipedia.org/wiki/Document_management_system [Dec. 8, 2010].
|
|
|
| 22 |
“Writing Software Requirements Specifications”. Available: http://www.techwrl. com/techwhirl/magazine/writing/softwarerequirementspecs.html [Nov. 11, 2010].
|
|
|
| 23 |
“Software documentation”. Available: http://en.wikipedia.org/wiki/Software_documentation [Dec. 8, 2010].
|
|
|
| 24 |
K.A. Johnson. “A technical communication intern’s first look at the agile development process”. Available: http://4378.pbworks.com/f/4378+Paper_kj.doc [Dec. 10, 2010].
|
|
|
| 25 |
“Technical Writer”. Available: http://en.wikipedia.org/wiki/Technical_writer [Dec. 10, 2010].
|
|
|
| 26 |
“Technical Writing Skills”. Avialable: http://www.the-aps.org/careers/careers1/gradprof/gwriting.htm [Dec. 10, 2010].
|
|
|
| 27 |
“Five Skills Every Technical Writer Needs”. Available: http://idratherbewriting.com/2007/09/26/five-skills-every-technical-writer-needs [Dec.10, 2010].
|
|
|
| 28 |
D. Longstreet. “The Agile Method and Other Fairy Tales”. Available: http://www.SoftwareMetrics.com/Agile [Nov. 11, 2010].
|
|
|
| 29 |
M. Coram and S. Bohner. “The Impact of Agile Methods on Software Project Management”. ECBS '05, Proceedings of the 12th IEEE International Conference and Workshops on Engineering of Computer-Based Systems, IEEE Computer Society Washington, DC, USA, Apr. 2005, pp. 363-370.
|
|
|
| 30 |
“Contract”. Available: http://www.thefreedictionary.com/contract [Dec 10, 2010].
|
|
|
| |
|
| |
|
| |
| |
|
| |
|
| |
| |
|
| |
|
| |
|
| Nitin Uikey : Colleagues
|
|
| Ugrasen Suman : Colleagues
|
|
| A. K. Ramani : Colleagues
|
|
