systemsdesignanalysis 1 chapter 21 implementation jerry post copyright 1997

8
1 S S Y Y S S T T E E M M S S D D E E S S I I G G N N A A N N A A L L Y Y S S I I S S Chapter 21 Chapter 21 Implementation Jerry Post Copyright © 1997

Upload: rosa-hodge

Post on 19-Jan-2018

218 views

Category:

Documents


0 download

DESCRIPTION

SYSTEMSDESIGN 3 Hardware administration Software development Support end user development Database administration Advocacy Access to corporate data Software training and support Corporate computing standards MIS Roles  Hardware administration  Software support  Corporate data access  Software development  End user support  Computing standards  DB administration  Advocacy

TRANSCRIPT

Page 1: SYSTEMSDESIGNANALYSIS 1 Chapter 21 Implementation Jerry Post Copyright  1997

1

SSYYSSTTEEMMSS

DDEESSIIGGNN

AANNAALLYYSSIISS Chapter 21Chapter 21

Implementation

Jerry PostCopyright © 1997

Page 2: SYSTEMSDESIGNANALYSIS 1 Chapter 21 Implementation Jerry Post Copyright  1997

2

SSYYSSTTEEMMSS

DDEESSIIGGNN

Implementation ActivitiesImplementation Activities

Install hardware Install software Convert data Train operators Train users Implement security

procedures Evaluate process

Page 3: SYSTEMSDESIGNANALYSIS 1 Chapter 21 Implementation Jerry Post Copyright  1997

3

SSYYSSTTEEMMSS

DDEESSIIGGNN

Hardwareadministration

Softwaredevelopment

Support end userdevelopment

Databaseadministration

Advocacy

Access tocorporate data

Software trainingand support

Corporatecomputingstandards

MIS RolesMIS Roles Hardware administration Software support Corporate data access Software development End user support Computing standards DB administration Advocacy

Page 4: SYSTEMSDESIGNANALYSIS 1 Chapter 21 Implementation Jerry Post Copyright  1997

4

SSYYSSTTEEMMSS

DDEESSIIGGNN

Centralization v. DecentralizationCentralization v. Decentralization

Centralization DecentralizationHardware Share data

Share expensive hardwareControl purchasesControl usageLess duplicationEfficient use of resources

Less chance of breakdownUsers get personalized machinesMicrocomputers are cheaper

Software CompatibilityBulk buying discountsEasier trainingEase of maintenance

Different user preferencesEasier accessCustomization

Data Easy backupEasier to shareLess duplicationSecurity control & monitoring

Not all data needs to be sharedEasier & faster accessControl & politics

Personnel Similar worker backgroundsEasier trainingStraightforward career pathSpecialized staffEasier to see & control costs

Faster response to usersMore time with usersBetter understanding &communicationDifferent career path

Page 5: SYSTEMSDESIGNANALYSIS 1 Chapter 21 Implementation Jerry Post Copyright  1997

5

SSYYSSTTEEMMSS

DDEESSIIGGNN

Conversion OptionsConversion Options

old

Direct cutover

Parallel

Pilot

Phased

dept or component 1dept or component 2dept or component 3dept or component 4

store 1store 2store 3store 4

New

New

old

Page 6: SYSTEMSDESIGNANALYSIS 1 Chapter 21 Implementation Jerry Post Copyright  1997

6

SSYYSSTTEEMMSS

DDEESSIIGGNN

Distributed ComputingDistributed Computing

Data and code run on multiple computers in different locations.

Need a good network. Need really good DBMS. Two-tier.

Client: User Interface, forms Server: Database and code

Three-tier Server

Database Middle-ware

Business rules Code modules

Client User interface, forms

Page 7: SYSTEMSDESIGNANALYSIS 1 Chapter 21 Implementation Jerry Post Copyright  1997

7

SSYYSSTTEEMMSS

DDEESSIIGGNN

Distributed ComputingDistributed Computing

Distributed Object Models CORBA: Common Object

Request Broker Architecture DCOM: Distributed

Computer Object Model, Active-X, (Microsoft)

Goals Location transparency. Scalability and expansion. Substitutability Modularity, replace rules or

DB, or front-end as needed.

Three-tier Forms and User Interface

interact with user on the client.

Events trigger code stored on a middle-ware server. Preferably following a standard distributed object model.

Code retrieves data from various servers as needed.

Page 8: SYSTEMSDESIGNANALYSIS 1 Chapter 21 Implementation Jerry Post Copyright  1997

8

SSYYSSTTEEMMSS

DDEESSIIGGNN

Development Process EvaluationDevelopment Process Evaluation

Project evaluation Did the project meet

forecast times? Did it stay within budget? Did it meet user needs? Estimate size: e.g., function

point evaluation. Set up process for software

maintenance User input for changes. Programmer standards. Documentation

consolidation.

Future project lessons What would you do

differently next time? What steps worked better

than expected? Can development time and

costs be reduced?