Slide 1 Copyright © 2003 Encapsule Systems, Inc. Hyperworx Platform Brief Modeling and deploying...

Copyright © 2003 Encapsule Systems, Inc. Slide 1

Hyperworx Platform Brief

Modeling and deploying component software services

with the Hyperworx™ platform

2003 MESDA Annual ConferenceNovember 14, Portland Maine


Introduction

What do we really need from software?

Software production today Introduction to the Hyperworx

platform Hyperworx Demo Questions & Answers


Big Picture: What Do We Need?

A better way to capture requirements

A consistent design methodology Flexible implementation strategy Better code-reuse mechanisms Isolation from changing

requirements Much better reliability and security


Today: Programming Languages

Procedural languages: Pseudo Object Oriented languages: Object Oriented languages:

Different languages for different problems.


Today: The Platform Wars

Microsoft Windows®

Commercial UNIX distributions Linux distributions

Platform choice driven by application availability and

cost.


Today: Code Re-Use

Shared libraries Component technologies Web services Dynamic language modules

Extensive hand integration required.


Today: Tools & Methodologies

Integrated development environments

Each has strengths & weaknesses.No compelling advantages.

Development methodologies

Need to be enforced by tools.


Emerging: Software Modeling

IBM/Rational Unified Modeling Language (UML) de facto industry

standard

$$$ + Very Complicated

Not worth it for small projects.

“Runable” UML is the Holy Grail.


Pause: Better Objects?

UML 2.0 specification just ratified

UML closely coupled to OOP

Adoption continues to be low…

Is Object Oriented Programming really the best approach for designing

systems?


Perspective: Objects & Systems

Objects: Excellent way to describe small

subsystems Production applications have 100’s,

1000’s of objects

Systems: Complex, state-machine-actuated

choreography of different objects

OOP itself is poorly suited for describing this intricate dance.


Perspective: Systems

Systems are best described in terms of:

State machines Data flow networks

Describing systems in OOP hard!


Perspective: Hardware Design

Proven methodology Low defect rate High investment in design tools High investment in model libraries Consider hardware engineering:

Intel 64-bit Itanium® 2 CPU contains

410 million transistors…


Perspective: Software Devices

Can we adapt thehardware designprocess to theproduction of componentsoftware systems?

Suppose we say that an object is analogous to a chip?


Aside: How Humans Think

Our brains are good at: Patterns Relationships

Our brains are bad at: State machines Parallel processing


The Hyperworx Platform

Adapts high-level hardware design metaphor to component software

Automates the tasks our brains can’t easily handle

Leverages our innate abilityto recognize patterns


Hyperworx Constituencies

Non-technical end-users

Software architects

Software implementers

Content / media producers


Conceptual Diagram

Operating System Platform (e.g. Microsoft Windows, Linux, Mac OSX…)

Hardware Platform (e.g. Intel, AMD, or IBM… CPU-based server or workstation)

System InputsUseful process + methodology

for preparing inputs for the machinery

System OutputsUseful improvement of current

software application composition methodologies

MechanismNon-obvious machinery for

manufacturing software applications

XML-encoded Hyperworx CSDL-format specification files

Platform/OS-native binary-format Hyperworx plug-in database (Hyperworx HyperPack modules)

Platform/OS-native binary-format Hyperworx software application

Platform/OS-native custom software application runtime memory image


Recombinant Modules™

Module

Outer context sink pins

Outer context source pins

Socket

Outer context

Module

Module

SocketSocket

SocketSocket

Inner context

Module

ProcessorProcessor

ProcessorProcessor

Inner context


Module Composition

Module

Processor

Processor

Processor

Socket

Socket

Processor

Socket


Simple Calculator Demo


Hyperworx Applications

Custom software generators Control and monitoring systems Distributed application infrastructure Web services integration /

deployment Media and signal processing Scientific applications Modularized SDK development


Hyperworx Packaging Options

Reduced feature graphical UI

Local service server

Remote service server

Full-featured development environment


Simple Website Generator Demo


Hyperworx Status

Core functionality complete

Work continues on user interface and example model kits

Reference customer beta site testing expected early 2004


Questions & Answers


Further Information Business and investor inquiries:

Fred Kinch, Acting CEO(978) 392-8934 • [email protected]

Technical & beta program inquiries:

Chris Russell, Founder & Software Architect(207) 846-7773 • [email protected]

Encapsule Systems, Inc.Yarmouth, Maine USA 04096

http://encapsule.com

Slide 1 Copyright © 2003 Encapsule Systems, Inc. Hyperworx Platform Brief Modeling and deploying...

Documents

Transcript of Slide 1 Copyright © 2003 Encapsule Systems, Inc. Hyperworx Platform Brief Modeling and deploying...