27 June 2015 Software Architecture John Cheesman Manager, Product Architecture Application Development Division www.cool.sterling.com.

Slides:



Advertisements
Similar presentations
Connected Health Framework
Advertisements

CASE tools Upper CASE tools: support for the analysis and design Lower CASE tools: support for construction and maintenance 1980s… Nowadays… Integrated.
1 Mind Visual Diff An architecture comparison tool December 16 th, 2014 – v0.2.2 Seyvoz Stephane Assystem.
ARCH-05 Application Prophecy UML 101 Peter Varhol Principal Product Manager.
CS487 Software Engineering Omar Aldawud
Filling the Gap Between System Design & Performance Verification Rafik HENIA, Laurent RIOUX, Nicolas SORDON Thales Research & Technology.
Formal Techniques in Software Engineering Universiteit AntwerpenIntroduction 1.1 Formal Techniques in Software Engineering 3de BAC Informatica Chapter.
Who am I Gianluca Correndo PhD student (end of PhD) Work in the group of medical informatics (Paolo Terenziani) PhD thesis on contextualization techniques.
© 2004 Visible Systems Corporation. All rights reserved. 1 (800) 6VISIBLE Holistic View of the Enterprise Business Development Operations.
Enterprise development reference architecture (EDRA) -Deepti Seelamsetti.
Component Patterns – Architecture and Applications with EJB copyright © 2001, MATHEMA AG Component Patterns Architecture and Applications with EJB JavaForum.
Amit, Keyur, Sabhay and Saleh Model Driven Architecture in the Enterprise.
IS6112 Application Modelling and Design Introduction.
1 © Wolfgang Pelz UML3 UML 3 Notations describe how to use reusable software. Package Component Deployment Node.
1 CS 426 Senior Projects Chapter 19: Interfaces and Components [Arlow & Neustadt 2005] February 28, 2008.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 5 Slide 1 Review 2.
Lecture 23: Software Architectures
1 Software Architecture: a Roadmap David Garlen Roshanak Roshandel Yulong Liu.
Demystifying Architectural Styles Nikunj Mehta 3/11/02Demystifying Architectural Styles2 Architectural Styles Characterize –Structure, i.e. external.
Page 1, July 3, 2015 CBSE – graduate course Component-Based Software Engineering Building reliable component-based systems Overview
Planning for Middleware Rose Gamble Leigh Davis Jamie Payton University of Tulsa.
Reuse Basic concepts. Rationale for reuse  Save calendar time  Save person hours  Reduce process risk  Increased quality  Standards compliance.
© 2006 IBM Corporation SOA on your terms and our expertise Discovering the Value of SOA SOA In Action SOA & End-2-End Business Driven Development using.
Software Product Line Architectures (SPLA) Nipun Shah
Copyright © WebGiro AB, All rights reserved. E-Commerce Integration Meta-Framework Andrzej Bialecki Chief System Architect TM The.
CONNECT EVERYTHING. ACHIEVE ANYTHING. ™ Top Ten Enterprise Service Bus (ESB) Myths Gordon Van Huizen CTO, Sonic Software March 17, 2005.
©Ian Sommerville 2004Software Engineering, 7th edition. Chapter 18 Slide 1 Software Reuse 2.
Praxis Softek Solutions Statement Of Qualification – J2EE.
February Semantion Privately owned, founded in 2000 First commercial implementation of OASIS ebXML Registry and Repository.
Introduction to the Enterprise Library. Sounds familiar? Writing a component to encapsulate data access Building a component that allows you to log errors.
Presenter - Donn Felker.  Senior Consultant for Microsoft Gold Certified Partner- Statêra.  8 years of experience in developing and architecting enterprise.
IEEM 5352 E-Enterprise Integration
Object Thinking. Alan Dean, Senior Technologist
© 2013 Visible Systems Corporation. All rights reserved. 1 (800) 6VISIBLE Achievement of an Integrated Applications Environment Enterprise.
CBD Papers Alexandre Alvaro. Lessons Learned through Six Years of Component-based Development Six years of component-based application development Using.
Guidelines for Component Reuse in Service Management Vincent P. Wade Department of Computer Science Trinity College Dublin Ireland
Test Driven Development Arrange, Act, Assert… Awesome Jason Offutt Software Engineer Central Christian Church
Slide 1 Standards Harmonization Through Semantics Unification Joe Zhou Xtensible Solutions Fran Clark Arpeggio Technology, LLC Progress Software Denver,
1 A Model-Driven Approach For Information System Migration Raymonde Le Delliou 1, Nicolas Ploquin 2, Mariano Belaunde 3, Reda Bendraou 4, Louis Féraud.
1 5 Nov 2002 Risto Pohjonen, Juha-Pekka Tolvanen MetaCase Consulting AUTOMATED PRODUCTION OF FAMILY MEMBERS: LESSONS LEARNED.
1 Planning for Reuse (based on some ideas currently being discussed in LHCb ) m Obstacles to reuse m Process for reuse m Project organisation for reuse.
INRIA - LaBRICharles Consel Jan-06 1 Domain-Specific Software Engineering Charles Consel Phoenix Research Group LaBRI /INRIA-Futurs January 2006.
Part VII: Design Continuous
Component Based Software Engineering Master of Software Engineering + Master of Information Technology 2010/2011 Conf.dr.ing. Ioana ora
Page 1, December 8, 2015 CBSE – graduate course Component-Based Software Engineering Building reliable component-based systems Overview
Software Engineering Emphasis for Engineering Computing Courses William Hankley Computing & Information Sciences Kansas State University.
OOPSLA workshop on Domain-Specific Visual Languages 1 Juha-Pekka Tolvanen, Steven Kelly, Jeff Gray, Kalle Lyytinen.
Chapter 19: Interfaces and Components [Arlow and Neustadt, 2005] University of Nevada, Reno Department of Computer Science & Engineering.
25 April Unified Cryptologic Architecture: A Framework for a Service Based Architecture Unified Cryptologic Architecture: A Framework for a Service.
XASTRO-2 Presentation CCSDS SAWG th November 2004.
Component Patterns – Architecture and Applications with EJB copyright © 2001, MATHEMA AG Component Patterns Architecture and Applications with EJB Markus.
Lecture 21: Component-Based Software Engineering
ARCH-06 Redesign & Harvest Mike Ormerod - Architect Christian Stiller - Senior Consultant Applied Technology Group.
1 4th of October, 2006 © ATHENA Consortium 2006 B5 EADS CCR piloting Nicolas Figay, EADS Flora Robin, EADS ATHENA Intermediate Review October 2006.
Lecture 2 Intro. To Software Engineering and Object-Oriented Programming (2/2)
B usiness- C entric M ethodology For Enterprise Agility & Interoperability Lubash Pyramid Challenges Today’s Approach Doctrine Operations Information Architecture.
Developing an IDM Information Delivery Manual Part 1. Industry Workgroup Training, Creating IDMs Alliance NA 2010 Dianne Davis, NA-IDM Coordinator Jan.
Enterprise Library 3.0 Memi Lavi Solution Architect Microsoft Consulting Services Guy Burstein Senior Consultant Advantech – Microsoft Division.
Component Based Software Engineering Master of Software Engineering + Master of Information Technology 2010/2011 Conf.dr.ing. Ioana ora
Integrating MBSE into a Multi-Disciplinary Engineering Environment A Software Engineering Perspective Mark Hoffman 20 June 2011 Copyright © 2011 by Lockheed.
Chapter 13 Logical Architecture.
Chapter 19: Interfaces and Components
Delivering Solutions to Business Needs
Software Reuse Objectives
Chapter 13 Logical Architecture.
Cost Xpert Group Copyright © 2001, Marotz, Inc..
Chapter 19: Interfaces and Components
Chapter 19: Interfaces and Components
Interfaces and Components
Chapter 19: Interfaces and Components
Presentation transcript:

