Question
click below
click below
Question
Normal Size Small Size show me how
cscitest4
Question | Answer |
---|---|
a top level executive who helps the organization use a KMS to create, store, and use knowledge to achieve organizational goals | chief knowledge officer |
the ability of computers to mimic or duplicate the functions of the human brain | artificial intelligence |
people, procedures, hardware, software, data, and knowledge needed to develop computer systems and machines that demonstrate the characteristics of intelligence | artificial intelligence systems |
the ability to learn from experiences and apply knowledge acquired from experience, handle complex situations, solve problems when important information is missing, determine what is important, react quickly and correctly to a new situation, ect | intelligent behavior |
a system that approximates the way a person sees, hears, and feels objects | perceptive system |
hardware and software that stores knowledge and makes inferences, similar to a human expert | expert system |
mechanical or computer devices that perform tasks requiring a high degre of precision or that are tedious or hazardous for humans | robotics |
the hardware and software that permit computers to capture, store, and manipulate visual images | vision systems |
processing that allows the computer to understand and react to statements and commands made in a "natural" language, such as English | natural language processing |
a combination of software and hardware that allows the computer to change how it functions or reacts to situations based on feedback it receives | learning systems |
a computer system that can simulate the functioning of a human brain | neural network |
an approach to solving large, complex problems in which a number of related operations or models change and evolve until the best one emerges | genetic algorithm |
programs and a knowledge base used to perform a specific task for a person, a process, or another program. also called intelligent robot or bot | intelligent agent |
a component of an expert system that stores all relevant information, data, rules, cases, and relationships used by the expert system | knowledge base |
a conditional statement that links conditions to actions or outcomes | rule |
rules that suggests certain conclusions | IF-THEN statements |
part of the expert system that seeks information and relationships from the knowledge base and provides answers, predictions, and suggestions similar to the way a human expert would | inference engine |
the process of starting with conclusions and working backward to the supporting facts | backward chaining |
the process of starting with the facts and working forward to the conclusions | forward chaining |
component of an expert system that allows a user or decision maker to understand how the expert system arrived at certain conclusions or results | explanation facility |
part of the expert system that provides convenient and efficient means of capturing and storing all the components of the knowledge base | knowledge acquisition facility |
the area of knowledge addressed by the expert system | domain |
the person or group who has the expertise or knowledge the expert system is trying to capture | domain expert |
a person who has training or experience in the design, development, implementation, and maintenance of an expert system | knowledge user |
a system that enables one or more users to move and react in a computer-simulated environment | virtual reality system |
the use of information systems to develop competitive strategies for people, organizations, or even countries | game theory |
a specialized system that combines traditional disciplines, such as science and medicine, with computer systems and technology | informatics |
people who, either themselves or through the organization they represent, ultimately benefit from the systems development project | stakeholders |
people who will interact with the system regularly | users |
a professional who specializes in analyzing and designing business systems | systems analyst |
a specialist responsible for modifying or developing programs to satisfy user requirements | programmer |
translating strategic and organizational goals into systems development initiatives | information systems planning |
the systems development phase during which problems and opportunities are identified and considered in light of the goals of the business | systems investigation |
the systems development phase that determines what the information system must do to solve the problem by studying existing systems and work processes to identify strengths, weaknesses, and opportunities for improvement | systems analysis |
the systems development phase that defines how the information system will do what it must do to obtain the problem solution | systems design |
the systems development phase involving the creation or acquiring of various system components detailed in the systems design, assembling them, and placing the new or modified system into operation | systems implementation |
the systems development phase that ensures the system operates and modifies the system so that it continues to meet changing business needs | systems maintenance and review |
a systems development approach that employs tools, techniques, and methodologies designed to speed application development | rapid application development (RAD) |
a process for data collection and requirements analysis in which users, stakeholders, and IS professionals work together to analyze existing systems, propose possible solutions, and define the requirements of a new or modified system | joint application development (JAD) |
a systems development project in which business managers and users assume the primary effort | end-user systems development |
tools that automate many of the tasks required in a systems development effort and encourage adherence to the SDLC | computer-aided software engineering (CASE) |
an approach to systems development that combines the logic of the systems development life cycle with the power of object-oriented modeling and programming | object-oriented systems development (OOSD) |
a document filled out by someone who wants the IS department to initiate systems investigation | system requests form |
assessment of the technical, economic, legal, operational, and schedule feasibility of a project | feasibility analysis |
assessment of whether the hardware, software, and other system components can be acquired or developed to solve the problem | technical feasibility |
the determination of whether the project makes financial sense of whether predicted benefits offset the cost and time needed to obtain them | economic feasibility |
the determination of whether laws or regulations may prevent of limit a systems development project | legal feasibility |
the measure of whether the project can be put into action or operation | operational feasibility |
the determination of whether the project can be completed in a reasonable amount of time | schedule feasibility |
an advisory group consisting of senior management and users from the IS department and other functional areas | steering committee |
an interview where the questions are written in advance | structured interview |
an interview where the questions are not written in advance | unstructured interview |
watching the existing system in action by one or more members of the analysis team | direct observation |
a method of gathering data where the data sources are spread over a wide geographic area | questionnaires |
the manipulation of collected data so that the development team members who are participating in systems analysis can use the data | data analysis |
a model of objects, associations, and activities that describes how data can flow between and around various objects | data-flow diagram (DFD) |
arrows that show the direction of data element movement | data-flow line |
representation of a function that is performed | process symbol |
representation of either a source or destination of a data element | entity symbol |
representation of a storage location for data | data store |
the determination of user, stakeholder, and organizational needs | requirements analysis |
an approach to gather data that asks users, stakeholders, and other managers about what they want and expect from the new or modified system | asking directly |
the stage of systems development that answers the question "how will the information system solve a problem?" | system design |
a description of the functional requirements of a system | logical design |
the specification of the characteristics of the system components necessary to put the logical design into action | physical design |
AKA green design, it involves systems development efforts that slash power consumption, require less physical space, and result in systems that can be disposed in a way that doesn't negatively affect the environment | environmental design |
a document that specifies in detail required resources such as hardware and software | request for proposal (RFP) |
the primary result of systems design, reflecting the decisions made and preparing the way for systems implementation | design report |
a stage of systems development that includes hardware acquisition, software acquisition or development, user preparation, hiring and training of personnel, site and data preparation, installation, testing, start-up, and user acceptance | systems implementation |
the decision regarding whether to obtain the necessary software from internal or external sources | make-or-buy decision |
the process of readying managers, decision makers, employees, other users, and stakeholders for new systems | user preparation |
preparation of the location of a new system | site preparation |
ensuring all files and databases are ready to be used with new computer software and systems | data preparation, or data conversion |
the process of physically placing the computer equipment on the site and making it operational | installation |
the process of making the final tested information system fully operational | start-up (cutover) |
stopping the old system and starting the new system on a given date | direct conversion (plunge/direct cutover) |
slowly replacing components of the old system with those of the new one | phase-in approach (piecemeal approach) |
running the new system for one group of users rather than all users | pilot start-up |
running both the old and new systems for a period of time and comparing the output of the new system closely with the output of the old system; any differences are reconciled | parallel startup |
a formal agreement signed by the users that states that a phase of the installation or the complete system is approved | user acceptance document |
use of a new or modified system | systems operation |
a stage of systems development that involves checking, changing, and enhancing the system to make it more useful in achieving user and organizational goals | systems maintenance |
the final step of systems development, involving the analysis of systems to make sure that they are operational as intended | systems review |
monitoring the system - the number of errors encountered, the amount of memory required, the amount of processing or CPU time needed, and other problems | system performance measurement |
software that measures all components of the computer-based information system, including hardware, software, database, telecommunications, and network systems | system performance products |