1 ©B. Henderson-Sellers SEMAT 2010 SEMAT – Definitions Track March 17, 2010 Chair: Brian Henderson-Sellers.

Slides:



Advertisements
Similar presentations
Ontology Assessment – Proposed Framework and Methodology.
Advertisements

Unified process(UP) UP is an OO system development methodology offered by Rational(Rational Rose) s/w, now a part of IBM Developed by Booach,Rambaugh,Jacobson--
Software Project Management
Requirements Engineering n Elicit requirements from customer  Information and control needs, product function and behavior, overall product performance,
Systems Engineering in a System of Systems Context
Shihong Huang Department of Computer Science & Engineering Florida Atlantic University 1st SEMAT Workshop March , 2010 Zurich Capturing the Essence.
L4-1-S1 UML Overview © M.E. Fayad SJSU -- CmpE Software Architectures Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I.
Creating Architectural Descriptions. Outline Standardizing architectural descriptions: The IEEE has published, “Recommended Practice for Architectural.
Business Area Analysis Focus: Domain View (selected business area) Goals: –Isolate functions and procedures that allow the area to meet its goals –Define.
171 Use Case Descriptions Chapter 4 – Facade Iteration Initial Requirements (Inception Phase)
Systems Engineering Foundations of Software Systems Integration Peter Denno, Allison Barnard Feeney Manufacturing Engineering Laboratory National Institute.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
1 CMPT 275 Software Engineering Requirements Analysis Process Janice Regan,
ISO 9001:2015 Revision overview - General users
© 2008 Prentice Hall11-1 Introduction to Project Management Chapter 11 Managing Project Execution Information Systems Project Management: A Process and.
Domain Modelling the upper levels of the eframework Yvonne Howard Hilary Dexter David Millard Learning Societies LabDistributed Learning, University of.
© 2011 Cisco and/or its affiliates. All rights reserved. Cisco Confidential 1 August 15th, 2012 BP & IA Team.
S/W Project Management
1 ©B. Henderson-Sellers SEMAT 2010 SEMAT Position Statement March 17, 2010 Brian Henderson-Sellers PhD, DSc, MASCE, FIMA, FACS, FIEAust, CPEng Director,
Object Oriented Analysis By: Don Villanueva CS 524 Software Engineering I Fall I 2007 – Sheldon X. Liang, Ph. D.
CLEANROOM SOFTWARE ENGINEERING.
© 2007 Open Grid Forum OGF Modeling Activities DMTF Alliance Partner Symposium Portland, 2007 July 18 Ellen Stokes
A Development Process Lecture Oo13 Objectory based method.
“Enhancing Reuse with Information Hiding” ITT Proceedings of the Workshop on Reusability in Programming, 1983 Reprinted in Software Reusability, Volume.
Business Analysis and Essential Competencies
ArchiMate Authors : eSchoolink Group - ITNLU. Contents 1. What’s ArchiMate ? 2. Why ArchiMate ? 3. Main Benefits of ArchiMate 4. Layers of ArchiMate 5.
©2007 · Georges Merx and Ronald J. NormanSlide 1 Chapter 1 Introduction to Java in the Context of Software Engineering.
Discussions for oneM2M Semantics Standardization Group Name: WG5 Source: InterDigital Communications Meeting Date: Agenda Item: WI-0005 ASN/MN-CSE.
Software Requirements Engineering CSE 305 Lecture-2.
An Introduction to Design Patterns. Introduction Promote reuse. Use the experiences of software developers. A shared library/lingo used by developers.
Certification and Accreditation CS Phase-1: Definition Atif Sultanuddin Raja Chawat Raja Chawat.
1 MFI-5: Metamodel for Process models registration HE Keqing, WANG Chong State Key Lab. Of Software Engineering, Wuhan University
METACASE. WHAT THIS PRESENTATION IS ABOUT  What’s META MODELING?  What’s METACASE?  METAEDIT+ 5.1 EVALUTION PROGRAM  Diagram and its kinds.
Zurich, March 2010 SEMAT Language Track. Zurich, March 2010 Language track proposal  General introduction  Each participant may provide.
Lecture 11 Managing Project Execution. Project Execution The phase of a project in which work towards direct achievement of the project’s objectives and.
Confidential 111 Financial Industry Business Ontology (FIBO) [FIBO– Business Entities] Understanding the Business Conceptual Ontology For FIBO-Business.
FFMII Introduction Juha Tiihonen Refer to FFMII Specification for details and explanations 1.
Definition of a taxonomy “System for naming and organizing things into groups that share similar characteristics” Taxonomy Architectures Applications.
Lecture 7: Requirements Engineering
1 Systems Analysis and Design in a Changing World, Thursday, January 18, 2007.
1 Introduction to Software Engineering Lecture 1.
Unified Modeling Language* Keng Siau University of Nebraska-Lincoln *Adapted from “Software Architecture and the UML” by Grady Booch.
UML Use Case Diagramming Guidelines. What is UML? The Unified Modeling Language (UML) is a standard language for specifying, visualizing, constructing,
L6-S1 UML Overview 2003 SJSU -- CmpE Advanced Object-Oriented Analysis & Design Dr. M.E. Fayad, Professor Computer Engineering Department, Room #283I College.
1 What is OO Design? OO Design is a process of invention, where developers create the abstractions necessary to meet the system’s requirements OO Design.
Systems Analysis and Design in a Changing World, Fourth Edition
Search Engine Optimization © HiTech Institute. All rights reserved. Slide 1 What is Solution Assessment & Validation?
University of Toronto at Scarborough © Kersti Wain-Bantin CSCC40 systems analysis 1 what is systems analysis? preparation of the system’s requirements/definition,
Software Design Process
27/3/2008 1/16 A FRAMEWORK FOR REQUIREMENTS ENGINEERING PROCESS DEVELOPMENT (FRERE) Dr. Li Jiang School of Computer Science The.
©B. Henderson-Sellers, Underpinning a Method Engineering Framework with a Powertype-based Metamodel – the FAME Project 3 rd AgentLink III Technical.
Distributed Accounting Working Group (DAWG) Distributed Accounting Models Research Group Monday, 22 July 2002 Tuesday, 23 July 2002 Edinburgh, Scotland.
Winter 2011SEG Chapter 11 Chapter 1 (Part 1) Review from previous courses Subject 1: The Software Development Process.
1 The Requirements Problem Chapter 1. 2 Standish Group Research Research paper at:  php (1994)
Requirement engineering & Requirement tasks/Management. 1Prepared By:Jay A.Dave.
WonderWeb. Ontology Infrastructure for the Semantic Web. IST Project Review Meeting, 11 th March, WP2: Tools Raphael Volz Universität.
Software Engineering Lecture 10: System Engineering.
5. 2Object-Oriented Analysis and Design with the Unified Process Objectives  Describe the activities of the requirements discipline  Describe the difference.
RUP RATIONAL UNIFIED PROCESS Behnam Akbari 06 Oct
Building Systems for Today’s Dynamic Networked Environments A Methodology for Building Sustainable Enterprises in Dynamic Environments through knowledge.
Architecture Ecosystem SIG March 2010 Update Jacksonville FL.
International Workshop 28 Jan – 2 Feb 2011 Phoenix, AZ, USA Modeling Standards Activity Team Model-based Systems Engineering (MBSE) Initiative Roger Burkhart.
OSLC PLM Reference model February Summary of the OSLC PLM Reference Model V0.2 February 22 nd 2011 Gray Bachelor Mike Loeffler OSLC PLM Workgroup.
Lisbon, 30 th March 2016 Gianluca Luraschi Gonçalo Cadete “Towards a Methodology for Building.
The Enhanced Entity- Relationship (EER) Model
Lecture 9- Design Concepts and Principles
Today in OOAD Today in Lab Review EU-Lease Assignment (Vision)
Seminar 1 Design of Informatics Systems
Rafael Almeida, Inês Percheiro, César Pardo, Miguel Mira da Silva
Lecture 9- Design Concepts and Principles
Presentation transcript:

