How erkan3034/masketakipsistemi works
Project type and purpose
• This is a small C#/.NET layered application built for a C# camp assignment.
• It consists of three projects in one solution:
a. Entities: domain model classes (e.g. Person).
b. Business: service interfaces and implementations, plus a connected (external) Mernis SOAP service.
c. WorkAround: the host application (UI or console) that ties everything together.
File structure
• Top-level solution: MaskeTakip.sln
• “Entities” (class library): domain entities.
• “Bussines” (class library):
• Abstract folder: IApplicantService, ISupplierService interfaces.
• Concrete folder: ForeignerManager, PersonManager, PttManager implementations.
• Connected Services folder: MernisServiceReference for external SOAP calls.
• “WorkAround” (executable): references Bussines and Entities, includes compiled resources.
Key README insight
• No further architectural detail; confirms this is a simple academic/demo project.
a. WorkAround Application (UI/Console)
b. Business Layer
• Service Interfaces (IApplicantService, ISupplierService)
• Service Implementations
• ConnectedService: MernisServiceReference
c. Entities Layer (domain classes)
d. External System: Mernis SOAP endpoint
Relationships and interactions
• WorkAround → Business Layer: calls service interfaces.
• Business Layer → Entities Layer: uses Person and other domain objects.
• Business Layer → MernisServiceReference: makes SOAP calls for identity verification.
Architectural patterns and design principles
• Layered (onion) architecture:
• Core: Entities (domain).
• Service Layer: Business logic and external calls.
• Presentation/Application Layer: WorkAround.
• Dependency rule: upper layers depend on lower layers, not vice versa.
• Interfaces for loose coupling and testability.
Technologies and frameworks
• .NET 6.0 class libraries and console/UI project.
• Connected Services (WCF/Soap) for Mernis integration.