View
214
Download
0
Tags:
Embed Size (px)
Citation preview
6.1 Copyright © 2014 Pearson Education, Inc. publishing as Prentice Hall
Building Information Building Information SystemsSystems
Chapter 13
VIDEO CASESVideo Case 1: IBM: Business Process Management in a SaaS EnvironmentVideo Case 2: IBM Helps the City of Madrid With Real-Time BPM SoftwareInstructional Video 1: BPM: Business Process Management Customer Story: Besthome StoreInstructional Video 2: Workflow Management: Visualized
13.2 Copyright © 2014 Pearson Education
Management Information Systems, Global EditionChapter 13: Building Information System
• Systems development: – Activities that go into producing an information
system solution to an organizational problem or opportunity
1.Systems analysis2.Systems design3.Programming4.Testing5.Conversion6.Production and maintenance
Overview of Systems Development
13.3 Copyright © 2014 Pearson Education
Management Information Systems, Global EditionChapter 13: Building Information System
Building a system can be broken down into six core activities.
FIGURE 13-4
THE SYSTEMS DEVELOPMENT PROCESS
13.4 Copyright © 2014 Pearson Education
Management Information Systems, Global EditionChapter 13: Building Information System
• 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?
Overview of Systems Development
13.5 Copyright © 2014 Pearson Education
Management Information Systems, Global EditionChapter 13: Building Information System
• 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
Overview of Systems Development
13.6 Copyright © 2014 Pearson Education
Management Information Systems, Global EditionChapter 13: Building Information System
• 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
Overview of Systems Development
13.7 Copyright © 2014 Pearson Education
Management Information Systems, Global EditionChapter 13: Building Information System
Overview of Systems DevelopmentTable 13.1 Design Specifications
Table 13.1 Design Specifications
OUTPUTMediumContentTiming
INPUTOriginsFlowData entry
USER INTERFACESimplicityEfficiencyLogicFeedbackErrors
DATABASE DESIGNLogical data modelVolume and speed requirementsFile organization and designRecord specifications
PROCESSINGComputationsProgram modulesRequired reportsTiming of outputs
MANUAL PROCEDURESWhat activitiesWho performs themWhenHowWhere
CONTROLSInput controls (characters, limit, reasonableness)Processing controls (consistency, record counts)Output controls (totals, samples of output)Procedural controls (passwords, special forms)
SECURITYAccess controlsCatastrophe plansAudit trails
DOCUMENTATIONOperations documentationSystems documentsUser documentation
CONVERSIONTransfer filesInitiate new proceduresSelect testing methodCut over to new system
TRAININGSelect training techniquesDevelop training modulesIdentify training facilities
ORGANIZATIONAL CHANGESTask redesignJob redesignProcess designOrganization structure designReporting relationships
13.8 Copyright © 2014 Pearson Education
Management Information Systems, Global EditionChapter 13: Building Information System
• 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
Overview of Systems Development
13.9 Copyright © 2014 Pearson Education
Management Information Systems, Global EditionChapter 13: Building Information System
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.
FIGURE 13-5
A SAMPLE TEST PLAN TO TEST A RECORD CHANGE
13.10 Copyright © 2014 Pearson Education
Management Information Systems, Global EditionChapter 13: Building Information System
• Conversion – Process of changing from old system to new system– Four main strategies
1. Parallel strategy2. Direct cutover3. Pilot study4. Phased approach
– Requires end-user training– Finalization of detailed documentation showing how
system works from technical and end-user standpoint
Overview of Systems Development
13.11 Copyright © 2014 Pearson Education
Management Information Systems, Global EditionChapter 13: Building Information System
• 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
Overview of Systems Development
13.12 Copyright © 2014 Pearson Education
Management Information Systems, Global EditionChapter 13: Building Information System
Table 13.2 Systems Development
SUMMARY OF SYSTEMS DEVELOPMENT ACTIVITIES
CORE ACTIVITY DESCRIPTION
Systems analysis Identify problem(s)Specify solutionsEstablish information requirements
Systems design Create design specifications
Programming Translate design specifications into code
Testing Unit testSystems testAcceptance test
Conversion Plan conversionPrepare documentationTrain users and technical staff
Production and maintenance
Operate the systemEvaluate the systemModify the system