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;
48 Cards in this Set
- Front
- Back
information systems planning
|
translating strategic and organizational goals into systems development initiatives
|
|
creative analysis
|
the investigation of new approaches to existing problems
|
|
critical analysis
|
the unbiased and careful questioning of whether system elements are related in the most effective ways
|
|
mission-critical systems
|
systems that play a pivotal role in an organization's continued operations and goal attainment
|
|
critical success factors (CSFs)
|
factors that are essential to the success of a functional area of an organization
|
|
systems investigation
|
they systems development phase during which problems and opportunities are identified and considered in light of the goals of bu the business
|
|
system analysis
|
the systems development phase involving the study of existing systems and work processes to identify strengths, weaknesses, and opportunities for improvement
|
|
systems design
|
the systems development phase that defines how the information system will do what it must do to obtain the problem solution
|
|
systems implementation
|
the systems development phase involving the creating or acquiring of various system components detailed in the systems design, assembling them, and placing the new or modified system into operation
|
|
systems maintenance and review
|
the systems development phase that ensures the system operates as intended and modifies the system so that it continues to meet changing business needs
|
|
operational prototype
|
a functioning prototype that accesses real data files, edits input data, makes necessary computations and comparisons, and produces real output
|
|
nonoperational prototype
|
a mock-ip, or model, that includes output and input specifications and formats
|
|
rapid application development
|
a systems development approach that employs tools, techniques, and methodologies designed to speed application development
|
|
joint application development
|
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 requirement s of a new or modified system
|
|
end0user systems development
|
any systems development project in which the primary effort is undertaken by a combination of business managers and users
|
|
project schedule
|
a detailed description of what is to be done
|
|
project milestone
|
a critical date for the completion of a major part of the project
|
|
project deadline
|
the date the entire project is to be completed and operational
|
|
critical path
|
activities that, if delayed, would delay the entire project
|
|
program evaluation and review technique
|
a formalized approach for developing a project schedule
|
|
gnaatt chart
|
a graphical tool used for planning, monitoring, and coordinating projects
|
|
computer-aided software engineering
|
tools that automate many of the tasks required in a systems development effort and encourage adherence to the SDLC
|
|
object-oriented systems development
|
an approach to systems development that combines the logic of the systems development life cycle with the power of object-oriented modeling and programming
|
|
systems request form
|
a document filled out by someone who wants the IS department to initiate systems investigation
|
|
feasibility analysis
|
assessment of the technical, economic, legal, operational. and schedule feasibility of a project
|
|
technical feasibility
|
assessment of whether the hardware, software, and other system components can be acquired or developed to solve the problem.
|
|
economic feasibility
|
the determination of whether the project makes financial sense and whether the predicted benefits offset the cost and time needed to obtain them
|
|
net present value
|
the preferred approach for ranking competing projects and determining economic feasibility
|
|
legal feasibility
|
the determination of whether laws or regulations may prevent or limit a systems development project
|
|
operational feasibility
|
the measure of whether the project can be put into action or operation
|
|
schedule feasibility
|
the determination of whether the project can be completed in a reasonable amount of time
|
|
systems investigation report
|
a summary of the results of the systems investigation and the process of feasibility analysis and recommendation of a course of action
|
|
steering committee
|
an advisory group consisting of senior management and users from the IS department and other functional areas
|
|
structured interview
|
an interview where the questions are written in advance
|
|
statistical sampling
|
selecting a random sample of data and applying the characteristics of the sample to the whole group
|
|
data analysis
|
the manipulation of collected data so that the development team members who are participating in systems analysis can use the data
|
|
data-flow diagram
|
a model of objects, associations, and activities that describes how data can flow between and around various objects
|
|
data-flow line
|
arrows that show the direction of data element movement
|
|
process symbol
|
representation of a function that is performed
|
|
data store
|
representation of a storage location for data
|
|
application flowcharts
|
diagrams that show relationships among applications or systems
|
|
grid chart
|
a table that shows relationships among the various aspects of a systems development effort
|
|
CASE repository
|
a database of system descriptions, parameters, and objectives
|
|
requirement analysis
|
the determination of user, stakeholder, and organizational needs
|
|
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
|
|
screen layout
|
a technique that allows a designer to quickly and effectively design the features, layout, and format of a display screen
|
|
report layout
|
a technique that allows designers to diagram and format printed reports
|
|
Systems Development Life Cycle 5
|
1. Systems investigation
2. systems analysis 3. Systems design 4. systems implementation 5. Systems maintenance and Review |