Laboratory Driven, Lean-to-Adaptive Prototyping in Parallel for Web Software Project Identification and Application Development in Health Science Research

Full-Text HTML XML Download Download as PDF (Size:147KB) PP. 62-68
DOI: 10.4236/jsea.2012.52010    3,919 Downloads   7,187 Views   Citations


Clinical research laboratories, bioinformatics core facilities, and health science organizations often rely on heavy planning based software development models to propose, build, and distribute software as a consumable product. Projects in non-agile software life cycles tend to have rigid “plan-design-build” milestones, increasing the amount of time needed for software development completion. Though the classic software development approach is needed for large-scale and organizational projects, clinical research laboratories can expedite software development while maintaining quality by using lean prototyping as a condition of project advancement to a committed adaptive software development cycle. Software projects benefit from an agile methodology due to the active and changing requirements often guided by experimental data driven models. We describe a lean to adaptive method used in parallel with laboratory bench work to develop quality software quickly that meets the requirements of a fast-paced research environment and reducing time to production, providing immediate value to the end user, and limiting unnecessary development practices in favor of results.

Cite this paper

Z. Dwight and A. Barnes, "Laboratory Driven, Lean-to-Adaptive Prototyping in Parallel for Web Software Project Identification and Application Development in Health Science Research," Journal of Software Engineering and Applications, Vol. 5 No. 2, 2012, pp. 62-68. doi: 10.4236/jsea.2012.52010.


[1] J. Highsmith, A. Cockburn and B. Boehm, “Agile Software Development: The Business of Innovation,” Computer, Vol. 34, No. 9, 2001, p. 3. doi:10.1109/2.947100
[2] D. W. Kane, M. M. Hohman, E. G. Cerami, et al., “Agile Methods in Biomedical Software Development: A Multi-Site Experience Report,” BMC Bioinformatics, Vol. 7, 2006, p. 273. doi:10.1186/1471-2105-7-273
[3] K. Rother, W. Potrzebowski, T. Puton, et al., “A Toolbox for Developing Bioinformatics Software,” Brief Bioinform, 29 July 2011.
[4] J. Pitt-Francis, M. O. Bernabeu, J. Cooper, et al., “Chaste: Using Agile Programming Techniques to Develop Computational Biology Software,” Philosophical Transactions of the Royal Society A, Vol. 366, No. 1878, 2008, pp. 3111-3136.
[5] R. S. Sadasivam, K. Delaughter, K. Crenshaw, et al., “Development of an Interactive, Web-Delivered System to Increase Provider-Patient Engagement in Smoking Cessation,” Journal of Medical Internet Research, Vol. 13, No. 4, 2011, p. e87. doi:10.2196/jmir.1721
[6] K. Gary, A. Enquobahrie, L. Ibanez, et al., “Agile Methods for Open Source Safety-Critical Software,” Software: Practice and Experience, Vol. 41, No. 9, 2011 pp. 945-962. doi:10.1002/spe.1075
[7] Z. Dwight, R. Palais and C. T. Wittwer, “uMELT: Prediction of High-Resolution Melting Curves and Dynamic Melting Profiles of PCR Products in a Rich Web Application,” Bioinformatics, Vol. 27, No. 7, 2011, pp. 1019-1020. doi:10.1093/bioinformatics/btr065
[8] S. Raman, “Lean Software Development: Is It Feasible?” Proceedings of the 17th Digital Avionics Systems Conference, Vol. 1, 1998, pp. C13/1-C13/8.
[9] R. Baskerville, B. Ramesh, L. Levina, et al., “Is Internet-Speed Software Development Different?” IEEE Software, Vol. 20, No. 6, 2003, pp. 70-77. doi:10.1109/MS.2003.1241369
[10] A. Cockburn, J. Highsmith and B. Boehm, “Agile Software Development: The People Factor,” Computer, Vol. 34, No. 11, 2001, pp. 131-133. doi:10.1109/2.963450
[11] J. Erickson, K. Lyytinen and K. Siau. “Agile Modeling, Agile Software Development, and Extreme Programming: The State of Research,” Journal of Database Management, Vol. 16, No. 4, 2005, pp. 88-100. doi:10.4018/jdm.2005100105
[12] V. Devedzic, S. Milenkovic, et al., “Teaching Agile Software Development: A Case Study,” IEEE Transactions on Education, Vol. 54, No. 2, 2011, pp. 273-278. doi:10.1109/TE.2010.2052104
[13] T. Dyba and T. Dingsoyr, “Empirical Studies of Agile Software Development: A Systematic Review,” Information and Software Technology, Vol. 50, No. 9-10, 2008, pp. 833-859. doi:10.1016/j.infsof.2008.01.006
[14] T. Dyba and T. Dingsoyr, “What Do We Know about Agile Software Development?” IEEE Software, Vol. 26, No. 5, 2009, pp. 6-9. doi:10.1109/MS.2009.145
[15] M. Aoyama, “Web-Based Agile Software Development,” IEEE Software, Vol. 15, No. 6, 1998, pp. 56-65. doi:10.1109/52.730844
[16] D. Karlstrom and P. Runeson, “Combining Agile Methods with Stage-Gate Project Management,” IEEE Software, Vol. 22, No. 3, 2005, pp. 43-49. doi:10.1109/MS.2005.59

comments powered by Disqus

Copyright © 2017 by authors and Scientific Research Publishing Inc.

Creative Commons License

This work and the related PDF file are licensed under a Creative Commons Attribution 4.0 International License.