Impact Analysis to Refactoring on the Current document Sony Corporation Toshiaki Kojima Mizuki Kanada.

Slides:



Advertisements
Similar presentations
Computer Systems & Architecture Lesson 2 4. Achieving Qualities.
Advertisements

What is proper format for the XDW document. In its first year, XDW has been exposed to feedback, and this public comment phase –to allow clarifications.
Applications in Registry Kevin Benson Paul Harrison
Universal Printer Description Format UPDF. UPDF Version 1.0 Agenda UPDF Overview –History –Design Last Call –Review changes –Approval or requirements.
Web Service Ahmed Gamal Ahmed Nile University Bioinformatics Group
Architecture Representation
Automating Bespoke Attack Ruei-Jiun Chapter 13. Outline Uses of bespoke automation ◦ Enumerating identifiers ◦ Harvesting data ◦ Web application fuzzing.
1. Introduction OASIS Reference Model for Service Oriented Architecture 2. ECF 4.0 Architecture 2.1 Core vs. Profiles 2.2 Major Design Elements 2.3.
1 Software Testing and Quality Assurance Lecture 12 - The Testing Perspective (Chapter 2, A Practical Guide to Testing Object-Oriented Software)
Design Creative Process of transferring the problem into a solution
Designing the system Conceptual design and technical design
XML Technologies and Applications Rajshekhar Sunderraman Department of Computer Science Georgia State University Atlanta, GA 30302
© 2005 Prentice Hall4-1 Stumpf and Teague Object-Oriented Systems Analysis and Design with UML.
SIM5102 Software Evaluation
OMNET++. Outline Introduction Overview The NED Language Simple Modules.
Introduction to the Enterprise Library. Sounds familiar? Writing a component to encapsulate data access Building a component that allows you to log errors.
1 © Talend 2014 Service Registry / WS-Policy Registry Training Slides 2014 Jan Bernhardt Zsolt Beothy-Elo
Effective C# 50 Specific Way to Improve Your C# Item 50 Scott68.Chang.
Updating and Improving the INTAMAP web service Madhu Rani 2012 Intern 1.
Metadata Harvesting The Hague, 13 & 14 January 2009 Julie Verleyen Scientific Coordinator, Europeana Office EuropeanaLocal Knowledge Sharing Workshop.
Interoperability Tests for IEC Scott Neumann November 12, 2009.
T Network Application Frameworks and XML Web Services and WSDL Sasu Tarkoma Based on slides by Pekka Nikander.
Resource Management and Accounting Working Group Working Group Scope and Components Progress made Current issues being worked Next steps Discussions involving.
Relating Testing to Quality –Timeliness of Testing –Quality Attributes Gauge by Testing –Roles Defining Test Discipline Activities Elaborating the Test.
THE GITB TESTING FRAMEWORK Jacques Durand, Fujitsu America | December 1, 2011 GITB |
CS 360 Lecture 3.  The software process is a structured set of activities required to develop a software system.  Fundamental Assumption:  Good software.
Introduction to MDA (Model Driven Architecture) CYT.
James Holladay, Mario Sweeney, Vu Tran. Web Services Presentation Web Services Theory James Holladay Tools – Visual Studio Vu Tran Tools – Net Beans Mario.
Testing Basics of Testing Presented by: Vijay.C.G – Glister Tech.
SOFTWARE DESIGN (SWD) Instructor: Dr. Hany H. Ammar
Basic Concepts Software Architecture. What is Software Architecture? Definition: – A software architecture is the set of principal design decisions about.
IRS XML Messaging Schemas 22-September Why are we talking about “Messaging Schemas”? IRS has a need to exchange data –Batch processing –Transaction.
General Comments from Sony Sony Corporation Toshiaki Kojima Mizuki Kanada.
(Business) Process Centric Exchanges
Approaching a Problem Where do we start? How do we proceed?
1 Schema Registries Steven Hughes, Lou Reich, Dan Crichton NASA 21 October 2015.
SE: CHAPTER 7 Writing The Program
Updates made to latest draft since Herndon Sony Corporation Toshiaki Kojima.
Control Systems Design Part: FS Slovak University of Technology Faculty of Material Science and Technology in Trnava 2007.
XASTRO-2 Overview Presentation CCSDS SAWG Athens Meeting 12 th April 2005.
Information Model for LMAP draft-ietf-lmap-information-model-02 and proposed changes for 03 IETF 91, Honolulu, November 2014 Trevor Burbridge, BT 1.
Human-readable SDD Content Debra Danielson CA. © 2005 Computer Associates International, Inc. (CA). All trademarks, trade names, services marks and logos.
1 Capturing Requirements As Use Cases To be discussed –Artifacts created in the requirements workflow –Workers participating in the requirements workflow.
FIMS Specification Group EBU-AMWA FIMS August 2011.
XML Grammar and Parser for WSOL Kruti Patel, Vladimir Tosic, Bernard Pagurek Network Management & Artificial Intelligence Lab Department of Systems & Computer.
1 UML Modeling of Spacecraft Onboard Instruments Takahiro Yamada, JAXA/ISAS April 2005.
FIMS Specification Group EBU-AMWA FIMS July 2011.
Conceptual design Tells the customer what the system will do Tells the customer what the system will do Answers: Answers: Where will the data come from?
Technical Support to SOA Governance E-Government Conference May 1-2, 2008 John Salasin, Ph.D. DARPA
ClearQuest XML Server with ClearCase Integration Northwest Rational User’s Group February 22, 2007 Frank Scholz Casey Stewart
Service Component Architecture (SCA) Policy TC … Face to Face Agenda – Jan 24,
Preface IIntroduction Objectives I-2 Course Overview I-3 1Oracle Application Development Framework Objectives 1-2 J2EE Platform 1-3 Benefits of the J2EE.
Updates made to latest draft since Herndon Sony Corporation Toshiaki Kojima.
Dialog Design I Basic Concepts of Dialog Design. Dialog Outline Evaluate User Problem Representations, Operations, Memory Aids Generate Dialog Diagram.
Meeting Structure EBU, Geneva 9am Tuesday 21 February pm Wednesday 22 February Rev3 EBU-AMWA FIMS February 2012.
CSS-SM Refactoring Proposal Scope –Allow inclusion of services or modifications to existing ones without having to reedit the entire CSS-SM book. Objectives.
Proposed Service Discovery Capability/Configuration Description EBU-AMWA FIMS.
An API for the Process Manager Component Meeting at Argonne June 5-6, 2003.
Fusion Design Overview Object Interaction Graph Visibility Graph Class Descriptions Inheritance Graphs Fusion: Design The overall goal of Design is to.
Copyright 2007, Information Builders. Slide 1 iWay Web Services and WebFOCUS Consumption Michael Florkowski Information Builders.
William H. Bowers – Specification Techniques Torres 17.
SwCDR (Peer) Review 1 UCB MAVEN Particles and Fields Flight Software Critical Design Review Peter R. Harvey.
Information Model for LMAP draft-ietf-lmap-information-model-02 (and beyond!) IETF Interim, Dublin, September 2014 Trevor Burbridge, BT 1.
1 © 2003, Cisco Systems, Inc. All rights reserved. DMTF and Cisco Profile overview/comparison August 17, 2005.
Enabling Grids for E-sciencE Agreement-based Workload and Resource Management Tiziana Ferrari, Elisabetta Ronchieri Mar 30-31, 2006.
I&C Lab Seminar Procedure for the Software Requirements Specification for Safety Critical Systems Seo Ryong Koo Korea Advanced Institute Science.
Web services, WSDL, SOAP and UDDI
Design Yaodong Bi.
Presentation transcript:

