Autonomic software version management system, method and program product
Under the present invention a software version is used on a first operational level by a set (e.g., one or more) of users. As the software version is being used, its performance is automatically monitored based on predetermined monitoring criteria. Specifically, data relating to the performance of t...
Gespeichert in:
Hauptverfasser: | , , |
---|---|
Format: | Patent |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
container_end_page | |
---|---|
container_issue | |
container_start_page | |
container_title | |
container_volume | |
creator | MILLER BRENT ALAN RABINOVITZ DANIEL SCOTT RAGO PATRICIA A |
description | Under the present invention a software version is used on a first operational level by a set (e.g., one or more) of users. As the software version is being used, its performance is automatically monitored based on predetermined monitoring criteria. Specifically, data relating to the performance of the software version is gathered. Once gathered, the data is automatically analyzed to determine if the actual performance met an expected performance. Based on the analysis, a plan is developed and executed. In particular, if the actual performance failed to meet the expected performance, the software version (or components thereof) could be revised (e.g., via patches, fixes, etc.) to correct the defects, or even rolled back to a previous operational level. Conversely, if the actual performance met or exceeded the expected performance, the software version could be promoted to a next operational level. |
format | Patent |
fullrecord | <record><control><sourceid>epo_EVB</sourceid><recordid>TN_cdi_epo_espacenet_US2004261070A1</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>US2004261070A1</sourcerecordid><originalsourceid>FETCH-epo_espacenet_US2004261070A13</originalsourceid><addsrcrecordid>eNqNyr0KwkAMAOAuDqK-Q8BV4VpF5yJKd3Uu4S79AXM5Lqni24vgAzh9yzcvmnoyicKjB5XOXpgJnpR1lAiMEXtiigb6ViPeAJMNEgBjgJSlz8hfw-RtWcw6fCitfi6K9eV8OzVbStKSJvQUydr7tXJuXx1Kd3R1uftvfQDM6zXK</addsrcrecordid><sourcetype>Open Access Repository</sourcetype><iscdi>true</iscdi><recordtype>patent</recordtype></control><display><type>patent</type><title>Autonomic software version management system, method and program product</title><source>esp@cenet</source><creator>MILLER BRENT ALAN ; RABINOVITZ DANIEL SCOTT ; RAGO PATRICIA A</creator><creatorcontrib>MILLER BRENT ALAN ; RABINOVITZ DANIEL SCOTT ; RAGO PATRICIA A</creatorcontrib><description>Under the present invention a software version is used on a first operational level by a set (e.g., one or more) of users. As the software version is being used, its performance is automatically monitored based on predetermined monitoring criteria. Specifically, data relating to the performance of the software version is gathered. Once gathered, the data is automatically analyzed to determine if the actual performance met an expected performance. Based on the analysis, a plan is developed and executed. In particular, if the actual performance failed to meet the expected performance, the software version (or components thereof) could be revised (e.g., via patches, fixes, etc.) to correct the defects, or even rolled back to a previous operational level. Conversely, if the actual performance met or exceeded the expected performance, the software version could be promoted to a next operational level.</description><edition>7</edition><language>eng</language><subject>CALCULATING ; COMPUTING ; COUNTING ; ELECTRIC DIGITAL DATA PROCESSING ; PHYSICS</subject><creationdate>2004</creationdate><oa>free_for_read</oa><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://worldwide.espacenet.com/publicationDetails/biblio?FT=D&date=20041223&DB=EPODOC&CC=US&NR=2004261070A1$$EHTML$$P50$$Gepo$$Hfree_for_read</linktohtml><link.rule.ids>230,308,777,882,25545,76296</link.rule.ids><linktorsrc>$$Uhttps://worldwide.espacenet.com/publicationDetails/biblio?FT=D&date=20041223&DB=EPODOC&CC=US&NR=2004261070A1$$EView_record_in_European_Patent_Office$$FView_record_in_$$GEuropean_Patent_Office$$Hfree_for_read</linktorsrc></links><search><creatorcontrib>MILLER BRENT ALAN</creatorcontrib><creatorcontrib>RABINOVITZ DANIEL SCOTT</creatorcontrib><creatorcontrib>RAGO PATRICIA A</creatorcontrib><title>Autonomic software version management system, method and program product</title><description>Under the present invention a software version is used on a first operational level by a set (e.g., one or more) of users. As the software version is being used, its performance is automatically monitored based on predetermined monitoring criteria. Specifically, data relating to the performance of the software version is gathered. Once gathered, the data is automatically analyzed to determine if the actual performance met an expected performance. Based on the analysis, a plan is developed and executed. In particular, if the actual performance failed to meet the expected performance, the software version (or components thereof) could be revised (e.g., via patches, fixes, etc.) to correct the defects, or even rolled back to a previous operational level. Conversely, if the actual performance met or exceeded the expected performance, the software version could be promoted to a next operational level.</description><subject>CALCULATING</subject><subject>COMPUTING</subject><subject>COUNTING</subject><subject>ELECTRIC DIGITAL DATA PROCESSING</subject><subject>PHYSICS</subject><fulltext>true</fulltext><rsrctype>patent</rsrctype><creationdate>2004</creationdate><recordtype>patent</recordtype><sourceid>EVB</sourceid><recordid>eNqNyr0KwkAMAOAuDqK-Q8BV4VpF5yJKd3Uu4S79AXM5Lqni24vgAzh9yzcvmnoyicKjB5XOXpgJnpR1lAiMEXtiigb6ViPeAJMNEgBjgJSlz8hfw-RtWcw6fCitfi6K9eV8OzVbStKSJvQUydr7tXJuXx1Kd3R1uftvfQDM6zXK</recordid><startdate>20041223</startdate><enddate>20041223</enddate><creator>MILLER BRENT ALAN</creator><creator>RABINOVITZ DANIEL SCOTT</creator><creator>RAGO PATRICIA A</creator><scope>EVB</scope></search><sort><creationdate>20041223</creationdate><title>Autonomic software version management system, method and program product</title><author>MILLER BRENT ALAN ; RABINOVITZ DANIEL SCOTT ; RAGO PATRICIA A</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-epo_espacenet_US2004261070A13</frbrgroupid><rsrctype>patents</rsrctype><prefilter>patents</prefilter><language>eng</language><creationdate>2004</creationdate><topic>CALCULATING</topic><topic>COMPUTING</topic><topic>COUNTING</topic><topic>ELECTRIC DIGITAL DATA PROCESSING</topic><topic>PHYSICS</topic><toplevel>online_resources</toplevel><creatorcontrib>MILLER BRENT ALAN</creatorcontrib><creatorcontrib>RABINOVITZ DANIEL SCOTT</creatorcontrib><creatorcontrib>RAGO PATRICIA A</creatorcontrib><collection>esp@cenet</collection></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>MILLER BRENT ALAN</au><au>RABINOVITZ DANIEL SCOTT</au><au>RAGO PATRICIA A</au><format>patent</format><genre>patent</genre><ristype>GEN</ristype><title>Autonomic software version management system, method and program product</title><date>2004-12-23</date><risdate>2004</risdate><abstract>Under the present invention a software version is used on a first operational level by a set (e.g., one or more) of users. As the software version is being used, its performance is automatically monitored based on predetermined monitoring criteria. Specifically, data relating to the performance of the software version is gathered. Once gathered, the data is automatically analyzed to determine if the actual performance met an expected performance. Based on the analysis, a plan is developed and executed. In particular, if the actual performance failed to meet the expected performance, the software version (or components thereof) could be revised (e.g., via patches, fixes, etc.) to correct the defects, or even rolled back to a previous operational level. Conversely, if the actual performance met or exceeded the expected performance, the software version could be promoted to a next operational level.</abstract><edition>7</edition><oa>free_for_read</oa></addata></record> |
fulltext | fulltext_linktorsrc |
identifier | |
ispartof | |
issn | |
language | eng |
recordid | cdi_epo_espacenet_US2004261070A1 |
source | esp@cenet |
subjects | CALCULATING COMPUTING COUNTING ELECTRIC DIGITAL DATA PROCESSING PHYSICS |
title | Autonomic software version management system, method and program product |
url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-20T13%3A04%3A37IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-epo_EVB&rft_val_fmt=info:ofi/fmt:kev:mtx:patent&rft.genre=patent&rft.au=MILLER%20BRENT%20ALAN&rft.date=2004-12-23&rft_id=info:doi/&rft_dat=%3Cepo_EVB%3EUS2004261070A1%3C/epo_EVB%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_id=info:pmid/&rfr_iscdi=true |