How can you describe the factors which will ensure the successful implementation of SDLC?

Answer 1

How can you describe the factors which will ensure the successful implementation of SDLC? Explain

Factors that will ensure the successful implementation of SDLC are given below:

Software developers will always be in a business setting. Developers will always have to look at the demand of the market, the popular price of different services and the actual earnings of this software. Using SDLC, developers will have a great chance of developing highly likable software for popular use.

There are several factors that will ensure the success of the implementation of SDLC. These factors are not the steps in SDLC rather they are the external factors that will dictate whether SDLC will be followed which in turn assure the success of the developed program.

1. Management Support

Developers, especially those who are working with a company have to work with managers in creating this type of software. Developing software will always have its price since it will involve humans working on software. Developers need to have the support of the management as much as possible since the management will dictate whether they need the product or not. For example, managers will say no to constant prototyping since it will always involve lots of personnel who should be working instead of testing the software.

2. Technical and Business Expertise

There are regular programmers and there are really smart programmers who just know what to do even when the software's objective is presented for the first time. These programmers know what SDLC model to use together with the languages or toolkits that need to be learn to ensure this program is a success. On the other hand, business expertise is also important in software development cycle since they will dictate the demand for particular software. Business expertise is also important in SDLC since they will determine whether the software will eventually be a factor in time and money saving.

3. Focal Point Designation

Some parts of the program should be considered more important than other parts. Choosing which one is very important since it will not only help or destroy the process of SDLC, it will also assist in developing or the burying of the software. Of course each program should be thoroughly checked but with a focal point, there will always be some strong points in the developed software compared to a mediocre service.

4. Well Defined Procedures

In every process there are procedures that seemed identical with another procedure. Developers should have a clear understanding of each phase, the goal of a certain step and evaluate of if the goal of a certain procedure is followed.

5. Proper Documentation for Maintenance:

Granting the results of the software development is a success; it's time to place them in all in papers. Success in building software will only be gauged once they are released to the pubic with ease. Although there will be problems, it's up to the developers to maintain these programs until these are decommissioned. If worst comes to worst and it has to go back to the drawing board, documentation will tell the developers where they might have done it wrong.

Answer: 2

Pros and Cons of Incremental Model:

Pros:

• Delivers an operational quality product at each stage, but one that satisfies only a subset of the clients requirements.
• A relative small number of programmers/developers may be used
• Reduces the traumatic effect of imposing a completely new product on the client organization by providing a gradual introduction.
• There is a working system at all times.
• Clients can see the system and provide feedback.
• Progress is visible, rather than being buried in documents.

Distributes feedback throughout the whole development cycle, leading to more stable artifacts

Cons:

• Each additional build has somehow to be incorporated into the existing structure without degrading the quality of what has been build to date.
• Addition of succeeding builds must be easy and straightforward.
• The more the succeeding builds are the source of enexpected problems, the more the existing structure has to be reorganized, leading to inefficiency and degrading internal quality and degrading maintainability.
• The incremental models can easily degenerate into the build and fix approach.
• Design errors become part of the system and are hard to remove.
• Clients see possibilities and want to change requirements.

Use of Incremental Model

2) When it is too risky to develop the whole system than incremental model is used.

To determine the estimate of project.

03018908040