viki
05-18-2010, 10:39 PM
Note: All the Assignments Solution which are provided on vuhelp are just like helping material for the students, U must make the required changes in it.
Q. 1: How can you describe the factors which will ensure the successful implementation of SDLC? Explain at least three.
Factors for Success
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 softwares 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; its 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, its 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.
(Marks: 10)
Q. 2: List down the pros and cons of Incremental Model? Also mention when to use the Incremental Model?
(Marks: 10)
Use of incremental model
An Incremental Pharmacy Informatics Model for Use in a Rural Hospital.
to estimate the retention indexes of aromatic compounds .
for Developing Computer-Based Learning Environments for Problem-Based Learning
Advantages
Generates working software quickly and early during the software life cycle.
More flexible - less costly to change scope and requirements.
Easier to test and debug during a smaller iteration.
Easier to manage risk because risky pieces are identified and handled during its iteration.
Incremental model includes use of the software by user to for changes.
This model dose not effect anyones business values because they provides core of the software which customer needs, to the customer first, which will help him/her to keep running his/her business.
It is flexible and easy to manage more manageable process and better software making and better software structure
Better risk management because you can confirm the outcome by the customer after every version that what ever u are making is according to plan or not and fix it in next version etc.
Testing is easy
Working functionality is produced earlier computation of value to cost ratio
Reduces risks of change in user requirements
Provides clients flexibility in decision making.
Risk management is incremental
Smaller scope for change in user requirements
Disadvantages
Each phase of an iteration is rigid and do not overlap each other.
Problems may arise pertaining to system architecture because not all requirements are gathered up front for the entire software life cyc
Each phase of an iteration is rigid and do not overlap each
other.
Problems may arise pertaining to system architecture because
not all requirements are gathered up front for the entire software life cycle
Larger picture cannot be seen until the entire system is built
Difficult to break down the total system at early stage of product development to determine
Reasonable increments
Q. 1: How can you describe the factors which will ensure the successful implementation of SDLC? Explain at least three.
Factors for Success
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 softwares 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; its 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, its 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.
(Marks: 10)
Q. 2: List down the pros and cons of Incremental Model? Also mention when to use the Incremental Model?
(Marks: 10)
Use of incremental model
An Incremental Pharmacy Informatics Model for Use in a Rural Hospital.
to estimate the retention indexes of aromatic compounds .
for Developing Computer-Based Learning Environments for Problem-Based Learning
Advantages
Generates working software quickly and early during the software life cycle.
More flexible - less costly to change scope and requirements.
Easier to test and debug during a smaller iteration.
Easier to manage risk because risky pieces are identified and handled during its iteration.
Incremental model includes use of the software by user to for changes.
This model dose not effect anyones business values because they provides core of the software which customer needs, to the customer first, which will help him/her to keep running his/her business.
It is flexible and easy to manage more manageable process and better software making and better software structure
Better risk management because you can confirm the outcome by the customer after every version that what ever u are making is according to plan or not and fix it in next version etc.
Testing is easy
Working functionality is produced earlier computation of value to cost ratio
Reduces risks of change in user requirements
Provides clients flexibility in decision making.
Risk management is incremental
Smaller scope for change in user requirements
Disadvantages
Each phase of an iteration is rigid and do not overlap each other.
Problems may arise pertaining to system architecture because not all requirements are gathered up front for the entire software life cyc
Each phase of an iteration is rigid and do not overlap each
other.
Problems may arise pertaining to system architecture because
not all requirements are gathered up front for the entire software life cycle
Larger picture cannot be seen until the entire system is built
Difficult to break down the total system at early stage of product development to determine
Reasonable increments