Sign Up Now
Get instant access to over 1 million+ study documents
OR
Already registered? click here to login
By creating your account, you agree to our terms of service, privacy policy and student honor code.
¶ … Software Development Lifecycles
Balancing increasingly complex requirements for new software applications with the constraints of costs, time and resources has made the use of software development lifecycles invaluable. The reliance on software development methodologies is increasing as shortages of programming expertise are leading to many companies relying on virtual project development teams (Batra, Xia, VanderMeer, Dutta, 2010). Virtual teams and the new reality of software development being global in scope are strong catalysts for the continued adoption and best practices of software development lifecycles (Cecil, 2004). The intent of this analysis is to evaluate the advantages and disadvantages of three dominant software development lifecycle methodologies including the Iterative Enhancement Life Cycle Model, the Prototyping Software Life Cycle Model and the Waterfall Software Development Lifecycle.
Advantages and Disadvantages by Software Development Lifecycles
Beginning with the Iterative Enhancement Life Cycle Model, which is designed to overcome the structural and time-based limitations of the Waterfall Model while integrating the benefits of Agile development, this model stresses continual iterations of improvement in code. As this technique is heavily based on Agile-based development methodologies and standards, it is well-suited for Web-based application development in Java, J2EE, C+, C++ and Python programming languages. Advantages of the Iterative Enhancement Life Cycle Model include rapid iteration of system coding modules, greater control of software quality assurance, and greater flexibility in responding to customers' specific requirements in the code (Carey,...
The disadvantages of this specific software development lifecycle are the level of expertise required to implement it as successfully as possible; the level of cross-functional discipline necessary for the teams using it to gain the greatest value from it; and the ability to control scope-creep with each iteration of software development. In larger organizations this approach will also lead to more potential conflict to ensure each specific area of software code is well integrated into the final application.
The Prototyping Software Life Cycle Model concentrates on creating an initial prototype as quickly as possible then continually improving it with reviews and quality assurance analysis over time. The initial prototype built using this approach is based on all known customer requirements and requests, then continually fine-tuned to evolving needs and requirements with each successive iteration (Carey, 1990). The goal of these iterations in this specific software development lifecycle is to eventually create a prototype that the customer will be able to evaluate and determine if the completed application will meet their needs or not (Carey, 1990). This approach has accelerated rapidly with Web-based development tools that can replicate actual system performance, complete with system integration performance simulations and measures of overall system performance.
The advantages and disadvantages of the Prototyping Software Life Cycle Model make this approach especially valuable for creating social media applications where there will be intensive user interaction with the applications once released. The advantages of this specific software development lifecycle include the ability to bring…
References
Batra, D., Xia, W., VanderMeer, D., & Dutta, K. (2010). Balancing agile and structured development approaches to successfully manage large distributed software projects: A case study from the cruise line industry. Communications of the Association for Information Systems, 27, 379.
Bersoff, E.H., & Davis, A.M. (1991). Impacts of life cycle models on software configuration management. Association for Computing Machinery.Communications of the ACM, 34(8), 104-104.
Carey, J.M. (1990). Prototyping: Alternative systems development methodology. Information and Software Technology, 32(2), 119-119.
Cecil, J. (2004). Development of virtual prototyping environments using an information modeling language. IIE Annual Conference.Proceedings,, 1-6.
Joint Application Design Describe how joint application design (JAD) might be considered a better information-gathering technique than the traditional method of requirements gathering? What are its shortcomings? The Joint Application Design (JAD) methodology could potentially be considered a better information gathering methodology compared to more traditional information gathering approaches given its highly structured approach to capturing and validating data. The highly methodical nature of the application design technique that concentrates on identifying
Delphi Study: Influence of Environmental Sustainability Initiatives on Information Systems Table of Contents (first draft) Green IT Current Methods and Solutions Green IT and energy costs Green It and Email Systems Green IT and ICT Green IT and ESS Green IT and TPS Green IT and DSS Green IT and other support systems Green IT and GHG reduction Green IT and the Government Sector Green IT and the Corporate Sector Future Prospects of Green IT in the software industry The paper focuses on how the
Security for Networks With Internet Access The continual process of enterprise risk management (ERM) has become an integral component of successful organizational assessment, because the process of accurately identifying various risk factors, and interpreting their potential advantages and disadvantages, ensures that a business remains capable of anticipating and addressing internal and external contingencies. The following ERM implementation plan for the security of internet-accessible networks is intended to provide a navigable framework
Role of Project Manager in Different Projects The project manager plays an instrumental role in ensuring project success. It could actually be argued that the project manager is the most important person in any project management environment (Meredith and Mantel, 2011). Essentially, the project manager carries the overall responsibility for ensuring the project is successfully planned, designed, executed, monitored, controlled, and closed (Thomsett, 2010; Young, 2013). Whereas the role of the
Human Resources Management - Maintaining a Competitive Edge in the Corporate Marketplace Change continues to reshape the workplace. Today's HR professional is called upon to help the organization retain its competitive edge in the marketplace. Along with representing the best interests of employees, HR professionals assume the role of strategic partner, administrative expert, and change agent. HR assumes a critical role in promoting the vision and shaping the focus of the
Role-based ERP systems are critical for the siloed, highly inefficient architectures of legacy ERP systems to be made more relevant, contribute greater financial performance, and lead to higher levels of overall customer satisfaction. c. Purpose of the study The purpose the study is evaluate how enterprises who adopt role-based ERP system implementations are able to attain higher levels of financial and operations-based performance vs. those that rely on silo-based, more functionally