Software Development Methodologies Definitions

Search Definitions
  • A

    acceptance testing

    Acceptance testing is a quality assurance (QA) process that determines to what degree an application meets end users' approval.

  • Agile retrospective

    An Agile retrospective is a meeting that's held at the end of an iteration in Agile software development.

  • Agile software development

    Agile is a type of software development methodology that anticipates the need for flexibility and applies a level of pragmatism to the delivery of the finished product.

  • application firewall

    An application firewall is an enhanced firewall that limits access by applications to the operating system (OS) of a computer... (Continued)

  • application security

    Application security, or appsec, is the practice of using security software, hardware, techniques, best practices and procedures to protect computer applications from external security threats.

  • artifact (software development)

    An artifact is a byproduct of software development that helps describe the architecture, design and function of software.

  • authorization

    Authorization is the process of giving someone permission to do or have something.

  • automated testing

    Automated testing is a process that validates if software is functioning appropriately and meeting requirements before it is released into production.

  • B

    BizDevOps (Business, Development and Operations)

    BizDevOps, also known as DevOps 2.0, is an approach to software development that encourages developers, operations staff and business teams to work together so the organization can develop software more quickly, be more responsive to user demand and ultimately maximize revenue.

  • bug

    In computer technology, a bug is a coding error in a computer program.

  • build server

    A build server is a machine on which a software project can be continuously built from changes that are committed to the repository.

  • C

    cache thrash

    Cache thrash is caused by an ongoing computer activity that fails to progress due to excessive use of resources or conflicts in the caching system.

  • Capability Maturity Model (CMM)

    The Capability Maturity Model (CMM) is a methodology used to develop and refine an organization's software development process.

  • code review

    Code review is a phase in the computer program development process in which the authors of code, peer reviewers, and perhaps quality assurance reviewers get together to review code, line by line... (Continued)

  • collaboration diagram

    A collaboration diagram, also known as a communication diagram, is an illustration of the relationships and interactions among software objects in the Unified Modeling Language (UML).

  • continuous quality

    Continuous quality is a systematic approach to finding and fixing software defects during all phases of the software development cycle.

  • cross-site request forgery (XSRF or CSRF)

    Cross-site request forgery (XSRF or CSRF) is a method of attacking a Web site in which an intruder masquerades as a legitimate and trusted user... (Continued)

  • D

    daily stand-up meeting

    A daily stand-up meeting is a short organizational meeting that is held early each day. The practice is commonly used in the Scrum development methodology.

  • DevOps Dojo

    DevOps Dojos provide software developers and operations engineers with an immersive learning environment where team members can gain practical work experience without having to worry about introducing errors into the production environment.

  • Disciplined Agile Delivery (DAD)

    Disciplined Agile Delivery (DAD) is a scalable Agile software delivery framework.

  • dynamic analysis

    Dynamic analysis is the testing and evaluation of a program based on execution with selected data... (Continued)

  • F

    feature-driven development (FDD)

    Feature-driven development (FDD) is an Agile software development methodology that can be used by development teams and managers with the intention of bringing a steady, continuous flow of new features to users at a set time.

  • G

    Gantt chart

    A Gantt chart is a horizontal bar chart developed as a production control tool in 1917 by Henry L. Gantt, an American engineer and social scientist.

  • I

    integer overflow

    Integer overflow is the result of trying to place into computer memory an integer (whole number) that is too large for the integer data type in a given system.

  • iteration

    In agile software development, an iteration is a single development cycle, usually measured as one week or two weeks. (Continued...)

  • iterative

    In the world of IT and computer programming, the adjective iterative refers to a process where the design of a product or application is improved by repeated review and testing.

  • iterative development

    Iterative development is a way of breaking down the software development of a large application into smaller chunks.

  • J

    Jenkins

    Jenkins is an open source continuous integration/continuous delivery and deployment (CI/CD) automation software DevOps tool written in the Java programming language.

  • L

    LDAP injection

    LDAP (Lightweight Directory Access Protocol) injection is a type of security exploit that is used to compromise the authentication process used by some websites.

  • Lean software development

    Lean software development is a concept that emphasizes optimizing efficiency and minimizing waste in the development of software.

  • living documentation

    Living documentation is a dynamic method of system documentation that provides information that is current, accurate and easy to understand.

  • M

    mob programming

    Mob programming is a software development technique where software development teams work on the same tasks at the same time.

  • MoSCoW method

    The MoSCoW method is a four-step approach to prioritizing which project requirements will provide the best return on investment (ROI).

  • P

    pair programming

    Pair programming is an Agile software development technique originating from Extreme programming (XP) in which two developers team together and work on one computer.

  • pigs and chickens

    Pigs and chickens is an analogy used in the Scrum software development model to define the type of role an attendee can play at a daily scrum meeting.

  • pipeline as code

    Pipeline as code is an approach to a continuous integration (CI) pipeline where the pipeline is expressed entirely in computer code.

  • product backlog grooming

    Product backlog grooming is an Agile software development process in which the development team revisits a pre-defined product backlog, working with stakeholders to prioritize and break the backlog list into user stories for future use.

  • product owner

    A product owner is a role on a Scrum team that is accountable for the project's outcome. The product owner is responsible for maximizing product's value by managing and optimizing the product backlog.

  • Project Management Professional (PMP)

    Project Management Professional (PMP) certification is a qualification program overseen by the Project Management Institute (PMI)... (Continued)

  • Q

    quality gate

    A quality gate is a milestone in an IT project that requires that predefined criteria be met before the project can proceed to the next phase.

  • R

    rapid application development (RAD)

    Rapid application development (RAD) is a model based on the concept that higher-quality products can be developed faster through more expedient processes, such as early prototyping, reusing software components and less formality in team communications.

  • release

    A release is the distribution of the final version or the newest version of a software application.

  • release plan

    In agile software development, a release plan is an evolving flowchart that describes which features will be delivered in upcoming releases. (Continued...)

  • S

    Scrum

    Scrum is a framework for project management that emphasizes teamwork, accountability and iterative progress toward a well-defined goal.

  • session ID

    A session ID is a unique number that a Web site's server assigns to identify a specific user for the duration of that user's visit (session)...

  • shift-right testing

    Shift-right testing is a method of continuously testing software while it is in a post-production environment.

  • smoke testing

    Smoke testing, also called build verification testing or build acceptance testing, is nonexhaustive software analysis that ascertains that the most crucial functions of a program work but does not delve into finer details.

  • Software Process Improvement and Capability Determination (SPICE)

    Software Process Improvement and Capability Determination (SPICE) is an international framework to assess software development processes.

  • software resilience testing

    Software resilience testing is a method of software testing that focuses on ensuring that applications will perform well in real-life or chaotic conditions.

  • source code analysis

    Source code analysis is the automated testing of source code for the purpose of debugging a computer program or application before it is distributed or sold.

  • specification by example (SBE)

    Specification by example (SBE) is a user-driven contextual approach to defining software requirements. This approach encourages communication between a project's business owners and the software development team while also aligning software specifications with user acceptance testing.

  • spiral model

    The spiral model is a systems development lifecycle (SDLC) method used for risk management that combines the iterative development process model with elements of the waterfall model.

  • sprint (software development)

    A sprint is a set period of time during which specific work has to be completed and made ready for review. In Agile software development, a sprint raditionally lasts 30 days.

  • SQL injection

    A SQL injection is a technique that attackers use to gain unauthorized access to a web application database by adding a string of malicious code to a database query.

  • SSADM (Structured Systems Analysis and Design Method)

    SSADM (Structured Systems Analysis and Design Method) is a widely used computer application development method in the United Kingdom, where its use is often specified as a requirement for government computing projects.

  • stand-up

    In agile software development, a stand-up is a daily progress meeting, traditionally held within a development area. Business customers may attend for the purpose of gathering information. (Continued...)

  • static testing

    Static testing is a software testing method that examines a program -- along with any associated documents -- but does not require the program to be executed.

  • systems development life cycle (SDLC)

    The systems development life cycle (SDLC) is a conceptual model used in project management that describes the stages involved in an information system development project, from an initial feasibility study through maintenance of the completed application.

  • T

    timebox

    In agile software development, a timebox is a defined period of time during which a task must be accomplished. (Continued...)

  • U

    use case

    A use case is a methodology used in system analysis to identify, clarify and organize system requirements.

  • user story

    A user story is a tool in Agile software development used to capture a description of a software feature from a user's perspective. The user story describes the type of user, what they want and why. A user story helps to create a simplified description of a requirement.

  • V

    V-Model (Vee-Model)

    The V-Model, also called the Vee-Model, is a product-development process originally developed in Germany for government defense projects... (Continued)

  • W

    WAG (estimate)

    A WAG (wild-ass guess) is an estimate for how long it will take to complete a project.  In agile and scrum software development, a WAG is often based upon historical experience. 

  • waterfall model

    The waterfall model is a linear, sequential approach to the software development lifecycle (SDLC) that is popular in software engineering and product development.

  • whole-team approach (team-based approach)

    The whole-team approach (team-based approach) is a style of project management in which everyone on the project team is held equally responsible for the quality and success of the project.

  • work breakdown structure (WBS)

    A work breakdown structure (WBS) is a chart in which the critical work elements, called tasks, of a project are illustrated to portray their relationships to each other and to the project as a whole.

Cloud Computing
App Architecture
ITOperations
TheServerSide.com
SearchAWS
Close