DOC PREVIEW
USC CSCI 599 - Week11_a

This preview shows page 1-2-3-27-28-29 out of 29 pages.

Save
View full document
View full document
Premium Document
Do you want full access? Go Premium and unlock all 29 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 29 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 29 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 29 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 29 pages.
Access to all documents
Download any document
Ad free experience
View full document
Premium Document
Do you want full access? Go Premium and unlock all 29 pages.
Access to all documents
Download any document
Ad free experience
Premium Document
Do you want full access? Go Premium and unlock all 29 pages.
Access to all documents
Download any document
Ad free experience

Unformatted text preview:

A Cooperative Approach to Support Software Deployment using the Software DockIntroductionTraditional Software Deployment MethodsRequirements of solutions for software deploymentSoftware Deployment Life CycleSoftware Dock (Overview)Software Dock ArchitectureSoftware Dock Architecture (Cont’d)Slide 9Slide 10Slide 11Slide 12Software Dock : Design IssuesSlide 14Slide 15Slide 16Slide 17Slide 18Slide 19Slide 20Slide 21Slide 22Related WorkCurrent StatusFuture WorkConclusionStrengths of the paperWeaknesses of the paperRelevance to Embedded SystemsA Cooperative Approach to Support Software Deployment using the Software Dock Dennis Heimbigner Richard S. Hall Alexander L. WolfSoftware Engineering Research LaboratoryUniversity of ColoradoIntroductionWhat is Software Deployment? The delivery, assembly and maintenance of a particular version of a software system at a site.In simple words it is the process that covers post-developmentactivities like configuration, release, installation, updating, adapting,reconfiguration and un-installation.Traditional Software Deployment MethodsThe foot and hand model: Run around on foot and install software by hand. - Only viable for small client base. - Expensive for the companies.The self-service model: The end users install the software themselves. - Scales well. - Low costs for the company. - Becomes difficult as the complexity of installation and configuration increases.Requirements of solutions for software deploymentIncremental updatesVersioningAutomatic installation and configurationCentralized InventoryDecentralized ControlSecurityScalabilitySupport for heterogeneous environmentsLive UpdatesLicensingSoftware Deployment Life CycleThe Software Deployment Life Cycle is an evolving collection of processes. These processes can either be performed on the software producer side or the customer side.Producer-side processesReleaseRetireCustomer-side processesInstallActivateDeactivateReconfigureUpdateAdaptRemoveSoftware Dock (Overview)It addresses most of the requirements cited earlier.It is a system of loosely coupled, cooperating, distributed components.It provides support for the producers by providing the release dock which acts as a central repository. In the release dock a standard semantic schema is used to specify deployment requirements of the software systems.At the customer end a field dock component provides an interface to the customer’s resources and deployed systems.Agents in the Software Dock travel from the release dock to the field dock in order to perform specific deployment tasks through the interface.A wide area event systems connects release docks to field docks for asynchronous, bidirectional activity.Software Dock ArchitectureSoftware Dock Architecture (Cont’d)Key ComponentsRelease DockField DockAgentsWide Area SystemSoftware Dock Architecture (Cont’d)Key ComponentsRelease Dock- It is a server at the producer side which acts as a release repository providing a web-based release mechanism.- Each software release is described by a standard deployment schema.- It provides programmatic interface for the agents to access its services and content.- It generates events when changes occur to the software releases managed by it.Field DockAgentsWide-Area Event ServiceSoftware Dock Architecture (Cont’d)Key ComponentsRelease DockField Dock - It is a server residing at the customer side which provides an interface to the customer, providing information about the resources and configuration of the system.- It provides customer side information, which is critical in any deployment process, in the form of a standardized and hierarchical registry. - Any changes in the registry generates an event that the agents receive to perform subsequent tasks.AgentsWide Area SystemSoftware Dock Architecture (Cont’d)Key ComponentsRelease DockField DockAgents- They do all the software deployment work.- There are different agents to perform software deployment processes like installation, update, adapt, reconfigure, and remove.- Each of these agents does its assigned task based upon the system information that it is provided through the interface at the field dock.Wide Area SystemSoftware Dock Architecture (Cont’d)Key ComponentsRelease DockField DockAgentsWide Area System- It provides a means of connectivity between producers and customers for push style capability.- Agents subscribe for events from the release docks using the wide-area event system.- Direct communication over the Internet and communication through events in the wide-area event system combined provide an opportunity to the producer and the customer to cooperate for deployment support.Software Dock : Design IssuesDeployable Software Description (DSD) format - It was developed to facilitate the creation of generic deployment process definitions.- It provides a standard schema to describe a software system family.- DSD family description is divided into multiple sections like identification, imported and system properties, property composition, assertions, dependencies, artifacts, interfaces, notifications, services, and activities.- Some of these sections can be directly associated with the five classes of semantic information that have to be provided by any software system model, namely Configuration, Assertions, Dependencies, Artifacts and Activities.Software Dock : Design IssuesDSD ExamplesProperty { Name = “Online Help” Type = “Boolean” Description = “Include online help.” … } Assertion { Condition = “($OS$ == ‘Solaris’) || ($OS$ == ‘Win95’)” Description = “Test for supported operating system.” … } Artifacts {Artifact {Guard = “($OS$ == ‘Solaris’)”SourceName = “help.html”Source = “/proj/doc”DestinationName = “help.html”Destination = “doc”Mutable = falseSignature=“3b8902d3410ec832”Type = “Documentation” … } Artifact {Guard = “($OS$ == ‘Win95’)”SourceName = “help.hlp” Source = “/proj/doc”DestinationName = “help.hlp”Destination = “doc”Mutable = falseSignature = “9283cd2378102f1a3b12ee”Type = “Documentation”…}}Software Dock : Design IssuesSoftware Dock Processes- Agents define all the software deployment processes. They are the active components of the Software Dock.- Software Dock framework


