Share This Article:

Improving Parallelism in Software Development Process

Abstract Full-Text HTML Download Download as PDF (Size:1062KB) PP. 489-499
DOI: 10.4236/jsea.2013.69059    3,546 Downloads   5,376 Views  
Author(s)    Leave a comment

ABSTRACT

Software development process basically consists of phases, planned and executed in series: 1) feasibility study; 2) requirements; 3) design and 4) implementation, prior to production and maintenance. At the end of each phase, there may be an official management decision (go/not go) depending upon cost, time or other reasons. Within each phase or across-phases, parallelism or concurrency can be achieved if modularity and/or independence of functionality exist(s). We propose a different approach to software development process that allows an improved parallel planning and execution of development effort beyond modularity and functionality independence. The goal is to shorten development time while possibly cutting cost and maintaining the same intended quality of performance. An example development is sketched.

Conflicts of Interest

The authors declare no conflicts of interest.

Cite this paper

T. Nguyen, "Improving Parallelism in Software Development Process," Journal of Software Engineering and Applications, Vol. 6 No. 9, 2013, pp. 489-499. doi: 10.4236/jsea.2013.69059.

References

[1] R. Pressman, “Software Engineering: A Practitioner’s Approach,” 7th Edition, McGraw-Hill Science/ Engineering/Math, Boston, 2010.
[2] S. Cimic, “Applying Agility to the Parallel Software Development Lifecycle,” Proceedings of Midwest Instruction and Computing Symposium, April 2007.
[3] Software Methodologies, 2013. http://softwaremethodologies.blogspot.com/2009/04/advantages-disadvantages-of-various. html
[4] S. Ambler, “Agile Modeling,” 2013. http://www.agilemodeling.com/style/activityDiagram.htm
[5] F. Hurley, “An Approach to Agile Automation Testing,” 2008. http://www.cigital.com/presentations/ Agile%20Automation%20Testing.pdf
[6] T. N. Nguyen, “Cancer and Deadly Infections in Institutions: Developing Use Cases for an MBE Application to Prevent Another Enron or Barings,” Proceedings of the Eighth International Multi—Conference on Computing in the Global Information Technology, Nice, July 2013.
[7] L. M. Applegate, R. D. Austin and D. L. Soule, “Corporate Information Strategy and Management,” 8th Edition, McGraw-Hill, Boston, 2009.
[8] N. Leeson, “Rogue Trader,” Little Brown Book Group, Boston, 2012
[9] B. Dharan and N. Rapoport, “Enron and Other Corporate Fiascos,” Foundation Press, New York, 2009.
[10] K. F. Brickey, “From Enron to WorldCom and Beyond: Life and Crime after Sarbanes-Oxley,” Washington University Law Quarterly, Vol. 81, No. 2, 2003, pp. 357-401.
[11] C. Celani, “The Story behind Parmalat’s Bankruptcy,” Executive Intelligence Review, Vol. 31, No. 2, 2004.
[12] L. McDonad and P. Robinson, “The Colossal Failure of Common Sense,” Crown Business, New York, 2009.
[13] C. G. Gross, “Claude Bernard and the Constancy of the Internal Environment,” Neuroscientist, Vol. 4, No. 1, 1998, pp. 380-385.
[14] N. Weiner, “Cybernetics or Control and Communication in the Animal and the Machine,” The Technology Press, 1948.
[15] A. S. Beer, “Brain of the firm: Managerial Cybernetics of Organization,” 5th Edition, Allen Lane, 1972.
[16] W. Cannon, “The Wisdom of the Body, The Norton Library,” Norton & Company, New York, 1963.

  
comments powered by Disqus

Copyright © 2018 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.