danielmmartinez/dosw-lab1-2026-int-camiloortiz-danielmosquera

Purpose and Scope

This is a small Java lab repository containing two executable programming challenges plus five text-based challenge responses. The README also serves as a candidate/profile landing document, referencing résumé assets.

Entry Points

• Java challenge entry points: Reto1/Reto1.java and Reto2/Reto2.java.

• Non-executable deliverables are stored as plain text in Reto3/Reto3.txt through Reto7/Reto7.txt.

• Repository overview and profile content are in README.md.

Challenge Execution Layer

Reto1/Reto1.java and Reto2/Reto2.java are the only implementation artifacts visible in the repository tree. Each should be treated as an independently compiled and run Java program rather than part of a shared application or package/module structure.

There is no visible build descriptor, source hierarchy, dependency manifest, or test framework. Execution therefore likely depends on direct JDK compilation and invocation per challenge.

Written-Response Deliverables

Challenges three through seven are document-oriented outputs:

• Reto3/Reto3.txt

• Reto4/Reto4.txt

• Reto5/Reto5.txt

• Reto6/Reto6.txt

• Reto7/Reto7.txt

These form a separate delivery path from executable code: they are consumed by reviewers directly rather than by a runtime pipeline.

Candidate/Profile Content

The repository includes résumé/profile material alongside the lab work:

• README.md

• HojaDanielMosquera

• Respuestas.md

README.md links the Daniel résumé asset and references another image asset, HojaDeVidaCamiloOrtiz.jpg, which is not present in the supplied tree. Consumers rendering the README may therefore encounter a missing image.

Runtime and Infrastructure Boundaries

The material runtime is Java/JDK for the two .java files. No server, database, cloud infrastructure, API integration, package manager, CI configuration, or external service dependency is represented in the tree.

The principal boundary is between standalone Java challenge execution (Reto1, Reto2) and static submission documents (Reto3–Reto7, résumé content).

Control and Data Flow

1. A user/reviewer selects an individual challenge directory.

2. For executable challenges, Java source is compiled and run directly from Reto1/Reto1.java or Reto2/Reto2.java.

3. For written challenges, the reviewer reads the corresponding RetoN/RetoN.txt.

4. README/profile assets are rendered independently of challenge execution.

There is no evidence of shared data flow, inter-challenge orchestration, or reusable domain layer across the challenge folders.