Fundamentals of Information Systems, Fifth Edition 8-1
Ch. 8 Key Terms
Asking directly—an approach to gather data that asks users, stakeholders, and other managers about what
they want and expect from the new or modified system.
Computer-aided software engineering (CASE)—tools that automate many of the tasks required in a
systems development effort and encourage adherence to the SDLC.
Data analysis—manipulation of the collected data so that the development team members who are
participating in systems analysis can use the data.
Data preparation, or data conversion—ensuring all files and databases are ready to be used with new
computer software and systems.
Data-flow diagram (DFD)—a model of objects, associations, and activities that describes how data can
flow between and around various objects.
Design report—the primary result of systems design, reflecting the decisions made and preparing the way
for systems implementation.
Direct conversion (also called plunge or direct cutover)—stopping the old system and starting the new
system on a given date.
Direct observation—watching the existing system in action by one or more members of the analysis team.
Economic feasibility—determination of whether the project makes financial sense and whether predicted
benefits offset the cost and time needed to obtain them.
End-user systems development—any systems development project in which the primary effort is
undertaken by a combination of business managers and users.
Feasibility analysis—assessment of the technical, economic, legal, operational, and schedule feasibility of
a project.
Information systems planning—translating strategic and organizational goals into systems development
initiatives.
Installation—the process of physically placing the computer equipment on the site and making it
operational.
Joint application development (JAD)—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.
Legal feasibility—determination of whether laws or regulations may prevent or limit a systems
development project.
Logical design—a description of the functional requirements of a system.
Make-or-buy decision—the decision regarding whether to obtain the necessary software from internal or
external sources.
Object-oriented systems development (OOSD)—approach to systems development that combines the
logic of the systems development life cycle with the power of object-oriented modeling and programming.
Operational feasibility—measure of whether the project can be put into action or operation.
Parallel 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. When users are
comfortable that the new system is working correctly, the old system is eliminated.
Phase-in approach, or piecemeal approach—slowly replacing components of the old system with those
of the new one. This process is repeated for each application until the new system is running every
application and performing as expected.
Physical design—the specification of the characteristics of the system components necessary to put the
logical design into action.
Pilot start-up—running the new system for one group of users rather than for all users.
Programmer—specialist responsible for modifying or developing programs to satisfy user requirements.
