Systems development life cycle Essay

1. Introduction

SDLC, The systems development life rhythm ( SDLC ) is a conceptual theoretical account used in undertaking direction that describes the phases involved in an information system development undertaking, from an initial feasibleness survey through care of the completed application.

Hence an array of system development life rhythm ( SDLC ) theoretical accounts has been created: Fountain, Spiral, rapid prototyping, synchronize and stabilise and Incremental. Although in the academic sense, SDLC can be used to mention to assorted procedures followed during the development of package, SDLC is typically used to mention to the oldest of the traditional theoretical accounts a waterfall methodological analysis.

We will write a custom essay sample on
Systems development life cycle Essay
or any similar topic only for you
Order now

2. Software Engineering Procedure

The SDLC supports a list of of import stages that are indispensable for developers, such as planning, analysis, design, and execution, and are explained more in item subsequently in this study. Traditionally the waterfall theoretical account was regarded as the original: which adhered to a sequence of phases in which the end product of each phase became the input for the following. No unequivocal theoretical accounts exist, but the stairss can be describe and divided as follows:

• Project planning, feasibleness survey, Initiation:

A feasibleness survey is a speedy scrutiny of the jobs, ends and expected cost of the system. Undertakings are normally evaluated in three countries of feasibleness: economical, operational, and proficient. In add-on, it is besides used as a usher to maintain the undertaking on path and to measure the advancement of undertaking ( Post & A ; Anderson, 2006 ) . Thus the end of the feasibleness surveies is to measure alternate systems solutions and to suggest the most executable and desirable concern application for development, ( Obrien & A ; Marakas, 2006 ) states that the feasibleness of a proposed concern system can be evaluated in four major classs

  • Organizational Feasibility: An illustration of how a concern supports the strategic concern precedences of the organisation.
  • Economic feasibleness: Identifies whether expected cost nest eggs, addition gross, increase net incomes and decreases in required investings will transcend the cost of developing and runing a proposed system.
  • Technical feasibleness: can be demonstrated if dependable hardware and package capable of run intoing the demands of a proposed systems can be acquired or developed by the concern in the needed clip.
  • Operational feasibleness: can be measured by the ability and willingness of direction, employees, clients, providers and others to run, usage, and back up a proposed system. for illustration if Tesco ‘s was to alter its package platform at the boulder claies to something wholly different, employees may get down to do to many mistakes and happen ways around utilizing it or merely all together rather, therefore it will neglect to demo operational feasibleness.

• Requirements assemblage and Systems Analysis:

( Hawrzyszkiewycz 2004 ) “ This measure defines the proposed concern solutions and any new or changed concerns procedures ” . The end at this phase is to happen any jobs and try to repair the system or better its productiveness and efficiency. The technique here is to interrupt the system into smaller pieces as it is easier to be explained to others and can be split up amongst different development squad. A draw dorsum of this though is that it takes clip and attempt to reintegrate all of the pieces ( Post & A ; Anderson, 2006 ) .

• Systems design:

Functions and operations are described in item during the design phase, including screen layouts, concern regulations, procedure diagrams and other certification. The end product of this phase will be to depict the new system as a aggregation of faculties or subsystems. ( Hawrzyszkiewycx 2004 ) states that system designs is a two measure procedure,

Broad design: which indentifies ‘ the chief architecture of the proposed system which may include the linguistic communication usage to develop the databases, web constellations, package demands and whether plans are to be developed utilizing internal coders or external contractors.

Detailed design: merely after the design stage is completed the elaborate design stage can be initiated, during this stage the database and plan faculties are design and detailed user and system interaction processs and protocols are documented.

• Build:

Software developers may put in ( or modify and so put in ) purchased package or they may compose new or custom design plans ( Senn 1989 ) . Just like the design stage, this stage is broken up into two separate bomber stages, development and execution. During the execution phase the constituents built during the development are put into operational usage. Normally this means that the new and old systems run parallel until users are trained in system operations and bing procedures converted to the new system. ( Hawrzyszkiewycz 2004 )

• Testing:

