Analysis III – Requirements fulfillment

To transform the structured requirements into several design strategies (high-end, middle, low-end) and select the one that is most likely to result in the desired IS.

 

A design strategy is a combination of system features, hardware and software needs, and acquisition method that characterize the nature of the IS and how it will be developed.

 

Deliverables à Systems proposal

 

System features:

1.  Minimum requirements for the new system

mandatory vs essential vs desirable features

2.  System development constraints

firm vs flexible restrictions

 

Hardware and software needs:

Figure 13.1

Step

To find out:

To project:

Inventory computer hardware

Type, status, estimated age, projected life, physical location, responsible party, financial arrangement of equipments on hand.

How well can the needs for hardware be met?

Estimate workloads

Figure 13.2

Will the system capable of handling current and future workloads?

Evaluate hardware
  • Average transaction time
  • Total volume capacity of the system
  • Idle time of the CPU
  • Memory size

For each kind of equipment available that appears to meet projected needs.

Whether new hardware is necessary?

Evaluate packaged software

Figure 13.7

Whether packaged software is suitable for part of or all the system?

Choose vendor

Figure 13.5

What extra vendor support services can be negotiated?

 

Acquisition method (Figure 13.3)

Method

Advantages

Disadvantages

Buy
  • Cheaper in the long-run
  • Customizable
  • Tax advantages
  • Full control
  • High initial cost
  • Risk of obsolescence
  • Risk of committing to a wrong choice
  • Full responsibility

Lease
  • No capital is tied up
  • No financing
  • Cost less than renting
  • No ownership when lease expires
  • Penalty for lease termination
  • More expensive than buying

Rent
  • No capital is tied up
  • No financing
  • Easy to change
  • No ownership
  • Most expensive

 

Design strategy selection – cost and benefit analysis

Tangible benefits: increase in processing speed, information accessibility, timeliness of information accessed, higher productivity, etc..

Tangible costs: cost of equipment, cost of development, etc..

Intangible benefits: improved decision-making, more competitive, improved good will, increased job satisfaction, etc..

Intangible costs: less competitive, deteriorated image, ineffective decision making, etc..

 

Systems proposal – a summary to management describing what the systems analyst has learned about the business and what is needed to improve its performance

 

Section

Content

Cover letter
  • Team members
  • Objectives of the study
  • Presentation time and place

Title page
  • Project name
  • Team members
  • Date

Table of contents
  • Useful for over 10 pages long

Executive summary

(Figure E14.1)
  • Who, what, when, why, and how of the proposal in 250 to 375 words
  • Recommendations
  • Management action

Systems study outline

(Figure E14.2)
  • Analysis I’s findings

Systems study details

(Figure E14.3)
  • Analysis II’s findings

Systems alternatives
  • Design strategies

Recommendations
  • Costs and benefits analysis

Summary
  • Importance of the project
  • Project feasibility

Appendices
  • Correspondence, graphs, diagrams