D3IS Acquisition & Development

IS Acquisition & Development: Glossary

Acceptance Testing
The final testing phase performed by end users to validate that a system meets business requirements and is ready for production deployment.
Agile Development
An iterative and incremental software development methodology that emphasizes flexibility, collaboration, continuous delivery, and rapid response to change.
Application Controls
Controls embedded within business process applications to ensure completeness, accuracy, authorization, and validity of transaction processing.
Baseline
A formally approved version of a configuration item that serves as the basis for further development and can be changed only through formal change management.
Black Box Testing
A testing method where the tester evaluates functionality without knowledge of the internal code structure. Tests are based on requirements and specifications.
Change Control Board (CCB)
A formal group responsible for reviewing, evaluating, approving, or rejecting proposed changes to a system or project. It ensures changes are managed and documented.
Change Management
A structured process for requesting, evaluating, approving, implementing, and reviewing changes to IT systems and infrastructure.
Configuration Management
The process of tracking and controlling changes to software and hardware configurations. It maintains the integrity of products by recording and managing configuration items.
Data Conversion
The process of migrating data from an existing system to a new system. It requires planning, validation, and verification to ensure data integrity.
DevOps
A methodology that combines software development and IT operations to shorten the systems development lifecycle while delivering features, fixes, and updates frequently.
Feasibility Study
An analysis conducted during the early stages of a project to determine whether the proposed system is technically, economically, and operationally viable.
Function Point Analysis (FPA)
A method for measuring the functional size of software based on the functions delivered to the user. It is independent of the technology used for implementation.
Integration Testing
Testing performed to verify that individual software modules or components work correctly when combined together as a group.
Object-Oriented Design
A software design approach that organizes code around objects (which combine data and behavior) rather than functions and logic.
Parallel Testing
A testing approach where the old and new systems run simultaneously to compare results and verify that the new system produces accurate output.
Prototyping
A development approach where a preliminary version of the system is built to clarify requirements and allow users to provide feedback before full development.
Quality Assurance (QA)
A systematic process of ensuring that software development and delivery meet specified requirements and standards throughout the development lifecycle.
Regression Testing
Testing conducted after changes or fixes to ensure that existing functionality has not been adversely affected by the modifications.
Requirements Traceability Matrix
A document that maps requirements to their corresponding test cases, ensuring all requirements are tested and accounted for throughout development.
SDLC (Systems Development Life Cycle)
A structured methodology for developing information systems through defined phases: feasibility, requirements, design, development, testing, implementation, and maintenance.
Sociability Testing
Testing that verifies a new or modified application can operate within its production environment without negatively impacting other existing systems.
System Testing
Testing performed on the complete, integrated system to evaluate compliance with specified requirements in a simulated production environment.
Unit Testing
The testing of individual program modules or components in isolation to verify that each unit functions correctly according to its design specifications.
User Acceptance Testing (UAT)
Formal testing conducted by end users to determine whether the system satisfies the acceptance criteria and business requirements before deployment.
V-Model
A software development model that pairs each development phase with a corresponding testing phase, emphasizing verification and validation at every stage.
Waterfall Model
A sequential software development methodology where each phase (requirements, design, implementation, testing, deployment, maintenance) must be completed before the next begins.
White Box Testing
A testing method where the tester has full knowledge of the internal code structure. Tests are designed to exercise specific code paths and logic.