Object-Oriented Modeling: A Roadmap
|
|
|
- Randolph Hancock
- 6 years ago
- Views:
Transcription
1 University of Paderborn Leiden University Object-Oriented Modeling: A Roadmap University of Paderborn Leiden University Software Development: Traditional (?) Approach implementation June 8, 2000 ICSE 2000: Future of Software Engineering 2 1
2 Software Development: Reality June 8, 2000 ICSE 2000: Future of Software Engineering 3 Software Development: Model-centered Approach abstracts from irrelevant details abstracts from implementation details June 8, 2000 ICSE 2000: Future of Software Engineering 4 2
3 Requirements for a Model and the Modeling Language Requirements for a Model user-friendly, understandable expressive correct, precise Requirements for a Modeling Language - visual, diagrammatic - structure & behavior - syntax & semantics June 8, 2000 ICSE 2000: Future of Software Engineering 5 History of Modeling Languages Historical Development ~ 70 Data Flow Diagrams (DFD) + Entity-Relationship Diagrams = Structured Analysis (SA) ~ 80 abstract data type: object-orientation ~ 90 > 50 object-oriented ing languages ~ 00 standardization: Unified Modeling Language June 8, 2000 ICSE 2000: Future of Software Engineering 6 3
4 Unified Modeling Language (UML) Unified Modeling Language (UML) union of > 9 diagram types structure: class / object diagram behavior: use case diagram statechart diagram activity diagram sequence diagram collaboration diagram implementation: component diagram deployment diagram constraints: object constraint language (OCL) June 8, 2000 ICSE 2000: Future of Software Engineering 7 Unified Modeling Language (UML) Unified Modeling Language (UML) pushed by Rational three amigos : Grady Booch, Jim Rumbaugh, Ivar Jacobson standardized by OMG (Object Management Group) version 1.1: november 1997 version 1.3: autumn 1999 version 2.0: Unified Process (RUP) under discussion This is not a talk about UML! June 8, 2000 ICSE 2000: Future of Software Engineering 8 4
5 Perspectives - Open Issues regions of the object-oriented ing landscape ing process (in the small) ing process (in the large) review composition constituents language structure June 8, 2000 ICSE 2000: Future of Software Engineering 9 Perspectives - Open Issues regions of the object-oriented ing landscape ing process (in the small) ing process (in the large) review composition constituents language structure June 8, 2000 ICSE 2000: Future of Software Engineering 10 5
6 Layered Language Structure Language Structure application-specific extensions application-specific prefaces domain-specific extensions domain-specific profiles (realtime, embedded, multimedia) ing language core language (core) syntax & semantics completeness concrete syntax (textual vs. graphical) June 8, 2000 ICSE 2000: Future of Software Engineering 11 Open Issues (1) Open issues in the Language Structure region: language architecture (core vs. profiles) hybrid notations (textual vs. graphical) completeness, expressiveness semantics June 8, 2000 ICSE 2000: Future of Software Engineering 12 6
7 Perspectives - Open Issues regions of the object-oriented ing landscape ing process ing process (in the large) (in the small) review composition constituents language structure June 8, 2000 ICSE 2000: Future of Software Engineering 13 Model Constituents (1) what are the basic building blocks of a? problem domain view 1 view 2 view 3 view 4 view integration of structural and behavioral views June 8, 2000 ICSE 2000: Future of Software Engineering 14 7
8 Model Constituents (2) what are the basic building blocks of a? problem domain core aspects (e.g.,concurrency) aspect weaver June 8, 2000 ICSE 2000: Future of Software Engineering 15 Model Constituents (3) what are the basic building blocks of a? problem domain pattern repository pattern repository ing by using patterns June 8, 2000 ICSE 2000: Future of Software Engineering 16 8
9 Model Constituents (4) what are the basic building blocks of a? problem domain ing by specialization framework applicationdependent June 8, 2000 ICSE 2000: Future of Software Engineering 17 Open Issues (2) Open issues in the Model Constituents region: ing units and their interdependencies views aspects, features patterns frameworks June 8, 2000 ICSE 2000: Future of Software Engineering 18 9
10 Perspectives - Open Issues regions of the object-oriented ing landscape ing process ing process (in the large) (in the small) review composition constituents language structure June 8, 2000 ICSE 2000: Future of Software Engineering 19 Model Composition what are the means to compose s? horizontal composition adding/removing parts? vertical composition refinement subsystems class-like descriptions June 8, 2000 ICSE 2000: Future of Software Engineering 20 10
11 Open Issues (3) Open issues in the Model Composition region: scalability horizontal / vertical composition techniques June 8, 2000 ICSE 2000: Future of Software Engineering 21 Perspectives - Open Issues regions of the object-oriented ing landscape ing process ing process (in the small) (in the large) review composition constituents language structure June 8, 2000 ICSE 2000: Future of Software Engineering 22 11
12 Modeling Process (in-the-small) what are the tasks during composing a? managing consistency between parts determing architecture Model-View-Controller (MVC) Architecture Controller View communication Model June 8, 2000 ICSE 2000: Future of Software Engineering 23 Modeling Process (in-the-small) what are the tasks during composing a? managing consistency between parts determing architecture Model-View-Communication-Controller (MVCC) Controller View Communication Model June 8, 2000 ICSE 2000: Future of Software Engineering 24 12
13 Open Issues (4) Open issues in the Modeling Process (in-the-small) region: consistency within the ing of coordination and communication June 8, 2000 ICSE 2000: Future of Software Engineering 25 Perspectives - Open Issues regions of the object-oriented ing landscape ing process (in the small) ing process (in the large) review composition constituents language structure June 8, 2000 ICSE 2000: Future of Software Engineering 26 13
14 Open Issues (5) Open issues in the Model Review region: animation / simulation techniques analytical techniques June 8, 2000 ICSE 2000: Future of Software Engineering 27 Perspectives - Open Issues regions of the object-oriented ing landscape ing process ing process (in the large) (in the small) review composition constituents language structure June 8, 2000 ICSE 2000: Future of Software Engineering 28 14
15 Open Issues (6) Open issues in the Modeling Process (in-the-large) region: frond-end / back-end transformations round-trip engineering process s support tools June 8, 2000 ICSE 2000: Future of Software Engineering 29 Conclusions (1) regions of the object-oriented ing landscape ing process (in the large) ing process (in the small) review composition constituents language structure June 8, 2000 ICSE 2000: Future of Software Engineering 30 15
16 Conclusions (2) Summary drawn a structured landscape identified a list of open issues Note: a lot of individual solutions exist Challenge for the Future Adaption and Integration of Solutions * *Footnote: UML might be a good platform! June 8, 2000 ICSE 2000: Future of Software Engineering 31 Conclusions (3) June 8, 2000 ICSE 2000: Future of Software Engineering 32 16
The Unified Software Development Process
The Unified Software Development Process Ivar Jacobson Grady Booch James Rumbaugh Rational Software Corporation TT ADDISON-WESLEY An Imprint of Addison Wesiey Longman, Inc. Reading, Massachusetts Harlow,
(c) Addison Wesley Chapter 1. ! Software production is an art. ! Two groups. ! Main causes of software failures
MACIASZEK, L.A. (2001): Requirements Analysis and System Design. Developing Information Systems with UML, Addison Wesley Chapter 1 Software Process Copyright 2000 by Addison Wesley Version 1.0 Software
Course Organization. Lecture 1/Part 1
Course Organization Lecture 1/Part 1 1 Outline About me About the course Lectures Seminars Evaluation Literature 2 About me: Ing. RNDr. Barbora Bühnová, Ph.D. Industrial experience Research Quality of
Process, Models, Methods, Diagrams Software Development Life Cyles. Part - II
Process, Models, Methods, Diagrams Software Development Life Cyles Part - II A bench-mark for measuring the maturity of an organization s software process CMM defines 5 levels of process maturity based
Software Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 4 Integrated Object-Oriented Methodologies: OPM and RUP 1 Object Process Methodology (OPM) Introduced by Dori in 1995. Primarily intended
Software development activities
Software development activities l Note activities not steps l l Often happening simultaneously Not necessarily discrete 1. Planning: mostly study the requirements 2. Domain analysis: study the problem
making money from customer use of kiosk attracting more customers to the store saving money if the kiosk replaces manual operations
Business Requirements Business requirements collected from multiple sources might conflict. For example, consider a kiosk product with embedded software that will be sold to retail stores and used by the
Development Process Bennett, McRobb and Farmer 1
Development Process Based on Chapter 5 Bennett, McRobb and Farmer Object Oriented Systems Analysis and Design Using UML 4 th Edition, McGraw Hill, 2010 1 In This Lecture You Will Learn: About the Unified
What You Didn t Know About RUP
Clic k to IBM Software Group What You Didn t Know About RUP Ivar Jacobson IBM Rational ihjacobs@us.ibm.com Jaczone AB ivar@jaczone.com Agenda What you may know about RUP What you should know about RUP
Chapter 3 Software Process Model
Usman Akram COMSATS Institute of information Technology lahore musmanakram@ciitlahore.edu.pk March 8, 2015 About software process model Outline 1 About software process model Build and Fix Model Why Models
1fJ.- HEWLETT. Architecting for Large-Scale Systematic Component Reuse. Martin L. Griss Software Technology Laboratories HPL July, 1998
1fJ.- HEWLETT ~~PACKAAD Architecting for Large-Scale Systematic Component Reuse Martin L. Griss Software Technology Laboratories HPL-98-132 July, 1998 E-mail: griss@hpl.hp.com systematic reuse, architecture,
Chapter 1 Software Process
MACIASZEK, L.A. (2005): Requirements Analysis and System Design, 2 nd ed. Addison Wesley, Harlow England, 504p. ISBN 0 321 20464 6 Chapter 1 Software Process Pearson Education Limited 2005 Topics The nature
Unified Process and Testing with EasyAccept. Peter Dolog dolog [at] cs [dot] aau [dot] dk E2-201 Information Systems February 22, 2007
![Unified Process and Testing with EasyAccept. Peter Dolog dolog [at] cs [dot] aau [dot] dk E2-201 Information Systems February 22, 2007](/thumbs/79/78923489.jpg "Unified Process and Testing with EasyAccept. Peter Dolog dolog [at] cs [dot] aau [dot] dk E2-201 Information Systems February 22, 2007")
Unified Process and Testing with EasyAccept Peter Dolog dolog [at] cs [dot] aau [dot] dk E2-201 Information Systems February 22, 2007 2 UP Unified Process, 1990 s Iterative, not agile Risk-driven development
Architecture Development Methodology for Business Applications
4/7/2004 Business Applications Santonu Sarkar, Riaz Kapadia, Srinivas Thonse and Ananth Chandramouli The Open Group Practitioners Conference April 2004 Topics Motivation Methodology Overview Language and
Other Agile Approaches & Methodologies
Other Agile Approaches & Methodologies 10 Most common Agile Methodologies Scrum XP Kanban => Lean House D. Sixth Annual State of Agile Survey: State of Agile Development, Atlanta, GA, VersionOne, 2012
Sistemi ICT per il Business Networking
Corso di Laurea Specialistica Ingegneria Gestionale Sistemi ICT per il Business Networking Requirements Engineering Docente: Vito Morreale (vito.morreale@eng.it) 17 October 2006 1 UP Phases 1. Inception
Software Processes. Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1
Software Processes Ian Sommerville 2004 Software Engineering, 7th edition. Chapter 4 Slide 1 Objectives To introduce software process models To describe three generic process models and when they may be
IBM Rational Systems Strategy
IBM Software Symposium 2006 IBM Rational Systems Strategy Bran Selic IBM Distinguished Engineer, Rational CTO Team Agenda The Systems Space Definitions and Issues Governance and Product Development Tools
DEVELOPMENT OF MBSE/UML MATURITY MODEL
DEVELOPMENT OF MBSE/UML MATURITY MODEL ÖZLEM DEMIRCI MASTER THESIS 2010 INFORMATICS DEVELOPMENT OF MBSE/UML MATURITY MODEL SUBJECT INFORMATION TECHNOLOGIES AND MANAGEMENT IN INFORMATICS DEVELOPMENT OF
Rational Unified Process
Rational Unified Process Software development Life Cycle The life of a software system can be represented as a series of cycle. A cycle ends with the release of a version of the system to the customers.
Software Processes. Objectives. Topics covered. The software process. Waterfall model. Generic software process models
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
Object-Oriented and Classical Software Engineering
Slide 3.1 Object-Oriented and Classical Software Engineering Seventh Edition, WCB/McGraw-Hill, 2007 Stephen R. Schach srs@vuse.vanderbilt.edu CHAPTER 3 Slide 3.2 THE SOFTWARE PROCESS Overview Slide 3.3
Objectives. The software process. Topics covered. Waterfall model. Generic software process models. Software Processes
Objectives Software Processes To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
Topics covered. Software process models Process iteration Process activities The Rational Unified Process Computer-aided software engineering
Software Processes Objectives To introduce software process models To describe three generic process models and when they may be used To describe outline process models for requirements engineering, software
Information Systems Architecture and Enterprise Modeling. Prof. Dr. Knut Hinkelmann
Information Systems Architecture and Enterprise Modeling Chapter 1: Introduction to Enterprise Architecture Motivation: Business IT Alignment Challenge: Agility Approach Enterprise Architecture Transparency
The software process
Software Processes The software process A structured set of activities required to develop a software system Specification; Design; Validation; Evolution. A software process model is an abstract representation
Software Lifecycle Models
Software Lifecycle Models Introduction into Software Engineering Lecture 18 Bernd Bruegge Applied Software Engineering Technische Universitaet Muenchen 1 Definitions Software life cycle Set of activities
MDA Overview Applied MDA
IBM Software Group MDA Overview Applied MDA Jim Amsden Senior Software Engineer IBM Rational Software jamsden@us.ibm,com Tutorial: MDA, UML, and applicability to SOA (C) IBM Corporation March 2006 Agenda!
Use-Case Diagram. Contents. Introduction. 1. Introduction. User-Centred Design (UCD) Users Requirements
Contents Use-Case Diagram MIT, Walailak University by Dr.Wichian Chutimaskul Introduction Business Model using Activity Diagram Domain Analysis using Use-Case Description Documenting Requirements using
Pearson Education 2007 Chapter 1 (RASD 3/e)
Chapter 1 (RASD 3/e) MACIASZEK, L.A. (2007): Requirements Analysis and System Design, 3 rd ed. Addison Wesley, Harlow England ISBN 978-0-321-44036-5 Chapter 1 Software Process Pearson Education Limited
Object-Oriented and Classical Software Engineering THE SOFTWARE PROCESS 9/17/2017. CHAPTER 3 Slide 3.2. Stephen R. Schach. Overview Slide 3.
Slide 3.1 CHAPTER 3 Slide 3.2 Object-Oriented and Classical Software Engineering THE SOFTWARE PROCESS Eighth Edition, WCB/McGraw-Hill, 2011 Stephen R. Schach Overview Slide 3.3 Overview (contd) Slide 3.4
SE310 Analysis and Design of Software
SE310 Analysis and Design of Software Lecture 7 REVIEW SM&D Chapters 1 to 11 & Notes February 13, 2018 Sam Siewert Domain Models Use Case Details UML is Universal Modeling Language [OMG, UML.org] Use to
CS/IT Secure Software Construction
CS/IT 328 - Secure Software Construction Chapter 4 UML the Unified Modeling Language Book: Fowler, UML Distilled, chap. 1.. 4 Notation: Notations and Meta-Models a graphical representation of a model,
2014 Oct.31 International Symposium on Practical Formal Approaches to Software Development. Copyright Prof. Dr. Shuichiro Yamamoto 2014
2014 Oct.31 International Symposium on Practical Formal Approaches to Software Development Nagoya University Dr. Prof. Shuichiro Yamamoto 1 Agenda Assurance case Pitfalls of assurance case Generic derivation
Redesigning the Organization with Information Systems
Chapter 14 Redesigning the Organization with Information Systems 14.1 2006 by Prentice Hall OBJECTIVES Demonstrate how building new systems produces organizational change Explain how a company can develop
The Review Of Business Information Systems Volume 6, Number 4
Augmenting Using UML: Improving Financial Analysis Joseph H. Callaghan (E-mail: callagha@oakland.edu), Oakland University Arline Savage (E-mail: savage@oakland.edu), Oakland University Vijayan Sugumaran
Analyze, Design, and Develop Applications
Analyze, Design, and Develop Applications On Demand Insurance Problems 1. We lose customers because we process new policy applications too slowly. 2. Our claims processing is time-consuming and inefficient.
Workflow-Processing and Verification for Safety- Critical Engineering: Conceptual Architecture Deliverable D6.1
Workflow-Processing and Verification for Safety- Critical Engineering: Conceptual Architecture Deliverable D6.1 FFG IKT der Zukunft SHAPE Project 2014 845638 Table 1: Document Information Project acronym:
Functional requirements and acceptance testing
Functional requirements and acceptance testing Lecture 3 Software Engineering TDDC88/TDDC93 autumn 2007 Department of Computer and Information Science Linköping University, Sweden Message from the course
The Top Thrill Dragster
EEC 421/521: Software Engineering The Software Process Prescriptive Process Models 1/22/08 EEC 421/521: Software Engineering 1 The Top Thrill Dragster 420 ft tall Max speed over 120 mph World s second
Introduction of RUP - The Rational Unified Process
Introduction of RUP - The Rational Unified Process Jong-Hoon Lee Dependable Software Laboratory Konkuk University References Textbook: The Rational Unified Process Made Easy A Practitioner s Guide to the
CIOReview SPARX SYSTEMS INTELLIGENTLY ARCHITECTING THE INFORMATION SILOS ENTERPRISE ARCHITECTURE SPECIAL
ENTERPRISE ARCHITECTURE SPECIAL The Navigator for Enterprise Solutions SEPTEMBER 07, 2016 CIOREVIEW.COM IN MY OPINION ERIC DONNELLY, SVP & CHIEF ENTERPRISE ARCHITECT, PNC CIO INSIGHTS MIKE ANDERSON, CIO,
A Metamodel for Agents, Roles, and Groups
A Metamodel for s, Roles, and s James Odell, Marian Nodine 2, and Renato Levy 3 is Software, Inc., 3646 West Huron River Drive, Ann Arbor, MI 4803-9489, USA email@jamesodell.com http://www.jamesodell.com
Practical Company Organization Modeling Guide
Objecteering Practical Guides Practical Company Organization Modeling Guide Author: Version: 1.0 Copyright: Softeam Softeam Consulting Team Supervised by Philippe Desfray Softeam 21 avenue Victor Hugo
Processes and Life- Cycles. Kristian Sandahl
Processes and Life- Cycles Kristian Sandahl 2 Maintenance Requirements Validate Requirements, Verify Specification Acceptance Test (Release testing) System Design (Architecture, High-level Design) Verify
Model-driven Engineering a promising approach for developing critical software applications
Model-driven Engineering a promising approach for developing critical software applications Abstract: Many different approaches and frameworks exist to use Model-driven Engineering (MDE). Some of these
Model-Based Integration of Component-Based Embedded Systems: A Case Study
Model-Based Integration of Component-Based Embedded Systems: A Case Study Mark Schulte The Boeing Company Phantom Works St. Louis, MO This work was sponsored by the DARPA/IXO Model-Based Integration of
What are requirements? Basics of Requirement Engineering. Definition of a Stakeholder. Stated Vs. Real Requirements. Stated Vs.
What are requirements? Basics of Requirement Engineering Muzaffar Iqbal Farooqi A requirement is a necessary attribute in a system, a statement that identifies a capability, characteristic, or quality
Coverage Analysis and Improvement of the Role Definitions of the Bombardier Software Engineering Process
Coverage Analysis and Improvement of the Role Definitions of the Bombardier Software Engineering Process Presented by Claude Y Laporte, Professor - Department of Software Engineering and IT École de technologie
E-Procurement Reference Model for Small Government Department
E-Procurement Reference Model for Small Government Department Hamirul Aini Hambali a, Nazib Nordin b, Haslina Mohd c a, b, c College of Arts and Sciences Universiti Utara Malaysia, 06010 Sintok, Kedah
Major attributes of the Lifecycle. The Systems Development Lifecycle. Project phases. Planning. Design. Analysis
Modelling and Systems Development Lecture 2 The Systems Development Lifecycle The four-phase model common to all system development projects Major attributes of the Lifecycle The project Moves systematically
IBM Rational Systems Developer, Version 7.0
Simplify model-driven development for software products and systems IBM Rational Systems Developer, Version 7.0 Highlights Offers integrated design and development, accommodating visualization and editing
Jochen(Joe)Krebs
What s Up RUP? Agile Portfolio Management Jochen(Joe)Krebs www.incrementor.com Speaker Jochen (Joe) Krebs www.jochenkrebs.com Author of Agile Portfolio Management (Microsoft Press 2008) Co author of IBM
Business modelling with UML
Business modelling with UML Aljaž Zrnec, Marko Bajec, Marjan Krisper Fakulteta za računalništvo in informatiko Univerza v Ljubljani Tržaška 25, 1000 Ljubljana, Slovenija aljaz.zrnec@fri.uni-lj.si Abstract
Lecture 1: Processes, Requirements, and Use Cases
Lecture 1: Processes, Requirements, and Use Cases 1 Development Processes Early Days: evolve a system Build and fix Leads to chaos Need for intelligent design Waterfall Model Requirements, Design, Code,
Smart Inventory Management System
Governors State University OPUS Open Portal to University Scholarship All Capstone Projects Student Capstone Projects Fall 2015 Smart Inventory Management System Ajay Akarapu Governors State University
Babu Madhav Institute of Information Technology, UTU 2017
Five Years Integrated M.Sc. (IT) Semester 3 Question Bank 060010312 CC9 Software Engineering Unit 1 Introduction to Software Engineering and Object-Oriented Concepts 1. What is software? 2. Which documents
Software Life-Cycle Management
Ingo Arnold Department Computer Science University of Basel Introduction Software Life-Cycle Management IT Governance and Process Overview Lecture Introduction IT Business The Problem Complexity Complex
Software Engineering Modern Approaches
Software Engineering Modern Approaches Chapter : Software Process Eric Braude and Michael Bernstein Maintenance Testing The Software Development Lifecycle Implementation Design Phase most relevant to this
MAP INTERFACE FOR IOWA DEPARTMENT OF TRANSPORTATION S ACCESS-ALAS
MAP INTERFACE FOR IOWA DEPARTMENT OF TRANSPORTATION S ACCESS-ALAS Aravind Gottemukkula Center for transportation education and research Iowa State University ABSTRACT This paper discusses the limitations
Enterprise Architecture Modeling with the Unified Modeling Language. Abstract
Chapter submitted to the book Enterprise Modeling and Computing with UML, IRM Press. Revised version. November 2005. Enterprise Architecture Modeling with the Unified Modeling Language Pedro Sousa 1,2,3,
The Product Creation Process
- 0. feasibility 1. definition 2. system 3. 4. integration & test 5. field monitoring needs verification core information Legend: in draft full under development most information 50% available in concept
Project Management and Software Development Processes: Integrating PMBOK and OPEN
Project Management and Software Development Processes: Integrating PMBOK and OPEN Maurício Covolan Rosito, Daniel Antonio Callegari and Ricardo Melo Bastos International Science Index, Computer and Information
Comparative Analysis of Ontology Charting with other Modelling Techniques
Comparative Analysis of Ontology Charting with other Modelling Techniques José Cordeiro and Joaquim Filipe Escola Superior de Tecnologia de Setúbal, Rua do Vale de Chaves, Estefanilha, 2910-761 Setúbal,
Expanding the Discipline of Enterprise Architecture Modeling to Business Intelligence with EA4BI
Expanding the Discipline of Enterprise Architecture Modeling to Business Intelligence with EA4BI Rudi Claes Inno.com Institute, Beerzel, Belgium Abstract. The current mainstream enterprise architecture
ARIS Expert Paper. March Steps to Business-Driven SOA.
ARIS Expert Paper ARIS Platform Expert Paper March 2007 10 Steps to Business-Driven SOA www.ids-scheer.com Find out more at: www.ids-scheer.com/soa Visionary architecture always requires good building
Systems and software product line engineering with SysML, UML and the IBM Rational Rhapsody BigLever Gears Bridge.
Global distributed development White paper July 2009 Systems and software product line engineering with SysML, UML and the IBM Rational Rhapsody BigLever Gears Bridge. Integrating MDD and SPL to effectively
Umeå University Department of Computing Science SE UMEÅ SWEDEN
Evaluating The PLUSS Domain Modeling Approach by Modeling the Arcade Game Maker Product Line Koteswar Rao Kollu (ens03kku@cs.umu.se) June 21 st, 2005 Master s Thesis in Computing Science, 10 credits Supervisor
Business Capabilities as Formalised Social Systems
Business Capabilities as Formalised Social Systems By Graham Berrisford What are the essential elements of a society? The sociological tradition suggests two alternatives: either [actors] or activities.
Ecosystem services in environmental sustainability: a formalized approach using UML
20th International Congress on Modelling and Simulation, Adelaide, Australia, 1 6 December 2013 www.mssanz.org.au/modsim2013 Ecosystem services in environmental sustainability: a formalized approach using
Chapter. Redesigning The Organization With Information Systems
Chapter Redesigning The Organization With Information Systems 1 Objectives Demonstrate how building new systems produces organizational change Explain how a company can develop information systems that
Assessing Quality in SysML Models
Assessing Quality in SysML Models Matthew Hause, Presented by James Hummell 1 Agenda How do I know if my model is of good quality? What is quality? Model-Based Engineering SysML and UML Examples: Requirements
A DECISION SUPPORT SYSTEM FOR WILDFIRE DAMAGE REDUCTION WITH UML
A DECISION SUPPORT SYSTEM FOR WILDFIRE DAMAGE REDUCTION WITH UML Kaloudis Spiros 1, Karetsos Sotiris 2, Costopoulou Constantina 2, Lorentzos Nikos 2, {kaloudis, skaret, tina, lorentzos}@aua.gr 1 Technological
CHAPTER 2 LITERATURE SURVEY
10 CHAPTER 2 LITERATURE SURVEY This chapter provides the related work that has been done about the software performance requirements which includes the sub sections like requirements engineering, functional
Software Development Methodologies
Software Development Methodologies Lecturer: Raman Ramsin Lecture 5 Integrated Object-Oriented Methodologies: USDP and EUP 1 Unified Software Development Process (USDP) Also known as Unified Process (UP)
Usine Logicielle. Position paper
Philippe Mils: Contact : Thales Resear & Technology Usine Logicielle Project Coordinator philippe.mils@thalesgroup.com Abstract Usine Logicielle Position paper Usine Logicielle is a project operated in
Organizational modeling in a semantic wiki
Organizational modeling in a semantic wiki João Pedro Mendes joao.mendes@ceo.inesc.pt Abstract The world has always experienced changes. But now these changes happen faster than ever. This has several
Lessons Learned from Development of Large-Scale Rules-Based System
Lessons Learned from Development of Large-Scale Rules-Based System Business Rules Forum Presented by: Lynne Harbin Philip Matkovsky October 2007 Orlando, FL 1 Abstract This presentation focuses on a real-world
INF5120 Modellbasert Systemutvikling Modelbased System development
INF5120 Modellbasert Systemutvikling Modelbased System development Lecture 6: 17.02.2014 Arne-Jørgen Berre arneb@ifi.uio.no or Arne.J.Berre@sintef.no 1 Content Oblig 1 details Goal Modeling, BMM, and Non
2/14/2013. Software Engineering. Session 3 Sub-Topic. 1 Strategy Alignment Elicitation Methodology. Dr. Jean-Claude Franchitti
Software Engineering Session 3 Sub-Topic Strategy Alignment Elicitation Methodology Dr. Jean-Claude Franchitti New York University Computer Science Department Courant Institute of Mathematical Sciences
Oracle Application Integration Architecture Mission Critical SOA Governance
Oracle Application Integration Architecture Mission Critical SOA Governance Jason Xie, Principal Strategy Product Manager Agenda SOA Governance Needs Risks without SOA Governance
Chapter 4 Requirements Elicitation
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 4 Requirements Elicitation Outline Today: Motivation: Software Lifecycle Requirements elicitation challenges Problem statement
How Conceptual Modeling Is Used
Communications of the Association for Information Systems 12-1-2009 How Conceptual Modeling Is Used Peter Fettke Institute for Information Systems at the German Institute for Artificial Intelligence (DFKI)
In this Lecture you will Learn: Development Process. Unified Software Development Process. Best Practice
In this Lecture you will Learn: Development About the Unified Software Development How phases relate to workflows in an iterative life cycle An approach to system development Major activities in the development
A lifecycle approach to systems quality: because you can t test in quality at the end.
Systems quality management White paper December 2009 A lifecycle approach to systems quality: because you can t test in quality at the end. Moshe S. Cohen, market/offering manager, quality management,
The good news. 34% of software projects succeed. Standish Group, CHAOS Report, 2003
The good news 34% of software projects succeed. Standish Group, CHAOS Report, 2003 1 The bad news That means 66% failed! Standish Group, CHAOS Report, 2003 2 Best Practices Develop Iteratively Manage Requirements
Processes and Techniques
Methods (AM) Processes and Techniques Noting those in Architect training It is illegal to copy, share or show this document (or other document published at http://avancier.co.uk) without the written permission
UML Extension for Business Modeling
UML Extension for Business Modeling version 1.1 1 September 1997 Rational Software Microsoft Hewlett-Packard Oracle Sterling Software MCI Systemhouse Unisys ICON Computing IntelliCorp i-logix IBM ObjecTime
Processes, Roles, and Events: UML Concepts for Enterprise Architecture
Processes, Roles, and Events: UML Concepts for Enterprise Architecture Alistair Barros, Keith Duddy, Michael Lawley, Zoran Milosevic, Kerry Raymond, Andrew Wood CRC for Enterprise Distributed Systems Technology
Software Life-Cycle Management
Ingo Arnold Department Computer Science University of Basel Introduction Software Life-Cycle Management IT Governance and Process Overview Lecture Introduction IT Business The Problem Complexity Complex
Business Architecture Fundamentals
Course Description 3 day - expert led hands-on In this turbulent and increasingly competitive global economy, and the rapid pace of change in business models involving changing technology and customer
Component-Based Software Engineering. ECE493-Topic 5 Winter Lecture 27 Component Based Development Process (Part A)
Component-Based Software Engineering ECE493-Topic 5 Winter 2007 Lecture 27 Component Based Development Process (Part A) Ladan Tahvildari Assistant Professor Dept. of Elect. & Comp. Eng. University of Waterloo
Analysis of the Completeness and Quality of the Essence specification
paluno The Ruhr Institute for Software Technology Institut für Informatik und Wirtschaftsinformatik Universität Duisburg-Essen Masterarbeit Analysis of the Completeness and Quality of the Essence specification
MODELING OF ONLINE LOCATION BASED SERVICES IN DAIRY MANAGEMENT SYSTEM THROUGH UML
I.J.E.M.S., VOL.6 (3) 2015: 158-163 ISSN 2229-600X MODELING OF ONLINE LOCATION BASED SERVICES IN DAIRY MANAGEMENT SYSTEM THROUGH UML 1* Mishra Suman Kumar, 2 Dhanda Namrita, 3 Pathak Peeyush Kumar 1 Institute
Requirements Engineering
Requirements Engineering Software Engineering Andreas Zeller Saarland University Requirements Engineering The Real World Requirements Engineering A description of what the system should do (but not how)
Software Development Methodologies. CSC 440: Software Engineering Slide #1
Software Development Methodologies CSC 440: Software Engineering Slide #1 Topics 1. The Waterfall Model 2. Agile Software Development 3. The Unified Process 4. Object-Oriented Analysis and Design 5. The
Incorporating Model-Driven Techniques into Requirements Engineering for the Service-Oriented Development Process
Incorporating Model-Driven Techniques into Requirements Engineering for the Service-Oriented Development Process Grzegorz Loniewski, Ausias Armesto, Emilio Insfran ISSI Research Group, Department of Computer
TOGAF ADM/MDA Synergy Project
TOGAF ADM/MDA Synergy Project Joint Report A White Paper by The Synergy Project Team November 2007 Copyright 2007 The Open Group All rights reserved. No part of this publication may be reproduced, stored
The Macro Process Is the Micro Process
The Macro Process Is the Micro Process Israel Gat, Director and Fellow (With many thanks to Murray Cantor, Tom Grant and Paul Ryan) IEEE Computer Society Symposium November 12, 2014 Bio Areas of research
Introduction to Software Engineering
Introduction to Software Engineering Lecture 1 Dr Eliane L. Bodanese 1 Agenda Introductions Ground Rules What is the course about & course information Course texts Lecture and Exercises Assessment Coursework