Chapter 13 Flashcards
Application Portfolio
Recommended applications that result from the planning and justification process in application development
IT Strategic Plan
long-term goals required to achieve the organization’s objectives
IT Steering Committee
A group of managers and staff decide on IT priorities and if technology meets the company’s needs
IS Operational Plan
lists projects, making sure they align with the IT strategic plan
IT Costs Downsides
Allocating Fixed Costs
Ongoing Costs
Unanticipated Costs
Long-Term Effects of Design Choices
IT Investment Benefits
Improved CRM/Decision Making
Used for Various Purposes
Benefits Realized when Implemented
Real-World Testing
Types of Conducting Cost-Benefit Analysis
Net Present Value (NPV)
Return on Investment (ROI)
Break-Even Analysis
Business Case Approach
Net Present Value (NPV)
A way to calculate whether the benefits of a project are worth more than its costs by comparing the current value of future benefits to the costs, using the company’s cost of funds
Return on Investment (ROI)
A measure of how well a company makes profits from its assets, calculated by dividing the net income by the average assets invested. A higher percentage means better performanc
Break-even analysis
Do benefits=investments
Business case approach
Involves writing a business case to justify funding for specific projects, describing current processes and how a new system can improve them
Application service provider (ASP)
Companies that gives businesses software and handles its setup, maintenance, and support for them
Software-as-a-service (SaaS)
Using a software online hosted by a company
Outsourcing in IT
Use of outside contractors or external organizations to acquire IT applications or services
Continuous application development
Process of steadily adding new computer code to a software project as the new code is written and tested
4 Fundamental Businesses Decisions for Acquiring IS
How much computer code to write?
How to pay for the application?
Where will the application run?
Where will the application originate?
Systems Development Life Cycle (SDLC)
A step-by-step process for planning, building, and managing big IT projects
Systems analysts
Analyze and design information systems
Programmers
Modify or write computer programs to meet user needs
Systems Stakeholders
People who are affected by changes in information systems
Systems Investigation
The first stage in Systen Development Life Cycle (SDLC) that examines the business problem or opportunity through a feasibility study
Feasibility Study
A check to see if a project can succeed and how likely it is to work
Systems Analysis
Studying the business problem the system will solve.
Systems Design
Describes how the new system will solve the business problem
Scope Creep
Adding extra features to a system during development
Programming
Turning system design into working computer code
Implementation
Switching from an old system to a new one
4 Conversion Methods
Direct
Pilot
Phased
Parallel
Direct Conversion
Switching from the old system to the new one all at once
Pilot Conversion
Testing the new system in one part of the organization before using it everywhere else
Phased Conversion
Introducing parts of the new system gradually until the whole system is up and running
Parallel Conversion
Running both the old and new systems at the same time for a period
Joint Application Design (JAD)
A group-based method to gather user requirements and create system designs
Rapid Application Development (RAD)
A method that uses special tools and an iterative approach to quickly create a high-quality system
Agile Development
A software development method that delivers functionality in short, rapid cycles (weeks) with frequent communication, development, testing, and delivery
End-User Development
An approach where the organization’s end users create their own applications with minimal or no help from the IT department
Shadow IT
Technology used by end users without approval from the organization’s IT department
Prototyping
An approach where an initial system is built quickly, then improved through multiple iterations based on user feedback.
Prototype
A small-scale working model of a system, focusing on the components most important to users.
Computer-Aided Software Engineering (CASE)
A development approach that uses specialized tools to automate tasks in the SDLC
Upper CASE tools
Tools used to automate the early stages of the SDLC (investigation, analysis, and design)
Lower CASE tools
Tools used to automate the later stages of the SDLC (programming, testing, operation, and maintenance)
Integrated CASE (ICASE) tools
CASE tools that link upper CASE and lower CASE tools together
Component-based development
A software development method that uses standard components to build applications.
Object-oriented development
A systems development method that starts by modeling real-world aspects necessary to perform a task
Containers
A method of developing applications that run independently of the server’s base operating system
