Application Independence – The separation of data and the definition of data from the applications that use these data

Application software – Software designed to process data and support users in an organization

Boundary – the line that marks the inside and outside of a system and that sets off one system from other systems in the organization

Cohesion – the extent to which a system or subsystem performs a single function

Component – an irreducible part or aggregation of parts that makes up a system, or a subsystem

Constraint – a limit to what a system can accomplish

Coupling – the extent to which subsystems depend on each other

Data – Raw facts about people, objects, and events in an organization

Database – a shared collection of logically related data designed to meet the information needs of multiple users in an organization

Data flow – Data in motion, moving from one place in a system to another

Data oriented approach – a strategy of information systems development that focuses on the ideal organization of data rather than on where and how they are used

Decomposition – the process of breaking the description of a system down into small components

End users – non information systems professionals in an organization

Environment – everything external to a system that interacts with the system

Information – data that have been processed and presented in a form suitable for human interpretation, often with the purpose of revealing trends or patterns

Information systems analysis and design – the process of developing and maintaining an information system

Interfaces – points of contact where a system meets its environment or where subsystems meet each other

Interrelated components – dependence of one part of the system on one or more other system part

JAD – a structured process in which users, managers and analysts work together for several days in a series of intensive meetings to specify or review systems requirements

Modularity – dividing a system into chunks or modules of equal size

PD – a system developed approach that originated in north Europe in which users and the improvement of their work lives are the central focus

Process logic – the steps by which data are transformed or moved and a description of the events that trigger these steps

Process oriented approach – an approach to developing information systems that focuses on how and when data are moved and changed

Prototyping – building a scaled down version of the desired information systems

Purpose – the overall goal or function of a system

System – a group of interrelated procedures used for a business functions, with an identifiable boundary, working together for some purpose

Systems analysis – phase of the SDLC in which the current system is studied and alternative replacement systems are proposed

Systems analyst – the organizational role most responsible for the analysis and design of information systems

Systems design – the phase of the SDLC in which the system chosen for development in systems analysis is first described independent of any computer platform and is then transformed into technology-specific details from which all programming and system construction can be accomplished

SDLC – the series of steps used to mark the phases of development for an information system

System development methodology – a standard process followed in an organization to conduct all the steps necessary to analyze, design, implement, and maintain information systems

Systems implementation and operation – final phase of the SDLC, in which the information system is coded, tested, and installed in the organization, and in which the information system is systematically repaired and improved

System planning and selection – the first phase of the SDLC, in which an organization’s total information system needs are analyzed and arranged, and in which a potential information systems project is identified and an argument for continuing or not continuing with the project is presented


Identifying and selecting systems development projects – is done by: 1. identifying potential development projects, 2. classifying and ranking IS development projects, selecting IS development projects

Baseline project plan BPP – the major outcome and deliverable from the project initiation and planning phase

Break even analysis – a type of cost benefit analysis to identify at what point benefits equal costs

Business case – a written report that outlines the justification for an information system

Discount rate - the interest rate used to computer the present value of future cash flows

Economic feasibility – a process of identifying the financial benefits and costs associated with a development project

Electronic commerce

Electronic data interchange – the use of telecommunications technologies to transfer business documents directly between organizations

Extranet

Incremental commitment – a strategy in systems analysis and design in which the project is reviewed after each phase and continuation of the project is rejustified in each of these reviews

Intangible benefit – a benefit derived from the creation of an information system that cannot be measured in dollars or with certainty

Intangible cost - a cost associated with an information system that cannot be easily measured in dollars or with certainty

Internet

Intranet

Legal and contractual feasibility – assessing potential legal and contractual ramifications due to the construction of a system

One time cost – a cost associated with project start up and development, or system start up

Operational feasibility – the process of assessing the degree to which a proposed system solves business problems or takes advantage of business opportunities

Political feasibility - the process of evaluating how key stakeholders within the organization view the proposed system

Present value – the current value of a future cash flow

Recurring cost – a cost resulting from the ongoing evolution and use of a system

Schedule feasibility – the process of assessing the degree to which the potential time frame and completion dates for all major activities within a project meet organizational deadlines and constraints for affecting change

Statement of work SOW – a document prepared for the customer during project initiation and planning that describes what the project will deliver and outlines generally at a high level all work required to complete the project

Tangible benefit - a benefit derived from the creation of an information system that can be measured in dollars and with certainty

Tangible cost – a cost associated with an information system that can be easily measured in dollars and with certainty

Technical feasibility – the process of assessing the development organization’s ability to construct a proposed system

Time value of money TVM – the process of comparing present cash outlays to future expected returns

Walkthrough – a peer group review of any product created during the systems development process

 

Code generators - CASE tools that enable the automatic generation of program and database definition code directly from the design documents, diagrams, forms and reports stored in the repository

Cross life cycle CASE - CASE tools designed to support activities tat occur across multiple phases of the systems development life cycle

Form and report generators - CASE tools designed to support the creation of system forms and reports in order to prototype how systems will look and feel to users

I – Case – an automated system development environment that provides numerous tools to create diagrams, forms and reports

Lower CASE -  CASE tools designed to support the systems implementation and operation phase of the systems development life cycle

Repository – a centralized database that contains all diagrams, forms and report definitions, data structure, data definions, process flows and logic, and definitions of other organizational and system components

Upper case – CASE tools designed to support the systems planning and selection, systems analysis, and systems design phases of the systems development life cycle