Redesigning the Organization with Information Systems

1
Redesigning the Organization with Information
Systems

• Chapter 9

2
Change

• Is the only constant
• Societys needs change
• Way of doing business changes
• Business information needs changes
• Old technologies effectiveness changes
• Old business operating procedures change

3
Systems

• Parts (components)
• Purpose
• Power / politics / position
• process

4
Building a system

• Means to change the four Ps.
• Parts hardware, software, people
• Purpose serve different needs
• Power / position / politics some up and some
  down
• Process should be seamless not just process
  re-engineering

5
Building a new system

• Is a planned organizational change
• Conversion
• Piloting
• Phase out
• In parallel
• Cold turkey

6
Planned organization change

• Multiple perspectives
• Multiple platforms
• Unix, Apple, Microsoft?
• Multiple playing field
• Work arrangement
• Work performance
• Human resource development

7
Four levels of change

• NS, WS, ND, WD
• NS ? Automation like data processing
• WS ? Rationalization of procedures
• ND ? Business process redesign
• WD ? Paradigm shift

8
Line versus Support

• Unless a new system is built for sale, the new
  system is for supporting a new business venture.
• With that purpose in mind, the new system should
  plan and build in support of the companys
  overall strategic plan

9
Methods for creating a new system blueprint

• Enterprise analysis
• Critical success factors analysis
• Both are used to elicit organizational wide
  information requirements

10
To build or not to build

• Capital budgeting model
• Payback
• Portfolio analysis
• Potential benefits (high versus low)
• Project risk (high versus low)
• Scoring analysis

11
System Personnel

• Information system steering committee to allocate
  resources to system projects
• Project teams
• Data administrators
• Systems administrators
• Systems operators
• Network administrators

12
Core activities in the system development process

• System analysis
• System design
• Programming
• Testing
• Conversion
• Production
• Maintenance
• System redesign

13
Systems Analysis

• Stakeholders
• Feasibility study
• Technical feasibility
• Economic feasibility
• Operational feasibilty
• Information requirement

14
Systems Design

• Design specifications
• Input, output
• User interface
• Database design
• Processing
• Manual operating procedures
• Controls and security
• Documentation
• Conversion and training
• Other indirect impacts and changes

15
Logical vs. physical design

• Logical design lays out the components of the
  system and their relationship to each other as
  they would appear to users
• Physical design actually translate logical design
  into a functioning system of people and machine.

16
Testing

• Unit testing conform to design
• System testing function as a whole
• Acceptance testing alpha version, beta version,
  gamma version, patchset

17
Level of complexity and risk

• Project size large, small
• Project structure simple, difficult
• Project technology strange, familiar
• Most complex a large, difficult, unfamiliar
  project could be riskier.
• Change from large to small, difficult to simple,
  strange to familiar