Preliminary analysis of presentations

Slides:



Advertisements
Similar presentations
1 Aspects of IEEE P1471 Viewpoints in Unified Modeling Language (UML) Manzur Ashraf, BRAC University Humayra Binte Ali, Dhaka University Md.Mahfuz Ashraf,
Advertisements

International Telecommunication Union © ITU-T Study Group 17 Integrated Application of URN Daniel Amyot University of Ottawa, Canada
System and Software Engineering Research 1 Motorola 2003 Integrated Application of MSC Clive Jervis Rapporteur Q15 Motorola UK Research Labs.
Language Specification using Metamodelling Joachim Fischer Humboldt University Berlin LAB Workshop Geneva
International Telecommunication Union © ITU-T Study Group 17 Use of ITU-T Formal Languages Amardeo Sarma NEC Europe Ltd.
Database System Concepts and Architecture
Three dimensions of formal languages Arve Meisingset Telenor R&D.
Based on Powerpoint slides by Gunter Mussbacher, Gregor v. Bochmann User Requirements Notation (URN) SEG3101 (Fall 2010)
Tool support for Distributed Object Technology
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Introduction To System Analysis and Design
1 SYSTEM and MODULE DESIGN Elements and Definitions.
Lecture 13 Revision IMS Systems Analysis and Design.
The Software Product Life Cycle. Views of the Software Product Life Cycle  Management  Software engineering  Engineering design  Architectural design.
Software Process Activities. Process activities Real software processes are inter-leaved sequences of technical, collaborative and managerial activities.
International Telecommunication Union ITU-T Study Group 17, Moscow, 30 March – 8 April 2005 New Recommendations on ODP Arve Meisingset Rapporteur Q15.
Basic Concepts The Unified Modeling Language (UML) SYSC System Analysis and Design.
Lesson 7 Guide for Software Design Description (SDD)
Workshop on Integrated Application of Formal Languages, Geneva J.Fischer Mappings, Use of MOF for Language Families Joachim Fischer Workshop on.
Enterprise Systems Architectures EGN 5621 Enterprise Systems Collaboration (Professional MSEM) Fall, 2012.
Information Systems Engineering. Lecture Outline Information Systems Architecture Information System Architecture components Information Engineering Phases.
CEN5011, Fall CEN5011 Software Engineering Dr. Yi Deng ECS359, (305)
FDT Foil no 1 On Methodology from Domain to System Descriptions by Rolv Bræk NTNU Workshop on Philosophy and Applicablitiy of Formal Languages Geneve 15.
Christoph F. Eick University of Houston Organization 1. What are Ontologies? 2. What are they good for? 3. Ontologies and.
Copyright SOLINET GmbH SDL & Requirements of Signalling Systems William H. Skelton SOLINET, Stuttgart.
ITU-T SDOs Amardeo Sarma Co-Chairman, ITU-T Study Group 17.
Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher(2009) with material from Amyot User Requirements Notation (URN)
UML Diagrams for Caradon developers Daniel DG Moth Core Development Group, Research Student University of Brighton, MSc Object Oriented Software Technology.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
International Telecommunication Union © ITU-T Study Group 17 Integrated Application of SDL Amardeo Sarma NEC Europe Ltd.
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
Slide no. 1  =====!"§!“!Nova§ ITU-T work on technical languages and general software issues Amardeo Sarma Chairman, ITU-T Study Group 10.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Class Diagrams. Terms and Concepts A class diagram is a diagram that shows a set of classes, interfaces, and collaborations and their relationships.
Yu, et al.’s “A Model-Driven Development Framework for Enterprise Web Services” In proceedings of the 10 th IEEE Intl Enterprise Distributed Object Computing.
A data flow approach to interoperability By Arve Meisingset.
Software Engineering Lecture 10: System Engineering.
2 Copyright © 2006, Oracle. All rights reserved. Defining Data Warehouse Concepts and Terminology.
1 Week 5 Software Engineering Fall Term 2015 Marymount University School of Business Administration Professor Suydam.
Introduction to UML.
An Overview of Requirements Engineering Tools and Methodologies*
Software Architecture
School of Business Administration
Software Process Activities.
Software Architecture
SDC – SDLC integration.
Herbert V. Bertine Lucent Technologies Amardeo Sarma NEC Europe Ltd.
Differents between Structured Analysis and UML
FORMAL SYSTEM DEVELOPMENT METHODOLOGIES
CHAPTER 2 CREATING AN ARCHITECTURAL DESIGN.
Copyright © 2011 Pearson Education, Inc. Publishing as Pearson Addison-Wesley Chapter 2 Database System Concepts and Architecture.
ITU languages for ODP - a personal view - I may be wrong!
Advanced Database Models
Chapter 2: Database System Concepts and Architecture
Systems Analysis and Design in a Changing World, 6th Edition
NTNU Dept of Telematics and SINTEF Telecom and Informatics, Norway
Design Model Like a Pyramid Component Level Design i n t e r f a c d s
Opening, purpose and summary of the framework
ITU-T Workshop 23 November 2002 on Use of Description Techniques
Analysis models and design models
Software Design Lecture : 15.
Software Design Lecture : 14.
Methodological dimensions
Introduction to Systems Analysis and Design Stefano Moshi Memorial University College System Analysis & Design BIT
Message Sequence Charts
Chapter 2 Database Environment Pearson Education © 2014.
Requirements Document
System architecture, Def.
Segments Introduction: slides minutes
Software Architecture
Presentation transcript:

