01 – Technical Specification

Create a Logical Model

Object Role Modeling (ORM). From the req and use cases -> extract OBJECTS, RELATIONSHIPS and ATTRIBUTES
Purpose of the logical model: Definition of the facts for the domain
ORM Notation
• ORM Object (oval)
• ORM Relationship (binary , ternary) …/… ex: (has/is in)
• ORM Facts (indicate how 2 or more items are related)
• ORM Constraints (Many-to-One, One-to-Many, Onr-to-One,Mamy-to-Many)

Lesson 2: Define Application Layer

Define the layers of your application:
Logical Application Layers helps developers and architects understand how a system works and where write their code. Logical division, physically can run on the same process (ex App_Code and UI code)
Advantages of layering
• Code maintainable
• Code understandable
• Code reuse
Layers of ASP.NET Applications
• User Interface: data entry, validation, search…
o Presentation (user Experience): aspx, ascx, css
o User interface code: Code-Behind
o Business Logic interaction code:
• Middle Tier
o Business service: (Domain Objects and Business Rules)
o Application layer/Service: (sometimes this code is put in a framework) ex: ENTERPRISE LIBRARY
o Database layer/Service: abstract the retrieval and storage of data in the DB
• Database Layer
o Database layer (idem)
o Stored Procedures
o Integrated services (SSIS or DTS)
o Database tables log or indexes: actual data
Define communication between layers
• In-process (direct, use of dll)
• Tcp-Ip (between Database services and Database)
• Named pipes

Create Physical Application Model for Developers

Component Diagram (UML)
• NODE -> represent hardware
• Notation: name layer :: name
Class Diagram (UML): methods and properties
• Class
• Interface
• Implement Class
• Association / Agregation
• Inheritance
• Enumeration
• Other item (abstract)
Sequence Diagram (UML):
Object interaction during execution (runtime) – message exchange
Collaboration Diagram (UML)
Activity Diagram (UML): used to model workflow
Pseudo-code