Upload File

pv213 eis in practice: 02 – architecture of the eis in the standard environment 1 pv213 enterprise...

  • Home
  • Documents
  • PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of
35
PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of the EIS in the standard environment

Upload: alexia-glenn

Post on 17-Jan-2018

226 views

Category:

Documents


2 download

Report

DESCRIPTION

3

TRANSCRIPT

Page 1: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1

PV213 Enterprise Information Systems in Practice

02 – Architecture of the EIS in the standard environment

Page 2: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 2

Page 3: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 3

Page 4: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 4

What is SW architecture?

The software architecture of a system is the set of structures needed to reason about the system, which comprise software elements, relations among them, and properties of both.

“Structure of structures”

Page 5: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 5

Why we need SW architecture?

Why SW architecture is created?Increase product quality

Functional requirementsNon-functional requirements

Understand product structureSpeedup development timeMinimize maintenance costs…

Page 6: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 6

Architect in history

The ideal architect should be a person of letters, a mathematician, familiar with historical studies, a diligent student of philosophy, acquainted with music, not ignorant of medicine, learned in the responses of jurisconsults, familiar with astronomy and astronomical calculations.

—Vitruvius, circa 25 BCVitruvius was a Roman architect and the author of the De architectura. Pont du Gard, France

Page 7: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 7

SW Architect – role in the teamKey responsibilities

Creating and documenting architectureHigh levelDesign decisions (especially non functional requirements)Guidelines

Communication between different stakeholdersRequirements with customer / analyst / business peoplePlanning with project managerSW architecture / design with developers, testers

Supervising project from technical point of view

We can differentiate: business architect, enterprise architect, solutions architect, application architect

Page 8: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 8

Non-functional requirementsProduct qualities which are often overlooked but they are important

part of the product.Performance – e.g. transactions per secondsScalability – ability to “grow” with increasing loadReliability – ensures integrity and consistencyAvailability – e.g. in percentage (99,9%)Security – system and its data cannot be compromisedMaintainability – ability to correct flaws without big impactsManageability – monitor system health, change of configurationExtensibility – ability to add new functionality without big changesTestability – ability to test…

Page 9: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 9

Architecture types – Monolithic (1-tier)First type in history (on mainframes)Everything in one monolithic application

User interfaceApplication (business) logicPersistence logic (database)

SimpleHard to fulfill some non-functional requirements

Non-scalableHard to extendHard to maintain

Today valid only in very special cases - embedded SW with small resources (CPU power, memory, without network connectivity)

Page 10: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 10

Architecture types – 2-tier ISeparation

First tier – User interface plus application logicSecond tier – Persistence (database)

Also called client / server architecture (popular in 1980s)Allows to easily share data from different clientsStill hard to fulfill some non-functional requirementsUsed mostly in desktop applications

Hard to change business logic (requires redeployment)Small modification for exceptional web applications

First tier – User interfaceSecond tier – Application logic and persistence

Not recommended for new development

Page 11: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 11

Architecture types – 2-tier II

Physical model Logical model

Page 12: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 12

Architecture types – 3-tier (n-tier) I

SeparationFirst tier – User interfaceSecond tier – Application logicThird tier – Persistence

Separation allows to increase quality of the systemE.g. change of the business logic doesn’t influence presentation tier (user interface)

Valid for most of web applicationsStandard in designing systems today

Page 13: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 13

Architecture types – 3-tier (n-tier) II

Physical model Logical model

Page 14: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 14

Architecture types – 3-tier (n-tier) III

Tiers representsmachine boundaries

Much easier to scale

Changes are separated

Page 15: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 15

Architecture types – Comparison of 2,3 and n-tier

2-tier n-tier

3-tier

Page 16: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 16

Architecture types – Possible structuring in n-tier

Logical model

Page 17: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 17

Thick and thin clientThick client provides rich functionality without server

Requires some installation on the client’s deviceCan run independently without serversCan use all HW device provides (rich and fast GUI, external HW)Migration to newer version (update) is harder

