Term
| Front-office information systems |
|
Definition
| support business functions that extend out to the organization’s customers (or constituents). |
|
|
Term
| Back-office information systems |
|
Definition
| support internal business operations of an organization, as well as reach out to suppliers (of materials, equipment, supplies, and services). |
|
|
Term
| Information systems architecture |
|
Definition
| a unifying framework into which various stakeholders with different perspectives can organize and view the fundamental building blocks of information systems. |
|
|
Term
|
Definition
| the raw material used to create useful information. |
|
|
Term
|
Definition
| the activities (including management) that carry out the mission of the business. |
|
|
Term
|
Definition
| how the system interfaces with its users and other information systems. |
|
|
Term
|
Definition
Interested not in raw data but in information that adds new business knowledge and helps managers make decisions.
Business entities and business rules |
|
|
Term
|
Definition
View data as something recorded on forms, stored in file cabinets, recorded in books and spreadsheets, or stored on computer.
Focus on business issues as they pertain to data. |
|
|
Term
|
Definition
| a representation of users’ data in terms of entities, attributes, relationships, and rules independent of data technology. |
|
|
Term
|
Definition
| Data structures, database schemas, fields, indexes, and constraints of particular database management system (DBMS). |
|
|
Term
|
Definition
SQL
DBMS or other data technologies |
|
|
Term
|
Definition
| Concerned with high-level processes |
|
|
Term
|
Definition
| a group of related processes that support the business. Functions can be decomposed into other subfunctions and eventually into processes that do specific tasks. |
|
|
Term
| cross-functional information system |
|
Definition
| a system that supports relevant business processes from several business functions without regard to traditional organizational boundaries such as divisions, departments, centers, and offices. |
|
|
Term
|
Definition
| activities that respond to business events. |
|
|
Term
|
Definition
| a user’s expectation of the processing requirements for a business process and its information systems. |
|
|
Term
|
Definition
| a set of rules that govern a business process. |
|
|
Term
|
Definition
| a step-by-step set of instructions and logic for accomplishing a business process. |
|
|
Term
|
Definition
| the flow of transactions through business processes to ensure appropriate checks and approvals are implemented. |
|
|
Term
|
Definition
| the technical design of business processes to be automated or supported by computer programs to be written by system builders. |
|
|
Term
|
Definition
| a language-based, machine-readable representation of what a software process is supposed to do, or how a software process is supposed to accomplish its task. |
|
|
Term
|
Definition
| a technique for quickly building a functioning, but incomplete model of the information system using rapid application development tools. |
|
|
Term
|
Definition
| technical designs that document how system users are to interact with a system and how a system interacts with other systems. |
|
|
Term
|
Definition
| a specification of how the user moves from window to window or page to page, interacting with the application programs to perform useful work. |
|
|
Term
|
Definition
| utility software that allows application software and systems software that utilize differing technologies to interoperate. |
|
|
Term
|
Definition
| approach allows any one building block to be replaced with another while having little or no impact on the other building blocks |
|
|
