Chapter 13: Building Info Systems Flashcards
4 Kinds of Structure Organizational Change
- automation
- rationalization
- business process redesign
- paradigm shifts
Automation
assisting employees with performing their tasks more efficiently and effectively
- productivity boost, decreases operational costs
- enhance data collection and analysis
- alters customer service interaction
Rationalization
streamlines standard operating procedures –> instructions and standardized tasks for consistency, quality, and efficiency
- eliminate unnecessary steps, decrease complexity
- focus on essential activities
Total Quality Management (TQM)
makes acheiving quality the responsibility of all within the organization
Six Sigma
measure of quality
goal for driving ongoing quality improvement progress
Business Process Redesign
business processes are analyzed, simplified, and redesigned
- organizes workflows to cut waste and eliminate repetitive tasks
- requires new “vision” how process is organized
- encourages cross-funcitonal collabs
makes sure process aligns with orgs goals
Paradigm Shift
more radical form of business change
- rethinking nature of business org
might encourage more adaptable and open environment, embracing experimentation
- necessitate collaboration against collab and teams
Business Process Redesign Steps
1) identify process for change
2) analyze existing process
3) design new process
4) implement new process
5) continuous measurement
Systems Development Process
new IS –> built as a solution to a problem or set of problems facing an org
systems development –> activities that go into producing an IS to an organizational prob or opportunity
structured problems solved with distinct activities
systems analysis –> systems design –> programming –> testing –> conversion –> production and maintenance
Systems Analysis
analysis of a problem that a firm tries to solve with an info system
1) define problem
2) identify causes
3) specifying solution
- Feasibility study
- info requirements
- systems proposal report
Feasibility Study
is the IS solution achievable
Info Requirements (sys analysis)
- defines the objectives of the new or modified system and develops a detailed description of the functions the new system must perform
- faulty requirements analysis is a leading cause of systems failure
Systems Design
how system will deliver functions identified during systems analysis
- should address all managerial, organizational, and tech components of a solution
ROLE OF END USERS
- user info requirements drive system building
- must have sufficient control over design process to ensure system reflects their business priorities and info needs
- insufficient user involvement in design effort is a major cause of failure
programming
system specification from design stage are translated into software program code
- might be purchased, licensed, or developed through 3rd party vendor
Testing
ensures system produces correct results through extensive and time consuming tests
Unit testing
testing each program separately in the system
System Testing
testing the funcitonality of system in its entirety
Acceptance Testing
final certification that the system is ready for production
Test plan
includes all preparations for tests
- work with end users to develop system testing
- includes conditions to be tested, and requirements and expected results
Conversion
changes from old system to new system
- required end users training and comprehensive documentation
Parallel Strategy
old system and new system run together for a time until everyone is assured the new one is correct
safest, most expensive
Direct Cutover Strategy
replaces old system in entirety with new system on appointed day
- risky, if issues costly
Pilot Study Strategy
new system introduced to pilot small population when working smoothly, installed