A Helpful Way to deal with Bolster Programming Sending Utilizing the Product Dock by R. Corridor, D. Heimbigner, A. Wolf.

Uploaded on:
Category: Home / Real Estate
Sachin Chouksey. Ebru Dincel. Layout. What is Software Deployment ? Programming Deployment ... Complete Installation strategy for programming framework on CD ROM ...
Slide 1

A Cooperative Approach to Support Software Deployment Using the Software Dock by R. Corridor, D. Heimbigner, A. Wolf Sachin Chouksey Ebru Dincel

Slide 2

Outline What is Software Deployment ? Programming Deployment Life Cycle Software Dock (Architecture) Deployable Software Description (DSD) Format Software Dock Processes Current, Related & Future Work. Wrap-up

Slide 3

Release Install Adapt Reconfigure Update Activate Deactivate Remove Retire What is Software Deployment?

Slide 4

Then Complete Installation method for programming framework on CD ROM Entire programming framework establishment Now Software makers and purchasers participating and arranging. "Upgrade" of Software Systems How is it changing ? This on account of high network

Slide 5

What do we require from sending advances ? Support for heterogeneity as far as stages and system situations. Semantic model to depict programming frameworks. Semantic model to depict target locales. Decentralized control for both programming makers and buyers.

Slide 6

Software Deployment Definitions Previously Installation of a product framework. Shortsighted & Incomplete perspective. At present An advancing accumulation of between related exercises. Programming organization life cycle.

Slide 7

Software Deployment Life Cycle Producer side Release Retire Consumer side Install Activate/Deactivate Reconfigure Update Adapt Remove

Slide 8

Software Dock Architecture Components Release Dock Field Dock Inter Dock Agents Event Service

Slide 9

Architecture: Release Dock Server dwelling at maker. Archive of programming frameworks. Electronic discharge instrument. Sexually transmitted disease. sending composition for every discharge. Operators perform arrangement process. Automatic interface for specialists. Creates occasions for changes made to a discharge. Specialists subscribe to occasions.

Slide 10

Architecture: Field Dock Server dwelling at buyer. Gives interface to shopper site. Site assets and arrangement (setting). Operators dock here and access interface. Institutionalized, various leveled data registry for a typical namespace.

Slide 11

Architecture: Agents Implement genuine usefulness. Just operator and programming framework depiction stacked onto buyer site from discharge dock. Specialist arranges framework for that objective site. Exact arrangement of comparing relics and different specialists then downloaded.

Slide 12

Architecture: Event Service Connectivity between programming makers and purchasers. Remote operators subscribe to occasions. Utilizes standard conventions over the web.

Slide 13

Architecture: Inter Dock Future usage. Support for "Manager" part. Head can determine action that ought to happen at a particular or set of locales. Worldwide perspective of shopper association. Convoluted arrangement situations addressable.

Slide 14

Where are We ? What is Software Deployment ? Programming Deployment Life Cycle Software Dock (Architecture) Deployable Software Description (DSD) Format Software Dock Processes Current, Related & Future Work Wrap-up

Slide 15

Schema of organization data System as accumulations and setups of properties Property { Name = " Online Help" Type = "Boolean" Description = "Incorporate online help." … .} Simple, non specific, various leveled method for portraying programming framework family/segment based improvement Critical bit of Software Dock Elements - Configuration -Assertions -Dependencies -Artifacts -Activities Deployable Software Description (DSD)

Slide 16

DSD: Configurations Relationships between programming curios. Assets gave by programming framework.

Slide 17

Consumer-side requirements for a fruitful sending. Declaration { Condition = "($OS$ = =\'Solaris\') || ($OS$ = =\'Win95\')" Description = "Test for bolstered working framework." … .} DSD: Assertions

Slide 18

DSD: Dependencies Consumer-side imperatives where a determination is conceivable if the requirement does not hold (e.g introducing subordinate subsystems).

Slide 19

Physical ancient rarities of the product framework. Ancient rarities { Guard = "($Online Help$ = genuine)" Artifact { Guard = "($OS$ = \'Solaris\')" SourceName ="help.html" Source = "/proj/doc" Destination = "doc" Mutable = false Signature = "a4ca443b" Type = "DOC" … } Artifact {… … } … .} DSD: Artifacts

Slide 20

DSD: Activities Any specific exercises outside of standard sending process.

Slide 21

Software Dock Processes Generic -Differential preparing Specific -Install (pull) -Update (pull/push, new DSD) -Reconfigure (pull, existing DSD) -Adapt (pull, implements consistency, existing DSD) -Remove (pull)

Slide 22

Related Work Configuration Management Tools (e.g. Adele, PCL,..) -no organization or diagram Schema based (e.g. OSD, AMS, ..) -not develop enough for computerization, unified Script based (e.g. GNU AutoConf,..) -not sufficiently rich, heuristics Recent utilities (e.g. InstallShield, netDeploy, ..) -not sufficiently rich for mechanization, better backing  Immature, fractional backing for arrangement exercises, and not institutionalized

Slide 23

Ongoing Work Current Java Prototype http://www.cs.colorado.edu/~serl -SIENA (occasion notice) -Voyager (IPC, versatile specialists) -pattern altering device (DSD altering, relic section) -dock station device (interface for sending process) Future -higher security (JVM 2.0) -remote operators and server -expanded DSD -organization strategies

Slide 24

Software Dock Advantages Decentralized through collaboration. Versatility because of centralization. Offbeat, bi-directional correspondence. Unification of depiction and procedure. Support for different sending forms. Advanced design administration. Support for multi-stage. Extensibility, dependability and institutionalization (outlines and components). Better execution results.

Slide 25

Issues in an Embedded Environment Security ("trusted" portable operators). Confirmation and approval. Asset compelled situations. Run-time reconfiguration, redesign, and down time. Stage changes (e.g. equipment). Constant insurances. Adaptation to internal failure, smooth corruption of administration.

View more...