iluwatar / iluwatar/java-design-patterns

Presentation-Abstraction-Control pattern

Open
#304 8 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

  • #1722 by @MightyCorn1105939355 — closed without merging
  • #2009 by @Linly1080 — closed without merging
epic: pattern info: help wanted type: feature
Dominant language
Java
Stars
94.7k
Forks
27.4k
Avg merge
3d 4h
Merged PRs (30d)
10

Description

Description:

The Presentation-Abstraction-Control (PAC) is a design pattern used in software architecture that focuses on the separation of concerns into three interconnected components:

  1. Presentation: Manages the user interface and user interactions.
  2. Abstraction: Encapsulates the business logic and data management.
  3. Control: Mediates the interaction between the presentation and abstraction layers.
Main Elements of the Pattern:
  • Presentation: Handles the graphical or textual representation of the application and the user inputs.
  • Abstraction: Contains the core functionality and business logic.
  • Control: Acts as an intermediary, coordinating the flow of data and commands between the presentation and abstraction layers.
References:
Acceptance Criteria:
  1. Implement a basic example of the PAC design pattern with clear separation between Presentation, Abstraction, and Control components.
  2. Ensure the code follows the project contribution guidelines as outlined in the Java Design Patterns Wiki.
  3. Provide comprehensive documentation and unit tests for the implemented pattern, demonstrating its functionality and interactions between components.

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Research direction

Start by reading the Java Design Patterns contribution guidelines and the linked PAC references, then compare the requested structure with existing examples in the repository. The issue names no implementation files or tests, so the relevant entry point must be located first. Done means a PAC example, comprehensive documentation, and unit tests covering component interactions, with the closed pull requests checked for prior work.

Written by the indexing model from the issue text.

Assessment

Tech stack
java
Domain
backend, documentation, testing
Issue type
Feature
Difficulty
5/5
Estimated time
Over a week
Activity status
Stale
Clarity
Mostly clear
Newbie friendliness
25/100

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.