1 ©B. Henderson-Sellers SEMAT 2010 SEMAT – Definitions Track March 17, 2010 Chair: Brian Henderson-Sellers

2 ©B. Henderson-Sellers SEMAT 2010 Overview 1 st The role of definitions in SEMAT 2 nd Contributions from SEMAT participants’ Position Statements

3 ©B. Henderson-Sellers SEMAT 2010 SEMAT Vision revisited Method or Process Model Metamodel Process Static aspects Dynamic aspects As enacted by real people on a specific project As documented Kernel language usage e.g. “Method” or “Process Model” composed of universals, practices, patterns etc. Kernel Language (rules) Process =method enactment Static aspects Dynamic aspects As enacted by real people on a specific project As documented for widespread usage As standardized

4 ©B. Henderson-Sellers SEMAT 2010 Let us start with an example Assume we have agreed upon this text as a definition: A team is a group of named people who interact with each other

5 ©B. Henderson-Sellers SEMAT 2010 What is a SEMAT definition? Team My team (Brian, Cesar, Atif) Class Its definition Thing Object x x x Atif Cesar Brian As a Venn diagram Organizational Grouping Team Object Thing Its definition Class Team both class & object Relationships are is-instance-of = set membership

6 ©B. Henderson-Sellers SEMAT 2010 Using OO modelling, can replace by Team My team (Brian, Cesar, Atif) Organizational Grouping No longer a class but a powertype pattern Class + Object Object Relationship is both is-instance-of and generalization Relationship is is-instance-of = set membership