Preliminary analysis of presentations Arve Meisingset Telenor R&D

Comments Categorisations of ASN.1, TTCN and UML are missing Core/Some Category Rick Core/Some   Rick Rele- vance Amardeo SDL   Clive MSC   Daniel URN   Bertram eODL       Enterprise viewpoint Information viewpoint Computational viewpoint Engineering viewpoint Technology viewpoint 15.04.2019

Open Distributed Processing Category Rick Core/Some   Rick Rele- vance Amardeo SDL   Clive MSC   Daniel URN   Bertram eODL       Enterprise viewpoint SDL MSC URN Information viewpoint Core? SDL Computational viewpoint Core SDL eODL Engineering viewpoint Core ? MSC URN(UCM) Technology viewpoint Some? 15.04.2019

Phases Summary Core/ Some URN Core URN eODL? Core MSC URN? eODL? Core Category Rick Rele- vance Summary Core/ Some   Amardeo SDL   Clive MSC   Daniel URN   Bertram eODL       Surveying Some URN Analysis Core MSC URN eODL? Overall design Core SDL MSC URN? eODL? Detailed design Core SDL MSC eODL Implementation Core SDL MSC Validation and testing Core SDL MSC URN Intro., train. and conv. Some URN Operation and use Some eODL? 15.04.2019

Scale of granularity ? ? Summary Core/Some SDL MSC URN Core MSC eODL Category Summary Core/Some   Rick Rele- vance Amardeo SDL   Clive MSC   Daniel URN   Bertram eODL       Module development Core ? MSC ? eODL System development Core? SDL MSC URN eODL System planning and organization Some? Interoperation plan. betw. organizat. SDL MSC Information society planning 15.04.2019

Media SDL MSC URN SDL? MSC? MSC Core SDL MSC eODL eODL Category Rick Rele- vance Amardeo Clive Daniel Bertram   SDL MSC URN eODL Alpha-gra. screens   Some?           Graphic screens   Some   SDL?         Reports   Some      MSC?       Databases   Some?           Telecom. lines   Some    MSC         Interoperation between processes   Core   SDL    MSC     eODL   15.04.2019

Application areas and Usages Category Rick Rele- vance Amardeo Clive Daniel Bertram   SDL MSC URN eODL Data oriented approach   Core?         eODL   Process oriented approach   Core   SDL    MSC   URN   eODL   End user help   ?           Application software development Core     SDL  MSC     URN   eODL   Application software management   Some?         eODL   Tool development   ?           15.04.2019

Language categories ? Summary Core/Some SDL MSC URN Core SDL MSC URN Category Summary Core/Some   Rick Rele- vance Amardeo SDL   Clive MSC   Daniel URN   Bertram       eODL Control flow Core SDL MSC URN Data flow Core ? MSC Precedence relations between data Transformations between data Some? ? Nesting of schemata Core? 15.04.2019

Structures and Implementations Category Summary Core/Some   Rick Rele- vance Amardeo SDL   Clive MSC   Daniel URN   Bertram       eODL Static structures Core? SDL URN eODL Behaviour Core SDL MSC URN(UCM) Abstract Some? SDL MSC URN eODL Detailed Core SDL MSC 15.04.2019

Schema types Summary Core/ Some Core eODL Core? eODL? SDL? eODL SDL Category Rick Rele- vance Summary Core/ Some   Amardeo SDL   Clive MSC   Daniel URN   Bertram       eODL Layout schema Contents schema Core External terminology schema Concept schema Internal terminology schema Distribution schema Some SDL eODL Physical schema Core? eODL? System schema SDL? eODL 15.04.2019

Levels and constraints Category Summary Core/Some   Rick Rele- vance Amardeo SDL   Clive MSC   Daniel URN   Bertram       eODL Instantiation language Core SDL eODL Type language Core SDL eODL Selection, projection and union 15.04.2019

Usage granularity Summary Core/Some SDL MSC URN SDL MSC URN eODL? SDL Category Summary Core/Some   Rick Rele- vance Amardeo SDL   Clive MSC   Daniel URN   Bertram       eODL Individual relative to task SDL MSC URN eODL? Individual to several tasks SDL MSC URN Office with collaborating individuals SDL MSC URN Organizations independ. of tasks URN Market segments with variations SDL MSC URN 15.04.2019

Usages: Closeness, intention, scenario and collaboration Category Rick Rele- vance   Amardeo SDL   Clive MSC   Daniel URN   Bertram       eODL Terminal users Core SDL ? ? Data users Core? Goals Core MSC? URN(GRL) eODL? Requirements Core SDL MSC URN Hands on use ? SDL Scenario language Core MSC URN(UCM) Translations between tiles ? ? Relations between tiles 15.04.2019

Summary Need more responses and validation. Some need for coordination of languages both use and mappings. The languages do not have focus on - technology - end user perspectives and use - management - data and media All the four points are essential to Telecom Operators. These conclusions may not be surprising. The Tile architecture seems to serve the role as an analysis tool, but needs better definitions and requirements, as concluded in the first workshop 15.04.2019