Systems Design, Implementation, Maintenance, and Review - PowerPoint PPT Presentation

1 / 50
About This Presentation
Title:

Systems Design, Implementation, Maintenance, and Review

Description:

Hardware design. Software design. Database design. Telecommunications design. Personnel design ... Technical & hardware problems. Corporate mergers & acquisitions ... – PowerPoint PPT presentation

Number of Views:74
Avg rating:3.0/5.0
Slides: 51
Provided by: drw71
Category:

less

Transcript and Presenter's Notes

Title: Systems Design, Implementation, Maintenance, and Review


1
Systems Design, Implementation, Maintenance, and
Review
  • Chapter 13

2
Learning Objectives
  • State the purpose of systems design
  • Differentiate logical physical design
  • Outlines key steps in design process
  • Define RFP discuss how it is used to drive
    the acquisition of hardware software
  • Describe techniques used to make systems
    selection evaluations.

3
Learning Objectives
  • List the advantages disadvantages of buying vs.
    developing software
  • Discuss the software development process some
    of the tools used
  • State the purpose of systems implementation
  • Discuss activities associated with systems
    implementation

4
Learning Objectives
  • State the importance of systems software
    maintenance
  • Discuss the activities involved in maintenance
  • Describe the systems review process.

5
Systems Design
6
Table 13.1
7
Logical Design
  • Output design types, format, content, frequency
  • Input design types, format, content, frequency
  • Processing design calculations, comparisons,
    manipulations
  • File database design capabilities and
    organization

8
Logical Design
  • Telecommunications design high-level network
    description
  • Procedures design automated manual
  • Controls security design
  • Personnel job design

9
Physical Design
  • Hardware design
  • Software design
  • Database design
  • Telecommunications design
  • Personnel design
  • Procedures controls design

10
Special System Design Considerations
  • Sign-on procedures
  • Interactive processing
  • Interactive dialog
  • Preventing, detecting, and correcting errors

11
Fig 13.1
12
Fig 13.2
13
Table 13.2
14
Emergency Alternate Procedures Disaster Recovery
  • Telecommunications backup
  • Personnel backup
  • Hardware backup
  • Software database backup

15
Hardware backup
  • Disaster recovery plans
  • Hot site
  • Cold site

16
Software Database Backup
  • Selective backups
  • Incremental backups
  • Image log

17
System Controls
  • Deterrence controls
  • Input controls
  • Processing controls
  • Output controls
  • Database controls
  • Telecommunications controls
  • Personnel controls

18
Fig 13.3
19
Table 13.3
20
Fig 13.4
21
Evaluation Techniques
  • Group consensus
  • Benchmark tests
  • Cost/benefit analysis
  • Point evaluation

22
Table 13.4
23
Fig 13.5
24
Fig 13.6
25
Fig 13.7
26
Systems Implementation
27
Fig 13.8
28
Make or Buy Software?
  • Externally developed software
  • Lower cost
  • Lower risk
  • Ease of installation

29
Make or Buy Software
  • Steps
  • Review needs requirements
  • Acquire software
  • Modify customize
  • Acquire software interfaces
  • Test accept the software
  • Maintain the software

30
Make or Buy Software
  • In-house developed software
  • Chief programmer teams
  • The programming life cycle

31
Fig 13.9
32
Fig 13.10
33
Tools Techniques for Software Development
  • Cross-platform development
  • Integrated development environments
  • CASE tools
  • Structured design
  • Structured programming
  • Structured walkthroughs

34
Table 13.9
35
Fig 13.11
36
Fig 13.12
37
Fig 13.13
38
Additional Implementation Activities
  • Acquiring database and telecommunication systems
  • User preparation
  • Hiring training IS personnel
  • Site preparation
  • Data preparation

39
Additional Implementation Activities
  • Installation
  • Testing
  • Unit testing
  • System testing
  • Volume testing
  • Integration testing
  • Acceptance testing

40
Fig 13.14
41
Fig 13.15
42
Systems Maintenance
43
Reasons for Maintenance
  • Changes in business processes
  • Requests from stakeholders, users, or managers
  • Errors in the program
  • Technical hardware problems
  • Corporate mergers acquisitions

44
Reasons for Maintenance
  • Government regulations
  • Changes in the operating system or hardware

45
Fig 13.16
46
Types of maintenance
  • Slipstream upgrade
  • Patch
  • Release
  • Version

47
Fig 13.17
48
Systems Review
49
Table 13.6
50
Factors to Consider During Systems Review
  • Mission
  • Goals
  • Hardware/ software
  • Database
  • Telecommunications
  • IS personnel
  • Control
  • Training
  • Costs
  • Complexity
  • Reliability
  • Efficiency
  • Response time
  • Documentation
Write a Comment
User Comments (0)
About PowerShow.com