Business Logic Layer
-
Upload
rigga-widar -
Category
Documents
-
view
223 -
download
0
Transcript of Business Logic Layer
-
8/3/2019 Business Logic Layer
1/28
Rizky Januar Akbar
-
8/3/2019 Business Logic Layer
2/28
Composed by all functional algorithms andcalculations that make the system work and
interact with other layers.
-
8/3/2019 Business Logic Layer
3/28
Object Model: models business entities. Business Rules:express all customers policies
and requirements. Services: to implement autonomous
functionalities. Workflows: define how documents and data are
passed around from one constituent module toanother and to and from other layers.
Security: role-based security to restrict access tobusiness objects only to authorized users.
-
8/3/2019 Business Logic Layer
4/28
The domain's object model is intended toprovide a structural view of the whole
system, including a functional description ofthe entities, their relationships, and theirresponsibilities.
-
8/3/2019 Business Logic Layer
5/28
Business Object: implementation of domainentity, a class that encapsulates data and
behaviour, or a helper class performingspecial calculations.
Data Transfer Object: to move data acrossthe layers (no behaviours).
-
8/3/2019 Business Logic Layer
6/28
-
8/3/2019 Business Logic Layer
7/28
Tier: a physical hardware and softwaresection of the system defined by one or more
servers that perform the same function. Layer: a way of organizing code.
-
8/3/2019 Business Logic Layer
8/28
Web: in ASP.NET process. Smart Client: bundled with the presentation
layer and run entirely on the user's machinewithin the application process.
-
8/3/2019 Business Logic Layer
9/28
Data Formatting CRUD Operations
Stored Procedure
-
8/3/2019 Business Logic Layer
10/28
Procedural patterns: a collection ofprocedures, each handling a single request
from the presentation layer Object-based patterns: a graph of
interrelated and interconnected objects eachrepresenting an entity or a concern in thebusiness and each object equipped with dataand behavior.
-
8/3/2019 Business Logic Layer
11/28
-
8/3/2019 Business Logic Layer
12/28
Simple procedural model that presents theapplication logic as a collection of logical
transactions. Mapping user action into series of procedural
code.
-
8/3/2019 Business Logic Layer
13/28
Simple Easy to implement
Ideal for project with small amount of logic,tight deadlines, and access to IDE. Can be broken down into simpler and
reusable routines.
-
8/3/2019 Business Logic Layer
14/28
Potential for code duplication. When code grows, hard to refactor.
-
8/3/2019 Business Logic Layer
15/28
-
8/3/2019 Business Logic Layer
16/28
-
8/3/2019 Business Logic Layer
17/28
Group transaction script into businesscomponent.
Servers as a container and packaged data andbehaviour together. Maps each entity into business component. Database driven.
-
8/3/2019 Business Logic Layer
18/28
Simple, with IDE supports.
-
8/3/2019 Business Logic Layer
19/28
Not suitable for complex entities.
-
8/3/2019 Business Logic Layer
20/28
-
8/3/2019 Business Logic Layer
21/28
-
8/3/2019 Business Logic Layer
22/28
Object based approach that focus onbehaviour of system and data flows.
-
8/3/2019 Business Logic Layer
23/28
OO approach. Can handle complex business logic.
-
8/3/2019 Business Logic Layer
24/28
Need complexity to handle complexity
-
8/3/2019 Business Logic Layer
25/28
Rebuild NHDemo Application. Create CDM and PDM of NHDemo Application.
Create schema in Oracle, SQL Server, or MySQL.
Try to connect to the different database bychanging web.config file (nhibernate-configuration section).
Buat CDM n PDMnya, lalu buat tabelnya ke salahsatu database, kemudian menggantiwebconfignya.
-
8/3/2019 Business Logic Layer
26/28
-
8/3/2019 Business Logic Layer
27/28
-
8/3/2019 Business Logic Layer
28/28
CDM, PDM (Power Designer 12.5) Solution
Page Design (Visio)
Deadlines:
05/10/2009 (NHDemo)
09/10/2009 (NCatalog)