Skip to main content

Methodology Terms

Comprehensive glossary of GISE methodology-specific terms and concepts. Understanding these terms is essential for effective communication and implementation of the GISE framework.

Core Methodology Terms​

4D Methodology​

The foundational framework of GISE consisting of four sequential phases:

  • Discover: Requirements gathering and analysis
  • Design: Architecture planning and technical specification
  • Develop: Implementation and testing with AI assistance
  • Deploy: Production deployment and operational setup

Context: "The 4D methodology ensures systematic progression from concept to production."

Blueprint​

A detailed technical specification that bridges design and implementation phases. Includes API specifications, database schemas, and deployment configurations.

Context: "Technical blueprints provide developers with precise implementation guidance." Related Terms: Technical Blueprint, System Design

Container-First Development​

Development approach that prioritizes containerized environments from the beginning of the project, ensuring consistency across development, testing, and production environments.

Context: "Container-first development eliminates environment-specific bugs and deployment issues." Related Terms: Container, Hosting, DevOps

GIT-First Approach​

Methodology principle that version controls all project artifacts, including documentation, diagrams, and configurations, not just source code.

Context: "GIT-first approach ensures complete project history and enables collaborative development." Related Terms: Git, Documentation as Code

Phase Gate​

Quality checkpoint between GISE phases that validates deliverables before proceeding to the next phase.

Context: "Phase gates ensure quality and completeness before advancing to the next development stage." Related Terms: Quality Gate, 4DDR, Review Process

Recipe​

Reusable pattern or template that provides proven solutions for common development tasks within the GISE methodology.

Context: "GISE recipes accelerate development by providing tested implementation patterns." Related Terms: Pattern, Template, Best Practice

Stakeholder Mapping​

Process of identifying all parties affected by or influencing a project, documenting their roles, interests, and communication requirements.

Context: "Stakeholder mapping ensures all perspectives are considered during the Discover phase." Related Terms: Requirements Gathering, User Research

Technical Blueprint​

Comprehensive technical specification document created during the Design phase that details system architecture, API contracts, database schemas, and deployment requirements.

Context: "Technical blueprints serve as the definitive reference for implementation teams." Related Terms: Design, API

Vibe Coding​

Development approach that combines AI assistance with human oversight to accelerate implementation while maintaining code quality and understanding.

Context: "Vibe coding sessions use AI to generate initial implementations that developers then review and refine." Related Terms: AI Pair Programming, Code Generation

Process and Workflow Terms​

Acceptance Criteria​

Specific, testable conditions that define when a user story or feature is complete and acceptable to stakeholders.

Context: "Clear acceptance criteria prevent scope creep and ensure deliverable quality." Related Terms: User Story, Definition of Done

Architectural Decision Record (ADR)​

Document that captures an important architectural decision along with its context, alternatives considered, and consequences.

Context: "ADRs help teams understand the reasoning behind technical choices and their implications." Related Terms: 4DDR, Architecture Documentation, Decision Log

4D Decision Record (4DDR)​

Lightweight decision documentation that captures decisions across all four GISE phases (Discover, Design, Develop, Deploy), extending traditional ADRs to cover the entire development lifecycle.

Context: "4DDRs ensure decision traceability from user research through production deployment." Related Terms: Decision Record, Phase Gate, Architectural Decision Record (ADR)

Continuous Integration/Continuous Deployment (CI/CD)​

Automated practices for integrating code changes and deploying applications to production environments.

Context: "CI/CD pipelines in GISE projects include quality gates and automated testing at each phase." Related Terms: Automation, Quality Gate

Decision Record​

Structured documentation that captures the context, rationale, and consequences of significant decisions made during project development.

Context: "Decision records provide future team members with understanding of why specific choices were made." Related Terms: 4DDR, Architectural Decision Record (ADR), Documentation

Decision Traceability​

The ability to track and understand the relationships between decisions, their evolution over time, and their impact on project outcomes.

Context: "4DDRs enable decision traceability across all phases, from user research to production deployment." Related Terms: 4DDR, Status Lifecycle, Audit Trail

Definition of Done​

Shared understanding of work quality standards that must be met before considering a deliverable complete.

Context: "The definition of done includes code review, testing, documentation, and security validation." Related Terms: Acceptance Criteria, Quality Standards

Epic​

Large body of work that can be broken down into multiple user stories and typically spans multiple development iterations.

Context: "Epics help organize complex features into manageable development increments." Related Terms: User Story, Feature

Feature Branch​

Git branching strategy where each feature is developed in an isolated branch before being merged into the main codebase.

Context: "Feature branches enable parallel development and code review before integration." Related Terms: Git, Pull Request

Minimum Viable Product (MVP)​

Version of a product with sufficient features to satisfy early customers and provide feedback for future development.

Context: "GISE methodology helps teams define and deliver MVPs efficiently through the 4D process." Related Terms: Prototype, Product Strategy

Pull Request (PR)​

Mechanism for proposing changes to a codebase that includes peer review and automated quality checks.

Context: "Pull requests in GISE projects must include updated documentation and pass all quality gates." Related Terms: Code Review, Quality Gate

Retrospective​

Regular team meeting to reflect on processes, identify improvements, and adjust practices for future iterations.

Context: "Phase retrospectives help teams continuously improve their implementation of GISE methodology." Related Terms: Continuous Improvement, Team Process

Sprint​

Time-boxed development cycle (typically 1-4 weeks) focused on delivering specific features or improvements.