Thin client delegates functionality to other devices (servers)Doesn’t require installation on the client’s deviceCannot run independently without serversAccess to HW is limitedMigration to newer version (update) is easierRequires some “specialized OS” (web browser, “player”, etc.)Servers are the bottleneck

In reality thick and thin clients overlap (browser plugins, zero installations, …).

Page 18: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 18

Example – Reservation system (refresh)

Reservation system allows toMake reservations for pool equipmentsCancel reservationsShow calendar with reservationsImport definition of equipments from external inventory systemSend usage statistics to management reporting system

Page 19: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 19

Example – Reservation system – Architectural thoughts I

You have to consider which architecture solves the best your functional and non-functional requirements with additional restrictions (constraints) to

Given budgetExpected timeframeSkills in your teamExpected live time of the productNon-technical constraints (team motivation, overall atmosphere, …)…

You can try to negotiate some (or all) constraints with project (or product) manager (business people, customer, …).

Live is not ideal but good communication with other people can simplify it!

Page 20: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 20

Example – Reservation system – Architectural thoughts II

Possible questions we have to ask

How users will use the Reservation system?Is program installation on user’s device required? Thick / thin client? What are prerequisites?Which operating systems are required to support?Which types of user’s devices are required (e.g. mobile)?

How data will be shared between users? Is sharing of data possible?How product will interact with external systems (inventory and reporting system)?How system will be maintained?How system will scale when amount of users grow?How possible new requirements will influence the system?…

Page 21: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 21

Example – Reservation system – 1-tier architecture?

Implies thick clientInstallation of client requiredUpdate of client can be complicated (distributed redeployment)

Sharing of data is complicatedEach user has its own copy of databaseNeeded to solve synchronization of databases (when number of users grow more data has to be transferred between clients)

Some functional requirements are hard to implement – e.g. export to reporting system

Which client will do it? What if he is ill?Another special application for export? How and who will start it?

Result: Inadequate architecture for our purposes

Page 22: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 22

Example – Reservation system – 2-tier architecture I?

Desktop application (thick client)User interface and application logic on the clientPersistence on the database server (data can be easily shared between clients)Installation of the client requiredUpdate of client can be complicated (distributed redeployment)Export of data still problematic

Result: Inadequate architecture for our purposes

Page 23: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 23

Example – Reservation system – 2-tier architecture II?

Web application (thin client)User interface on the client (web browser)

No need to do installationChange in the application means redeployment only on the server

Application logic and persistence on the database serverApplication logic e.g. in stored procedures – logic is tightly bind to the databaseImplies database which support such configuration (vendor lock-in)Export of data

Automatically by scheduled stored procedures (scheduled jobs)Special application on the database serverManually in the web GUI by special user

Result: Better than 2-tier desktop application but still some flaws

Page 24: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 24

Example – Reservation system – 3-tier architecture I?

Desktop application (thick client)User interface on the clientApplication logic on the application serverPersistence on the database serverEasier to switch to different databaseInstallation of the client still requiredPerformance of user interface can be slower than in 2-tier (application logic executed on the application server – network boundaries)Better scalable than in 2-tier (application server can also cache common data shared by multiple clients without need to load them from DB)Still need to solve update of client (user interface)Export of data solved on the application serverUsed in cases when you need advanced and fast GUI

Result: 3-tier desktop application doesn’t solve deployment issues

Page 25: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 25

Example – Reservation system – 3-tier architecture II?

Web application (thin client)User interface on the client (web browser)

No need to do installationChange in the application means redeployment only on the application (web) server

Application logic on the application (web) serverPersistence on the database serverExport of data

Special application (or just component) on the application (web) serverManually in the web GUI by special user

Scales quite wellIf weakest point is application server add additional server If weakest point is database use clustered database (there are some limits)

Standard how applications are build today (a lot of “support” on the internet)

Result: 3-tier web application is the best for our needs

Page 26: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 26

Example – Reservation system – Deployment diagram IPossible deployment for

intranetUsers need just standard web browser (no need for installations)For communication between clients and server just HTTP is used (we are in “secure” area)Web and Application server contains main part of the solutionNew version of the application means just redeployment on Web and Application (+SQL) serverCommunication with external systems is via HTTP (HTTPs)For storing data is used standard SQL database

