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;
47 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, deploying, using, and updating an information system
|
|
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
|
|
Waterfall approach
|
an SDLC approach that assumes the various phases of a project can be completed sequentially
|
|
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
|
systems 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 needed
|
|
Incremental development
|
a development approach that completes parts of a system in several iterations and then puts them into operation for users
|
|
Systems development methodology
|
guidelines to follow for completing every activity in systems development, including specific models, tools, and techniques
|
|
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 systems analyst complete development tasks
|
|
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, James Rumbaugh, and Ivar Jacobson
|
|
Use case
|
an activity the system carries out, usually in response to a request by the user
|
|
Discipline
|
a set of functionally related activities that together contribute to one aspect of a UP development project
|
|
Artifacts
|
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 view an information system as a collection of interacting object 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 a system and showing what user interactions are required to complete tasks
|
|
Object-oriented design (OOD)
|
defining all of the types of object necessary to communicate with people and devices in the system, showing how the object 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 messages that the object send to each other
|
|
Naturalness
|
characteristic of the object-oriented approach that describes its match with the way people usually think about their world
|
|
Reuse
|
benefit of the object-oriented approach that allows classes and object to be invented once and used many times
|
|
User interface object
|
an object the user interacts with while using the system, such as a button, menu item, text box, or label
|
|
Attributes
|
object characteristics that have values, such as the size, shape, color, location, and caption of a button or label or the name, address, and phone number of a customer
|
|
Methods
|
behaviors or operations that describe what an object is capable of doing
|
|
Problem domain objects
|
objects that are specific to a business application
|
|
Class
|
a type or classification to which all similar objects belong
|
|
Instance
|
a synonym for object
|
|
Messages
|
communications between object in which one object asks another object to invoke, or carry out, one of its methods
|
|
Association Relationships
|
naturally occurring relationships between objects, such as when a customer is associated with its orders
|
|
Multiplicity
|
the number of associations between objects
|
|
Encapsulation
|
combining attributes and methods into one unit and hiding its 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 which one class of objects shares some characteristics of another class
|
|
Superclass
|
a general class in a generalization / specialization hierarchy, which can be extended by a subclass
|
|
Subclass
|
a specialized class in a generalization / specialization hierarchy, which contains additional attributes and methods distinguishing it from a more general class that it extends
|
|
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, including models, descriptions, and references that link the various models
|