Impact Analysis to Refactoring on the Current document Sony Corporation Toshiaki Kojima Mizuki Kanada

Current Specification (Part1) Structure 1. Scope 2. Conformance Language 3. Reference Documents 4. Overview 5. High-Level Architectures 6. Media Service Management 6.1 Service Lifecycle 6.2 Job Management 7. Media Service Awareness 7.1. Service Registry 7.2 Service Description

Current Specification (Part1) Structure 8. Media Service Behavior 8.1 Common Service Behavior Operation Implementation pattern Input and Output Media Error and exception handling Failure Recovery Job Queue Job Execution Priority Events Notification Media Referencing Jobs Errors 8.2 Service Interface Overview Time Constraints Profiles

Current Specification (Part2) Structure Description of "Message (type)" Message –Types Parameters –Description –Type –Occurrence –Inclusion –Default Value –Service Description –Normative Requirements

Modified Specification (Part2) Structure Description of "Resource" and "Message" Resource –Resources –Data Types Messages –Parameters Description Type Occurrence Inclusion Default Value Service Description Normative Requirements Job Resource Capture Job Resource Capture Messages

Expected Changes to the Current Specification S01 Service Interface S011 Schema Design S0111 Base Schema S0112 Base Message S0113 Job & Queue Management S0114 Service Description Inquiry S012 Common Functions S0121 Command S0122 Errors S0123 Status S0124 Job/Queue Information S0125 Metadata S0126 Business Media Object(BMO) S0127 Time Constraints S0128 Profile S013 Atoms S014 Service Consumer Interface S02 Service Description S01 Service Interface S011 Schema Design S0111 Base Schema S012 Base Resources S0121 Resources S0122 Services S0123 Profiles and Atoms S0124 Queues S0125 Jobs S0126 Formats S0127 Business Media Objects S0128 Resource References S013 Base Data Type S0131 Attribute Groups S0132 Simple Types S0133 Complex Types S0134 Enumeration S0135 Control Type

Expected Changes to the Current Specification S01 Service Interface S011 Schema Design S0111 Base Schema S0112 Base Message S0113 Job & Queue Management S0114 Service Description Inquiry S012 Common Functions S0121 Command S0122 Errors S0123 Status S0124 Job/Queue Information S0125 Metadata S0126 Business Media Object(BMO) S0127 Time Constraints S0128 Profile S013 Atoms S014 Service Consumer Interface S02 Service Description S014 Base Messages and Faults S0141 QueryJoobRequeseType S0142 QueryJobResponseType S0143 MessageJobRequestType S0144 MessageJobResponseType S0145 MessageQueryRequestType S0146 MessageQueryResponseType S0147 QueryServiceDescriptionRequestType S0148 QueryServiceDescriptionResponseType S0149 FaultType S01410 AsyncEndPointType S015 ServiceConsumer Interfaces S02 Service Description

Expected Changes to the Current Specification S3 Capture Service S31 Capture Service Interface S311 Messages S32 Capture Service Description S33 Capture Service Configuration S34 Service Compliance S3 Capture Service S31 Capture Service Interface S311 Capture Resources S312 Capture Data Type S313 Capture Messages and Faults S32 Capture Service Description S33 Capture Service Configuration S34 Service Compliance Job Resource Capture Job Resource Capture Messages

Action Items on the Current Specification Fix the Data Model Propose a strawman schema based on the data model Review the strawman schema one by one –Occurrence –Inclusion –Meanings etc. Modify Part1 at least Operation Implementation pattern –Description of the new concept could be described in the Implementation Guideline Modify Part2 whole structure –Both Base and all Service documents Create Service Description based on the new structure Full Document Review