Week 1

Chapter 1

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?

Both the system analysis and design methodologies help either a large or small business to reap the rewards of utilizing information to tis full capacity. It is important to use both of these methods to make sure the system is created to better the company or customer the system is going to be built to. Like many other products taking the easy route may have a result of a product that insufficient. Another key point to take in mind would be to produce the system right would help avoid making improvements in the future. When using the “engineering” approach would be more beneficial when creating a system for a dangerous workplace. For instance, the approach is concentrated in a loss prevention placing emphasis on physical features of the workplace as a potential cause of injury.

8. How might prototyping be used as part of the SDLC?

Considering that prototyping is building a small model of the information system you want to deign while allowing you to see it on a small scale. When used as a supplement to the SDLC, it enhances the analyst to understand what the user wants. It also allows you to make changes based on your needs and review how the effects of the changes.

Chapter 2

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.

The eight criteria are:

* Cost

* Functionality

* Vendor Support

* Viability of Vendor

* Flexibility

* Documentation

* Response Time

* Ease...