Key Terms - Part 1 Flashcards
Abstract Class
A class that describes a category or set of objects, but never includes individual objects or instances. It exists so subclasses can inherit from it.
Activity Diagrams
A UML diagram that describes user (or system) activities, the person who does each activity, and the sequential flow of these activities.
Predictive Approach to the SDLC
An approach that assumes the project can be planned in advance, and that the new information system can be developed according to that plan.
Adaptive Approach to the SDLC
An approach that assumes that the project must be more flexible and adapt to changing needs as the project progresses.
Alpha Version
A test version that is incomplete, but ready for some level of rigorous integration or usability testing.
Beta Version
A test version that is stable enough to be tested by end users over an extended period of time.
Client-Server Architecture
A computer network configuration with users’ computers and a central computer that provide common services.
Component Diagram
A UML implementation diagram that shows the overall system architecture and the logical components within it. It identifies the logical, reusable, and transportable system components that define the system architecture.
Communication Diagram
A UML interaction diagram that emphasizes the objects that send and receive messages for a specific use case.
Data Access Class
A class that is used to retrieve data from and send data to a database. It is used to implement the bridge between data stored in program objects, and the data existing in the relational database.
Database Normalization
A formal technique for evaluating and improving the quality of a relational database schema. It determines whether a database is flexible, and whether it contains “wrong” kinds of redundancy.
Database Management System (DBMS)
A system software component that manages and controls one or more databases.
Deployment
The final phase of the SDLC, in which the solution, either a system or a subsystem, is put into operation.
Design Pattern
Standard design techniques and templates that are widely recognized as good practice. They were identified by the Gang of Four (GoF) and are used in object-oriented programming.
Dialog Metaphor
A metaphor for human-computer interaction, in which user and computer accomplish a task by engaging in a conversation or dialog via text voice, or tools such as labeled buttons.
Digital Signature
A technique in which a document is encrypted by using a private key to verify who wrote the document.
Encryption
The process of altering data so unauthorized users can’t view them.
Decryption
The process of converting encrypted data back to their original state.
End Users
Individuals or groups of individuals who use an information system to accomplish specific tasks or goals. They interact directly with the system and use it to carry out their work or activities.
Event
Something that occurs at a specific time and place, can be precisely identified, and must be remembered by the system.
Human-Computer Interaction (HCI)
The field of study that focuses on optimizing how users and computers interact by designing interactive computer interfaces that satisfy users’ needs.
Integrity Control
A control that rejects invalid data inputs, prevents unauthorized data outputs, and protects data and programs against accidental or malicious tampering.
Object
A “thing” in an information system that responds to messages by executing functions or methods.
Object-Oriented Design (OOD)
Process by which a set of detailed object-oriented design models are built and then used by the programmers to write and test the new system.
Model
Representation of some aspect of a system.
Pair Programming
Extreme Programming (XP) practice in which two programmers work together on designing, coding, and testing software.
Perfect Technology Assumption
The assumption that a system runs under perfect operating and technological conditions.
Project
A planned undertaking that has a beginning and an end, that produces some definite result.
Relational Database
A database that stores information in tables or relations, with rows representing unique records and columns representing data elements.
Requirements
In a system, the activities that the system must perform or support, and the constraints that the system must meet.
Requirements Determination
The process of identifying, analyzing, and documenting the needs and constraints of stakeholders for a new or improved system.
Scrum
An adaptive software development methodology of which the objective is to be quick, agile, intense, and go the entire distance.
Systems Development Life Cycle (SDLC)
The entire process consisting of all activities required to build, launch, and maintain an information system.
Security Controls
The controls that protect the assets of an organization from all threats, with a primary focus on external threats.
Stakeholders
Individuals who have an interest in the successful implementation of the system.
System
An information system is a set of interrelated computer components that collects, processes, stores, and provides as output the information needed to complete business tasks.
System Interface
Input or output that requires minimal human interaction.
System Vision Document
A document to help define the scope of a new system.
System Development Methodology
A set of comprehensive guidelines for the SDLC that includes specific models, tools, and techniques.
Top-Down Development
A development order that implements top-level modules first.
Botton-Up Development
A development that implements low-level detailed modules first.
Three-Layer Architecture
A client-server architecture that divides an application into a view layer, a business logic layer, and a data layer.
Unified Modeling Language (UML)
Standard set of model constructs and notations defined by the Object Management Group.
Unified Process (UP)
Object-oriented system development methodology that uses UML for system models and describes a new, adaptive SDLC.
Unit Testing
Test of an individual method, class, or component before it is integrated with other software.
Usability Test
A test to determine whether a method, class, subsystem, or system meets user requirements.
Use Case
An activity that the system performs, usually in response to a request by a user.
Use Case Realization
The process of elaborating the detailed design with interaction diagrams for a particular use case.
User Goal Technique
A technique to identify use cases by determining what specific goals or objectives must be completed by a user.
User Interface
System interfaces (inputs and outputs) that more directly involve a system user.
