1 / 7

CT-044 – Módulo 2 Decompose Specifications for Developers

In this lesson module, you will learn how to create a logical model using Object Role Modeling (ORM) techniques. We will delve into ORM notations, objects, relationships, facts, and constraints, enhancing your ability to identify key system components. Following this, you will explore the concept of application layers, understanding how to divide your system's code into logical sections such as user interface, business logic, and database layers. Through hands-on labs, you will create and define these logical structures, preparing you for effective software deployment.

caldwell-dunlap
Télécharger la présentation

CT-044 – Módulo 2 Decompose Specifications for Developers

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. CT-044 – Módulo 2Decompose Specifications for Developers

  2. Logical Model • Lesson 1: Create a Logical Model • Object Role Modeling (ORM) (img) • The ORM Notation • ORM Objects • ORM Relationship • ORM Facts • ORM Constraints • Using the ORM Diagrams to Identify Objects, Properties, Methods, Entities, and Fields. • Lab: Create a Logical Model

  3. Application Layers • Lesson 2: Define Application Layers • Define the Layers of Your Application • The logical layers of your system represent how you plan to divide your code into logical pieces or groups.

  4. Application Layers (cont.) • SomeCommonLogicalLayers • User Interface • Presentation (oruserexperience) • User interface code • Business logicinteractioncode • MiddleTier • Business layer (or business services) (domain objects and business rules) • Application layer (orapplicationservices) (log errors or cache data for performance. .NET Enterprise Library) • Databaselayer (ordatabaseservices) • DatabaseLayer • Databaselayer • Storedprocedures • Integrationservices • Database tables, log, and indexes

  5. Applications Layers (cont.) • Define Communication Between Layers (img) • The application layers define the logical abstractions you intend for the code in the system. • You will need to consider how you intend to deploy these logical layers in a physical environment. • The environment might constrain your deployment options, or you might have other concerns. • Lab: Define Logical Application Layers

More Related