How syskantechnosoft/2105pythonbatch works
Project type and purpose
• This is not a single application but a monorepo of multiple small sample projects and exercises for “2105PythonBatch” training.
• It contains educational micro-projects in Python (Day1Python, Day2Python, IntroToTDD, WikiAutomationPython, etc.), Java (HelloWorld2, CommunityLibrariAPI, JavaDay2, JavaDay3, JavaDay4, LibraryAPI, encapsulation, etc.), web front-ends (PyBookFrontend, DOM examples), BDD/Selenium automation (BDD/wikiautomation2, WikiAutomationJava), and various docs and reviews.
File structure
• Top-level folders each represent an independent module or lesson:
• DayN…Python: Python language fundamentals
• CommunityLibrariAPI / LibraryAPI: Java REST API microservices (Spring or plain Java)
• WikiAutomation… / BDD: Automation test suites using Selenium/WebDriver + Cucumber
• DOM, clientsidereview, asyncjs: Front-end JavaScript/HTML demos
• encapsulation, JavaDayN: Java OOP exercises
• IntroToTDD, Seleniumwaits, Seleniumbasics: Testing frameworks and patterns
• Each Java project follows a Maven layout (pom.xml, src/main/java, src/test/java). Python exercises follow plain-script layouts with modules and tests.
README
• Only a title (“2105PythonBatch”) is provided—no high-level architecture described.
• We must infer that this repo’s “architecture” is a structured curriculum rather than a runtime system.
a. Main components
• Monorepo root (“2105PythonBatch”)
• Language tracks: Python track, Java track, Front-end track, Automation track
• Within each track: individual micro-projects (e.g. Day1Python, CommunityLibrariAPI)
• Shared artifacts: documentation & review materials, common utilities
b. Relationships and interactions
• There is no runtime data flow between modules; each is standalone
• We show “uses” or “depends on” relationships: e.g., Java API modules depend on ConnectionUtil and DAOs; BDD suites depend on Selenium/WebDriver and feature definitions
c. Architectural patterns & design principles
• Maven Standard Directory Layout for Java projects (separation of src/main vs src/test)
• MVC style layering in API services (controllers → services → DAOs → entities)
• BDD pattern: feature files → step definitions → page objects
• TDD approach in Python demo (tests first → implementation)
d. Key technologies
• Java 8+ w/ Maven, JAX-RS or Spring-style controllers, JDBC utilities
• Python 3 scripts + pytest or unittest for tests
• Cucumber/Gherkin for BDD, Selenium WebDriver for automation
• HTML/CSS/JavaScript for front-end demos