Final Study Guide
Chapter 10: Information Systems Development
Systems Development: process of creating and maintaining information systems
You can’t buy an information system
Every system designed to address specific problem
System implementation
System testing
Test plan: consists of sequences of actions that users will take when using a new system
Product quality assurance (PQA): the career of testing
Beta testing: process of allowing future system users to try out the new system on their own
System conversion
Pilot = most frequent
Implement entire system on limited portion of business
If fails, is contained within limited boundary
Phased
New system installed in phases across organization
Some systems are so tightly integrated they can’t be done in pieces
Parallel
New system runs in parallel with old until sure everything’s okay
Expensive
Taxing on employees
Plunge
Organization shuts off old system and starts new
Risky (should be avoided)
Life cycle
Systems definition
Define system goals and scope Assess feasibility
Cost
Schedule
Technical
Organizational
Form a project team
Business analysts: specialize in understanding business needs, strategies, and goals and helping businesses implement systems to accomplish their competitive strategies
Systems analysts: IT professionals who understand both business and technology
Requirements analysis – users should determine & approve requirements
Component design
Hardware
Software
Data
Procedures
People
Implementation
Maintenance
Patch: software developers group fixes for high-priority failures into a patch that can be applied to all copies of a product
Service packs: bundling fixes of low-priority problems into large groups
Potential issues
Requirements definition
Asking departments what they need in system
Best time to resolve issues
Requirements changes
Scheduling and budgeting challenges
Technology changes (if technology changes, finish process, then update)
Diseconomies of
Systems Development: process of creating and maintaining information systems
You can’t buy an information system
Every system designed to address specific problem
System implementation
System testing
Test plan: consists of sequences of actions that users will take when using a new system
Product quality assurance (PQA): the career of testing
Beta testing: process of allowing future system users to try out the new system on their own
System conversion
Pilot = most frequent
Implement entire system on limited portion of business
If fails, is contained within limited boundary
Phased
New system installed in phases across organization
Some systems are so tightly integrated they can’t be done in pieces
Parallel
New system runs in parallel with old until sure everything’s okay
Expensive
Taxing on employees
Plunge
Organization shuts off old system and starts new
Risky (should be avoided)
Life cycle
Systems definition
Define system goals and scope Assess feasibility
Cost
Schedule
Technical
Organizational
Form a project team
Business analysts: specialize in understanding business needs, strategies, and goals and helping businesses implement systems to accomplish their competitive strategies
Systems analysts: IT professionals who understand both business and technology
Requirements analysis – users should determine & approve requirements
Component design
Hardware
Software
Data
Procedures
People
Implementation
Maintenance
Patch: software developers group fixes for high-priority failures into a patch that can be applied to all copies of a product
Service packs: bundling fixes of low-priority problems into large groups
Potential issues
Requirements definition
Asking departments what they need in system
Best time to resolve issues
Requirements changes
Scheduling and budgeting challenges
Technology changes (if technology changes, finish process, then update)
Diseconomies of