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
Project
|
A 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
|
|
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
|
|
Waterfall Approach
|
As 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
|
|
Incremental Development
|
A development approach that completes parts of a system in several iterations and then puts them into operation for users
|
|
System Development Methodology
|
"Guidelines to follow for completing every activity in systems development
|
|
Model
|
A representation of an important aspect of the real world
|
|
Unified Modeling Language (UML)
|
A standard set of model constructs and notations developed specifically for object-oriented development
|
|
Tool
|
Software support that helps create models or other components required in the project
|
|
CASE Tool
|
A computer-aided system engineering tool that helps a system analyst complete development task
|
|
Technique
|
A collection of guidelines that help an analyst complete a system development activity or task
|
|
Best Practices
|
Generally accepted approaches for completing a system development task that have been proven over time to be effective
|
|
Unified Process (UP)
|
"An object-oriented system development methodology originally developed by Grady Booch
|
|
Use Case
|
"An activity the system carries out
|
|
Discipline
|
A set of functionally related activities that together contribute to one aspect of a UP development project
|
|
Artifact
|
UP work products
|
|
Problem Domain
|
The area of the user's business that needs an information system solution
|
|
Object-oriented Approach
|
A system development approach 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 message
|
|
Object-oriented Analysis (OOA)
|
Defining all of the types of objects that do the work in a system and showing what user interactions 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
|
|
Object-oriented Programming (OOP)
|
"Writing statements in a programming language to define what each type of object does
|
|
Naturalness
|
"Characteristic of the object-oriented approach that describes its match with the way people usually think about their world - that is
|
|
Reuse
|
Benefit of the object-oriented approach that allows classes and objects to be invented once and used many times
|
|
User Interface Object
|
"An object the user interacts with while using the system
|
|
Attributes
|
"Object characteristics that have values
|
|
Methods
|
Behaviors or operations that describe what an object is capable of doing
|
|
Problem Domain Objects
|
"Objects that are specific to a business application - for example
|
|
Class
|
A type or classification to which all similar objects belong
|
|
Instance
|
A synonym for object
|
|
Messages
|
"Communications between objects in which one object asks another object to invoke
|
|
Association Relationship
|
"Naturally occurring relationships between objects
|
|
Multiplicity
|
The number of association between objects
|
|
Encapsulation
|
Combining attributes and methods into one unit and hiding it internal structure of objects
|
|
Information Hiding
|
A characteristic of object-oriented development in which data associated with an object are not visible to the outside world
|
|
Identity
|
A unique reference to an object that allows another object to find it and send it a message
|
|
Persistent Objects
|
Objects that a system remembers and that are available for use over time
|
|
Inheritance
|
A concept in which one class of objects shares some characteristics of another class
|
|
Superclass
|
"A general class in a generalization/specialization hierarchy
|
|
Subclass
|
"A specialization class in a generalization/specialization hierarchy
|
|
Generalization/Specialization Hierarchy
|
A classification system that structures or ranks classes from the more general superclass to the more specialized subclasses; also called inheritance hierarchy
|
|
Polymorphism
|
A characteristic of objects that allows them to respond differently to the same message
|
|
Repository
|
"A database of information about the system used by a CASE tool
|
|
Round-trip Engineering
|
Automating the process of synchronizing graphical models with program code so changes to code automatically update the models and change to models automatically update the code.
|