-
-
Notifications
You must be signed in to change notification settings - Fork 689
Use Cases
Ivan Paulovich edited this page Jan 15, 2020
·
7 revisions
Use Cases are delivery independent, they show the intent of a system.
Use Cases are algorithms which interpret the input to generate the output data.
Application architecture is about usage, a good architecture screams the business use cases to the developer and framework concerns are implementation details. On Manga sample the user can Register
an account then manage the balance by Deposits
, Withdrawals
and Transfers
.
Following the list of Use Cases:
Use Case | Description |
---|---|
Register | An customer can register an account using his personal details. |
Deposit | The customer can deposit an amount. |
Transfer | The customer can transfer money from one account to another. |
Withdraw | A customer can withdraw money but not more that the current balance. |
Get Customer Details | Get customer details including all related accounts and transactions. |
Get Account Details | Get account details including transactions. |
Close Account | Closes an account, requires balance to be zero. |
- Value Object
- Entity
- Aggregate Root
- Repository
- Use Case
- Bounded Context
- Entity Factory
- Domain Service
- Application Service
- Single Responsibility Principle
- Open-Closed Principle
- Liskov Substitution Principle
- Interface Segregation Principle
- Dependency Inversion Principle
- Swagger and API Versioning
- Microsoft Extensions
- Feature Flags
- Logging
- Data Annotations
- Authentication
- Authorization