Context: "GISE phases can be organized into sprints with clear deliverables and review points." Related Terms: Iteration, Agile

Status Lifecycle​

Defined progression of states that a decision record or deliverable moves through from initial proposal to final resolution.

Context: "4DDR status lifecycle includes Proposed → Accepted → Superseded → Deprecated → Archived states." Related Terms: 4DDR, Decision Record, Process Management

Superseded​

Status indicating that a decision has been replaced by a newer decision due to changed requirements or better solutions.

Context: "Superseded 4DDRs maintain historical context while pointing to replacement decisions." Related Terms: Status Lifecycle, 4DDR, Change Management

User Story​

Short description of a feature from the end user's perspective, typically following the format "As a [user], I want [goal] so that [benefit]."

Context: "User stories drive feature development and ensure focus on user value throughout the GISE process." Related Terms: Acceptance Criteria, Epic

Quality and Standards Terms​

Code Review​

Systematic examination of source code by peers to identify bugs, improve quality, and share knowledge.

Context: "Code reviews in GISE projects also verify adherence to architectural decisions and patterns." Related Terms: Pull Request, Quality Assurance

Quality Assurance (QA)​

Systematic activities to ensure deliverables meet defined quality standards and requirements.

Context: "QA in GISE methodology includes automated testing, security scans, and compliance validation." Related Terms: Testing Strategy, Quality Gate

Quality Gate​

Checkpoint that enforces quality standards before allowing progression to the next development phase.

Context: "Quality gates prevent technical debt and ensure consistent standards across all deliverables." Related Terms: Phase Gate, Definition of Done

Technical Debt​

Implied cost of additional rework caused by choosing quick solutions instead of better approaches that would take longer.

Context: "GISE methodology includes explicit technical debt tracking and remediation planning." Related Terms: Code Quality, Refactoring

Test Coverage​

Measure of how much source code is exercised by automated tests, typically expressed as a percentage.

Context: "GISE projects maintain minimum test coverage thresholds as part of quality gates." Related Terms: Regression Testing, Unit Testing, Integration Testing

Documentation and Communication Terms​

Documentation as Code​

Practice of storing documentation in version control systems alongside source code, often written in markup languages.

Context: "Documentation as code ensures technical documentation stays synchronized with implementation." Related Terms: GIT-First Approach, Git

Living Documentation​

Documentation that automatically updates based on code changes, staying current without manual intervention.

Context: "API documentation generated from code comments exemplifies living documentation principles." Related Terms: API Documentation, Code Comments

Runbook​

Document containing procedures for maintaining and operating a system in production environment.

Context: "Deployment runbooks ensure consistent and reliable production operations." Related Terms: Operations Manual, Standard Operating Procedure

Standard Operating Procedure (SOP)​

Documented process that provides step-by-step instructions for routine operational activities.

Context: "SOPs ensure consistent execution of critical processes across team members." Related Terms: Runbook, Process Documentation

Technology and Architecture Terms​

API Gateway​

Service that acts as an entry point for multiple backend services, handling routing, authentication, and other cross-cutting concerns.

Context: "API gateways provide centralized control and monitoring for microservice architectures." Related Terms: Microservices, Service Architecture

Microservices​

Architecture pattern that structures applications as collections of loosely coupled, independently deployable services.

Context: "GISE methodology provides guidance on when to choose microservices versus monolithic architectures." Related Terms: Service Architecture, Distributed Systems

Monolith​

Architecture pattern where all components of an application are interconnected and deployed as a single unit.

Context: "Modular monoliths are often recommended as a starting point in GISE projects." Related Terms: Architecture Pattern, System Design

REST API​

Architectural style for distributed systems that uses HTTP methods and follows specific constraints for resource interaction.

Context: "GISE projects typically use RESTful APIs for service communication and client interfaces." Related Terms: API, HTTP

Team and Collaboration Terms​

Cross-functional Team​

Group with all skills necessary to deliver features, including development, design, testing, and domain expertise.

Context: "GISE methodology works best with cross-functional teams that can execute all four phases." Related Terms: Team Composition, Skill Diversity

Pair Programming​

Agile software development technique where two programmers work together at one workstation.

Context: "Pair programming sessions enhance knowledge sharing and code quality in GISE projects." Related Terms: Code Review, Knowledge Sharing

Product Owner​

Person responsible for defining product requirements, prioritizing features, and accepting completed work.

Context: "Product owners guide the Discover phase and validate deliverables throughout GISE implementation." Related Terms: Stakeholder, Requirements Management

Scrum Master​

Facilitator who helps teams implement Agile practices and removes impediments to progress.

Context: "Scrum masters can help teams adopt and improve their GISE methodology implementation." Related Terms: Agile Coach, Process Improvement

Technical Lead​

Senior developer responsible for technical decisions, architecture guidance, and team mentoring.

Context: "Technical leads play crucial roles in GISE Design and Deploy phases." Related Terms: Architecture, Technical Leadership

Usage Guidelines​

For New Team Members​

Start with Core Methodology Terms to understand GISE fundamentals before diving into specific technical concepts.

For Project Managers​

Focus on Process and Workflow Terms and Quality and Standards Terms to understand project management aspects.

For Technical Teams​

Review Technology and Architecture Terms along with core methodology concepts for comprehensive understanding.

For Stakeholders​

Team and Collaboration Terms and Documentation and Communication Terms provide context for effective project participation.

Related Resources: