Term
| The application portfolio |
|
Definition
| is a prioritized list of both existing and potential IT applications of a company. |
|
|
Term
| Organizational strategic plan |
|
Definition
| states the firms overall mission, the goals that follow from that mission, and the broad steps necessary to reach these goals. |
|
|
Term
|
Definition
| delineates the way an organizations information resources should be used to accomplish its mission. |
|
|
Term
|
Definition
| is a set of long-range goals that describe the IT infrastructure and major IT initiatives needed to achieve the goals of the organization. |
|
|
Term
| The IT steering committee |
|
Definition
| is comprised of managers and staff representing various organizational units. This committee establishes IT priorities and ensures that the MIS function meets the needs of the enterprise. |
|
|
Term
|
Definition
| consists of a clear set of projects that the IT department and functionalarea managers will execute in support of the IT strategic plan. |
|
|
Term
|
Definition
| derived from IT strategy. |
|
|
Term
|
Definition
| summary of information needs of the functional areas and of the organization as a whole. |
|
|
Term
| Objectives of the IT function |
|
Definition
| best current estimate of the goals. |
|
|
Term
| Constraints of the IT function |
|
Definition
| technological, financial, personnel and other resource limitations. |
|
|
Term
|
Definition
| prioritized inventory of present applications and a detailed plan of projects to be developed or continued. |
|
|
Term
| Resource allocation and project management |
|
Definition
| listing of who is going to do what, how and when. |
|
|
Term
|
Definition
| are those costs that remain the same regardless of change in the activity level. For IT, fixed costs include infrastructure cost, cost of IT services, and IT management cost |
|
|
Term
| Total cost of ownership (TCO) |
|
Definition
| Formula for calculating cost of acquiring, operating and controlling an IT system. |
|
|
Term
| The Net Present Value (NPV) |
|
Definition
| method converts future values of benefits to their present-value equivalent by discounting them at the organizations cost of funds. |
|
|
Term
|
Definition
| measures the effectiveness of management in generating profits with its available assets. |
|
|
Term
|
Definition
| determines the point at which the cumulative dollar value of the benefits from a project equals the investment made in the project. |
|
|
Term
| The business case approach |
|
Definition
| A business case is one or more specific applications or projects. Its major emphasis is the justification for a specific required investment, but it also provides the bridge between the initial plan and its execution. |
|
|
Term
| An application service provider is an agent or a vendor who assembles the software needed by enterprises and packages the software with services such as development |
|
Definition
| operations, and maintenance. |
|
|
Term
|
Definition
| is a method of delivering software in which a vendor hosts the applications and provides them as a service to customers over a network, typically the Internet. |
|
|
Term
|
Definition
| is acquiring IT applications from external contractors or organizations. |
|
|
Term
| The systems development life cycle (SDLC) |
|
Definition
| is the traditional systems development method that organizations use for large-scale IT projects. |
|
|
Term
|
Definition
| is the main task of the Systems Investigation phase. |
|
|
Term
|
Definition
| Assessment of whether hardware, software and communications components can be developed and /or acquired to solve a business problem. |
|
|
Term
|
Definition
| Assessment of whether a project is an acceptable financial risk and if the organization can afford the expense and time needed to complete it |
|
|
Term
| Organizational feasibility |
|
Definition
| Organizations ability to access the proposed project. |
|
|
Term
|
Definition
| Assessment of the human issues involved in a proposed project, including resistance to change and skills and training needs. |
|
|
Term
|
Definition
| or deployment is the process of converting from the old system to the new system. Four major conversion strategies: |
|
|
Term
|
Definition
| . Implementation process in which the old system is cut-off and the new system turned on at a certain point in time. |
|
|
Term
|
Definition
| . Implementation process that introduces the new system in one part of the organization on a trial basis, when new system is working property, it is introduced in other parts of the organization. |
|
|
Term
|
Definition
| . Implementation process that introduces components of the new system in stages, until the entire new system is operational. |
|
|
Term
|
Definition
| . Implementation process in which the old system and the new system operate simultaneously for a period of time. Rarely used today if at all. |
|
|
Term
| Joint application design (JAD) |
|
Definition
| . A group based tool for collecting user requirements and creating system designs. |
|
|
Term
| Computer-Assisted Software Engineering (CASE) |
|
Definition
|
|
Term
| Integrated Computer-Assisted Software Engineering (ICASE) Tools . |
|
Definition
| CASE tools that provide links between upper CASE and lower CASE tools. |
|
|
Term
| Rapid Application Development (RAD) |
|
Definition
| is a development method that uses special tools and an iterative approach to rapidly produce a high-quality system. |
|
|
Term
|
Definition
| Development method that delivers functionality in rapid iterations requiring frequent communication, development, testing, and delivery. |
|
|
Term
|
Definition
| is a development method that has the actually user develop their own application(s) for use. |
|
|
Term
| Component-Based Development |
|
Definition
| Uses standard components to build applications. |
|
|
Term
| Object-oriented development |
|
Definition
| does not begin with the task to be performed, but with aspects of the real world that must be modeled to perform that task. |
|
|
Term
| Prototyping. Approach that defines an initial list of user requirements |
|
Definition
| builds a prototype system and then improves the system in several iterations based |
|
|
Term
| Computer-Assisted Software Engineering (CASE) |
|
Definition
| is a ddevelopment approach that uses specialized tools to automate many of the tasks in the SDLC; upper CASE tools in SDLC automate the early stages of the SDLC, and lower case tools automate the later stages. |
|
|
Term
| Integrated Computer-Assisted Software Engineering (ICASE) Tools |
|
Definition
| CASE tools that provide links between upper CASE and lower CASE tools. |
|
|
Term
| Component-Based Development |
|
Definition
| Uses standard components to build applications. |
|
|
Term
| Object-oriented development |
|
Definition
| does not begin with the task to be performed, but with aspects of the real world that must be modeled to perform that task. |
|
|
Term
| Request for proposal (RFP) |
|
Definition
| is a document sent to potential vendors to submit a proposal describing their software package and explain how it would meet the companys needs. |
|
|
Term
| Service Level Agreements (SLAs) |
|
Definition
| are formal agreements that specify how work is to be divided between the company and its vendors. |
|
|
