software development

Software Development Matrix
Name of the student
University

Abstract
As technology advances, systems and methodologies for development of specialized IT systems have to kick in. Today, very many methods for software development exist. However, each project has its specific demands and therefore calls for a particular methodology (Masood, Shang & Yousaf, 2014). Although all these methods are geared toward the same finish line, they comprise varying procedures and approaches, which are best suitable for varying situations. It is therefore critical to determine the needs of a project and fit in with the right methodology matching the requirements. The establishment of the best methodology demands an analysis of the pros and cons of each of the methods. It is also important to note that no single method that is perfect, they all have defects. Due to the latter, as for the given projects, the advantages of a method must be weighed against the disadvantage in determining the suitability of the technique. For a system to be viable, the benefits must outweigh the disadvantages. This paper explores the various ways of software development and lists the pros and the cons. The article also contains the main software assurance concert of all the methodologies.
Software Development Methodology Pros and Cons Software Assurance Concerns
Waterfall Model Pros: uses clear stepwise structure
The end goal is determined early
Excellent transfer of information after each step
Cons: difficult to make changes
Client/user input is minimal
Testing is delayed till completion May not meet user/client needs adequately as their involvement is limited
Prototype Model Pros: extensive user/client involvement
Early detection of errors
Users can understand the system better
Cons: prototypes may confuse users in using the actual
The project can easily exceed original plans
Too much investment in building prototypes rather than the actual system Developers may try using available prototypes even in cases where they are not optimal
Agile Software Development Pros: excellent response to a change
Tolerant of uncertainty
Fast review cycles
Flexibility in releasing features
Minimal up-front
Cons: Flexibility may lead to a delay
Unpredictable
Poor human resource management The project is not all figured out at the start, and this may lead to the development of excellent or poor software making it unpredictable
Rapid Application Development Pros: Requires minimal coding
Prototypes can be made in little time
Components are independent for easy update
Cons: requires highly skilled labor
Useful for systems that can be modularized only
Demands commitment from the user and the developer for frequent user interfacing This method demands frequent user interfacing, and the developers may not be fully committed leading to failure of the project
Dynamic Systems Development Pros: high requirement evolution flexibility
User/client is involved in the process
Strict time and budget adherence
Emphasizes testing
Cons: development is progressive
Demands full commitment to DSDM process
Requires business and technically skilled labor
Demands continuous user involvement
Requires heavy documentation The software is user customized and, therefore, use of already existing software may result in failure
Spiral Model Pros: highly flexible
Easy to monitor
Suitable for complex projects
Emphasizes client satisfaction
Employs robust risk analysis
Highly customizable
Cons: expensive to implement
Risk analysis demands expertise
Non-ideal for small projects
The success of the spiral model is highly dependent on risk analysis and an error in this process may result in the overall failure of the whole project
Extreme Programming Pros: pays excellent attention to time and cost
Employs simplicity in coding
Traceable progress and accountability
Allows all team members to participate in the design stage
Cons: focused on the code more than the design
Lacks code quality assurance
Not suited for geographically separated developers
In pursuit of simplicity, the code quality may be compromised leading to ineffective software
Feature-Driven Development Pros: suitable for large projects
Built upon industry’s best-recognized practices
Risk reduction through the building in parts
Cons: not suitable for small projects
Extensive reliance on the chief programmer
Documentation is absent The lack of documentation makes the software difficult to update
Joint Application Development Pros: involves extensive research
High-quality assurance
Low cost
Cons: may consume a lot of time in the planning stage
Implementation requires expertise The success of the method is highly dependent on the implementation stage at which in case of an error the system may be ineffective
Lean Development Pros: quick delivery of the MVP
Minimal expenses
Great team motivation
Cons: documentation requires perfection
Requires highly skilled developers While the developers may be motivated about the finished product, they may lose focus on the objectives demanding intense supervision or failure may occur
Rational Unified Process Pros: precise documentation
Little requirement for integration
Cons: requires intensive expertise
Complicated to understand The methodology procedure is complicated, and a small deviation may result in full failure of the project
Scrum Development Pros: highly adaptable to changes
Testing is conducted after each iteration
Cons: Inefficient documentation
Demand specialized control Too much timeframe adjustments make timely delivery almost impossible
ReferenceMasood, Z.

, Shang, X., & Yousaf, J. (2014). Usability Evaluation Framework for Software Engineering Methodologies. Lecture Notes on Software Engineering, 2(3), 225-232. doi: 10.7763/lnse.2014.v2.127