1 INF5120 Modellbasert systemutvikling COMET-S Business Modelling COMET-S Requirements Modelling UPMS SOA profile COMET-S: COMET with Standards, for s See COMET, Forelesning F Arne J. Berre COMET-S Business Modelling COMET - (S) with use of new OMG standards, BMM and BPMN
2 Sales & Planning Vessel Schedule W ork Order Exec. Monitoring Seismic Acquisition Vessel Op eratio n Prod. stat istics Do wntim e stat. Op. Mgr NCR Reporting & Monitoring Support Engineering Registrator Secretariat application ClubRegister ObtainClubInfoand deliver to registeringprocessor ExistingClubInfo Edit and accept existingclubinfo Club registration Information AskClubRegisterto check if Club already exists Existi ngclubinfo Ask to edit and confirm existing ClubInfo Ask to register Club [Club Exists] Check if Club exists [Club do not Exists] Add Club Registrator Secretariat application ClubRegister ObtainClubInfoand deliver to registeringprocessor ExistingClubInfo Edit and accept existingclubinfo Club registration Information AskClubRegisterto check if Club already exists Existi ngclubinfo Ask to edit and confirm existing ClubInfo Ask to register Club [Club Exists] Check if Club exists [Club do not Exists] Add Club : Registrator registerclub : Secretariat Application clubexists registerclub : ClubRegister : Registrator registerclub : Secretariat Application : ClubRegister clubexists registerclub Arnor er en kul type Dette er et forsøk på å fylle denne kommenten med text Model world BMM Real world Context Business 0,1 model Goal Model Business model Goal Model Context statement Business Resource Model 0,1 Context statement Business Resource Model BPMN Vision for change Risk analysis Business Process & Role Model Vision for change Risk analysis Requirements model Prototype Other requirements Business Process & Role Model WARM Work Element Analysis Model System Boundary Use case Scenario Model Concepts& Artifacts Processes Actors Business Domain Busines domain to system domain mapping Subsystem grouping and BCE (Combine Ref Arch) BM analysis BCE Model Architecture model Workflow Domain UPMS w/soa profile and role modeling Component structure and internal design Interface and interaction specification Platform specific model UMT Config model Component implementation model PIM Data Types User Domain Business Domain User Interface Tier User Tier User Resource Tier Business Tier Resource Tier RA Presentation Tier User Dialog Tier LA LS RA Component Infrastructure & Workflow Engine ( Microworkflow) Legacy System Domain Deployment Business Model (What and why) Requirements Model (What) Prototypes Context statement Goal Model Business process model Business Resource model System Boundary Model Use case scenario Model Other requirements Arnor er en kul type Dette er et forsøk på å fylle denne kommenten med text Vision for change Risk analysis Work Analysis Refinement Architecture Model (How) Subsystem1 Subsystem 2 BCE Model Iterative & Incremental Subsystem4 Subsystem3 Component structure model Component interaction model Interface & Information Model Problem domain Solution domain Platform Specific model (HowSolution) Platform profile model Applications Business components General components OS HW Component Implementation Model
3 Business Model The Business Model is used to express the part played by the Product (system or component) being developed in the context of the business that will fund its development (or purchase it) and use it. The Business Model includes goals, business processes, steps within business processes, roles and resources. The scope (or domain) of the model is any part of the world defined as interesting for a company, organisation or others, and which has some impact on the required behaviour or other characteristic of the Product. The business model might be broadly or narrowly scoped, e.g. describing the entire business of a company or describing the immediate environment and context of a Product under consideration. Structuring concepts Business Model in context of Vision for change Scoping Statement context for Context Business Model Context statement Risk analysis Goal model Community model 1 1 BMM 1.. Business Process & Roles Model 1 refined by 1 refines BPMN Work analysis Refinement 1.. Business Resource Model refines 1 refined by 1
4 COMET Business Modeling Meta model Enabled by 1.. Goal met by to meet Enabling behaviour objective of subgoals 1.. has 1.. executes behaviour of constrains Community constrained by constrained by Behavioural Policy represents Business Process 0..1 constrains has resources model of constrains Business Rule constrained by resource in modelled as 0..1 constrains 1.. modelled as 0..1 Resource Resource in Role Step affected by actor for performed by is generated by affects generates 1.. constrained by identifier for Event Artifact Resource Actor Resource fulfils fulfilled by Role identified by results in resource 1 subject for recipient sender 1.. concerns 1.. issued to received by artifact Resource as Artefact represented information flow artifact in Business Message result of Scoping statements The context statement, which defines the scope and positions this business model in its context. Vision for change, which describes what to improve, the motivation (i.e. what is wrong with the current situation), a description or indication of what the improvements might be and a gap analysis. Risk analysis, which identifies the business and technical risks related to a development project for the proposed Product.
5 Context statement Methods and Techniques The first step in developing any business model is to identify and record the names of all people who will have an interest in having the Product developed or in its use, the business stakeholders, together with the nature of their interest. The following are examples of business stakeholders who should be involved: people who will authorise funding for development of the Product; people who are responsible for design and maintenance of the business processes to be supported by the Product; people who will use the Product; people who will be responsible for the acceptance of the Product; people who will be responsible for managing operation of the Product. Vision for change The vision for change document is short and describes what the Product will be and why it is needed. It will consist of some or all of the following elements: General business/product vision and goals, including background explaining why the Product is needed; Business opportunities and business benefits; Product description and technical business vision how the Product might be deployed and used; Presentation material summarising the above.
6 Goal Model The goal model describes a loose hierarchy of goals of the business within the particular area of concern, starting with the goals of a Business Stakeholder in developing or buying the Product, and leading to the detailed business goals met by the Product or its users when using it. The Goal Model is discovered by a process of workshops and interviews involving all stakeholders (as identified in development of the Context Statement). Goals must be achievable, preferably measurable, and not selfevident, and should have clear and detailed implications. It should be reasonable (but not necessarily appropriate, and almost certainly not correct) to assert an alternative. The implications should be expressible in terms of a set of sub-goals or enabling processes. Business Resource Model The Business Resource Model is an information model that identifies and defines the main things (and concepts) of the domain that are relevant to the Product. The Business Resource Model is generally prepared at the same time as the associated Business Process & Roles model, and methods and techniques used are similar, i.e. activities that include brain-storming sessions, structured workshops, interviews and feed-back sessions, and detailed modelling using a UML tool. Object flows in the activity diagrams are candidates for business resources.
7 Business Process & Role Model Purpose The objective of the Business Process Model is to identify and detail all the business processes supported by the Product to the extent necessary to detail the roles of the Product (and its components, i.e. Application Components, Business Components and Tool Components). Methods and Techniques The Business Process Model is derived through a set of activities that encompass brain-storming sessions, structured workshops, interviews and feed-back sessions, and detailed modelling using a UML tool. Work Element Analysis (WARM) In WARM refinement of the Business Process model, the kinds of step performed by resources in the model are further categorised as follows: A Human Step is a step performed by a human with no involvement of the Product being modelled. A Tool Step is a step performed by a human user interacting with a tool that is part of the Product. The human user will use some form of interactive device (e.g. a GUI) to interact with the Product. A Tool Step is a candidate for realisation by a Tool Component. An Immediate Step is a step that is required to complete as soon as possible, and whose intermediate states are of no concern to the business. It is performed autonomously, with no intervention from a human. An Immediate Step may be mapped to an Operation on a Business Component (Process) in the Architecture Model.
8 BMM Business Motivation Model (OMG) New 2007 standard from OMG, based on input from the Business Rules Community Example of a relevant metamodel, with a domain specific language, and editor support with EMF/GMF. What BMM Offers Standardizes common Business terms and Business relationships Provide a open medium for communicating Business Plans Provides a bridge for relating the WHAT and the WHY to the HOW: Business Processes Business Rules Organizational Structure
9 BMM (Metamodel) BMM overview executed by s Architecture/ Community
10 BMM modeling Concrete Syntax No mandated syntax. Which is best? Textual Syntax EU-Fly is vulnerable to direct competition from low-cost airlines on many of its single-sector routes.revenue from business travel is critical Structured Syntax Graphical Syntax
11 Graphical Syntax Option Concepts, e.g. Influencer Relationships, e.g. judges Implemented in Eclipse, using GMF (Graphical Modeling Framework) Example
12 Partition into Views BizModeler from XACTIUM (developed through EMF and GMF) Editor support for BMM See example tutorial at:
13 Support in Tool Intelligent Links
14 Relationship Categories Made operative by, Supported by, Achievement supported by, Supported By 3 Composed of s Composed Of Made by, Responsibility of, Defined by Affects employment of, On achievement of Responsibility of Affects Model management Folder/Namespace Structure Drag and drop between Models, Folders and Diagrams Rule based language for slicing and dicing
15 BPMN Business Process Modeling Notation (OMG) Ref BPMN 1.1 BPMN editor in Eclipse Ref. Lecture F02 and Oblig 1a 2 new proposals for BPMN 2.0 per February 10th 2008 COMET-S Requirements and User Modelling Ref. Goal-oriented use cases (Alistair Cockburn, course responsible INF5120 (IN-MMO) with A.J. Berre at UiOI/Ifi in 1997/1998, PhD UiO 2003)
16 Model world BMM Real world Context Business 0,1 model Goal Model Business model Goal Model Context statement Business Resource Model 0,1 Context statement Business Resource Model BPMN Vision for change Risk analysis Business Process & Role Model Vision for change Risk analysis Requirements model Prototype Other requirements Business Process & Role Model WARM Work Element Analysis Model System Boundary Use case Scenario Model Concepts& Artifacts Processes Actors Business Domain Busines domain to system domain mapping Subsystem grouping and BCE (Combine Ref Arch) BM analysis BCE Model Architecture model Workflow Domain UPMS w/soa profile and role modeling Component structure and internal design Interface and interaction specification Platform specific model UMT Config model Component implementation model PIM Data Types User Domain Business Domain User Interface Tier User Tier User Resource Tier Business Tier Resource Tier RA Presentation Tier User Dialog Tier LA LS RA Component Infrastructure & Workflow Engine ( Microworkflow) Legacy System Domain Deployment Use Case Model The Use Case Model describes the system in terms of Actors use cases scenario descriptions It is defined a use case template to be used as a vehicle for developing the use case model. Non functional requirements are part of the use case model as these kinds of requirements are associated with use cases according to the use case template. General non functional requirements that applies for the whole system are associated with the system boundary which is also included in the use case model.
17 Purpose of Use Case Model Capture system requirements Specify system behavior as Use Cases Set the system boundary Specify system environment as Actors Describe interactions between System and Actors Drive system development process A Use Case specifies a sequence of actions, including variants, that the system can perform and that yields an observable result of value to a particular actor. A Use Case is User visible User-meaningful Easy for a user to confirm (or change) Precise enough as specification
18 System Boundary Goals Identify and describe system boundaries, main services and actors. Assure a common understanding of the system and its purpose. Identify interactions between the system and its environment. Deliverables A high-level UML Use case diagram showing the system, the actors and the actors responsibilities. A detailed UML Use case diagram showing the system boundary, the actors and their main use cases. Each use case should be numbered for later reference. General extra requirements that applies for the complete system are associated with the System Boundary Identify actors Answer the following questions: Who uses the system? Who maintains the system? What other systems use this system? Who gets information from the system? Who provides information to the system? Does anything happen automatically at preset times? Who starts and shut down the system? Examples: persons/roles, software systems, things/objects (hardware) networks, etc. Describe the actors responsibilities (short)
19 Identify use cases Go through the list of actors and identify what services they need to fulfil their obligations Answer the following Questions What services will the actor want to get from the system? Which events will the actor initiate and which events will the actor be interested in? Which events/notifications occur? (the notifications reaching the actor independent of his interest (e.g error notifications)) Use case Scenario Model Description The Use Case Scenario Model digs into the identified use cases and describes these in detail. A use case template is used as a vehicle for this detailing. Goal Capture and understand the requirements. Deliverables Detailed UML use case diagram and descriptions in accordance to Use case template Activities Fill in Use Case template
20 Use case template Use case <number> Use case <name> Each use case is identified for later reference. Priority Priority with respect to implementation, marked Goal Actors Pre-conditions Description of the goal(s) for the use case, derived from the Goal Model in the Business Model. Description of the roles involved in the use case and their responsibilities. Description of the pre-conditions for the use case. Postconditions Façade Quality requirements Description of the post-conditions for the use case. Description of methods/operations that the system should provide to realize the use case. Description of extra requirements for this use case. Issues such as uptime, availability, security, performance, etc. can be recorded here. Scenario Description of the use case scenarios. This includes the primary scenario and related secondary scenarios. Description Step Action 1 Step 1 description. 2 Step 2 description. n Step n description. Quality / Non-functional requirements Non functional requirements Description of non functional requirements for this use case Consider: Performance Uptime Availability Security Scalability Distribution Reliability and more...
21 RA Analysis Description The Reference architecture analysis is the first step in modeling the architecture, representing an intermediate step between Business Domain Models and the architecture design. The Reference Architecture Analysis is developed using a use case driven approach and provides the basis for the initial development of the Architecture Model. Goal The Reference Architecture Analysis should provide the link between analysis and design, in particular the link between the Use Case Model and the Architecture Model. Deliverables Detailed use case diagram with subsystem grouping. Updated use case descriptions following the use case template. First version of the Component Structure using the bus architecture pattern (Object Management Architecture pattern). Prototype Goals Reduce technical risk Reduce the possibility of user dissatisfaction Deliverables Prototype Activities Identify technical uncertainties Develop UI, get feedback from users Test the risky technical solutions Start prototyping early Useful for the common understanding Best way of communicating with end user? Useful for identifying more user requirements
22 OORAM role modeling See professor Trygve Reenskaug website See BabyUML & Role Modeling With book reference Working with objects. The OOram Software Engineering Method. Manning/Prentice Hall ISBN OORAM role model
23 Role model Synthesis UPMS SOA profile A collaboration oriented perspective on service modeling input to UPMS standardisation Derived from work by Model Driven Solutions Inspired by OORAM role modeling
24 Why the SOA Profile s Architecture is a network of participants interacting in well defined ways through services SOA Profile adds richness to relationships that define the interactions Embraces SOA as both a business and a technology concept Advantages of SOA profile Intuitive and complete support for modeling services in UML Support for bi-directional asynchronous services between multiple parties Support for s Architectures where parties provide and use multiple services. Support for services defined to contain other services. Easily mapped to and made part of a business process specification. Compatibility with UML, BPDM and BPMN for business processes Direct mapping to web services. Top-down, bottom up or meet-in-the-middle modeling. Design by contract or dynamic adaptation of services. To specify and relate the service capability and its contract No changes to UML.
25 s and Contracts A is a capability offered by one entity or entities to others using well defined terms and conditions and interfaces. Contract A specification for the terms and conditions of a service including the interactions (Contract type) An exchange agreement between specific (bound) participants (Signed contract) SOA Profile by Example Using UML for s Architectures with the SOA Profile
26 Example use case Enable a marketplace of dealers and manufacturers with a services architecture. Many to many relationship between dealers and manufactures. Participants proprietary systems should be hidden behind services Growing set of services should support long-lived and multi-party services All relationships are peer-peer, there is no controller the challenge is then reliable interoperability and collaborative behavior between loosely coupled agents SOA Marketplace Example Order Conformation Shipped Mechanics Are Us Dealer Status Acme Industries Manufacturer Ship Req Shipped Physical Delivery GetItThere Freight Shipper Delivered
27 Marketplace s Mechanics Are Us Dealer Status Consumer Physical Delivery Consumer Provider Order Conformation Shipped Provider GetItThere Freight Shipper Acme Industries Manufacturer Ship Req Shipped Delivered Provider Consumer s Architecture for the dealer network
28 Focus on the middle Contract Contract Contract Contract Collaborative View A Contract represents the terms and conditions by which a service is provided and consumed. The Contract is the specification of the middle a collaboration between the provider and consumer. The service contract specifies the roles each party plays, the interfaces they offer and the behavior of enacting the service. The service contract is binding on those participating in the service Structural View The service interface types, which are the types of the roles, define the interaction points (service ports) for providing and using services. The service contract can scale up to choreographed and nested asynchronous interactions over an extended time period which is the norm for business services. Multiparty contracts are easily supported The service contract (collaboration and service interfaces) are a unit a single specification of a service without regard for implementation or dependencies.
29 [Web] s Implement the s Architecture Web Order Conformation Shipped Web Mechanics Are Us Dealer Status Physical Delivery Web Web GetItThere Freight Shipper Acme Industries Manufacturer Ship Req Shipped Delivered Web Contracts Specify Points is consumed here is provided here Contracts can be reused for any number of services architectures, components or processes. Providers and consumers are loosely coupled through by agreeing on the middle statically or dynamically. Contracts do not require or depend on internal processes or redundant complementary protocols. Matching of contracts (provider and consumer having different contracts) is an orthogonal concern Lollypop notation is optional
30 Why do service contracts have several parts? Design goals for service contracts: Bi-lateral and multi-lateral service contracts Asynchronous interaction in both directions Choreographed behavior of the services (not the ends) Nesting of service contracts (building more complex contracts out of simpler ones) UML Interfaces don t cut it, options are: Substantial overall of UML semantics (including behavioral semantics) to allow for the above requirements as part of an extended interface concept Introduce this service contract pattern don t change UML but allow for tools to make it easy Our option don t change or distort UML, instead document a simple pattern for services in UML. Consider adding bi-directional and nested interfaces to UML - later. A bi-directional service contract Collaborative View Structural View May include pre and post conditions
31 Choreography for bi-directional service contract Choreography View Data Compound Contract Composition reduces complexity while providing for arbitrarily complex service contracts Any role can initiate any sub-service Can be built top down or bottom up
32 Compound Contract Structural View Interface can be flattened in PSM mapping to a technology, such as WSDL or Corba Each role binding implies a port On the role s type A s Architecture (SOA) shows how Participants Provide and Use s for a Common Purpose. Contract is USED here.
33 Participants Participant Participant Participants can play roles in multiple services architectures, defining their external requirements. Each service contract they are bound to must interact through a compatible port. Participants are the types of participant roles in the services architecture. Inside the Manufacturer Order Conformation Web Web Order Processing Web Shipped Web Shipping Web Ship Req Shipped Delivered Web Web Web Receivables Event
34 Internal s Architectures The composite is the boundary and other participants help implement this external requirement. Corresponding Composite Structure A Realization models the capability to provide a single service Works well for SCA A service component can be implemented with internal services and/or with a business process or by wrapping existing capabilities. Here the manufacturer delegates to internal service realizations.
35 Summary View of Dependencies Multiplexed Parts Assertion of compliance Ports that can statically or dynamically support multiple service contracts
36 Profile Metamodel The Profile The profile only stereotypes those elements of the meta model that are specific to SOA. Normal features of UML are assumed. Additional constraints, such as pre and post conditions, use standard UML elements without change.
37 Provisioning Profile Process Example Dealer: Place Purchase Order Part of the dealer business process Call an operation within the manufacturer business process Accept and handle return events from the manufacturer business process Conform to the behavior of the ordering service contract
38 Dealer Business Process Places purchase orders using the Ordering within the Purchasing Advanced SOA Profile Capabilities s architectures at the business and technology level Specification of contract interaction protocol (choreography) Composition of compound contracts from more basic contracts Contract specifications independent of participants Integration of non-complementary interfaces Interactions involving 3 or more participants Contract specialization
39 Summary Usable today Cannot afford to wait for: UML publication and then vendor adoption Focused on SOA concerns not taking on classification etc Simple (only 13 stereotypes) Emphasis on contracts and architecture Addresses business and technical architecture 77 UPMS light for INF5120 exercise
Den europeiske byggenæringen blir digital hva skjer i Europa? Steen Sunesen Oslo, 30.04.2019 Agenda 1. 2. CEN-veileder til ISO 19650 del 1 og 2 3. EFCA Guide Oppdragsgivers krav til BIMleveranser og prosess.
ISO 41001:2018 «Den nye læreboka for FM» Norsk tittel: Fasilitetsstyring (FM) - Ledelsessystemer - Krav og brukerveiledning ISO 41001:2018 Kvalitetsverktøy i utvikling og forandring Krav - kapittel 4 til
Relational Algebra 1 Unit 3.3 Unit 3.3 - Relational Algebra 1 1 Relational Algebra Relational Algebra is : the formal description of how a relational database operates the mathematics which underpin SQL
Capturing the value of new technology How technology Qualification supports innovation Avanserte Marine Operasjoner - Fra operasjon til skip og utstyr Dag McGeorge Ålesund, 1 Contents Introduction - Cheaper,
Invitation to Tender FSP FLO-IKT /2013/001 MILS OS April 15th 2013 Forfatter Prosjektittel 19.04.2013 19.04.2013 1 Introduction AGENDA Important aspects regarding the competition and Invitation to tender
Hvordan komme i gang med ArchiMate? Det første modelleringsspråket som gjør TOGAF Praktisk Logica 2012. All rights reserved No. 3 Logica 2012. All rights reserved No. 4 Logica 2012. All rights reserved
Side 1 av 5 NTNU Norges teknisk-naturvitenskapelige universitet Institutt for telematikk EXAM TTM4128 SERVICE AND RESOURCE MANAGEMENT EKSAM I TTM4128 TJENESTE- OG RESSURSADMINISTRASJON Contact person /
A Study of Industrial, Component-Based Development, Ericsson SIF8094 Fordypningsprosjekt Ole Morten Killi Henrik Schwarz Stein-Roar Skånhaug NTNU, 12. des. 2002 Oppgaven Studie av state-of-the-art : utviklingsprosesser
Store og komplekse informasjonssystemer Gruppetime uke 35 email@example.com Agenda - Repetisjon av begrepene fra rammeverket (miniforelesningene) - Gjennomgang av Hanseth og Lyytinen (2010) - Gjennomgang
INF520 Modellbasert systemutvikling COMET Business Modelling COMET Requirements Modelling Forelesning 2.03.2007 Brian Elvesæter firstname.lastname@example.org COMET Business Modelling with WesternGeco Survey
Risikofokus - også på de områdene du er ekspert - hvordan kan dette se ut i praksis? - Ingen er for gammel til å begå nye dumheter Nytt i ISO 9001:2015 Vokabular Kontekst Dokumentasjonskrav Lederskap Stategi-politikk-mål
Little Mountain Housing Feedback from January 2012 Open Houses Presentation to Little Mountain Community Advisory Group Overview Open house attendance 409 signed in 600+ total Comment forms submitted 326
Antenor Management System v5 Grunnlag: 11 år med erfaring og tilbakemeldinger Antenor Management System v5 AMS v5 første versjon lanseres 13. november 100% uavhengig plattform 100% dedikert til Quality
SRP s 4th Nordic Awards Methodology 2018 Stockholm 13 September 2018 Awards Methodology 2018 The methodology outlines the criteria by which SRP judges the activity of Manufacturers, Providers and Service
Public roadmap for information management, governance and exchange 2015-09-15 SINTEF email@example.com Skate Skate (governance and coordination of services in egovernment) is a strategic cooperation
Information search for the research protocol in IIC/IID 1 Medical Library, 2013 Library services for students working with the research protocol and thesis (hovedoppgaven) Open library courses: http://www.ntnu.no/ub/fagside/medisin/medbiblkurs
Department of Computer and Information Science Examination paper for TDT4252 and DT8802 Information Systems Modelling Advanced Course Academic contact during examination: Phone: Examination date: Examination
Status for IMOs e-navigasjon prosess John Erik Hagen, Regiondirektør Kystverket E-Navigasjoner skal føre til: - økt navigasjonssikkerhet - økt effektivitet i shipping - enklere adgang til havner og farvann,
Human Factors relevant ved subsea operasjoner? Arne Jarl Ringstad, Lead Advisor Human Factors and Organizational Safety Classification: Internal 2012-01-30 Hva er Human Factors? Human factors is the scientific
5 E Lesson: Solving Monohybrid Punnett Squares with Coding Genetics Fill in the Brown colour Blank Options Hair texture A field of biology that studies heredity, or the passing of traits from parents to
Referansearkitektur use cases Kjell Sand SINTEF Energi AS NTNU Institutt for elkraftteknikk 1 Begrunnelse for arkitektur use cases Med det brede perspektivet Smart grids har, er det nødvendig å dele det
Hvordan føre reiseregninger i Unit4 Business World Forfatter: firstname.lastname@example.org Denne e-guiden beskriver hvordan du registrerer en reiseregning med ulike typer utlegg. 1. Introduksjon 2. Åpne vinduet
Transformations Moving Objects We need to move our objects in 3D space. Moving Objects We need to move our objects in 3D space. An object/model (box, car, building, character,... ) is defined in one position
Side 1 av 8 Norwegian University of Science and Technology DEPARTMENT OF COMPUTER AND INFORMATION SCIENCE MID-TERM EXAM TDT4258 MICROCONTROLLER SYSTEM DESIGN Wednesday 3 th Mars 2010 Time: 1615-1745 Allowed
Server-Side Eclipse Bernd Kolb email@example.com Martin Lippert it-agile GmbH firstname.lastname@example.org 2006 by Martin Lippert, email@example.com; made available under the EPL v1.0 Outline Introduction Why Eclipse?
Dynamic Programming Longest Common Subsequence Class 27 Protein a protein is a complex molecule composed of long single-strand chains of amino acid molecules there are 20 amino acids that make up proteins
A New Paradigm for Health Management of Bridges Presentation Overview Introduction AASHTO Grand Challenges SAFETEA-LU LTBP Is the Problem Unique? RCM A New Paradigm Design, Build, Maintain---Asset Management
Server-Side Eclipse Martin Lippert akquinet agile GmbH firstname.lastname@example.org 2006 by Martin Lippert, email@example.com; made available under the EPL v1.0 Outline Introduction Why Eclipse?
Uke 5 Magnus Li firstname.lastname@example.org INF3290 26/27.09.2017 Repetisjon av begreper Diskusjonsoppgaver I første innlevering ønsker vi et brukerperspektiv i et informasjonssystem - Hva kan inngå i et slikt informasjonssystem?
Dagens forelesning Overordnet bilde av mennesker (aktører), oppgaver, informasjon og systemer (verktøy) Participatory design Utviklingsprosesser Oppgaveanalyse Oppgavemodellering Oppgaveanalyse Kjært navn
Erfaringer fra en Prosjektleder som fikk «overflow» Per Franzén, Project Manager August 30 th, 2017 ERFARINGER FRA EN PROSJEKTLEDER SOM FIKK «OVERFLOW» AV GDPR BEGREPER OG INSTRUKSER Purpose limitation
Øystein Haugen, Professor, Computer Science MASTER THESES 2015 Professor Øystein Haugen, room D1-011 1 Hvem er jeg? Øystein Haugen, nytilsatt professor i anvendt informatikk på Høyskolen i Østfold, avdeling
Blockchain Hva er det og hvordan komme igang? Thaline M Telnes Graduate consultant Thaline.email@example.com 07 Feb 2019 1 Hva er Blockchain for Business IBMs platform & løsninger Hvordan komme igang? 2 1
LESSON 7 Slope Intercept Formula LESSON 7 Slope-Intercept Formula Here are two new words that describe lines slope and intercept. The slope is given by m (a mountain has slope and starts with m), and intercept
Side 1 av 5 NTNU Norges teknisk-naturvitenskapelige universitet BOKMÅL Fakultet for informasjonsteknologi, matematikk og elektroteknikk Institutt for datateknikk og informasjonsvitenskap AVSLUTTENDE EKSAMEN
NIRF 17. april 2012 En praktisk anvendelse av ITIL rammeverket Haakon Faanes, CIA,CISA, CISM Internrevisjonen NAV NAVs ITIL-tilnærming - SMILI NAV, 18.04.2012 Side 2 Styring av tjenestenivå Prosessen omfatter
VIKINGTIDSMUSEET Plan- og designkonkurranse/design competition Elektronisk innlevering/electronic solution for submission: Det benyttes en egen elektronisk løsning for innlevering (Byggeweb Anbud). Dette
Skjema for spørsmål og svar angående: Skuddbeskyttende skjold Saksnr. 201300129 TED: 2014/S 017-026835 Nr Dokument Referanse Svar 1 Kvalifikasjonsgrunnlag Er det mulig å få tilsendt Nei 27.01.2014 27.01.2014
Den som gjør godt, er av Gud (Multilingual Edition) Arne Jordly Click here if your download doesn"t start automatically Den som gjør godt, er av Gud (Multilingual Edition) Arne Jordly Den som gjør godt,
UNIVERSITETET I OSLO INF1300 Introduksjon til databaser Dagens tema: Eksempel Klisjéer (mønstre) Tommelfingerregler Institutt for informatikk Dumitru Roman 1 Eksempel (1) 1. The system shall give an overview
HVILKE ENDRINGER KAN BRANSJEN FORVENTE SEG FREMOVER SETT FRA ET BRUKERPERSPEKTIV CHRISTIAN HEIBERG, EXECUTIVE DIRECTOR CBRE AS NORSK EIENDOM 26.04.18 ALT FORANDRES FROM SURVIVAL OF THE FITTEST TO SURVIVAL
1 Issues and challenges in compilation of activity accounts London Group on environmental accounting 21st meeting 2-4 November 2015 Statistics Netherlands The Hague Kristine E. Kolshus firstname.lastname@example.org Statistics
Plain Language Association International s 11 th conference Improving Customer Relationships September 21-23, 2017 University of Graz, Austria hosted by Klarsprache.at Copyright of this presentation belongs
Internationalization in Praxis The way forward internationalization (vt) : to make international; also: to place under international control praxis (n) : action, practice: as exercise or practice of an
part of Aker From Policy to personal Quality Aker Solutions Bjørn Lende VP Quality Management MMO October 2011 2011 Aker Solutions Our vision and values Built on more than 170 years of industrial tradition
Databases 1 Extended Relational Algebra Relational Algebra What is an Algebra? Mathematical system consisting of: Operands --- variables or values from which new values can be constructed. Operators ---
Verifying security since 1999 ISO-standarderfor informasjonssikkerhet ISO/IEC 27000-serien Information technology Security techniques oiso/iec 27000 Information security management systems Overview and
6 DMSD has stood for process monitoring in fastening technology for more than 25 years. HONSEL re- rivet processing back in 990. DMSD 2G has been continuously improved and optimised since this time. All
TILLEGGSSPØRSMÅL BILLETT- OG ADMINISTRASJONSSYSTEM KINONOR AS COMPLEMENTARY QUESTIONS POINT OF SALE SOFTWARE PACKAGE KINONOR AS Spm.1 : Konkurransegrunnlag: 1.3 Deltilbud Billett- og administrasjonssystemet,
Utvikling av skills for å møte fremtidens behov Janicke Rasmussen, PhD Dean Master email@example.com Tel 46410433 Skills project results Background for the project: A clear candidate profile is defined
May legally defined terms be useful for improved interoperability in the public sector? Prof. Dag Wiese Schartum, Norwegian Research Center for Computers and Law, University of Oslo How may terms be legally
1 Emnedesign for læring: Et systemperspektiv v. professor, dr. philos. Vidar Gynnild Om du ønsker, kan du sette inn navn, tittel på foredraget, o.l. her. 2 In its briefest form, the paradigm that has governed
GeWare: A data warehouse for gene expression analysis T. Kirsten, H.-H. Do, E. Rahm WG 1, IZBI, University of Leipzig www.izbi.de, dbs.uni-leipzig.de Outline Motivation GeWare Architecture Annotation Integration
IN-MMO Obligatorisk oppgave 1 Brian Elvesæter firstname.lastname@example.org 1 Conference Centre Portal (CCP) 2 1 Oblig 1: Problem description [1/3] The Conference Center Portal is an Internet portal that organizers
Initiating Event BB4 Initiating Event Type 3 End Control Type Type 2 End Control 2 B5/C2 Feiltre, hendelsestre og RIFmodell Rolf Bye, Studio Apertura Initiating Event structure C & C3 Omission structure
Endelig ikke-røyker for Kvinner! (Norwegian Edition) Allen Carr Click here if your download doesn"t start automatically Endelig ikke-røyker for Kvinner! (Norwegian Edition) Allen Carr Endelig ikke-røyker
Emneevaluering GEOV272 V17 Studentenes evaluering av kurset Svarprosent: 36 % (5 av 14 studenter) Hvilket semester er du på? Hva er ditt kjønn? Er du...? Er du...? - Annet PhD Candidate Samsvaret mellom
Han Ola of Han Per: A Norwegian-American Comic Strip/En Norsk-amerikansk tegneserie (Skrifter. Serie B, LXIX) Peter J. Rosendahl Click here if your download doesn"t start automatically Han Ola of Han Per:
Prosjektet Digital kontaktinformasjon og fullmakter for virksomheter Digital contact information and mandates for entities Nordisk Adressemøte / Nordic Address Forum, Stockholm 9-10 May 2017 Elin Strandheim,
Software applications developed for the maritime service at the Danish Meteorological Institute Anne Marie Munk Jørgensen (email@example.com), Ove Kjær, Knud E. Christensen & Morten L. Mortensen Danish Meteorological
Utah s Reading First Jan Dole, Michelle Hosp, John Hosp, Kristin Nelson, Aubree Zelnick UCIRA Conference November 3-4, 2006 Overview Background on Reading First Utah s Reading First Reading First Components
Trigonometric Substitution Alvin Lin Calculus II: August 06 - December 06 Trigonometric Substitution sin 4 (x) cos (x) dx When you have a product of sin and cos of different powers, you have three different
part of Aker Motivasjon og erfaringer Kristin M. Berntsen/Soffi Westin/Maung K. Sein 09.12.2011 2011 Aker Solutions Motivasjon for Aker Solutions Forutsetning Vilje fra bedrift og se nytteverdien av forskning.
Andrew Gendreau, Olga Rosenbaum, Anthony Taylor, Kenneth Wong, Karl Dusen The Process Goal Definition Data Collection Data Preprocessing EDA Choice of Variables Choice of Method(s) Performance Evaluation
Familieeide selskaper - Kjennetegn - Styrker og utfordringer - Vekst og nyskapning i harmoni med tradisjoner Resultater fra omfattende internasjonal undersøkelse og betraktninger om hvordan observasjonene
University of Oslo Department of Informatics INF5120 - Modellering med objekter Oblig 2, V2004 Skrevet av: Gruppe 16 Geir Atle Hegsvold (gahegsvo) Harald Maalen (haralm) André Sollie (andresol) 2 Index
Ny personvernlovgivning er på vei Er du forberedt? 23. august 2017 There are lines you cannot cross. There are rules to the game. But within the lines and following the rules, you are only limited by your
FORSLAG FRA SEF TIL NY STILLAS - STANDARD 1 Bakgrunnen for dette initiativet fra SEF, er ønsket om å gjøre arbeid i høyden tryggere / sikrere. Både for stillasmontører og brukere av stillaser. 2 Reviderte
INF2120 Tools at your fingertips Version 070124 23-Jan-07 INF2120 Prosjekt i modellering 1 Eclipse og RSM en god IDE? med foiler også av Andreas Limyr og Gøran K. Olsen før begge Ifi, nå begge Sintef 23-Jan-07
Utstyr for avstandsmåling Dommersamling 14. mars 2015 Stein Jodal Dommersamlingen 2012 Regulert i R 14-3 Kunstige hjelpemidler, uvanlig utstyr og uvanlig bruk av utstyr Anmerkning: Komiteen kan lage en
Endringer i neste revisjon av / Changes in the next revision of 1. October 2015 INFORMASJON PÅ NORSK 2 INTRODUKSJON 2 ENDRINGER FOR KATALOG 1.0.3 OG PAKKSEDDEL 1.0.2 3 ENDRINGER FOR ORDRE 1.0.3 4 ENDRINGER
MDA Tool Support for SOI Mike Rosen CTO, AZORA Technologies, Inc. Mike.Rosen@Azoratech.com Mike Rosen ACCESS TO THE EXPERTS Consultant Chief Enterprise Architect for service and component based systems
Søknadsskjema Strategiske Partnerskap Anne Kloster Holst Seniorrådgiver SIU Oslo 29. 1.2016 Hva skal beskrives i søknaden? A. General Information B. Context C. Priorities D. Participating Organisations
Trust in the Personal Data Economy Nina Chung Mathiesen Digital Consulting Why does trust matter? 97% of Europeans would be happy for their personal data to be used to inform, make recommendations or add
OOSU 22.sept 2010 PATTERNS (mønstre) Hva er et Pattern opprinnelsen Mal for en Patternbeskrivelse Hva er et Pattern Language? Ulike typer Pattern vi anvender innen systemutvikling Dagens Pensum : (kursorisk
Introduction to DK- CERT Vulnerability Database By Peter Rickers and Mikael Stamm 1 Fundamental Idea Securing of networks, in-house and externally Savings for the costumers Making admission to the correct
Sikkert Drillingnettverk på CAT-D Rig Med fokus på IT sikkerhet i offshore bransjen Kristiansand, 21/10/2014, Asgeir Skretting, Dag Tang Sikkert Drillingnettverk på CAT-D Rig Agenda Hvorfor sikker offshore
Tillit i hierarkiske og gjensidige relasjoner Lars Huemer, Professor, BI Partnerforum 29 mai 2017 Temaer Hva er en relasjon? Hva er en hierarkisk relasjon? Hva er en gjensidig relasjon? Hva er tillit i
Reporting Services - oversigt Microsoft Dynamics C5 Version 2008 Oversigt over Microsoft Reporting Services rapporter Summary Efterfølgende vises en oversigt over de rapporter som er indeholdt i Microsoft
INF5120 Modellbasert systemutvikling Interoperability Frameworks Information and ontologies s Forelesning 23.04.2007 Arne-Jørgen Berre Arne.J.Berre@sintef.no Pensum litteratur F Foiler fra alle forelesningene,
Personvernreglenes betydning for stordata, analyse, AI, agreggerte data, etc Eva Jarbekk Tekna, 7. september 2017 Hva gjelder GDPR egentlig for? Ikke for anonyme data Med anonyme data kan man gjøre hva
ANNUAL SPONSORSHIP OPPORTUNITIES MVP SPONSORSHIP PROGRAM CALLING ALL VENDORS! Here is your chance to gain company exposure while strengthening your dealer Association at the same time. Annual Sponsorship