Page 27: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 27

Example – Reservation system – Deployment diagram IIPossible deployment

for big amount of clientsLoad balancer distributes requests to different nodesThere are multiple web and application server nodesSQL database is configured to be clustered database on several nodes

Page 28: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 28

Example – Reservation system – Deployment diagram for internet

Possible deployment for internet environmentWeb browsers use HTTPS instead of HTTPInternet firewall restricts protocols just to HTTPSTo increase performance static content (pictures, videos, static HTML pages, …) are handled on special web server nodeIntranet firewall restricts protocols to HTTP and SQL*Net and requests only from application serverCommunication in the intranet is just HTTP

Page 29: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 29

Example – Reservation system – Deployment with redundancy

Possible deployment with redundancyEach critical node is backed up by the same nodeIn case of failure (e.g. HW) second (standby) node will handle requestStandby nodes add additional costs but do nothing in normal behaviorWeak points are external systems which we cannot influence

Page 30: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 30

Example – Reservation system – Deployment with load balancing redundancyPossible deployment with load

balancing redundancyLoad balancer distributes requests either to Web and Application server 1 or 2Load balancer is backed upWeb and Application Server must be stateless or load balancer must take into account user’s sessionIn two node deployment for Web and Application server one node must be able to handle all requests (in some decreased performance)Standard SQL databases cannot be easily load balanced. Often they are weak points in scalability

Page 31: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 31

Recommendations and what you have to think about I

For majority of new EIS applications use 3-tier (n-tier) web based architectureBackup critical systems (calculate losses in case of not functional system)Know expected number of user’s

In the beginning it can be hard to guess especially for applications which will become popular

Be prepared for increasing number of usersCloud computing can help you

Do load testing before system goes to productiveOnly a few projects do this

Be prepared to use your system from internetYou have to take care more about the security on the internet

Be prepared for different user devices (standard PC, tablet, mobile)There is increasing importance of mobile devices

Page 32: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 32

Recommendations and what you have to think about II

Prepare the architecture before any development startsWhen real development starts it is too late to create the architecture

Keep in mind all important non-functional requirementsCreate documentation and guidelines for developers and share the knowledge

Better is to make an architecture meeting than just telling to developers “here are documents and read them”Do it continuously and iteratively

Setup tools helping you finding abnormalities in the architecture from codeDo the code reviews to find “code smells”Adapt architecture through the lifetime to fit into new requirementsRole of architect is not valid only in the beginning but through the whole lifetime of the project

A lot of projects starts with good architecture but degrade through the lifetime as requirements change

Page 33: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 33

Different architectures examples IWhich architecture type (number of tiers, type of the client)

do you recommend for following usages?Simple game on mobile device without connectivity to the network

1-tier, thick clientGame on mobile device with possibility to use multiplayer functionality and sharing game scores

3-tier, thick clientApplication for managing business trips which must run on mobile devices and standard PCs

3-tier, thin client (web application)Mobile application for collecting data from house construction in the field and reporting them to the headquarter (must work offline)

3-tier, thick client

Page 34: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 34

Different architectures examples IIManagement reporting application with advanced graphical interactive reports which must run on “any” device

3-tier, thin client (web application with some technology which allows displaying interactive reports e.g. Flash or HTML5)

Industry application for reporting weather conditions3-tier, thick client (embedded SW)

News application aggregating data from different sources3-tier, thin client (web application)

Project management application3-tier, thin client (web application)

Computational intensive application (simulation of chemical processes)

3-tier, thick client (special desktop application), distributed computing

Page 35: PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 02 – Architecture of

PV213 EIS in Practice: 02 – Architecture of the EIS in the standard environment 35

Děkuji za pozornost.


eis, eis baby - | DAS informative MamaBlogdiekleinebotin.at/wp-content/uploads/2016/08/EIS-EIS-BABY-EBOOK.pdf · Eis, Eis Baby 6 WER WIR SIND daniela Bloggerin, Selbermacherin, immer

Initial Results of EIS Shinsuke Imada (NAOJ) EIS Team

PV213 EIS in Practice: 06 – Development process 1 PV213 Enterprise Information Systems in Practice 06 – Development process

