How apodwikat/aydinuniversity-courses-projects works
Project types and purposes
• At the solution root you have two distinct projects:
a) SoftwareDesignApplication – a multi-layer .NET e-commerce/order management system, consisting of Data, Entities, Service, WebAPI (REST), and an ASP.NET MVC/WebUI front end.
b) UniTrack – a Java Swing-style desktop application for student/course/enrollment management with a local database backend.
File structures
• SoftwareDesignApplication
• Top-level Zips:
– SiparisYonetimiNetCore.Data.zip – data-access layer (Entity Framework or ADO.NET)
– …Entities.zip – domain/entity definitions
– …Service.zip – business logic layer
– …WebAPI.zip – REST API exposing service functionality
– …WebAPIUsing.zip – client code consuming the WebAPI
• SiparisYonetimiNetCore.WebUI – ASP.NET MVC app with Areas/Admin for back-office and Controllers/Views for public UI. Assets in wwwroot (Bootstrap, jQuery, custom CSS/JS).
• UniTrack
• Presentation folder with PDF documentation.
• Project folder: SQL script + Java source under src (panels for Student, Course, Department, etc.), DBConnection utility.
Key takeaways from the README
• These are course projects from Istanbul Aydın University Computer Engineering.
a. Main components
• For SoftwareDesignApplication:
1) Database (SQL Server or other)
2) Data Access Layer (SiparisYonetimiNetCore.Data)
3) Domain/Entities (SiparisYonetimiNetCore.Entities)
4) Business Logic/Service Layer (SiparisYonetimiNetCore.Service)
5) RESTful Web API (SiparisYonetimiNetCore.WebAPI)
6) API Client (SiparisYonetimiNetCore.WebAPIUsing)
7) Web UI (ASP.NET MVC) with two sub-areas: Public UI and Admin Area
8) External libraries/frameworks (Entity Framework, ASP.NET Core MVC, Bootstrap, jQuery)
• For UniTrack:
1) Desktop UI (Java Swing panels)
2) DBConnection utility
3) Local Database (MySQL/SQL Server via JDBC script)
4) Java business logic embedded in panel controllers
b. Relationships and interactions
• SoftwareDesignApplication:
• Web UI ↔ Web API via HTTP (JSON)
• Web API → Service layer calls business methods
• Service layer → Data Access for CRUD operations
• Data Access → Database
• WebUI also uses local session extensions and file helpers
• UniTrack:
• UI panels call DBConnection to execute SQL
• DBConnection ↔ Database directly
• Panels coordinate each other through common in-memory models
c. Architectural patterns and design principles
• SoftwareDesignApplication:
• N-Tier (Presentation, API, Business, Data)
• Separation of concerns (Entities vs. Service vs. Data vs. UI)
• RESTful API for decoupling front end and back end
• UniTrack:
• MVC-like within a desktop app; each panel handles its own view and controller logic
• Single point of database connectivity (DBConnection util)
d. Key technologies/frameworks
• SoftwareDesignApplication:
• .NET 7.0, ASP.NET Core MVC, Entity Framework Core (or ADO.NET)
• Bootstrap, jQuery on the client
• JSON REST API
• UniTrack:
• Java (JDK Swing), JDBC for DB connectivity
• SQL script for schema setup