Studied by 0 people
Looks like no one added any tags here yet for you.
Automation
Increases efficiency and replaces manual tasks
Rationalization of procedures
Streamlines standard operating procedures
Total Quality Management
Makes achieving quality an end responsibility of all people and functions within an organization
Six sigma
A specific measure of quality; most companies quality but use it as a goal for driving ongoing quality improvement programs
Business process redesign
Analyze, simplify, and redesign business processes and reorganize workflow, combine steps, and eliminate repetition
Paradigm Shift
Rethink nature of business, define new business model, and change nature of organization
Business Process Management
Variety of tools, methodologies to analyze, design, optimize processes and use by firms to manage business process redesign
Identify processes for change
Analyze existing processes
Design the new process
Implement the new process
Continuous measurement
Steps in BPM:
Waterfall Systems Development
A sequential, multistage system development process
Waterfall Systems Development
Work on the next stage cannot begin until the results of the current stage are reviewed and approved or modified as necessary
Investigation
Analysis
Design
Construction
Integration
Testing and implementation
Six phases of Waterfall Systems Development:
Systems Investigation
Initial phase in the development whose purpose is to gain a clear understanding of the specifics of the problem to solve or the opportunity to address
Joint Application Development
A structured meeting process than can accelerate and improve the efficiency and effectiveness of the investigation, analysis, and design phases of a system development project
Functional Decomposition
A technique used during the investigation, analysis and design phases to define the business processes included within the scope of the system
Systems Analysis
Gathering data on the existing system, determining requirements for the new system, considering alternatives within identified constraints, and investigating the feasibility of alternative solutions
Pareto Principle (80-20 rule)
An observation that for many events, effects come from 20 percent of the causes
Technical Feasibility
Examines whether a project is feasible within the technology
Economic Feasibility
Determines whether the expected benefits associated the expected costs sufficiently to make the project financially attractive
Legal Feasibility
The process of determining whether the laws or regulations development project
Operational Feasibility
The process of determining how a system will be well, it will meet various system performance expectations
Schedule Feasibility
The process of determining whether a project can be time frame
System Design
Creates a complete set of technical specifications that can be used to construct the information system
User Interface Design
Integrates concepts and methods from computer science, graphics design, and psychology to build interfaces that are accessible, easy to use, and efficient
Design User Interface
How the user experiences the information system determines whether the system will be accepted and used
Design System Security and Controls
Specific system security and controls must be developed for all aspects of the information system
Disaster recovery plan
A documented process to recover an organization’s business information system assets including hardware, software, data, networks, and facilities in the event of a disaster
Construction
Converts the system design into an operational system
Create and load data
This step involves making sure that all files and databases are populated and ready to be used with the new information system
Unit Testing
Testing that ideally forces an individual its various functions and user features
Integration testing
Involves linking all of the individual components together and testing them as a group to uncover any defects between individual components
System testing
Testing the complete, integrated system to validate that the information system meets all specified requirements
Volume Testing
Involves evaluating the performance of the information system under varying yet realistic work volume and operating conditions
User Acceptance Testing
Testing is performed by trained system users to verify that the system can complete required tasks in a real world environment
User preparation
The process of readying managers, decision makers, employees, other users, and stakeholders to accept and use the new system
Site preparation
Can be as simple as rearranging the furniture in an office to make for for a computer
Installation
The process of physically placing the computer equipment on the site and making it operational
Cut-over
The process of switching from an old information system to a replacement system
Direct conversion
A high risk approach in implementation
Phase-in approach
Involves slowly phasing the new system’s components as the old system’s components are phased out
Pilot start-up
Running a complete new system for only one group of users
Parallel start-up
Running both the old and new systems and comparing outputs
Systems operation
Involves using the new or modified system under all kinds of operating conditions
Systems review
The process of analyzing systems to are operating as intended
Maintenance
A stage of systems development that involves changing and enhancing the system to make it more useful in achieving user and organizational goals
Slipstream upgrade
Patch
Release
Version
Four accepted categories signify the amount of change involved in maintenance
Slipstream upgrade
A minor upgrade; a code bug
Patch
A minor change to make a correction or enhancement
Release
A significant change; software changes are required
Version
A major program change
Systems Disposal
Involves those activities ensuring the orderly dissolution of the system
Communicate intent
Terminate contracts
Make backups of data
Delete sensitive data
Dispose of hardware
Steps involved in system disposal
Agile Development
An iterative system development process that develops the system in “sprint” increments lasting from two weeks to two months
Scrum
A method to keep the agile system development and moving quickly
Scrum master
Coordinates all activities in agile development
Product owner
Represents the project stakeholders and is responsible for communicating and aligning the project priorities between the stakeholders and development team
Extreme programming
Promotes incremental development of a system using short development cycles
DevOps
The practice of blending the tasks performed by the development staff and the IT operations group to enable faster and more reliable software releases
