Cases on SYSTEM ANALYSIS METHOD

CASES

MIS 470

Prepared For

Muntasir Alam – [MtA]

Prepared By

M Zahid Hossain

ID 081 370 030

28 December, 2010

CASE 1                        SYSTEM ANALYSIS METHOD             PAGE 208

Question 1: Do you think Fred did a thorough evaluation of the fourth-generation software product? What benefits do you think can be derived from using such a tool?

Answer:

No, I think Fred did not do a thorough evaluation of the fourth-generation software product, because he had skipped some of the steps of prototyping approach and bypass several problem solving steps and phases.

Benefit derived from using prototyping approach tool:

  • Reduces development time.
  • Reduces development costs.
  • Requires user involvement.
  • Developers receive quantifiable user feedback.
  • Facilitates system implementation since users know what to expect.
  • Results in higher user satisfaction.
  • Exposes developers to potential future system enhancements.

Question 2: Did Fred view prototyping as an alternative to the traditional systems development life cycle? If so, how should he have viewed it?

Answer:

Yes, Fred viewed prototyping as an alternative to the traditional systems development life cycle, although he did not use it properly.

He should have viewed it as the process of building a model of a system. He should have employed it in building an information system that intuitive and easy to manipulate for end users. In sum Fred should have used it the system development method.


Question 3: What systems Analysis phases would have been skipped by prototyping approach Fred proposed to follow? What do you think would have been the results of the employee benefits project if Fred had approached the project in the manner he originally envisioned?

Answer:

We know there are several phases in system analysis.

Fred skipped the following phases of the system analysis phases:

  1. Comparing present and desired capability properly
  2. Feasibility Analysis
  3. System Historical Data
  4. How the system would be maintained

The results of the employee benefits project if Fred had approached the project in the manner he originally envisioned:

  • The facilities of the fourth generation tools can be rally realized
  • The feasibility of applying this 4th generation tools can be identified
  • The economic benefits can be found
  • How the system can be implemented and maintained can be identified.
  • Complete system development and product life cycle are accomplished

CASE 2                        REQUIREMNET DISCOVERY   PAGE 253

Question 1: Working with your teammates, research any problem that you are aware of with your school’s registration system, financial aid system, or the like. Use the brainstorming techniques to identify the problems’ causes and effects and construct and Ishikawa diagram.

Answer:

The registration process of our university is very old and lengthy process. There are many problems in our registration process:

Types of problems:

  1. It is not online. Students have to come university and do their advising by logging in ftp server.
  2. Security Problem, scope of illegal advising
  3. Server disconnections

Causes of problems:

  1. Using manual system, and not using up-to-date technology
  2. Effective plan of advising process.
  3. Number of courses offered by university is not adequate comparing to the number and students

Effects of problems:

  1. Absence of proper distribution of courses, students cannot get desired courses
  2. Wasting lots of time

Ishikawa diagram


CASE 3                        SYSTEM DESIGN         PAGE 390

Answer to the question no 1

Total Benefit = 26000+34000+41000+55000+66000 = $222,000

Total Cost = 125000+4700+5500+6300+7000 = $148,500

The payback period:

4 years benefit = = 26000+34000+41000+55000 = $156000

4 years cost = 125000+4700+5500+6300 = $141,500

So payback period is less than 4 years.

3 years benefit = = 26000+34000+41000 = $101,000

3 years cost = 125000+4700+5500 = $135,200

So payback period is = 3 + (4th years cost /4th years benefit)

= 3 + (6300/55000)

= 3 + 0.11

= 3.11 years

ROI: (Benefits-Cost)/Cost

= (222000-148500)/(148500)

= 0.4949 or 49.49%

Annual ROI = 0.4949/5 = 0.09899 = 9.9%

Answer to the question no 2

It depends on the situation. For example,

  1. Candidate A will be chosen, if the company has time restrictions, it needs the system as soon possible. Because, candidate A will take the minimum time.
  2. Again Candidate A will be chosen if the company needs more specifications on technological feasibility. Because Candidate A’s system has the most technically feasible solution.
  3. Candidate C can be chosen when company focus on budget, solution at least price, as he/she is offering the most economically  feasible solution
  4. Candidate B can be chosen, if the company considers operation feasibility.

CASE 4                        SYSTEM DESIGN METHODS   PAGE 418

Question a: Think back to your programming courses. What are some problems you have had responding to programming assignments?

Answer:

Problems I have had responding to programming assignments:

  1. Understanding the system requirement
  2. Efficiency,  finishing the project in time
  3. Making the system user friendly
  4. Present the system/solution to the user and my supervisor

Question b: What did Keith learn about working from his own specifications?

Answer:

Keith learned about working from his own specifications are:

  1. Except the Programming knowledge a programmer needs to have good communication and presentation skill. He/she must have the idea how to present his solution to the user properly
  2. A programmer must have confidence, as he/she needs to convince the people with his/her confidence.
  3. Must make the code user friendly also needs it easy to edit.

Question c: As a systems analyst working on the design phase of a project, what types of people did Keith have to communicate with? Why does communication become tougher during systems design than during systems analysis?

Answer:

As a systems analyst working on the design phase of a project, Keith had to communicate with

  • Her supervisor
  • Colleagues, programmers
  • Her Boss
  • System analyst
  • To whom the company is going to sell the system
  • Other departments like account, finance, marketing
  • End users and customers

Communication become tougher during systems design than during systems analysis, because during system analysis the system analyst have to only deal with the system and emphasize on the usefulness to the system designer. The communication channel to a system analyst is low. But in system design the programmer has to communicate with larger people like supervisor, system analyst, the end user and customer.

The system analyst gives the system designer idea what system is needed, the system designer needs to design the system, and not only design, but also make it user friendly, also present it to the people who may not have technological knowledge.

So it becomes tougher during system design.