During the integrating and trial phase, the package artefacts ‘ , online aid, and trial informations are migrated from the development environment to a separate trial environment. At this point, all trial instances are run to verify the rightness and completeness of the package. Successful executing of the trial suite confirms a robust and complete migration capableness. In add-on, mention informations is finalized for production usage and production users are identified and linked to their appropriate functions. The concluding mention informations ( or links to cite informations beginning files ) and production user list are compiled into the Production Initiation Plan and the system is used by experimentation to guarantee that the package does non neglect, besides the codification is tested iteratively at each degree ( Senn 1989 ) .

• Installation, Implementation and Deployment:

Execution is a critical measure in the deployment of information engineering to back up employees, clients, and other concern stakeholders, the system execution phase involves hardware and package acquisition, package development, proving of plans and processs, transition of informations resources and to boot involves the educating and preparation of terminal users and specializer who will run the new system. All together this is the concluding phase where the undertaking is eventually used by the concern ( Obrien & A ; Marakas, 2006 ) .

• Care:

Once a system is to the full implemented and is being used in concern operation, the care map begins ; this involves the life of the system which may include alterations and sweetenings before its decommissioning. ( Obrien & A ; Marakas, 2006 ) states that the care activity includes a station execution reappraisal procedure to guarantee that freshly implemented systems run into the concern aims set up for them. ( Hawrzyszkiewycx ( 2004 ) supports the statement that care is required to extinguish mistakes in the system during its working life and to better the system in the visible radiation of alterations by monitoring, measuring and modifying operational concern systems to do desirable or necessary betterments.

3. Evaluation and Reason for Adopting SDLC for a little Pc Application

The acceptance of the SDLC for the development of a little application on a personal computer will non be appropriate because the SDLC is merely what is says it is – the Life Cycle of the system package. The SDLC is a procedure usage to pull off clip and resources on a undertaking, from the designation of a demand for the system Initiation ) to turn overing it out to the user ( Implementation ) to de-supporting or no longer necessitating it ( Disposition ) , Each stage of the SDLC requires certification, coverage, and blessing. This assures that a undertaking can non acquire out of manus either by altering the way or going a fiscal black hole and the undertaking patrons are cognizant at every measure of precisely what is traveling on as it is documented. Therefore it is sensible to presume that the development of a little application on a personal computer does non necessitate the acceptance of the SDLC theoretical account whereas a big systems which have squads of designers, analysts, coders, examiners and users must work together to make the 1000000s of lines of custom-written codification that thrust endeavors today, will without a uncertainty demand to follow an SDLC solution to pull off the resources of such a undertaking.

4. Evaluation Of the Traditional SDLC Strengths & A ; Restrictions

The Waterfall Model

The waterfall theoretical account is the most classical consecutive life rhythm ; each stage must be completed in its entireness before the following stage can get down. ( Post & A ; Anderson, 2006 ) states that one advantage of the SDLC is the formality facet which makes it easier to develop employees and to measure the advancement of the development every bit good as guaranting that stairss are non skip, such as user blessing, certification and proving. In add-on with 80 per centum of MIS resources spent of care, adhering to criterions whilst constructing the system makes it easier to modify and keep in the hereafter because of the certification generated and the sustain consistence, nevertheless the formality of the SDLC attack can be debatable as it increases the cost of development and lengthens the development clip ( Post & A ; Anderson, 2006 )

The formality of the SDLC method besides causes jobs with undertakings that are difficult to specify, unlike newer methods like Agile which helps package development squads to react to the capriciousness of edifice package through incremental, iterative work meters, known as dashs ( Cohn, Mike 2006 ) . Agile Methods purpose at leting organisations to present rapidly, alteration rapidly and alter frequently. While, agile techniques vary in pattern and accent, they portion common features, including iterative development and a focal point on inter-action and communicating. Keeping regularity allows development squads to accommodate quickly to altering demands, and working in close propinquity, concentrating on communicating, means squads can do determinations and act on them instantly, instead than wait on correspondence. It is besides of import to cut down non-value adding intermediate artifacts to let more resources to be devoted to merchandise development for early completion.

