Compare and Contrast Software Development
Step 7: Compare and Contrast Software Development Methodologies
Open source developed software methodology is a model that focuses on making the source code available to the general public for utilization or adjustment from its original design. Open-source code is supposed to be a joint effort, where programmers enhance the source code and share the changes within the community (Fogel, 2015). Open source is free. There are little or no upfront expenses for open-source software. An organization can apply this system for as long as they want without thinking of making payments for any installation, activation and monthly subscription costs. The version is not supported. People require a license to operate them. The terms of a software license are used to release the code. Depending on the terms of license, other people may then download, adjust, and publish their edition back to the community. Open-source is easily modifiable. This is because users are given access to the source code. Security is not guaranteed. This is because there are always hundreds of developers that work on these platforms, and as such, there is a probability that some of them may have malicious intentions. Open-source provides room for potential and external ideas because it allows many developers and users to work on it (Fogel, 2015). The model addresses various cybersecurity issues, and they include buffer overflow, SQL injection, “day zero attacks,” and source-dependent attacks.
Commercially developed software methodologies focus on designing and developing software for sale or licensing to end users or software that is to be used for commercial purposes. These models are paid for. The expenses include but are not limited to base fee for software, annual licensing and support fees, and fees for integration and services. The version is supported, since providers aim to keep the paying customer happy. One requires a license to operate them. This model cannot be modified. Source codes are usually not made available to users, and therefore, there is no way an organization can make any changes to it. Security is guaranteed. Source code is made unavailable to the public, and this makes it less vulnerable to cyber attackers (O’Neill, 2011). A number of cybersecurity issues are addressed by this software development methodology; they encompass source-independent attacks, Denial of Service (DoS) attacks, rootkits, and Trojans.
As the name suggests, internally developed software methodologies are perceived to be for internal use only or models that meet the internal needs of an organization. These models are costly. The expenses vary from a couple of thousands to a few hundred thousand dollars, and the cost depends on the intricacy of the system wanted. The providers of this model offer constant support. One requires a license to operate them. The model cannot be modified. This is because users are denied access to the source code, and it is nearly always kept secret (Tiako, 2019). Security is guaranteed. Software is developed for the organization, and thus secured and controlled by it. The cybersecurity issues that internally developed software methodologies tackle includes the following: man-in-the middle attacks, brute force attacks, and phishing.
Step 8: Software Development Matrix
The pros and cons of open source, commercial, and internally developed software development methodologies
Open-source
Pros
• This model is free. There are little or no upfront expenses for open-source software.
• It provides a free-code analysis to the public.
Cons
• Software assurance needs and expectations are high. This is because it is vulnerable to attacks because the source code is readily available to the public.
Commercial
Pros
• Software assurance needs and expectations are low. This is because it is way more secure since its source code is not availed to the public.
• This software conforms to the functional objective and works as planned.
• The software development plan offer confidence in the interim and end products
Cons
• It is expensive. The expenses such as base fee for software, annual licensing and support fees, and fees for integration and services make this model costly.
Internal
Pros
• Software assurance needs and expectations are low. This is because it is way more secure since its source code is not availed to the public.
• This model does not negatively affect safety and it contributes to the safety of the system.
Cons
• It is very costly. License fees associated with this model can be quite high.
Matrix: comparison
Details Open-source Commercial Internal
Description Focuses on making the source code available to the general public for utilization or adjustment from its original design Focus on designing and developing software for sale or licensing to end users or software that is to be used for commercial purposes Designed and developed for internal use only or to meet the internal needs of an organization
Cost There are little or no upfront expenses for open-source software. Cost is high, and the expenses include but are not limited to base fee for software, annual licensing and support fees, and fees for integration and services.
Costs associated with this system are high
Support The version is not supported The version is supported. This is attributable to the fact that service providers strive to keep the paying customer happy The providers offer constant support.
Licensure One requires a license to operate them One requires a license to operate them One requires a license to operate them
Source code Users are given access to source code. Users are denied access to the source code Users are denied access to the source code
Flexibility They are easily modifiable Cannot be modified Cannot be modified
Security Security is not guaranteed Security is guaranteed. Security is guaranteed.
Ideas Provide room for potential and external ideas Ideas restricted to software developers Ideas restricted to software developers
Cybersecurity issues addressed Buffer overflow, SQL injection, “day zero attacks,” and source-dependent attacks.
Source-independent attacks, Denial of Service (DoS) attacks, rootkits, and Trojans.
man-in-the middle attacks, brute force attacks, and phishing
References
Fogel, K. (2015). Producing Open Source Software: How to Run a Successful Free Software
Project. Sebastopol, CA: O’Reilly Media.
O’Neill, E. (2011). User-Developer Cooperation in Software Development: Building
Common Ground and Usable Systems. Berlin, Germany: Springer Science & Business Media.
Tiako, P. (2019). Software Applications: Concepts, Methodologies, Tools, and Applications:
Concepts, Methodologies, Tools, and Applications. Hershey, PA: IGI Global.
