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;
39 Cards in this Set
- Front
- Back
|
Project
|
a planned undertaking that has a beginning and an edn and that produces a desired result or product
|
|
|
Systems Development Life Cycle (SDLC)
|
the entire process of builing, deploying, using, and updating an info system
|
|
|
Predictive Approach
|
an SDLC approach that assumes the development projet can be planned and organized in advance and that the new info system acn 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 and 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 Method
|
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 user's 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 info system that satisfies the user's 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 technicial or processing problems associated with an info system
|
|
|
System Development Methodology
|
comprehensive guidelines to follow for completing every activitiy in the SDLC, including specific models, tools, and techniques
|
|
|
Model
|
a representation of an important aspect of the real world
|
|
|
Tool
|
software support that helps create models of other components required in the project
|
|
|
Technique
|
a collection of guidelines that help an analyst complete a system development activity or task
|
|
|
Structured Approach
|
system development suing structured analysis, structured design, 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 constructs
|
|
|
Top-Down Programming
|
dividing more compelxt programs into a hierarchy of program modules
|
|
|
Strucutred 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
|
|
|
Strucutured Analysis
|
a technique used to define what the processing system needs to do, what data it needs to store and use, and what inputs and outputs are needed
|
|
|
Data Flow Diagram (DFD)
|
a 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
|
a traditional system development methodoly thought to be more rigorous and complete than the structured approach, beacuse of its focus on strategic planning, data modeling, and automated tools
|
|
|
Object Oriented Approach
|
an approach to system development that views an info 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
|
defining all of the types of objects that do the work in the system and showing what uses 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
|
|
|
Object Oriented Programming
|
writing statements in a programming language to define what each type of object does, including the message that the object sends to each other
|
|
|
Class Diagram
|
a graphical model used in the object oriented approach to show classes of objects in the system
|
|
|
Unified Process (UP)
|
an object oriented system development methodology offered by IBM's Rational Software
|
|
|
Repository
|
a database that stores info about the system in a visual modeling tool, including models, descriptions, and references that link the various models together
|
