You are on page 1of 28

Rizky Januar Akbar

Composed by all functional algorithms and calculations that make the system work and interact with other layers.

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 to another and to and from other layers. Security: role-based security to restrict access to business objects only to authorized users.

The domain's object model is intended to provide a structural view of the whole system, including a functional description of the entities, their relationships, and their responsibilities.

Business Object: implementation of domain entity, a class that encapsulates data and behaviour, or a helper class performing special calculations. Data Transfer Object: to move data across the layers (no behaviours).

Tier: a physical hardware and software section of the system defined by one or more servers that perform the same function. Layer: a way of organizing code.

Web: in ASP.NET process. Smart Client: bundled with the presentation layer and run entirely on the user's machine within the application process.

Data Formatting CRUD Operations Stored Procedure

Procedural patterns: a collection of procedures, each handling a single request from the presentation layer Object-based patterns: a graph of interrelated and interconnected objects each representing an entity or a concern in the business and each object equipped with data and behavior.

Simple procedural model that presents the application logic as a collection of logical transactions. Mapping user action into series of procedural code.

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.

Potential for code duplication. When code grows, hard to refactor.

Group transaction script into business component. Servers as a container and packaged data and behaviour together. Maps each entity into business component. Database driven.

Simple, with IDE supports.

Not suitable for complex entities.

Object based approach that focus on behaviour of system and data flows.

OO approach. Can handle complex business logic.

Need complexity to handle complexity

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 by

changing web.config file (nhibernateconfiguration section).


Buat CDM n PDMnya, lalu buat tabelnya ke salah

satu database, kemudian mengganti webconfignya.

CDM, PDM (Power Designer 12.5) Solution Page Design (Visio)


Deadlines:
05/10/2009 (NHDemo)

09/10/2009 (NCatalog)