7 ©B. Henderson-Sellers SEMAT 2010 Expanding My team (Brian, Cesar, Atif) Organizational Grouping GroupMemberNames Organizational Grouping Kind Intra-Action: Boolean Relationship is is-instance-of Relationship is generalization Intra-Action = YES GroupMemberNames Team Relationship is classification

8 ©B. Henderson-Sellers SEMAT 2010 More mathematical representation Organizational GroupingKind class x x x Partnership Company Team Organizational GroupingKind Team x x x x x x x x x x x x x Partnership Company Team Organizational Grouping class TeamCompany Organizational Grouping x x My team

9 ©B. Henderson-Sellers SEMAT 2010 Strictly, in mathematics A power set P(S) or 2 S is the set of all subsets of S What we call a powertype is only a subset of P(S) and is called a family of sets over S

10 ©B. Henderson-Sellers SEMAT 2010 Superimposing SEMAT vision Method or Process Model Metamodel Process Kernel language usage Kernel Language (rules) Process =method enactment My team (Brian, Cesar, Atif) Organizational Grouping GroupMemberNames Organizational GroupingKind Intra-Action Intra-Action=YES GroupMemberNames Team

11 ©B. Henderson-Sellers SEMAT 2010 This is similar to ISO architecture Language/rules domain Method/usage domain Endeavour Domain methodologiesassessmentqualitytools Kernel language

12 ©B. Henderson-Sellers SEMAT 2010 Our original example text A team is a group of named people who interact with each other OrganizationalGroupingKind OrganizationalGrouping

13 ©B. Henderson-Sellers SEMAT 2010 Contributions from Position Statements Definition of “software engineering” problematical Rough draft fast – refine iteratively over time Focus on Basics – avoid methodology wars – several position statements expressed caution Several address teams, team structures and other people issues Several talk of method “components” (or similar name) and SME (e.g. Firesmith, Spence, Humphrey, Fujitsu)

14 ©B. Henderson-Sellers SEMAT 2010 More contributions Several talk of how to measure success Is project management in scope? (Page-Jones argues against; others argue for) Inclusion of user interface (Constantine) Several mention taxonomy (Page-Jones), metamodels and ontologies (Firesmith, Bezivin, Henderson-Sellers) No agreed terminology (Spence notes widespread multiple meanings of “release” in industry)

15 ©B. Henderson-Sellers SEMAT 2010 How to proceed in the future? Identify what concepts require an SE definition (work with Universals Track) Agree on all these definitions in words including its name (seek overall consistent terminology but allow well-documented synonyms) Model them formally – link to kernel language possibilities include ontologies, metamodels, formal languages like VDM, category theory etc. Kernel language domain concepts can be partially validated w.r.t. method domain ones

16 ©B. Henderson-Sellers SEMAT 2010 Last look at original example text A team is a group of named people who interact with each other OrganizationalGroupingKind OrganizationalGrouping The challenge (at least to me) is to maintain focus on one specific domain and not accidentally merge two

17 ©B. Henderson-Sellers SEMAT 2010 How to Proceed Today? Agree on an overall architecture esp. w.r.t. links to Kernel Language Track and Universals Track Ensure Track proposals are flexible enough to align with Theory Track deliberations How to support Assessment Track Discuss sources of definitions Identify high level groupings of definitions to allocate to Track subgroups Identify Definition Track members willing to research likely contentious definitions