PV213 Enterprise Information Systems in Practice 0 4 – Quality assurance

PV213 Enterprise Information Systems in Practice 0 9 – Quality assurance

PV213 EIS in Practice: 04 – Quality assurance1 PV213 Enterprise Information Systems in Practice 04 – Quality assurance

British Championships - Judo Technologies · Rush Judo Moberly British Championships Pinewood EIS Sheffield. Clyde-Core Judo Academy EIS Sheffield-Kin Ryu Sportif EIS Sheffield. EIS

VOLUME D: AIRSPACE - Brisbane Airport NEW PARALLEL RUNWAY DRAFT EIS/MDP FOR PUBLIC COMMENT D3-25 VOLUME D: AIRSPACE Airspace Architecture

PV213 Enterprise Information Systems in Practice 07 – Architecture of the EIS in the cloud PV213 EIS in Practice: 07 – Architecture of the EIS in the

Eis Sysadmin

Eis resumido

PV213 EIS in Practice: 08 - Integration of EIS with other systems 1 PV213 Enterprise Information Systems in Practice 08 - Integration of EIS with other

Executive Information System (EIS) · โครงสร้างของระบบ EIS ระบบ EIS รองรับแผนที่ออนไลน์ได้จากหลาย

PV213 Enterprise Information Systems in Practice 0 7 – Architecture of the EIS in the cloud

EIS Alumni Association Lifetime Memberseisalumni.org/wp-content/uploads/2017/05/EISAA... · Runa Gokhale , EIS '14 Marcia Goldoft , EIS '85 Brant Goode , EIS '04 Alyson Goodman ,

Data-Oriented Architecture - RTIcommunity.rti.com/.../archive/Data-Oriented_Architecture.pdfEnterprise Information System (EIS). The enterprise information system keeps track of historical

Manual EIS

Improving modularity of interactive ... - HAL archive ouverteteractive software with the MDPC Architecture. EIS 2007, Engineering Interactive Systems Joint Working Conference, Mar

PV213 EIS in Practice: 10 – Testing 1 PV213 Enterprise Information Systems in Practice 10 – Testing

Electrical Research Institute - SINTEF4SP EIS 65.z 4SP EIS 66.z 4SP EIS 67.z 4SP EIS 68.z 10 0 10 1 10 2 10 3-15-10-5 0 Frequency (Hz) theta 4SP EIS 78.z 4SP EIS 79.z 4SP EIS 80.z

EIS - 중역정보시스템

Electronic Ignition Kit— Models: EIS-N135 (Natural Gas ... · PDF fileElectronic Ignition Kit— Typical Installation Models: EIS-N135 (Natural Gas) EIS-N200 (Natural Gas) EIS-P200

PV213 EIS in Practice: 10 – Deployment, Migration, Maintenance 1 PV213 Enterprise Information Systems in Practice 10 – Deployment, Migration, Maintenance

Eis presentation

PV213 EIS in Practice: 06 – Architecture of the EIS in the standard environment 1 PV213 Enterprise Information Systems in Practice 06 – Architecture of

PV213 Enterprise Information Systems in Practice 08 - Integration of EIS with other systems

I EIS I EIS

Eis Introduction

PV213 EIS in Practice: 07 – Architecture of the EIS in the cloud 1 PV213 Enterprise Information Systems in Practice 07 – Architecture of the EIS in the

อัลบั้มรูปภาพอบรม Eis

PV213 EIS in Practice: 02 – Starting with EIS 1 PV213 Enterprise Information Systems in Practice 02 – Starting with EIS

PV213 Enterprise Information Systems in Practice 0 5 – Security, Configuration management

PV213 EIS in Practice: 07 - Architecture of the EIS in the cloud1 PV213 Enterprise Information Systems in Practice 07 - Architecture of the EIS in the

EIS Community Engagement and Consultation Reporteisdocs.dsdip.qld.gov.au/Gladstone Liquefied Natural Gas/EIS/EIS Jun 09... · GLNG EIS Community Engagement and Consultation Report

EIS Overview & Case Studies Presentation EIS 2016