system analysis
•Chapter 1, Problems/Exercises, Questions 1 and 8
1. Why is it important to use systems analysis and design methodologies when building a system? Why not just build the system in whatever way seems to be “quick and easy?” What value is provided by using an “engineering” approach?
Ans: While analyzing and designing a system, we take into consideration the flexibility, scalability, performance, maintainability and testability. When these capabilities are not taken into consideration, we see a high probability for system failure. Conversely, if too much of analysis and design goes into building a system, we see similar symptoms of failure. Considerable skill and practice goes into building successful systems. It is worth to note that only 20% or less of the software projects ever succeed.
8. How might prototyping be used as part of the SDLC?
Ans: Prototyping is the part of feasibility analysis phase of SDLC. A simulated prototype of the target system is created which gives the initial feel of the target system. This also helps in pre-analyzing the behavior of the target system.
•Chapter 2, Problems/Exercises, Questions 3 and 4.
3. In the section on choosing off-the-shelf software, eight criteria are proposed for evaluating alternative packages. Suppose the choice is between alternative custom software developers rather than prewritten packages. What criteria would be appropriate to select and compare among competing bidders for custom development of an application? Define each of these criteria.
Ans: The book states the criteria for off-the-shelf software as: Cost, Functionality, Vendor Support, Viability of Vendor, Flexibility, Documentation, Response Time and Ease of Installation. The only other criteria I could come up with it Ease of Use. When you are trying to pick out a software package from an off-the-shelf type, you want to make sure that your employees will be able to use the software with as little issues as possible. If they are
1. Why is it important to use systems analysis and design methodologies when building a system? Why not just build the system in whatever way seems to be “quick and easy?” What value is provided by using an “engineering” approach?
Ans: While analyzing and designing a system, we take into consideration the flexibility, scalability, performance, maintainability and testability. When these capabilities are not taken into consideration, we see a high probability for system failure. Conversely, if too much of analysis and design goes into building a system, we see similar symptoms of failure. Considerable skill and practice goes into building successful systems. It is worth to note that only 20% or less of the software projects ever succeed.
8. How might prototyping be used as part of the SDLC?
Ans: Prototyping is the part of feasibility analysis phase of SDLC. A simulated prototype of the target system is created which gives the initial feel of the target system. This also helps in pre-analyzing the behavior of the target system.
•Chapter 2, Problems/Exercises, Questions 3 and 4.
3. In the section on choosing off-the-shelf software, eight criteria are proposed for evaluating alternative packages. Suppose the choice is between alternative custom software developers rather than prewritten packages. What criteria would be appropriate to select and compare among competing bidders for custom development of an application? Define each of these criteria.
Ans: The book states the criteria for off-the-shelf software as: Cost, Functionality, Vendor Support, Viability of Vendor, Flexibility, Documentation, Response Time and Ease of Installation. The only other criteria I could come up with it Ease of Use. When you are trying to pick out a software package from an off-the-shelf type, you want to make sure that your employees will be able to use the software with as little issues as possible. If they are