Business Layer. The active entities that are the subjects (e.g., business actors or business roles) that perform behavior such as business processes.

Slides:



Advertisements
Similar presentations
Privacy By Design Sample Use Case
Advertisements

Toward an Agent-Based and Context- Oriented Approach for Web Services Composition IEEE TRANSACTIONS ON KNOWLEDGE AND DATA ENGINEERING, VOL. 17, NO. 5,
Object-oriented modeling Class/Object Diagrams
Customer Service Solutions using SOA The Seamless Customer Experience Improve Customer Care through Multi- Channel Integration Rajesh Shewani Software.
Asper School of Business University of Manitoba Systems Analysis & Design Instructor: Bob Travica Analyzing system data: Class diagram Updated: October.
Jan 16, Ron McFadyen1 Ch 9. Use-case model: drawing System Sequence Diagrams Iteration 1: a simple cash-only success scenario of Process Sale.
Database Security and Auditing: Protecting Data Integrity and Accessibility Chapter 5 Database Application Security Models.
Lecture 12: Chapter 22 Topics: UML (Contd.) –Relationship Structural Behavioral –Diagram Structural Behavioral.
UML – Class Diagrams.
Rutgers University Libraries What is RUcore? o An institutional repository, to preserve, manage and make accessible the research and publications of the.
Chapter 14 (Web): Object-Oriented Data Modeling
September 2001Chapter 10: B2B Grows Up Key questions answered in this chapter: What are the four stages to the evolution of B2B capabilities? What are.
C++ Training Datascope Lawrence D’Antonio Lecture 11 UML.
Chapter 5 Database Application Security Models
Web Service Architecture Part I- Overview and Models (based on W3C Working Group Note Frank.
1 Business Models Modeling. 2 Why Model the Business Business modeling is a technique to help answer critical questions, such as: What do the workers.
Service Oriented Enterprise CS409 Application Services Even Semester 2007.
UML CLASS DIAGRAMS. Basics of UML Class Diagrams What is a UML class diagram? Imagine you were given the task of drawing a family tree. The steps you.
ORGANIZATIONAL STRUCTURE
Introduction to Enterprise Systems
Key questions answered in this chapter:  What are the four stages to the evolution of B2B capabilities?  What are the three categories of B2B?  Describe.
Chapter 13 (Online): Object-Oriented Databases
Business Modeling : basic concepts Extracted from Rational UML Profile for business modeling.mht.
Chapter – 6. Requirements Capture - Difficult A System has many Users. Each of them know what to do but no one knows the entire picture. Users do not.
SOFTWARE DESIGN AND ARCHITECTURE LECTURE 09. Review Introduction to architectural styles Distributed architectures – Client Server Architecture – Multi-tier.
© 2006 Prentice Hall Business Publishing Accounting Information Systems, 10/e Romney/Steinbart1 of 96 C HAPTER 17 Special Topics in REA Modeling for the.
1 University of Palestine E-Business ITBS 3202 Ms. Eman Alajrami 2 nd Semester
CS3773 Software Engineering Lecture 04 UML Class Diagram.
Developed by Reneta Barneva, SUNY Fredonia for CSIT 425 Requirements Modeling.
CHAPTER 13: OBJECT-ORIENTED DATA MODELING (OVERVIEW) © 2013 Pearson Education, Inc. Publishing as Prentice Hall 1 Modern Database Management 11 th Edition.
Business ByDesign (Case Study II) EGN 5621 Enterprise Systems Collaboration Fall, 2011.
July 09, 2008 NIH Project Management Community Project Scope and Change Management Discussion This document is confidential and is intended solely for.
IPortal Bringing your company and your business partners together through customized WEB-based portal software. SanSueB Software Presents iPortal.
Actors and Use Case Diagrams Month Day, Year. Agenda Training Plan Overview Review Detailing Requirements with Requisite Pro Concepts Setting Up XDE Integration.
The Static Analysis Model Class Diagrams Prof. Hany H. Ammar, CSEE, WVU, and Dept. of Computer Science, Faculty of Computers and Information, Cairo University.
1 CMPT 275 Software Engineering Requirements Analysis Phase Requirements Analysis activity Janice Regan,
McGraw-Hill/Irwin ©2003. The McGraw-Hill Companies. All Rights Reserved Chapter 13 Delivering Service Through Intermediaries and Electronic Channels Service.
Discovering object interaction. Use case realisation The USE CASE diagram presents an outside view of the system. The functionality of the use case is.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
Kal Bugrara, Ph.DSoftware Engineering Northeastern University Fundamentals Of Software Engineering Lecture V.
(c) Addison Wesley Copyright © 2000 by Addison Wesley Version 1.0
Design Model Lecture p6 T120B pavasario sem.
Digital Libraries Lillian N. Cassel Spring A digital library An informal definition of a digital library is a managed collection of information,
© 2013, published by Flat World Knowledge Chapter 10 Understanding Software: A Primer for Managers 10-1.
Chapter 2 Introduction to Enterprise Systems Partial adoption from Magal and Word | Integrated Business Processes with ERP Systems | © 2011 Timothy L.
Analysis Yaodong Bi. Introduction to Analysis Purposes of Analysis – Resolve issues related to interference, concurrency, and conflicts among use cases.
Chapter 1 Introduction to Electronic Commerce. Learning Objectives In this chapter, you will learn about: The basic elements of electronic commerce Differences.
Gerhard Dueck -- CS3013Analysis 1. Gerhard Dueck -- CS3013Analysis 2 Why analysis?  Yield a more precise specification of the requirements.  Introduce.
UML Fundamental Elements. Structural Elements Represent abstractions in our system. Elements that encapsulate the system's set of behaviors. Structural.
Models of the OASIS SOA Reference Architecture Foundation Ken Laskey Chair, SOA Reference Model Technical Committee 20 March 2013.
UML (Unified Modeling Language)
CINCOM ACQUIRE KNOWLEDGE-BASED SELLING PLATFORM CONFIDENTIAL | UNDER NON-DISCLOSURE WIN MORE BUSINESS. OPERATE EFFICIENTLY. DELIVER AS PROMISED CINCOM.
Use Case Diagrams A Detailed Description. Use Case Diagrams Use case diagrams describe relationships between users and use cases A use case is a (usually.
MGT 307 Week 2 Learning Team Organizational Behavior Forces Discussion To purchase this material click on below link
MGT 307 Week 4 Learning Team Evaluating Performance Through Motivation and Conflict Management Discussion To purchase this material click on below link.
FIN 415 Week 1 Individual Assignment Risk Management Overview Paper To purchase this material click below link
Marlon Dumas marlon . dumas ät ut . ee
INTERPROFESSIONAL COLLABORATION (IPC) AND HORIZONTAL INTEGRATION:
Course Outcomes of Object Oriented Modeling Design (17630,C604)
Introduction to Rental Management
Subject Name: MANGEMENT INFORMATION SYSTEM Subject Code:10IS72
Business Models Modeling.
Delivering Service Through Intermediaries and Electronic Channels
B2B E-Commerce Chapter 2.
Business Model Opportunities and Barriers. Context of BM Definition of BM Opportunities Barriers.
Use Case Realization Describes a collaboration among analysis classes that shows how a specific use case is realized Consists of flow-of-events analysis,
E-Commerce Lecture 6.
Chapter 1 Overview of Electronic Commerce
Grid Services B.Ramamurthy 12/28/2018 B.Ramamurthy.
Entity-Relationship Diagram (ERD)
Presentation transcript:

Business Layer

The active entities that are the subjects (e.g., business actors or business roles) that perform behavior such as business processes or functions (capabilities). Business actors may be individual persons (e.g., customers or employees), but also groups of people (organization units) and resources that have a permanent (or at least long-term) status within the organizations. Typical examples of the latter are a department and a business unit.

The passive entities (business objects) that are manipulated by behavior such as business processes or functions. The passive entities represent the important concepts in which the business thinks about a domain.

A business actor is defined as an organizational entity capable of (actively) performing behavior.

The company ArchiSurance is modeled as a business actor that is composed of two departments. The Travel insurance seller role is assigned to the travel department. In this role, the travel department performs the Take out insurance process, which offers a service that is accessible via the business interface assigned to this role.

A business role is defined as a named specific behavior of a business actor participating in a particular context.

In the model below, two business roles (Luggage insurance seller and Travel insurance seller) are involved in a collaboration that results in a Combined insurance selling service. The left hand illustrates the delivery of a Luggage insurance selling service via a business interface. The right hand shows how a business process, Take out insurance, is assigned to the Travel insurance seller and realizes the Travel insurance selling service.

Business collaboration is defined as a (temporary) configuration of two or more business roles resulting in specific collective behavior in a particular context.

The model in the model below illustrates a possible use of the collaboration concept. In this example, selling an insurance product involves the Sales department and a department specialized in that particular type of insurance. The example also shows that one role, in this case the Sales department, can participate in more than one collaboration.

A business interface declares how a business role can connect with its environment.

In the model below, the business services provided by the Luggage insurance seller and its collaboration with the Medical insurance seller are exposed by means of a web form and call center business interface, respectively.

A business object is defined as a unit of information that has relevance from a business perspective.

The model below shows a business object Invoice, which aggregates (multiple) business objects Invoice line. Two possible realizations of this business object exist: an Electronic invoice (data object) and a Paper invoice (representation). The business process Create invoice creates the invoice and the invoice lines, while the business process Send invoice accesses the business object Invoice.