The Department of Defense (DoD) decided to get out of their comfort zone by taking an opposite approach to software development with the utilization of open-source software (OSS) (O’Brien & Marakas, 2011). The DoD considered that OSS is nearly equivalent to most other commercial software and should be used throughout the entire DoD. The DoD is drawn to the open-source software’s positive ability to be easily used and quickly modified. The creation of new developments and decreased expenses for maintenance and ownership are other assets to OSS. The publicly available software continues to improve through the daily review of wide range of peers who searches for deficiencies. The DoD used web based communities with the idea that software
…show more content…
This is accomplished by combining new projects with existing projects. Each project should be easily named with a strong mission statement. The third step is to choose and apply a common license that provides a thorough list of rights and responsibilities for each of the software developers and users. The fourth step is to establish governance to make it possible for multiple companies to successfully work each of the projects in unison. Forkability is an important part of this step, because it recycles an existing project’s software into new projects. The fifth step is to establish collaboration by brainstorming the ideas of everyone involved with the project which develops better projects than only using one person’s ideas. The sixth step is to create project technical direction by determining the interaction and recyclability of the involved components, important technical concerns, platforms involved, and basic developer guidelines. The final step is to announce the existing projects to the public (Scott, Wheeler, Lucas, & Herz, 2011).
References
Scott, J., Wheeler, D., Lucas, M., & Herz, J. (2011). Software Tech News. DoD and Open Source Software: Lessons Learned, Challenges Ahead. Running Open Technology Development Projects. 14(1). 26-31. Retrieved from https://www.csiac.org/wp-content/uploads/2016/02/2011_02_01_DoDandOpenSourceSoftware.pdf
O’Brien, J., Marakas, G. (2011) Management of Information Systems. New York, NY. McGraw-Hill Irwin, Retrieved from
This is accomplished by combining new projects with existing projects. Each project should be easily named with a strong mission statement. The third step is to choose and apply a common license that provides a thorough list of rights and responsibilities for each of the software developers and users. The fourth step is to establish governance to make it possible for multiple companies to successfully work each of the projects in unison. Forkability is an important part of this step, because it recycles an existing project’s software into new projects. The fifth step is to establish collaboration by brainstorming the ideas of everyone involved with the project which develops better projects than only using one person’s ideas. The sixth step is to create project technical direction by determining the interaction and recyclability of the involved components, important technical concerns, platforms involved, and basic developer guidelines. The final step is to announce the existing projects to the public (Scott, Wheeler, Lucas, & Herz, 2011).
References
Scott, J., Wheeler, D., Lucas, M., & Herz, J. (2011). Software Tech News. DoD and Open Source Software: Lessons Learned, Challenges Ahead. Running Open Technology Development Projects. 14(1). 26-31. Retrieved from https://www.csiac.org/wp-content/uploads/2016/02/2011_02_01_DoDandOpenSourceSoftware.pdf
O’Brien, J., Marakas, G. (2011) Management of Information Systems. New York, NY. McGraw-Hill Irwin, Retrieved from