Business System Analysis

Chapter 1 Problems/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 seems to be “quick and easy?” What value is provided by using an “engineering” approach?

It’s important to use systems analysis and design methodologies when building a system because it ensure the quality of the system being built, it is also tested and you are following an appropriate process that is very structural. If you build a system in whatever way seems to be quick and easy, it can result in a poorly developed system, yes it can be easier and cheaper but in the long run it can require extra work to maintain and more money to maintain it. The value that is provided by using an engineering approach is well designed, precise and systematic. 8.) How might prototyping be used as part of the SDLC?

Prototyping is part of the feasibility analysis phase of SDLC. A simulated prototype of the target system is created which gives the initial fee of the target system. This also helps in pre-analyzing the behavior of the target system.

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 criteria for evaluating alternative packages from custom software developers would be: cost, functionality, and response time. As with custom software, you know from your bid that vendor support, viability of vender, flexibility, documentation and ease of installation is taken care of, as the vendor will install the system, supply appropriate documentation, will ensure flexibility of software (if in the bid) and will offer support for its own software that it wrote for the company.

As far as viability of vender, I would hope that someone checked out the company before giving a bid. When trying to decide which software a developer is going to go with we would want to follow pretty much the same criteria they we followed when going with an off-the-shelf software. Regardless if it’s an off-the-shelf or custom made I would still want the software to have the same features. Will the software developer have some sort of warranty; will they stand behind their product? Will it be easily installed? Cost, usefulness and will the developing company offer some sort of documentation.

Off the shelf software, also known as “shrink-wrapped” or “canned” software, refers to standard (not custom) software applications. When you take off the shelf software out of the package, you automatically agree to the terms and conditions of the software license and agreement. The most common criteria for choosing off the shell software are the following: Cost, Functionality, Vendor Support, Flexibility, Documentation, Response, Time, and Ease of Installation.

4. How might the project team recommending an ERP design strategy justify its recommendation as compared with other types of design strategies?

By using a strategy through cost saving due to facilitated reuse/raw materials inventory and by innovating, integrating and transforming their design processes.