The SDLC nevertheless works best if the full system can be accurately specified in the beginning. That is, users should cognize what the system should make long before the system is created. ( Post & A ; Anderson, 2006 ) further explains that because of the rigidness of the SDLC, the development of more modern applications are hard, hence the combination of bing SDLC theoretical accounts and the creative activity of other options theoretical accounts and methodological analysiss are adopted as defined subsequently in this paper.


  • Easier to utilize.
  • Easier to pull off because of rigidness
  • Phases are completed at specific stage intervals
  • Requirements are really good understood.


  • range accommodation during the life rhythm can kill a undertaking
  • Working package is non produced until the life rhythm is complete.
  • Not suited for long and on-going undertakings.
  • In appropriate where demands are at a moderate to high hazard of altering
  • Alternative development mythologies

One direction advantage of the traditional SDLC method is the consecutive series of undertakings ; on the other manus utilizing the traditional SDLC has many drawbacks. For illustration, when following a traditional SDLC methodological analysis, the stiff concatenation of stages may later do it impossible for developers to improved ways to supply functional demands as the undertaking is being built, which consequences in the interior decorators remaking their work. Alternatively coders should be involved in the planning and design stages, so that they may be able to place betterments much earlier in the procedure, therefore heightening the effectivity of undertaking activities, ( FFIEC IT Handbook ( 2009 ) .

Development solutions such as iterative and Rapid prototyping address many of the defects of a traditional SDLC. And a brief description of two the newer methodological analysiss are outlined below along with some advantages and disadvantages for comparing intents.

Agile Development Model

Agile package development is a conceptual model for set abouting package technology undertakings. Agile methods effort to minimise hazard and maximise productiveness by developing package in short loops and de-emphasizing work on secondary or interim work artifacts ‘ .

The cardinal differences between agile and traditional methodological analysiss are as follows:

  • Development is incremental instead than consecutive.
  • Peoples and interactions are emphasized.
  • Working package is the precedence instead than elaborate certification.
  • Customer coaction is used, instead than contract dialogue.
  • Reacting to alter is emphasized, instead than extended planning.

Rapid Prototyping theoretical account

Rapid prototyping is a procedure for making a realistic theoretical account of a merchandise ‘s user interface ( Najjar, L. J. ( 1990 ) , Using rapid prototyping, you model the expression and feel of the user interface without puting the clip and labor required to compose existent codification ( Najjar, L. J. ( 1990 ) .


  • Saves clip and money
  • Promotes consistence in user interface design
  • Allows early client engagement
  • Reduces clip required to make a merchandise functional specification


  • Normally does non bring forth reclaimable codification
  • Lacks an obvious fillet point

5. Decision

It can be seen from the above comparing that differing doctrines can bring forth radically different positions of a system. However, both the Traditional SDLC and the options produce valid working systems every bit good as their portion in drawbacks

The “ one size fits all ” attack to using SDLC methodological analysiss is no longer appropriate. Each SDLC methodological analysis is merely effectual under specific conditions. ( Traditional SDLC methodological analysiss are frequently regarded as the proper and disciplined attack to the analysis and design of package applications but the drawback is that it takes a considerable sum of clip and all of the system inside informations have to be specified upfront.

Methodologies like Rapid Prototyping instead are a via media of rigidness and no rigidness. These new intercrossed methods were created to bridge the spread with the development of more modern application developments demands. Newer the less methodological analysiss like Agile are most appropriate when volatility and uncertainness exist in the development demands, and the SDLC is good when the demands are already defined.

6. Bibliography

  • Najjar, L. J. ( 1990 ) . Rapid prototyping ( TR 52.0020 ) . Atlanta, GA: IBM Corporation. hypertext transfer protocol: //
  • FFIEC IT Handbook ( 2009 ) . Alternative development methodological analysiss http: //
  • Senn James A. ( 1989 ) , Analysis & A ; Design of Information Systems, Introduction to Information Systems, pg27 – 32 Ch1 McGraw-Hill Co- Singapore
  • Post. G & A ; Anderson. D ( 2006 ) , Management Information Systems, Organizing Business Solutions, pg 448 – 459 Ch 4 McGraw-Hill Co- New York
  • Igor Hawryszkiewycz. ( 1998 ) , Introduction to System Analysis & A ; Design, The Development Process, pg120 – 136 Ch 7 Prentice Hall- Australia
  • Obrien A. O & A ; Marakas.M. ( 1989 ) , Management Information Systems, Introduction to Information Systems, pg27 – 32 Ch1 McGraw-Hill Co- Singapore

Hi there, would you like to get such a paper? How about receiving a customized one? Check it out