Use LEFT and RIGHT arrow keys to navigate between flashcards;
Use UP and DOWN arrow keys to flip the card;
H to show hint;
A reads text to speech;
147 Cards in this Set
- Front
- Back
|
Ch. 1, Introduction to Information Systems Book
application (or app) |
program designed to support a specific task or business process. |
|
|
Ch. 1, Introduction to Information Systems Book business intelligence (BI) systems |
Provide computer-based support for complex, nonroutine decisions, primarily for middle managers and knowledge workers. |
|
|
Ch. 1, Introduction to Information Systems Book computer-based information system (CBIS) |
An information system that uses computer technology to perform some or all of its intended tasks. |
|
|
Ch. 1, Introduction to Information Systems Book dashboards |
A special form of IS that support all managers of the organization by providing rapid access to timely information and direct access to structured information in the form of reports. |
|
|
Ch. 1, Introduction to Information Systems Book data items |
An elementary description of things, events, activities, and transactions that are recorded, classified, and stored but are not organized to convey any specific meaning. |
|
|
Ch. 1, Introduction to Information Systems Book database |
A collection of related files or tables containing data. |
|
|
Ch. 1, Introduction to Information Systems Book electronic commerce (e-commerce) systems |
A type of inter-organizational information system that enables organizations to conduct transactions, called business-to-business electronic commerce, and customers to conduct transactions with businesses, called business-to-consumer electronic commerce. |
|
|
Ch. 1, Introduction to Information Systems Book enterprise resource planning (ERP) systems |
Information systems that correct a lack of communication among the functional area ISs by tightly integrating the functional area ISs via a common database. |
|
|
Ch. 1, Introduction to Information Systems Book ergonomics |
The science of adapting machines and work environments to people; focuses on creating an environment that is safe, well lit, and comfortable. |
|
|
Ch. 1, Introduction to Information Systems Book expert systems (ESs) |
Attempt to duplicate the work of human experts by applying reasoning capabilities, knowledge, and expertise within a specific domain. |
|
|
Ch. 1, Introduction to Information Systems Book functional area information systems (FAISs) |
ISs that support a particular functional area within the organization. |
|
|
Ch. 1, Introduction to Information Systems Book A device such as a processor, monitor, |
hardwarekeyboard, or printer. Together, these devices accept, process, and display data and information. |
|
|
Ch. 1, Introduction to Information Systems Book information |
Data that have been organized so that they have meaning and value to the recipient. |
|
|
Ch. 1, Introduction to Information Systems Book information system (IS) |
Collects, processes, stores, analyzes, and disseminates information for a specific purpose. |
|
|
Ch. 1, Introduction to Information Systems Book information technology (IT) |
Relates to any computer-based tool that people use to work with information and support the information and information-processing needs of an organization. |
|
|
Ch. 1, Introduction to Information Systems Book information technology components |
Hardware, software, databases, and networks. |
|
|
Ch. 1, Introduction to Information Systems Book information technology infrastructure |
IT components plus IT services. |
|
|
Ch. 1, Introduction to Information Systems Book information technology platform |
Formed by the IT components of hardware, software, networks (wireline and wireless), and databases. |
|
|
Ch. 1, Introduction to Information Systems Book information technology services |
IT personnel use IT components to perform these IT services: develop information systems, oversee security and risk, and manage data. |
|
|
Ch. 1, Introduction to Information Systems Book informed user |
A person knowledgeable about information systems and information technology. |
|
|
Ch. 1, Introduction to Information Systems Book interorganizational information systems (IOSs) |
Information systems that connect two or more organizations. |
|
|
Ch. 1, Introduction to Information Systems Book knowledge |
`Data and/or information that have been organized and processed to convey understanding, experience, accumulated learning, and expertise as they apply to a current problem or activity. ` information that is contextual, relevant, and useful. `knowledge is information in action |
|
|
Ch. 1, Introduction to Information Systems Book knowledge workers |
Professional employees such as financial and marketing analysts, engineers, lawyers, and accountants, who are experts in a particular subject area and create information and knowledge, which they integrate into the business. |
|
|
Ch. 1, Introduction to Information Systems Book network |
A connecting system (wireline or wireless) that permits different computers to share resources. |
|
|
Ch. 1, Introduction to Information Systems Book procedures |
The set of instructions for combining hardware, software, database, and network components in order to process information and generate the desired output |
|
|
Ch. 1, Introduction to Information Systems Book software |
A program or collection of programs that enable the hardware to process data. |
|
|
Ch. 1, Introduction to Information Systems Book supply chain |
The flow of materials, information, money, and services from suppliers of raw materials through factories and warehouses to the end customers. |
|
|
Ch. 1, Introduction to Information Systems Book transaction processing system (TPS) |
Supports the monitoring, collection, storage, and processing of data from the organization’s basic business transactions, each of which generates data. |
|
|
Ch. 1, Introduction to Information Systems Book Chief Information Officer |
Highest-ranking IS manager; is responsible for all strategic planning in the organization |
|
|
Ch. 1, Introduction to Information Systems Book IS Director |
Manages all systems throughout the organization and the day-to-day operations of the entire IS organization |
|
|
Ch. 1, Introduction to Information Systems Book Information Center Manager |
Manages IS services such as help desks, hot lines, training, and consulting |
|
|
Ch. 1, Introduction to Information Systems Book Applications Development Manager |
Coordinates and manages new systems development projects |
|
|
Ch. 1, Introduction to Information Systems Book Project Manager |
Manages a particular new systems development project |
|
|
Ch. 1, Introduction to Information Systems Book Systems Manager |
Manages a particular existing system |
|
|
Ch. 1, Introduction to Information Systems Book Operations Manager |
Supervises the day-to-day operations of the data and/or computer center |
|
|
Ch. 1, Introduction to Information Systems Book Programming Manager |
Coordinates all applications programming efforts |
|
|
Ch. 1, Introduction to Information Systems Book Systems Analyst |
Interfaces between users and programmers; determines information requirements and technical specifications for new applications |
|
|
Ch. 1, Introduction to Information Systems Book Business Analyst |
Focuses on designing solutions for business problems; interfaces closely with users to demonstrate how IT can be used innovatively |
|
|
Ch. 1, Introduction to Information Systems Book Systems Programmer |
Creates the computer code for developing new systems software or maintaining existing systems software |
|
|
Ch. 1, Introduction to Information Systems Book Applications Programmer |
Creates the computer code for developing new applications or maintaining existing applications |
|
|
Ch. 1, Introduction to Information Systems Book Emerging Technologies Manager |
Forecasts technology trends; evaluates and experiments with new technologies |
|
|
Ch. 1, Introduction to Information Systems Book Network Manager |
Coordinates and manages the organization’s voice and data networks |
|
|
Ch. 1, Introduction to Information Systems Book Database Administrator |
Manages the organization’s databases and oversees the use of database-management software |
|
|
Ch. 1, Introduction to Information Systems Book Auditing or Computer Security Manager |
Oversees the ethical and legal use of information systems |
|
|
Ch. 1, Introduction to Information Systems Book Webmaster |
Manages the organization’s World Wide Web site |
|
|
Ch. 1, Introduction to Information Systems Book Web Designer |
Creates World Wide Web sites and pages |
|
|
Ch. 1, Introduction to Information Systems Book FIGURE 1.3: It takes technology (hardware, software, databases, and networks) with appropriate procedures to make a CBIS useful for people.
|
|
|
|
Ch. 2, Introduction to Information Systems Book
|
1 |
|
|
Ch. 2, Introduction to Information Systems Book
|
1 |
|
|
Ch. 2, Introduction to Information Systems Book
|
1 |
|
|
Ch. 2, Introduction to Information Systems Book
|
1 |
|
|
Ch. 2, Introduction to Information Systems Book
|
1 |
|
|
Ch. 2, Introduction to Information Systems Book
|
1 |
|
|
Ch. 2, Introduction to Information Systems Book
|
1 |
|
|
Ch. 2, Introduction to Information Systems Book
|
1 |
|
|
Ch. 2, Introduction to Information Systems Book
|
1 |
|
|
Ch. 5, Introduction to Information Systems Book
Big Data |
refer to the vast and constantly increasing amounts of data that modern organizations need to capture, store, process, and analyze |
|
|
Ch. 5, Introduction to Information Systems Book
petabytes of data |
A petabyte is approximately 1,000 terabytes, or trillions of bytes
|
|
|
Ch. 5, Introduction to Information Systems Book
Data governance |
managing information across an entire organization, a formal set of business processes and policies that are designed to ensure that data are handled in a certain, well-defined fashion. The objective is to make information available, transparent, and useful for the people who are authorized to access it, from the moment it enters an organization until it is outdated and deleted. |
|
|
Ch. 5, Introduction to Information Systems Book
Master data management |
is a process that spans all organizational business processes and applications. It provides companies with the ability to store, maintain, exchange, and synchronize a consistent, accurate, and timely “single version of the truth” for the company’s master data. |
|
|
Ch. 5, Introduction to Information Systems Book
Master data |
are a set of core data, such as customer, product, employee, vendor, geographic location, and so on, that span the enterprise information systems. |
|
|
Ch. 5, Introduction to Information Systems Book
Transaction data, |
which are generated and captured by operational systems, describe the business’s activities, or transactions
|
|
|
Ch. 5, Introduction to Information Systems Book exabyte |
is one trillion terabytes
|
|
|
Ch. 5, Introduction to Information Systems Book Data redundancy: |
The same data are stored in multiple locations.
|
|
|
Ch. 5, Introduction to Information Systems Book Data isolation: |
Applications cannot access data associated with other applications. |
|
|
Ch. 5, Introduction to Information Systems Book Data inconsistency: |
Various copies of the data do not agree. |
|
|
Ch. 5, Introduction to Information Systems Book Data security: |
Because data are “put in one place” in databases, there is a risk of losing a lot of data at once. Therefore, databases have extremely high security measures in place to minimize mistakes and deter attacks.
|
|
|
Ch. 5, Introduction to Information Systems Book Data integrity: |
Data meet certain constraints; for example, there are no alphabetic characters in a Social Security number field. |
|
|
Ch. 5, Introduction to Information Systems Book
Data independence: |
Applications and data are independent of one another; that is, applications and data are not linked to each other, so all applications are able to access the same data. |
|
|
Ch. 5, Introduction to Information Systems Book
Bit |
(binary digit) represents the smallest unit of data a computer can process.
|
|
|
Ch. 5, Introduction to Information Systems Book
binary |
means that a bit can consist only of a 0 or a 1. |
|
|
Ch. 5, Introduction to Information Systems Book
byte |
A group of eight bits represents a single character. A byte can be a letter, a number, or a symbol. |
|
|
Ch. 5, Introduction to Information Systems Book
field. |
A logical grouping of characters into a word, a small group of words, or an identification number |
|
|
Ch. 5, Introduction to Information Systems Book
record |
A logical grouping of related fields
|
|
|
Ch. 5, Introduction to Information Systems Book
data file or a table. |
A logical grouping of related records
|
|
|
Ch. 5, Introduction to Information Systems Book
database. |
a logical grouping of related files constitutes a database.
|
|
|
Ch. 5, Introduction to Information Systems Book
data model |
is a diagram that represents entities in the database and their relationships
|
|
|
Ch. 5, Introduction to Information Systems Book
An entity |
a person, place, thing, or event—such as a customer, an employee, or a product—about which information is maintained. Entities can typically be identified in the user’s work environment. A record generally describes an entity.
|
|
|
Ch. 5, Introduction to Information Systems Book
instance of an entity |
is a specific, unique representation of the entity
|
|
|
Ch. 5, Introduction to Information Systems Book
attribute |
Each characteristic or quality of a particular entity is called an attribute. For example, if our entities were a customer, an employee, and a product, entity attributes would include customer name, employee number, and product color.
|
|
|
Ch. 5, Introduction to Information Systems Book
primary key. |
Every record in a file must contain at least one field that uniquely identifies that record so that it can be retrieved, updated, and sorted.
|
|
|
Ch. 5, Introduction to Information Systems Book
secondary key |
is another field that has some identifying information but typically does not identify the record with complete accuracy.
|
|
|
Ch. 5, Introduction to Information Systems Book
entity-relationship (ER) modeling, |
Designers plan and create the database through the process of entity-relationship modeling, using an entity-relationship diagram.
|
|
|
Ch. 5, Introduction to Information Systems Book
entity-relationship diagram |
ER diagrams consist of entities, attributes, and relationships. Entities are pictured in boxes, and relationships are represented as diamonds. The attributes for each entity are listed, and the primary key is underlined. |
|
|
Ch. 5, Introduction to Information Systems Book
ER DIAGRAM RULES - Relationships |
illustrate an association between two entities. A relationship has a name that is a verb. Cardinality and modality are the indicators of the business rules in a relationship.
|
|
|
Ch. 5, Introduction to Information Systems Book ER DIAGRAM RULES - Cardinality |
refers to the maximum number of times an instance of one entity can be associated with an instance in the related entity. |
|
|
Ch. 5, Introduction to Information Systems Book ER DIAGRAM RULES - Modality |
refers to the minimum number of times an instance of one entity can be associated with an instances in the related entity. |
|
|
Ch. 5, Introduction to Information Systems Book ER DIAGRAM RULES - Figure 5.3 displays the cardinality and modality symbols. |
Cardinality can be 1 or Many, and its symbol is placed on the outside of the relationship line, closest to the entity. Modality can be 1 or 0, and its symbol is placed on the inside of the relationship line, next to the cardinality symbol. |
|
|
Ch. 5, Introduction to Information Systems Book
ER DIAGRAM RULES - ER DIAGRAM MODEL PAGE 147 |
Students register for courses, and they also register their cars for parking permits. In this example, STUDENT, PARKING PERMIT, CLASS, and PROFESSOR are entities,
|
|
|
Ch. 5, Introduction to Information Systems Book
ER DIAGRAM RULES - entity classes. |
Entities of a given type are grouped in entity classes.
|
|
|
Ch. 5, Introduction to Information Systems Book
ER DIAGRAM RULES - Entity instances |
have identifiers, which are attributes (attributes and identifiers are synonymous) that are unique to that entity instance
|
|
|
Ch. 5, Introduction to Information Systems Book ER DIAGRAM RULES - attributes, or properties, |
Entities have attributes, or properties, that describe the entity’s characteristics.
|
|
|
Ch. 5, Introduction to Information Systems Book
ER DIAGRAM RULES - Entities |
are associated with one another in relationships, which can include many entities. (Remember that relationships are represented by diamonds on ER diagrams.)
|
|
|
Ch. 5, Introduction to Information Systems Book
ER DIAGRAM RULES - degree of the relationship. |
The number of entities in a relationship is the degree of the relationship.
|
|
|
Ch. 5, Introduction to Information Systems Book
ER DIAGRAM RULES - binary relationships. |
Relationships between two items are called binary relationships. |
|
|
Ch. 5, Introduction to Information Systems Book
ER DIAGRAM RULES - There are three types of binary relationships: |
one-to-one, one-to-many, and many-to-many. |
|
|
Ch. 5, Introduction to Information Systems Book ER DIAGRAM RULES - one-to-one (1:1) relationship |
, a single-entity instance of one type is related to a single-entity instance of another type. Figure 5.4a
|
|
|
Ch. 5, Introduction to Information Systems Book ER DIAGRAM RULES - one-to-many (1:M) relationship |
is represented by the CLASS–PROFESSOR relationship in Figure 5.4a. This relationship means that a professor can have one or more courses, but each course can have only one professor.
|
|
|
Ch. 5, Introduction to Information Systems Book
ER DIAGRAM RULES - many-to-many (M:M) relationship |
is represented by the STUDENT–CLASS relationship in Figure 5.4a. This M:M relationship indicates that a student can have one or more courses, and a course can have one or more students |
|
|
Ch. 5, Introduction to Information Systems Book
ER DIAGRAM RULES - ER modeling is valuable because? |
it allows database designers to communicate with users throughout the organization to ensure that all entities and the relationships among the entities are represented. This process underscores the importance of taking all users into account when designing organizational databases. Notice that all entities and relationships in our example are labeled in terms that users can understand. Now that you understand how a database is designed, you can turn your attention to database management systems. |
|
|
Ch. 5, Introduction to Information Systems Book
database management system (DBMS) |
is a set of programs that provide users with tools to add, delete, access, modify, and analyze data stored in a single location. |
|
|
Ch. 5, Introduction to Information Systems Book
relational database model |
it is popular and easy to use, is based on the concept of two-dimensional tables. A relational database is usually designed with a number of related tables. Each of these tables contains records (listed in rows) and attributes (listed in columns).
|
|
|
Ch. 5, Introduction to Information Systems Book
flat file |
contains all of the records and attributes.
|
|
|
Ch. 5, Introduction to Information Systems Book
Structured query language (SQL) |
The most commonly performed database operation is requesting information. Structured query language (SQL) is the most popular query language used for this operation. SQL allows people to perform complicated searches by using relatively simple statements or key words. Typical key words are SELECT (to specify a desired attribute), FROM (to specify the table to be used), and WHERE (to specify conditions to apply in the query).
|
|
|
Ch. 5, Introduction to Information Systems Book
query by example (QBE). |
In QBE, the user fills out a grid or template—also known as a form—to construct a sample or a description of the data desired. Users can construct a query quickly and easily by using drag-and-drop features in a DBMS such as Microsoft Access. Conducting queries in this manner is simpler than keying in SQL commands.
|
|
|
Ch. 5, Introduction to Information Systems Book
data dictionary |
When a relational model is created, the data dictionary defines the required format for entering the data into the database. The data dictionary provides information on each attribute, such as its name, whether it is a key or part of a key, the type of data expected (alphanumeric, numeric, dates, and so on), and valid values. Data dictionaries can also provide information on why the attribute is needed in the database; which business functions, applications, forms, and reports use the attribute; and how often the attribute should be updated. |
|
|
Ch. 5, Introduction to Information Systems Book
Normalization |
is a method for analyzing and reducing a relational database to its most streamlined form to ensure minimum redundancy, maximum data integrity, and optimal processing performance. When data are normalized, attributes in the table depend only on the primary key. When you normalize the data, you want to eliminate repeating groups and have normalized tables, each containing only a single entity.
|
|
|
Ch. 5, Introduction to Information Systems Book
Data warehouses |
designed to access large groups of related records. data warehouse is a repository of historical data that are organized by subject to support decision makers in the organization
|
|
|
Ch. 5, Introduction to Information Systems Book
data mart |
is a low-cost, scaled-down version of a data warehouse that is designed for the end-user needs in a strategic business unit (SBU) or an individual department. Data marts can be implemented more quickly than data warehouses, often in less than 90 days. Further, they support local rather than central control by conferring power on the user group. |
|
|
Ch. 5, Introduction to Information Systems Book
basic characteristics of data warehouses and data marts include - Organized by business dimension or subject. |
Data are organized by subject—for example, by customer, vendor, product, price level, and region. This arrangement differs from transactional systems, where data are organized by business process, such as order entry, inventory control, and accounts receivable.
|
|
|
Ch. 5, Introduction to Information Systems Book
basic characteristics of data warehouses and data marts include - online analytical processing |
Typically, organizational databases are oriented toward handling transactions. That is, databases use online transaction processing (OLTP), where business transactions are processed online as soon as they occur. The objectives are speed and efficiency, which are critical to a successful Internet-based business operation. Data warehouses and data marts, which are designed to support decision makers but not OLTP, use online analytical processing. |
|
|
Ch. 5, Introduction to Information Systems Book Online analytical processing (OLAP) |
involves the analysis of accumulated data by end users. |
|
|
Ch. 5, Introduction to Information Systems Book basic characteristics of data warehouses and data marts include - Integrated. |
Data are collected from multiple systems and then integrated around subjects. For example, customer data may be extracted from internal (and external) systems and then integrated around a customer identifier, thereby creating a comprehensive view of the customer.
|
|
|
Ch. 5, Introduction to Information Systems Book basic characteristics of data warehouses and data marts include - Time variant. |
Data warehouses and data marts maintain historical data (i.e., data that include time as a variable). Unlike transactional systems, which maintain only recent data (such as for the last day, week, or month), a warehouse or mart may store years of data. Organizations utilize historical data to detect deviations, trends, and long-term relationships. |
|
|
Ch. 5, Introduction to Information Systems Book basic characteristics of data warehouses and data marts include - Nonvolatile. |
Data warehouses and data marts are nonvolatile—that is, users cannot change or update the data. Therefore the warehouse or mart reflects history, which, as we just saw, is critical for identifying and analyzing trends. Warehouses and marts are updated, but through IT-controlled load processes rather than by users. |
|
|
Ch. 5, Introduction to Information Systems Book basic characteristics of data warehouses and data marts include - Multidimensional data structure |
Typically the data warehouse or mart uses a multidimensional data structure. Recall that relational databases store data in two-dimensional tables. In contrast, data warehouses and marts store data in more than two dimensions. For this reason, the data are said to be stored in a multidimensional structure. A common representation for this multidimensional structure is the data cube. |
|
|
Ch. 5, Introduction to Information Systems Book business dimensions, |
data in data warehouses and marts are organized by business dimensions, which are subjects such as product, geographic area, and time period that represent the edges of the data cube. |
|
|
Ch. 5, Introduction to Information Systems Book Data Cube Model |
Figure 5.11 for an example of a data cube, you see that the product dimension is comprised of nuts, screws, bolts, and washers; the geographic area dimension is comprised of east, west, and central; and the time period dimension is comprised of 2011, 2012, and 2013. Users can view and analyze data from the perspective of these business dimensions. This analysis is intuitive because the dimensions are presented in business terms that users can easily understand.
|
|
|
Ch. 5, Introduction to Information Systems Book The environment for data warehouses and marts includes the following: |
Source systems that provide data to the warehouse or mart
Data-integration technology and processes that prepare the data for use Different architectures for storing data in an organization’s data warehouse or data marts Different tools and applications for the variety of users. Metadata, data-quality, and governance processes that ensure that the warehouse or mart meets its purposes |
|
|
Ch. 5, Introduction to Information Systems Book The environment for data warehouses and marts includes the following: Source Systems. |
- The data requirements can range from a single source system, as in the case of a data mart, to hundreds of source systems, as in the case of an enterprise-wide data warehouse.
-Modern organizations can select from a variety of source systems: operational/transactional systems, enterprise resource planning (ERP) systems, Web site data, third-party data (e.g., customer demographic data), and more. The trend is to include more types of data (e.g., sensing data from RFID tags). These source systems often use different software packages (e.g., IBM, Oracle) and store data in different formats (e.g., relational, hierarchical). - |
|
|
Ch. 5, Introduction to Information Systems Book The environment for data warehouses and marts includes the following: Data Integration. |
- In addition to storing data in their source systems, organizations need to extract the data, transform them, and then load them into a data mart or warehouse. This process is often called ETL, but the term data integration is increasingly being used
-Data extraction can be performed either by handwritten code (e.g., SQL queries) or by commercial data-integration software. |
|
|
Ch. 5, Introduction to Information Systems Book The environment for data warehouses and marts includes the following: Storing the Data. |
-most common architecture is one central enterprise data warehouse, without data marts, are accessed by all users and represent the single version of the truth.
- Another architecture is independent data marts. This architecture stores data for a single application or a few applications, such as marketing and finance. -hub and spoke. This architecture contains a central data warehouse that stores the data plus multiple dependent data marts that source their data from the central repository. Because the marts obtain their data from the central repository, the data in these marts still comprise the single version of the truth for decision-support purposes. |
|
|
Ch. 5, Introduction to Information Systems Book The environment for data warehouses and marts includes the following:Metadata. |
maintain data about the data, known as metadata, in the data warehouse. |
|
|
Ch. 5, Introduction to Information Systems Book The environment for data warehouses and marts includes the following: Data Quality. |
-Most organizations find that the quality of the data in source systems is poor and must be improved before the data can be used in the data warehouse. - long-term solution is to improve the quality at the source system level. This approach requires the business owners of the data to assume responsibility for making any necessary changes to implement this solution. |
|
|
Ch. 5, Introduction to Information Systems Book
(ERP) |
enterprise resource planning (ERP) systems
|
|
|
Ch. 5, Introduction to Information Systems Book Data warehouse framework Model. |
Unfortunately, many source systems that have been in use for years contain “bad data”. As a result, data-profiling software should be used at the beginning of a warehousing project to better understand the data. For example, this software can provide statistics on missing data, identify possible primary and foreign keys, and reveal how derived values (e.g., column 3 = column 1 + column 2) are calculated. Subject area database specialists (e.g., marketing, human resources) can also assist in understanding and accessing the data in source systems.
|
|
|
Ch. 5, Introduction to Information Systems Book bad data |
missing or incorrect data, are poorly documented.
|
|
|
Ch. 5, Introduction to Information Systems Book
The environment for data warehouses and marts includes the following: Governance. |
To ensure that BI is meeting their needs, organizations must implement governance to plan and control their BI activities. Governance requires that people, committees, and processes be in place.
|
|
|
Ch. 5, Introduction to Information Systems Book
The environment for data warehouses and marts includes the following: Users. |
organization begins to obtain business value from BI; all of the prior stages constitute creating BI infrastructure.
|
|
|
Ch. 5, Introduction to Information Systems Book
information producers |
whose primary role is to create information for other users. IT developers and analysts typically fall into this category.
|
|
|
Ch. 5, Introduction to Information Systems Book information consumers |
including managers and executives—are information consumers, because they utilize information created by others. |
|
|
Ch. 5, Introduction to Information Systems Book
benefits of data warehousing include the following: |
` End users can access needed data quickly and easily via Web browsers because these data are located in one place.
` End users can conduct extensive analysis with data in ways that were not previously possible. `End users can obtain a consolidated view of organizational data. These benefits can improve business knowledge, provide competitive advantage, enhance customer service and satisfaction, facilitate decision making, and streamline business processes. |
|
|
Ch. 5, Introduction to Information Systems Book
data warehouses have some limitations. |
First, they can be very expensive to build and to maintain. Second, incorporating data from obsolete mainframe systems can be difficult and expensive. Finally, people in one department might be reluctant to share data with other departments.
|
|
|
Ch. 5, Introduction to Information Systems Book
(RFP) |
request for proposals (RFP)
|
|
|
Ch. 5, Introduction to Information Systems Book
Knowledge management (KM) |
Knowledge management (KM) is a process that helps organizations manipulate important knowledge that comprises part of the organization’s memory, usually in an unstructured format. For an organization to be successful, knowledge, as a form of capital, must exist in a format that can be exchanged among persons. In addition, it must be able to grow.
|
|
|
Ch. 5, Introduction to Information Systems Book
. Intellectual capital (or intellectual assets) |
is another term for knowledge. |
|
|
Ch. 5, Introduction to Information Systems Book
explicit knowledge
|
is the knowledge that has been codified (documented) in a form that can be distributed to others or transformed into a process or a strategy
|
|
|
Ch. 5, Introduction to Information Systems Book
tacit knowledge |
`organization’s experiences, insights, expertise, know-how, trade secrets, skill sets, understanding, and learning. `organizational culture, which reflects the past and present experiences of the organization’s people and processes, as well as the organization’s prevailing values. `generally imprecise and costly to transfer. `highly personal. `it is unstructured, it is difficult to formalize or codify, in contrast to explicit knowledge |
|
|
Ch. 5, Introduction to Information Systems Book
. Knowledge management systems (KMSs) |
`help an organization make the most productive use of the knowledge it has accumulated. need to integrate explicit and tacit knowledge into formal information systems |
|
|
Ch. 5, Introduction to Information Systems Book
best practices, |
the most effective and efficient ways of doing things, readily available to a wide range of employees. Enhanced access to best-practice knowledge improves overall organizational performance.
|
|
|
Ch. 5, Introduction to Information Systems Book
The KMS Cycle - Model |
|
|
|
Ch. 5, Introduction to Information Systems Book
The KMS Cycle - Create knowledge. |
Knowledge is created as people determine new ways of doing things or develop know-how. Sometimes external knowledge is brought in.
|
|
|
Ch. 5, Introduction to Information Systems Book
The KMS Cycle - Capture knowledge. |
New knowledge must be identified as valuable and be represented in a reasonable way.
|
|
|
Ch. 5, Introduction to Information Systems Book The KMS Cycle - Refine knowledge. |
New knowledge must be placed in context so that it is actionable. This is where tacit qualities (human insights) must be captured along with explicit facts.
|
|
|
Ch. 5, Introduction to Information Systems Book The KMS Cycle - Store knowledge. |
Useful knowledge must then be stored in a reasonable format in a knowledge repository so that others in the organization can access it. |
|
|
Ch. 5, Introduction to Information Systems Book
The KMS Cycle - Manage knowledge. |
Like a library, the knowledge must be kept current. It must be reviewed regularly to verify that it is relevant and accurate. |
|
|
Ch. 5, Introduction to Information Systems Book
The KMS Cycle - Disseminate knowledge. |
Knowledge must be made available in a useful format to anyone in the organization who needs it, anywhere and anytime. |
