System Development - Assignment Example

System Development Life Cycle (SDLC) 0 Introduction System Development Life Cycle (SDLC) refers to the multistep process that starts with the initiation, analysis, design, and execution, and proceeds all the way through the maintenance and disposal of the system. The typical activities include determining budgets, gathering system necessities, and writing in depth user documentation. The activities implementation for the duration of each systems development project varies. The SDLC begins with a business need, followed by an assessment of the purpose a system must have to please the need, and ends when the gain of the system no longer exceed its maintenance costs (Radack, 2009).

As SDLC is comprised of seven distinct stages: planning, analysis, design, development, testing, execution, and maintenance. This paper takes a detailed explanation on whether or not all systems development projects use the SDLC. Further, will determine whether or not it’s wise to recommend the SDLC as a CTO for all my organizations’ technology projects.To Explain Whether Or Not, All Systems Development Projects Use The SDLCIn every project there must be activities associated with project initiation, planning, analysis, design, execution, and deployment.

The use of the SDLC framework is mandatory for all major information technology development projects and is also applicable for smaller IT efforts. The nature of the project determines the best approach to use. In order for the information system to succeed, it’s mandatory to use all seven phases. Although SDLC has many different versions of information systems, follow-up with different steps as well (Avison & Fitzgerald 2006).Sarkar et al (2006), note that there are advantages and disadvantages in the SDLC systems.

By understanding and learning these differences will help in the process of considering using an SDLC system. Whether or not you or your organization will ever become interested in using these systems; the knowledge of their existence and the capabilities that they offer will be an asset of ones awareness.To determine Whether or not you would recommend the SDLC as a CTO for all your Organization’s Technology ProjectsThe Software development lifecycles (SDLC) help to describe the processes, procedures, and artefacts a team is used in an organization.

When recommending the SDLC implementation, all of these methodologies they have places where they work well and where they do not. Cockburn (2000) indicates that the factors that go into selecting an SDLC include team location, team size, the risk of errors, when to market, the number of probable changes, how long the project last, and maintenance releases will be required.Further, understanding the basic concepts of software development methodologies is necessary to be able to evaluate the best software development lifecycle (SDLC) methodologies.

Since, all software projects go through the phases of requirements gathering, business analysis, system design, execution, and quality assurance assessment. Furthermore, when opting for an SDLC for both software development and software maintenance, the criteria will take into consideration my organization size, the type of product, duration from development to release, my team location, and my team experience (Gruner et al., 2007).Moreover, construction of quality software is not an easy activity.

Using SDLC for developing the software reduces risk, increases quality, develops visibility, makes project management easier, and presents a standardization that allocate more than one developer to work on a project. On the other hand, developing software without an SDLC increases the chance of failure of the team and the project (Fitzgerald, 1998).ReferencesAvison, D., & Fitzgerald, G. (2006). Information systems development: Methodologies,techniques and tools (4th ed.). London, UK: McGraw-Hill.

Cockburn, A. (2000). Selecting a project’s methodology. Software, IEEE 17, 4. doi:10.1109/52.854070 Retrieved fromhttp://www.eee.metu.edu.tr/~bilgen/Cockburn647.pdf Fitzgerald, B. (1998). An empirical investigation into adoption of systems developmentmethodologies. Information & Management 34, 317-328.Gruner, S., Klopper, R., & Kourie, D. (2007). Assessment of a framework to compare softwareDevelopment methodologies. Proceedings of the 2007 Annual Research Conference ofthe South African Institute of Computer Scientists and Information, 56-65.doi:10.1145/1292491.1292498.Sarkar, S.

, Sindhgatta, R., & Pooloth, K. (2008). A collaborative platform for applicationknowledge management in software maintenance projects. Proceedings of the 1stBangalore Annual Compute Conference . doi: 10.1145/1341771.1341774Radack, S. (2009).The System Development Cycle. Retrieved from http://csrc.nist.gov/publications/nistbul/april2009_system-development-life-cycle.pdf