Reading...
Play button
Play button
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;
67 Cards in this Set
- Front
- Back
|
Systems analysis
|
process of understanding and specifying in detail what the information system should accomplish
|
|
|
Systems design
|
process of specifying in detail how the many components of the information system should be implemented
|
|
|
Systems analyst
|
business professional who uses analysis and design techniques to solve business problems using IT
|
|
|
system
|
collection of interrelated components that function together to achieve some outcome
|
|
|
subsystem
|
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 subsystem and the manual part of a system
|
|
|
customer relationship management (CRM) system
|
system that supports marketing, sales, and service operations involving direct and indirect customer interaction
|
|
|
information system:
|
collection of interrelated components that collect, process, store and provide as output the information needed to compute business tasks
|
|
|
supply chain management (SCM) system
|
system that seamlessly integrates product development, product acquisition, manufacturing, and inventory management
|
|
|
accounting and financial management (AFM) system
|
system that records accounting information needed to produce financial statements and other reports used by investors and creditors
|
|
|
human resources management (HRM) system
|
system that supports employee-related tasks such as payroll, hiring and training
|
|
|
manufacturing management system
|
system that controls internal production process that turn raw materials into finished goods
|
|
|
knowledge management system (KMS)
|
system that supports the storage of and access to documents from all parts of the organization
|
|
|
collaboration support system (CSS)
|
system that enables geographically distributed personnel to collaborate on projects and tasks
|
|
|
business intelligence system
|
system that supports strategic planning and executive decision making
|
|
|
enterprise resource planning (ERP)
|
process in which an organization commits to using an integrated set out software packages for key information systems
|
|
|
database
|
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 systems
|
|
|
techniques:
|
strategies for completing specific system development activities
|
|
|
soft skills:
|
skills in non-technical areas such as interviewing, team-manager, and leadership
|
|
|
hard skills:
|
skills in technical areas such as database design, programming, and telecommunications
|
|
|
business process reengineering:
|
technique that seeks to alter the nature of the work done in a business function, with the objective of radically improving performance
|
|
|
strategic planning:
|
process during which executives try to answer questions about the company, such as where the business is now, where they want the business to be, and what they have to do to get there
|
|
|
information systems strategic plan:
|
plan defining the technology and applications that the information systems function needs to support the organization's strategic plan
|
|
|
application architecture plan:
|
description of the integrated information systems that the organization needs to carry out its business functions
|
|
|
technology architecture plan:
|
description of the hardware, software, and communications networks required to implement planned information systems
|
|
|
project:
|
planned undertaking that has a beginning and an end and that produces a desired result or product
|
|
|
systems development life cycle (SDLC):
|
the entire process of building, deploying, using, and updating an information system
Planning, Analyzing, Designing, Implementing, Supporting |
|
|
predictive approach
|
an SDLC approach that assumes the development project can be planned and organized in advance and that the new information system can be developed according to the plan
|
|
|
adaptive approach
|
an SDLC approach that is more flexible, assuming that the project cannot be planned out completely in advance but must be modified as it progresses
|
|
|
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 falls into the next phase
|
|
|
spiral model
|
an adaptive SDLC approach that cycles over and over again through development activities until a project completes
|
|
|
prototype
|
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 components, they are repeated until the system is closer to what is ultimately needed
|
|
|
incremental development
|
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
|
activities of the SDLC whose objective is to understand the user needs and develop requirements
|
|
|
problem domain
|
the area of the user's business for which a system is being developed
|
|
|
design activities
|
activities of the SDLC during which the system and programs are designed
|
|
|
application
|
portion of the new information system that satisfies the user's needs in the problem domain
|
|
|
implementation activities
|
activities of the SDLC during which the new system is programmed and installed
|
|
|
support activities
|
activities of the SDLC whose objective is to keep the system running productively after it is installed
|
|
|
help desk
|
availability of support staff to assist users with any technical or processing problem associated with information system
|
|
|
system development methodology
|
comprehensive guidelines to follow for completing every activity in the systems development life cycle, including specific models, tool, and techniques
|
|
|
model
|
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 (IDE)
|
tools that help programmers with a variety of programming task
|
|
|
visual modeling tools
|
tools that help the analyst create and verify important system models, often generating program code
|
|
|
technique
|
collection of guidelines that help an analyst complete a system development activity or task
|
|
|
structured approach
|
system development using structured analysis, structured design, and structured programming techniques
|
|
|
structured program
|
program or a program module that has one beginning and one ending, and each step in the program consists of sequence, decision, or repetition constructs
|
|
|
top-down programming
|
dividing more complex programs into a hierarchy or program modules
|
|
|
structured design
|
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
|
graphical model showing the hierarchy of program modules produced by the structured design technique
|
|
|
structured analysis
|
technique used to define what processing the system needs to do, what data it needs to store and use, and what inputs and outputs are needed
|
|
|
data flow diagram (DFD)
|
structured analysis model showing the inputs, processes, storage, and outputs of a system
|
|
|
entity-relationship diagram (ERD)
|
a structured analysis and information engineering model of the data needed by a system
|
|
|
information engineering:
|
traditional system development methodology thought to be more rigorous and complete than the structured approach, because of its focus on strategic planning, data modeling, and automated tools
|
|
|
object-oriented approach:
|
approach to system development that views an information system as a collection of interacting objects that work together to accomplish tasks
|
|
|
object:
|
a thing in the computer system that can respond to messages
|
|
|
object-oriented analysis (OOA):
|
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 (OOD):
|
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
|
|
|
unified process (UP):
|
object-oriented system development methodology offered by IBM's rational software
|
|
|
repository:
|
database that stores information about the system in a visual modeling tool, including models, descriptions, and references that link various models together
|
