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;
87 Cards in this Set
- Front
- Back
system analysis
|
the process of understanding and specifying in detail what the information system should accomplish
|
|
systems design
|
the process of specifying in detail how the many components of the information system should be physically implemented
|
|
systems analyst
|
a business professional who uses analysis and design techniques to solve business problems using information technology
|
|
system
|
a collection of interrelated components that function together to achieve some outcome
|
|
information systems
|
a collection of interrelated components that collect, process, store, and provide as output the information needed to complete business tasks
|
|
subsystems
|
a system that is part of a larger system
|
|
functional decomposition
|
dividing a system into components based on subsystems that are further divided into smaller subsystems
|
|
system boundary
|
the separation between a system and its environment that inputs and outputs must cross
|
|
automation boundary
|
the separation between the automated part of a system and the manual part of a system
|
|
customer relationship management system
|
a system that supports marketing, sales, and service operations involving direct and indirect customer interaction
|
|
supply chain management system
|
a system that seamlessly integrates product development, product acquisition, manufacturing, and inventory management
|
|
accounting and financial management system
|
a system that records accounting information needed to produce financial statements and other reports used by investors and creditors
|
|
human resource management system
|
a system that supports employee related tasks such as payroll, benefits, hiring, and training
|
|
manufacturing management system
|
a system that controls internal production processes that turn raw materials into finished goods
|
|
knowledge management system
|
a system that supports the storage and access to documents from all parts of the organization
|
|
collaboration support system
|
a system that enables geographically distributed personnel to collaborate on projects and tasks
|
|
business intelligence system
|
a system that supports strategic planning and executive decision making
|
|
enterprise resource planning
|
a process in which an organization commits to using an integrated set of software packages for key information systems
|
|
database
|
a centrally managed collection of data that is accessible to many users and systems at the same time
|
|
tools
|
software products used to help develop analysis and design specifications and completed system components
|
|
techniques
|
strategies for completing specific system development activities
|
|
soft skills
|
skills in nontechnical areas such as interviewing, team management, and leadership
|
|
hard skills
|
skills in technical areas such as database design, programming, and telecommunications
|
|
business process re-engineering
|
a technique that seeks to alter the nature of the work done in a business function, with the objective of radically improving performance
|
|
strategic planning
|
a process during which executives try to answer questions about the company such as where the business is now, where they want to be, and what they have to do to get there
|
|
information systems strategic plan
|
the plan defining the technology and application that the information systems function needs to support the organizations strategic plan
|
|
application architecture plan
|
a description of the integrated information systems that the organization needs to carry out its business functions
|
|
technology architecture plan
|
a description of the hardware, software, and communications networks required to implement planned information systems
|
|
project
|
a planned undertaking that has a beginning and an end and that produces a desired result or product
|
|
systems development life cycle
|
teh entire process of building, deploying, using, and updating an information system
|
|
phases
|
related system development activities, which are grouped into categories of project planning, analysis, design, implementation and support
|
|
waterfall model
|
an SDLC approach that assumes the various phases of a project can be completed sequentially--one phase leads(falls) into the next phase
|
|
spiral model
|
an adaptive SDLC approach that cycles over and over again through development activities until a project is complete
|
|
prototype
|
a preliminary working model showing some aspect of a larger system
|
|
iteration
|
system development process in which work activities--analysis, design, implementation--are done once, then again, and yet again on different system components; they are repeated until the system is closer to what is ultimately needed
|
|
incremental development
|
a development approach that completes parts of a system in several iterations and then puts them into operation for users
|
|
project planning
|
the initial activities of the SDLC, whose objective is to identify the scope of the new system and plan the project
|
|
analysis activities
|
the activities of the SDLC whose objective is to understand the user needs and develop requirements
|
|
problem domain
|
the area of the users business for which a system is being developed
|
|
design activities
|
the activities of the SDLC during which the system and programs are designed
|
|
application
|
the portion of the new information system that satisfies the users needs in the problem domain
|
|
implementation activities
|
the activities of the SDLC during which the new system is programmed and installed
|
|
support activities
|
the activities of the SDLC whose objective is to keep the system running productively after it is installed
|
|
help desk
|
the availability of support staff to assist users with any technical or processing problem associated with an information
|
|
system development methodology
|
comprehensive guidelines to follow for completing every activity in the systems development life cycle, including specific models, tools, and techniques
|
|
model
|
a representation of an important aspect of the real world
|
|
tool
|
software support that helps create models or other components required in the project
|
|
integrated development environments
|
tools that help programmers with a variety of programming tasks
|
|
visual modeling tools
|
tools that help the analyst create and verify important system models, often generating program code.
|
|
technique
|
a collection of guidelines that help an analyst complete a system development activity or task
|
|
structured approach
|
system development using structured analysis, and structured programming techniques
|
|
structured program
|
a program or program module that has one beginning and one ending, and for which each step in the program execution consists of sequence, decision, or repetition
|
|
top-down programming
|
dividing more complex programs into a hierarchy of program modules
|
|
structured design
|
a technique providing guidelines for deciding what the set of programs should be, what each program should accomplish, and how the programs should be organized into a hierarchy
|
|
structure chart
|
a graphical model showing the hierarchy of program modules produced by the structured design techniques
|
|
structured analysis
|
a technique used to define what processing the system needs to do, what data it needs to store and use, and what input and outputs are needed
|
|
data flow diagram
|
a structured analysis model showing the inputs, processes, storage, and outputs of a system
|
|
entity-relationship diagram
|
a structured analysis and information engineering model of the data needed by a system
|
|
information engineering
|
a traditional system development methodology thought to be more rigorous and complete than the structured approach because of its focus on strategic planning, and automated tools
|
|
object-oriented approach
|
an approach to system development that views an information systems as a collection of interacting objects that work together to accomplish tasks
|
|
0bject
|
a thing in the computer system that can respond to messages
|
|
object-oriented analysis
|
defining all of the types of objects that do the work in the system and showing what use cases are required to complete tasks
|
|
object-oriented design
|
defining all of the types of objects necessary to communicate with people and devices in the system, showing how objects interact to complete tasks, and refining the definition of each type of object so it can be implemented with a specific language or environment
|
|
0bjec oriented programming
|
writing statments in a programming language to define what each type of object does, including the messages that the objects send to each other
|
|
class diagram
|
a graphical model used in the object-oriented approach to show classes of objects in the system
|
|
unified process
|
an object-oriented system development methodology offered by IBM's Rational Software
|
|
repository
|
a database that stores information about the system in a visual modeling tool, including models, descriptions, and references that link the various models together
|
|
project management
|
organizing and directing other people to achieve a planned result within a predetermined schedule and budget
|
|
oversight committee
|
clients and key managers who review and direct the project
|
|
user
|
the person or group of people who will use the new system
|
|
agile software development
|
a philosophy of software development that embraces flexibility and agility
|
|
weighted scoring
|
a method to prioritize projects based on criteria with unequal weights
|
|
business benefits
|
the benefits that accrue to the organization; often measured in monetary terms
|
|
system scope document
|
a document--containing problem description, business benefits, and system capabilities--to help define the scope of a new system
|
|
proof of concept prototype
|
a very preliminary prototype built to illustrate that a solution to a business need is feasible
|
|
context diagram
|
a data flow diagram showing the scope of a system
|
|
PERT/CPM chart
|
a technique for scheduling a project based on individual tasks or activities
|
|
gantt chart
|
a bar chart that represents the tasks and activities of the project schedule
|
|
slack time
|
the amount of time a task can be delayed without affecting the project schedule (also called float)
|
|
milestone
|
a definite completion point in a schedule in a schedule that is marked by a specific deliverable or event
|
|
risk management
|
the project management area in which the team tries to identify potential trouble spots that could jeopardize the success of the project
|
|
cost/benefit analysis
|
the analysis to compare costs and benefits to see whether investing in the new development of a new system will be beneficial
|
|
net present value
|
the present value of dollar benefits and costs an investment such as a new system
|
|
payback period
|
the time period in which the dollar benefits have offset the dollar costs
|
|
return on investment
|
a measure of the percentage gain from an investment such as a new system
|
|
tangible benefits
|
benefits that can be measured or estimated in terms of dollars and that accrue to the organization
|
|
intangible benefits
|
benefits that accrue to the organization but that cannot be measured quantitatively or estimated accurately
|