27 June 2015 Software Architecture John Cheesman Manager, Product Architecture Application Development Division

 Sterling Software Topics Sterling Software ADG & CBD Industry / Partners Application development approach Feedback / Discussion

 Sterling Software Sterling Software ADG & CBD Application Development Group –Model-Based Toolsets, 100% code generation –Rigour, Traceability, Consistency –Enterprise Application Market –“CASE” WorldWide CBD Customer Advisory Board –80+ members, 6-monthly meetings, monthly telecons –Component Specification Standard –Incorporate best practice into the tools and method –Customers doing CBD since 1995

 Sterling Software Industry / Partners UML –partners in UML 1.0 and 1.1 Microsoft Repository –joint Engine and Information model design with Microsoft NIST –$1.6 million US grant for CBD research and application –Patterns, Frameworks, Component Specification & Architectures Catalysis –worked with D’Souza and Wills to apply concepts –Yes, we have bought the book!

 Sterling Software Application Development Approach Assembly from heterogeneous components Application (legacy) Integration Business Models -> Binaries Frameworks: generation toolsets manifest application architectures; applications “customise” Generated Framework Application Runtime Application Development ToolSet generate Application Model Development time

 Sterling Software Application Development Approach Technology-neutral component modeling & specification architecture (COOL:Spex) CBD Outside, IE/OO/(CBD) Inside Layered Architectures

 Sterling Software Feedback / Discussion Standards (CBD96). As-Is often dominates –new roads in London Organisational, Cultural Issues –project funding/management, internal champions Keep it Simple –Messages take a long time to arrive –Distortion en-route Specification vs Implementation –Components Outside, Anything inside –Don’t need an OOP –Care with model semantics (e.g. subtyping vs subclassing) Business Rules - where are they ? Separate Business Process from Business Objects –variable vs stable Replace vs Reuse - dependency management