Modern System Analyst Chapter 1
HW: Ch. 1 problems and exercises
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 appears to be “quick and easy”? What value is provided by using an “engineering” approach?
2. How might prototyping be used as part of the SDLC?
3. Compare Figures 1-2 and 1-3. What similarities and differences do you see?
4. Compare Figures 1-2 and 1-4. Can you match steps in Figure 1-4 with phases in Figure 1-2? How might you explain the differences between the two figures?
5. Compare Figures 1-2 and 1-12. How do they differ? How are they similar? Explain how Figure 1-12 conveys the idea of speed in development.
6. Compare Figures 1-2 and 1-9. How does Figure 1-9 illustrate some of the problems of the traditional waterfall approach that are not illustrated in Figure 1-2? How does converting Figure 1-9 into a circle (like Figure 1-2) fix these problems?
7. Explain how object-oriented analysis and design differs from the traditional approach. Why isn’t RUP (Figure 1-13) represented as a cycle? Is that good or bad? Explain your response
1. It is important to use system analysis and design methodologies because it will ensure that your work is well thought out, complete, and comprehensible to others on your project team. By following the methodologies, support will be provided for a wide range of tasks, including conducting thorough interviews to determine what your system should do, planning and managing the activities in a systems development project, diagramming the system’s logic, and designing the reports your system will generate. You cannot just build a system in a way that appears to be quick and easy because if you develop something, put it on the market and it does not work, you will have to take it off the market and will have to fix the problem. By using an engineering approach, you can go through a cycle and go straight to the analysis part to see what is going on
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 appears to be “quick and easy”? What value is provided by using an “engineering” approach?
2. How might prototyping be used as part of the SDLC?
3. Compare Figures 1-2 and 1-3. What similarities and differences do you see?
4. Compare Figures 1-2 and 1-4. Can you match steps in Figure 1-4 with phases in Figure 1-2? How might you explain the differences between the two figures?
5. Compare Figures 1-2 and 1-12. How do they differ? How are they similar? Explain how Figure 1-12 conveys the idea of speed in development.
6. Compare Figures 1-2 and 1-9. How does Figure 1-9 illustrate some of the problems of the traditional waterfall approach that are not illustrated in Figure 1-2? How does converting Figure 1-9 into a circle (like Figure 1-2) fix these problems?
7. Explain how object-oriented analysis and design differs from the traditional approach. Why isn’t RUP (Figure 1-13) represented as a cycle? Is that good or bad? Explain your response
1. It is important to use system analysis and design methodologies because it will ensure that your work is well thought out, complete, and comprehensible to others on your project team. By following the methodologies, support will be provided for a wide range of tasks, including conducting thorough interviews to determine what your system should do, planning and managing the activities in a systems development project, diagramming the system’s logic, and designing the reports your system will generate. You cannot just build a system in a way that appears to be quick and easy because if you develop something, put it on the market and it does not work, you will have to take it off the market and will have to fix the problem. By using an engineering approach, you can go through a cycle and go straight to the analysis part to see what is going on