1 / 24

LHC Software Engineering Workshop

LHC Software Engineering Workshop. Joe Sventek 18-20 March 1998. 18 March 1998. Architecture. Expert. Why an architecture? Establish the domain of discourse Support the evolution of the system of applications Support use/reuse of artifacts Form the basis of framework development

wnguyen
Télécharger la présentation

LHC Software Engineering Workshop

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. LHC Software Engineering Workshop Joe Sventek 18-20 March 1998

  2. 18 March 1998 Architecture

  3. Expert Why an architecture? • Establish the domain of discourse • Support the evolution of the system of applications • Support use/reuse of artifacts • Form the basis of framework development • Functional versus other qualities?

  4. Healthcare Architecture Event Service Rule Agent Transaction Monitor Info Mgr Info Mgr Info Mgr Presentation UI InteractionModel MSA DM

  5. Monitoring Architecture WS Server WAN Derived Fabric Correlator Correlator Instrumentation Fabric Probes

  6. 18 March 1998 Components

  7. Component Structure  I/F1 I/F2 I/F3

  8. Component Structure • Aggregation versus Inheritance • Navigation around surface • “Potentially distributable” • DataFlow versus Objects + RPC

  9. 18 March 1998 Integration Technology

  10. CORBA ObjectAdapter Object IDLSpecification Client Skeleton Stubs ORB

  11. What this really means! Client Object Skeleton Stubs ObjectAdapter ORBRuntime ORBRuntime OperatingSystem OperatingSystem Factory Trader Locator

  12. Communication Mechanisms • CORBA - single definition language, multiple implementation languages • DCOM - multiple definition languages, “multiple” implementation languages • RMI - single definition language, single implementation language • Their object models are essentially isomorphic • Publish/subscribe? • OrbixTalk - integrated into CORBA • TIBCO ObjectBus - proprietary API

  13. 18 March 1998 Application Frameworks

  14. Framework Issues • Use IDL for defining the interfaces to potentially distributable components • Frameworks are not the same as class libraries • The framework is in control - it provides the main() of the application, calling user-provided code you have provided

  15. Framework Issues  I/F1 I/F2 I/F3 • In the healthcare example, the lines of code represented by the green area is 90% of the code! • Frameworks are domain-specific

  16. 18 March 1998 Domain Decomposition

  17. Domain Decomposition • What is a domain? • Define a glossary • Enumerate components and dependencies • Work through use cases • what is common • what is variable • Specify the architecture • standard functionality desired of all components • isolate areas needing innovation/variability Iterate

  18. 19 March 1998 Migration Process

  19. Comments on Migration Process • Really need management buy-in all the way down … • Incremental approach to “Nirvana” • Re-architecture usually only pays off in second and future iterations • Core team must be small, composed of technical “thought leaders” • Need a process when schedule pressures hit • Code walk-throughs are easier when you have computational support

  20. 19 March 1998 Centralized Expertise

  21. HP Experience with Centralized Teams • Must have a strong team leader to keep the architecture and artifacts moving forward • Core team must include customers • Requires frequent face-to-face meetings • Weekly status phone conferences • 6-month delivery cycle • Quarterly management reviews

  22. Requirements of IT • Licensing agreements for agreed-upon tools • Automated installation and license tracking • Support contracts on hardware • Training

  23. 20 March 1998 Planning

  24. Comments on Planning Discussion Delivery Date # of Resources Functionality You cannot optimize all three of these at the same time - fix twoand the third must float!

More Related