CH 13

Chapter 13
Building Information
Systems
VIDEO CASES
Video Case 1: IBM: Business Process Management in a SaaS Environment
Video Case 2: IBM Helps the City of Madrid With Real-Time BPM Software
Instructional Video 1: BPM: Business Process Management Customer Story:
Besthome Store
Instructional Video 2: Workflow Management: Visualized
6.1 Copyright © 2014 Pearson Education, Inc. publishing as Prentice

Management Information Systems, Global Edition
Chapter 13: Building Information System
Overview of Systems Development
• Systems development:
– Activities that go into producing an information system
solution to an organizational problem or opportunity
1.Systems analysis
2.Systems design
3.Programming
4.Testing
5.Conversion
6.Production and maintenance
13.2 Copyright © 2014 Pearson Education

THE SYSTEMS DEVELOPMENT PROCESS
Building a system can be

broken down into six core
activities.
FIGURE 13-4

• Systems analysis
– Analysis of problem to be solved by new system
• Defining the problem and identifying causes
• Specifying solutions
– Systems proposal report identifies and examines alternative
solutions
• Identifying information requirements
– Includes feasibility study
• Is solution feasible and good investment?
• Is required technology, skill available?

• System analysis (cont.)

– Establishing information requirements
• Who needs what information, where, when,
and how
• Define objectives of new/modified system
• Detail the functions new system must perform
– Faulty requirements analysis is leading cause of
systems failure and high systems development
cost

• Systems design
– Describes system specifications that will deliver
functions identified during systems analysis
– Should address all managerial, organizational, and
technological components of system solution
– Role of end users
• User information requirements drive system building
• Users must have sufficient control over design process to ensure
system reflects their business priorities and information needs
• Insufficient user involvement in design effort is major cause of
system failure

Table 13.1 Design Specifications
OUTPUT PROCESSING DOCUMENTATION

Medium Computations Operations documentation
Content Program modules Systems documents
Timing Required reports User documentation
Timing of outputs
INPUT CONVERSION
Origins MANUAL PROCEDURES Transfer files
Flow What activities Initiate new procedures
Data entry Who performs them Select testing method
When Cut over to new system
USER INTERFACE
How
Simplicity TRAINING
Where
Efficiency Select training techniques
Logic CONTROLS Develop training modules
Feedback Input controls (characters, limit, reasonableness) Identify training facilities
Errors Processing controls (consistency, record counts)
ORGANIZATIONAL CHANGES
Output controls (totals, samples of output)
DATABASE DESIGN Task redesign
Procedural controls (passwords, special forms)
Logical data model Job redesign
Volume and speed SECURITY Process design
requirements
Table 13.1 Design Specifications
Access controls Organization structure design
File organization and Overview of Systems Development
Catastrophe plans Reporting relationships
design Audit trails
Record specifications

• Programming:
– System specifications from design stage are translated into
software program code
• Testing
– Ensures system produces right results
– Unit testing: Tests each program in system separately
– System testing: Test functioning of system as a whole
– Acceptance testing: Makes sure system is ready to be used
in production setting
– Test plan: All preparations for series of tests

A SAMPLE TEST PLAN TO TEST A RECORD CHANGE
FIGURE 13-5 When developing a test plan, it is imperative to include the various conditions to be tested, the requirements for each
condition tested, and the expected results. Test plans require input from both end users and information systems
specialists.

• Conversion
– Process of changing from old system to new system
– Four main strategies
1. Parallel strategy
2. Direct cutover
3. Pilot study
4. Phased approach
– Requires end-user training
– Finalization of detailed documentation showing how
system works from technical and end-user standpoint

• Production and maintenance

– System reviewed to determine if revisions needed
– May include post-implementation audit document
– Maintenance
• Changes in hardware, software, documentation, or
procedures to a production system to correct errors,
meet new requirements, or improve processing efficiency
– 20% debugging, emergency work
– 20% changes to hardware, software, data, reporting
– 60% of work: User enhancements, improving documentation,
recoding for greater processing efficiency

Table 13.2 Systems Development
SUMMARY OF SYSTEMS DEVELOPMENT ACTIVITIES

CORE ACTIVITY DESCRIPTION
Systems analysis Identify problem(s)
Specify solutions
Establish information requirements
Systems design Create design specifications
Programming Translate design specifications into

code
Testing Unit test

Systems test
Acceptance test
Conversion Plan conversion

Prepare documentation
Train users and technical staff
Production and Operate the system

maintenance Evaluate the system
Modify the system

CH 13

Uploaded by

Copyright:

Available Formats

CH 13

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

CH 13

Uploaded by

Copyright:

Available Formats

Chapter 13

6.1 Copyright © 2014 Pearson Education, Inc. publishing as Prentice

Overview of Systems Development

13.2 Copyright © 2014 Pearson Education

THE SYSTEMS DEVELOPMENT PROCESS

Building a system can be

13.3 Copyright © 2014 Pearson Education

Overview of Systems Development

13.4 Copyright © 2014 Pearson Education

Overview of Systems Development

• System analysis (cont.)

13.5 Copyright © 2014 Pearson Education

Overview of Systems Development

13.6 Copyright © 2014 Pearson Education

Table 13.1 Design Specifications

OUTPUT PROCESSING DOCUMENTATION

13.7 Copyright © 2014 Pearson Education

Overview of Systems Development

13.8 Copyright © 2014 Pearson Education

A SAMPLE TEST PLAN TO TEST A RECORD CHANGE

13.9 Copyright © 2014 Pearson Education

Overview of Systems Development

13.10 Copyright © 2014 Pearson Education

Overview of Systems Development

• Production and maintenance

13.11 Copyright © 2014 Pearson Education

Table 13.2 Systems Development

SUMMARY OF SYSTEMS DEVELOPMENT ACTIVITIES

Systems design Create design specifications

Programming Translate design specifications into

Testing Unit test

Conversion Plan conversion

Production and Operate the system

13.12 Copyright © 2014 Pearson Education

You might also like