View Full Document

USC CSCI 599 - Week11_a

Documents in this Course
Week8_1

Week8_1

22 pages

Week2_b

Week2_b

10 pages

LECT6BW

LECT6BW

20 pages

LECT6BW

LECT6BW

20 pages

5

5

44 pages

12

12

15 pages

16

16

20 pages

Nima

Nima

8 pages

Week1

Week1

38 pages

Week11_c

Week11_c

30 pages

afsin

afsin

5 pages

October5b

October5b

43 pages

Week11_2

Week11_2

20 pages

final

final

2 pages

c-4

c-4

12 pages

0420

0420

3 pages

Week9_b

Week9_b

20 pages

S7Kriegel

S7Kriegel

21 pages

Week4_2

Week4_2

16 pages

sandpres

sandpres

21 pages

Week6_1

Week6_1

20 pages

4

4

33 pages

Week10_c

Week10_c

13 pages

fft

fft

18 pages

LECT7BW

LECT7BW

19 pages

24

24

15 pages

14

14

35 pages

Week9_c

Week9_c

24 pages

Week11_67

Week11_67

22 pages

Week1

Week1

37 pages

LECT3BW

LECT3BW

28 pages

Week8_c2

Week8_c2

19 pages

Week5_1

Week5_1

19 pages

LECT5BW

LECT5BW

24 pages

Week10_b

Week10_b

16 pages

Week11_1

Week11_1

43 pages

Week7_2

Week7_2

15 pages

Week5_b

Week5_b

19 pages

LECT14BW

LECT14BW

24 pages

T7kriegel

T7kriegel

21 pages

0413

0413

2 pages

3

3

23 pages

C2-TSE

C2-TSE

16 pages

10_19_99

10_19_99

12 pages

s1and2-v2

s1and2-v2

37 pages

Week10_3

Week10_3

23 pages

jalal

jalal

6 pages

1

1

25 pages

T3Querys

T3Querys

47 pages

CS17

CS17

15 pages

porkaew

porkaew

20 pages

LECT4BW

LECT4BW

21 pages

Week10_1

Week10_1

25 pages

wavelet

wavelet

17 pages

October5a

October5a

22 pages

p289-korn

p289-korn

12 pages

2

2

33 pages

rose

rose

36 pages

9_7_99

9_7_99

18 pages

Week10_2

Week10_2

28 pages

Week7_3

Week7_3

37 pages

Load more
Download Week11_a
Our administrator received your request to download this document. We will send you the file to your email shortly.
Loading Unlocking...
Login

Join to view Week11_a and access 3M+ class-specific study document.

or
We will never post anything without your permission.
Don't have an account?
Sign Up

Join to view Week11_a 2 2 and access 3M+ class-specific study document.

or

By creating an account you agree to our Privacy Policy and Terms Of Use

Already a member?