Posted: December 11th, 2022

Software Development Life Cycle Assessment

Software Development Life Cycle Assessment

Basic models and methodologies of the software development life cycle
Waterfall model is one of the SDLC models. The model incorporates a stiff structure that demands all requirements in the system to be described at the very beginning of a project. Only then can the design and development phases start. Once development has been completed, the product goes through tests against the initial needs and rework is assigned. Another SDLC model is known as prototyping. In this methodology, the focus of the design team is to generate an early model of the new software, system or application. This prototype will not have full functionality or be meticulously tested, but will provide external clients with a sense of what is to come (Crookshanks, 2014). Then, opinions can be collected and executed all through the rest of the SDLC stages.
The spiral methodology is also an SDLC model. This model enables teams to take on numerous SDLC models based on the given project’s risk patterns. It utilizes a chronological approach while functioning like a prototype. In this manner, it delivers an incomplete system but is under continuous assessment. The largest differentiating factor though is that it puts focus on risk analysis. DevOps is yet another SDLC model. As its name suggests, DevOps is built on the premise that development teams and operational teams need to work together so as to update delivery and support (Crookshanks, 2014). The agile model is in this list of SDLC models as well. This model perceives “fast failure” as a positive thing. The approach generates constant release cycles, featuring tiny, incremental changes from the prior release. The product is tested at each iteration. The model thus assists teams to spot and tackle minute issues on projects before they change to more significant problems.
Development methodology that fits my organization
The spiral model best fits my organization. This is because it allows development teams to create highly customized products, and integrate user feedback in the initial phases of the project. This way, customer satisfaction is maximized.
Phases of the software life cycle
The requirement gathering and analysis is the first phase. This is the stage where the requirements of a business are collected. The phase entails identifying the users of the system, how the system will be utilized, and data that should be input and output in the system. The requirements are then assessed for their soundness. The second phase is the design phase. This is where the software and system is developed from the requirement specifications gathered in phase one. System design assists in specifying system and hardware requirements and also assists in describing the general architecture of the system (Fujita & Mejri, 2016). The third phase pertains to implementation. In this stage, the task is divided into units and actual code is initiated. This phase is the major focus of for the developer because this is where coding is initiated. Notably, it is the longest stage of the SDLC.
Testing is the fourth phase. The code is tested against requirements after being developed. This is aimed at ensuring that the product is really tackling the needs identified and collected during the first phase. The types of functional testing done thus include system testing, unit testing, acceptance testing, integration testing, and non-functional testing (Everett & Raymond McLeod, 2007). Deployment is the fifth phase. This is the stage where the product is deployed to the clients for their use after successful testing. Maintenance is the last phase. In this phase, the software is maintained and improved from time to time to adjust to changes.
Security principles and their application throughout the software life cycle
i. Integrate an industry-standard security model-this approach purposes to instill best practices and rock-solid security design principles into the organization.
ii. Educate the staff on software security-this focuses on ensuring that all the staff involved in the project gains knowledge and becomes updated on software security standards to decrease unsafe design and development practices.
iii. Assigning responsibility on the security of software-This will entail developing a software security group to teach, evaluate, and put into effect security measures across the organization.
iv. Setting up and instituting an all-inclusive risk management process-this entails pointing out main security risks within the cycle and implementing a mitigation plan. These are also key factors to ensuring the appropriate security design, and ensuring an efficient guide in SDLC implementation with regards to engaging with stakeholders and regulating scope-creep.
Elements of a maturity model
The maturity model has five main elements. Level 0 is one of the elements. There is no stable environment for implementation at this level. As such, the goals and processes of an organization are not perceived centrally during execution projects and there is hardly communication. Level A is another element. At this level, the basis of activities is the results of preceding projects and the demands of the present one (Bonham, 2018). Past successes can be replicated because of the steady planning and control. Another element is level B. This is where the implementing process is documented all through the organization instead of per aspect. Level C is an element as well. This is where projects are initiated, and the process management or change management supervises them (Bonham, 2018). The last element is level D. The entire organization puts focus on the constant enhancement of the implementation processes. The organization has the means to identify weaknesses and fortify the execution process proactively.

References
Bonham, S. S. (2018). Actionable Strategies Through Integrated Performance, Process,
Project, and Risk Management. Artech House.
Crookshanks, E. (2014). Practical Software Development Techniques: Tools and Techniques
for Building Enterprise Software. New York, NY: Apress.
Everett, G. D., & Raymond McLeod, J. (2017). Software Testing: Testing Across the Entire
Software Development Life Cycle. Hoboken, NJ: John Wiley & Sons.
Fujita, H., & Mejri, M. (2016). New Trends in Software Methodologies, Tools and
Techniques: Proceedings of the Fifth SoMeT 06. Amsterdam, Netherlands: IOS Press.

Check Price Discount

Study Notes & Homework Samples: The role of mutual funds in Saudi Arabia »Marketing & Online Advertising