An integrated life-cycle model for software maintenance
An integrated life-cycle model is presented for use in a software maintenance environment. The model represents information about the development and maintenance of software systems, emphasizing relationships between different phases of the software life cycle. It provides the basis for automated to...
Gespeichert in:
Veröffentlicht in: | IEEE transactions on software engineering 1988-08, Vol.14 (8), p.1128-1144 |
---|---|
Hauptverfasser: | , , , |
Format: | Artikel |
Sprache: | eng |
Schlagworte: | |
Online-Zugang: | Volltext bestellen |
Tags: |
Tag hinzufügen
Keine Tags, Fügen Sie den ersten Tag hinzu!
|
container_end_page | 1144 |
---|---|
container_issue | 8 |
container_start_page | 1128 |
container_title | IEEE transactions on software engineering |
container_volume | 14 |
creator | Yau, S.S. Nicholl, R.A. Tsai, J.J.-P. Liu, S.-S. |
description | An integrated life-cycle model is presented for use in a software maintenance environment. The model represents information about the development and maintenance of software systems, emphasizing relationships between different phases of the software life cycle. It provides the basis for automated tools to assist maintenance personnel in making changes to existing software systems. The model is independent of particular specification, design, and programming languages because it represents only certain 'basic' semantic properties of software systems: control flow, data flow, and data structure. The software development processes by which one phase of the software life cycle is derived from another are represented by graph rewriting rules, which indicate how various components of a software system have been implemented. This approach permits analysis of the basic properties of a software system throughout the software life cycle. Examples are given to illustrate the integrated software life-cycle model during evolution.< > |
doi_str_mv | 10.1109/32.7624 |
format | Article |
fullrecord | <record><control><sourceid>proquest_RIE</sourceid><recordid>TN_cdi_proquest_journals_195579561</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>7624</ieee_id><sourcerecordid>24928358</sourcerecordid><originalsourceid>FETCH-LOGICAL-c292t-dfa6c938934c191166c83a6fb5cfb331db906b33bcaef233933ad90aa0dda85a3</originalsourceid><addsrcrecordid>eNqN0U1LxDAQBuAgCq4fePVYPOipa5LZpJ3jsvgFC170HNJ0Il26zZp0kf33tq548KKnGWYeBoaXsQvBp0JwvAU5LbScHbCJQMAclOSHbMI5lrlSJR6zk5RWnHNVFGrCinmXNV1Pb9H2VGdt4yl3O9dStg41tZkPMUvB9x82DiM70s52js7YkbdtovPvespe7-9eFo_58vnhaTFf5k6i7PPaW-0QSoSZEyiE1q4Eq32lnK8ARF0h10NTOUteAiCArZFby-valsrCKbve393E8L6l1Jt1kxy1re0obJORJUjQWv0NZzhYVf4LFoUcL179gquwjd3wrRGoVIFKiwHd7JGLIaVI3mxis7ZxZwQ3Yx4GpBnzGOTlXjZE9KO-Vp8cyoMn</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>195579561</pqid></control><display><type>article</type><title>An integrated life-cycle model for software maintenance</title><source>IEEE Electronic Library (IEL)</source><creator>Yau, S.S. ; Nicholl, R.A. ; Tsai, J.J.-P. ; Liu, S.-S.</creator><creatorcontrib>Yau, S.S. ; Nicholl, R.A. ; Tsai, J.J.-P. ; Liu, S.-S.</creatorcontrib><description>An integrated life-cycle model is presented for use in a software maintenance environment. The model represents information about the development and maintenance of software systems, emphasizing relationships between different phases of the software life cycle. It provides the basis for automated tools to assist maintenance personnel in making changes to existing software systems. The model is independent of particular specification, design, and programming languages because it represents only certain 'basic' semantic properties of software systems: control flow, data flow, and data structure. The software development processes by which one phase of the software life cycle is derived from another are represented by graph rewriting rules, which indicate how various components of a software system have been implemented. This approach permits analysis of the basic properties of a software system throughout the software life cycle. Examples are given to illustrate the integrated software life-cycle model during evolution.< ></description><identifier>ISSN: 0098-5589</identifier><identifier>EISSN: 1939-3520</identifier><identifier>DOI: 10.1109/32.7624</identifier><identifier>CODEN: IESEDJ</identifier><language>eng</language><publisher>New York: IEEE</publisher><subject>Computer engineering ; Computer languages ; Computer programming ; Computer science ; Control system synthesis ; Costs ; Electrical engineering ; Graphs ; Integrated ; Integrated software ; Life cycles ; Personnel ; Programming languages ; Proposals ; Repair & maintenance ; Software ; Software development ; Software maintenance ; Software systems ; Software tools ; Systems development</subject><ispartof>IEEE transactions on software engineering, 1988-08, Vol.14 (8), p.1128-1144</ispartof><rights>Copyright Institute of Electrical and Electronics Engineers, Inc. (IEEE) Aug 1988</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c292t-dfa6c938934c191166c83a6fb5cfb331db906b33bcaef233933ad90aa0dda85a3</citedby><cites>FETCH-LOGICAL-c292t-dfa6c938934c191166c83a6fb5cfb331db906b33bcaef233933ad90aa0dda85a3</cites></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/7624$$EHTML$$P50$$Gieee$$H</linktohtml><link.rule.ids>314,780,784,796,27924,27925,54758</link.rule.ids><linktorsrc>$$Uhttps://ieeexplore.ieee.org/document/7624$$EView_record_in_IEEE$$FView_record_in_$$GIEEE</linktorsrc></links><search><creatorcontrib>Yau, S.S.</creatorcontrib><creatorcontrib>Nicholl, R.A.</creatorcontrib><creatorcontrib>Tsai, J.J.-P.</creatorcontrib><creatorcontrib>Liu, S.-S.</creatorcontrib><title>An integrated life-cycle model for software maintenance</title><title>IEEE transactions on software engineering</title><addtitle>TSE</addtitle><description>An integrated life-cycle model is presented for use in a software maintenance environment. The model represents information about the development and maintenance of software systems, emphasizing relationships between different phases of the software life cycle. It provides the basis for automated tools to assist maintenance personnel in making changes to existing software systems. The model is independent of particular specification, design, and programming languages because it represents only certain 'basic' semantic properties of software systems: control flow, data flow, and data structure. The software development processes by which one phase of the software life cycle is derived from another are represented by graph rewriting rules, which indicate how various components of a software system have been implemented. This approach permits analysis of the basic properties of a software system throughout the software life cycle. Examples are given to illustrate the integrated software life-cycle model during evolution.< ></description><subject>Computer engineering</subject><subject>Computer languages</subject><subject>Computer programming</subject><subject>Computer science</subject><subject>Control system synthesis</subject><subject>Costs</subject><subject>Electrical engineering</subject><subject>Graphs</subject><subject>Integrated</subject><subject>Integrated software</subject><subject>Life cycles</subject><subject>Personnel</subject><subject>Programming languages</subject><subject>Proposals</subject><subject>Repair & maintenance</subject><subject>Software</subject><subject>Software development</subject><subject>Software maintenance</subject><subject>Software systems</subject><subject>Software tools</subject><subject>Systems development</subject><issn>0098-5589</issn><issn>1939-3520</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>1988</creationdate><recordtype>article</recordtype><sourceid>8G5</sourceid><sourceid>ABUWG</sourceid><sourceid>AFKRA</sourceid><sourceid>AZQEC</sourceid><sourceid>BENPR</sourceid><sourceid>CCPQU</sourceid><sourceid>DWQXO</sourceid><sourceid>GNUQQ</sourceid><sourceid>GUQSH</sourceid><sourceid>M2O</sourceid><recordid>eNqN0U1LxDAQBuAgCq4fePVYPOipa5LZpJ3jsvgFC170HNJ0Il26zZp0kf33tq548KKnGWYeBoaXsQvBp0JwvAU5LbScHbCJQMAclOSHbMI5lrlSJR6zk5RWnHNVFGrCinmXNV1Pb9H2VGdt4yl3O9dStg41tZkPMUvB9x82DiM70s52js7YkbdtovPvespe7-9eFo_58vnhaTFf5k6i7PPaW-0QSoSZEyiE1q4Eq32lnK8ARF0h10NTOUteAiCArZFby-valsrCKbve393E8L6l1Jt1kxy1re0obJORJUjQWv0NZzhYVf4LFoUcL179gquwjd3wrRGoVIFKiwHd7JGLIaVI3mxis7ZxZwQ3Yx4GpBnzGOTlXjZE9KO-Vp8cyoMn</recordid><startdate>19880801</startdate><enddate>19880801</enddate><creator>Yau, S.S.</creator><creator>Nicholl, R.A.</creator><creator>Tsai, J.J.-P.</creator><creator>Liu, S.-S.</creator><general>IEEE</general><general>IEEE Computer Society</general><scope>AAYXX</scope><scope>CITATION</scope><scope>3V.</scope><scope>7WY</scope><scope>7WZ</scope><scope>7X7</scope><scope>7XB</scope><scope>87Z</scope><scope>88E</scope><scope>88F</scope><scope>88I</scope><scope>88K</scope><scope>8AL</scope><scope>8FE</scope><scope>8FG</scope><scope>8FI</scope><scope>8FJ</scope><scope>8FK</scope><scope>8FL</scope><scope>8G5</scope><scope>ABJCF</scope><scope>ABUWG</scope><scope>AFKRA</scope><scope>ARAPS</scope><scope>AZQEC</scope><scope>BENPR</scope><scope>BEZIV</scope><scope>BGLVJ</scope><scope>CCPQU</scope><scope>DWQXO</scope><scope>FRNLG</scope><scope>FYUFA</scope><scope>F~G</scope><scope>GHDGH</scope><scope>GNUQQ</scope><scope>GUQSH</scope><scope>HCIFZ</scope><scope>JQ2</scope><scope>K60</scope><scope>K6~</scope><scope>K7-</scope><scope>K9.</scope><scope>L.-</scope><scope>L6V</scope><scope>M0C</scope><scope>M0N</scope><scope>M0S</scope><scope>M1P</scope><scope>M1Q</scope><scope>M2O</scope><scope>M2P</scope><scope>M2T</scope><scope>M7S</scope><scope>MBDVC</scope><scope>P5Z</scope><scope>P62</scope><scope>PQBIZ</scope><scope>PQBZA</scope><scope>PQEST</scope><scope>PQQKQ</scope><scope>PQUKI</scope><scope>PTHSS</scope><scope>Q9U</scope><scope>8FD</scope><scope>H8D</scope><scope>L7M</scope><scope>7SC</scope><scope>L~C</scope><scope>L~D</scope></search><sort><creationdate>19880801</creationdate><title>An integrated life-cycle model for software maintenance</title><author>Yau, S.S. ; Nicholl, R.A. ; Tsai, J.J.-P. ; Liu, S.-S.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c292t-dfa6c938934c191166c83a6fb5cfb331db906b33bcaef233933ad90aa0dda85a3</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>1988</creationdate><topic>Computer engineering</topic><topic>Computer languages</topic><topic>Computer programming</topic><topic>Computer science</topic><topic>Control system synthesis</topic><topic>Costs</topic><topic>Electrical engineering</topic><topic>Graphs</topic><topic>Integrated</topic><topic>Integrated software</topic><topic>Life cycles</topic><topic>Personnel</topic><topic>Programming languages</topic><topic>Proposals</topic><topic>Repair & maintenance</topic><topic>Software</topic><topic>Software development</topic><topic>Software maintenance</topic><topic>Software systems</topic><topic>Software tools</topic><topic>Systems development</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Yau, S.S.</creatorcontrib><creatorcontrib>Nicholl, R.A.</creatorcontrib><creatorcontrib>Tsai, J.J.-P.</creatorcontrib><creatorcontrib>Liu, S.-S.</creatorcontrib><collection>CrossRef</collection><collection>ProQuest Central (Corporate)</collection><collection>ABI/INFORM Collection</collection><collection>ABI/INFORM Global (PDF only)</collection><collection>Health & Medical Collection</collection><collection>ProQuest Central (purchase pre-March 2016)</collection><collection>ABI/INFORM Global (Alumni Edition)</collection><collection>Medical Database (Alumni Edition)</collection><collection>Military Database (Alumni Edition)</collection><collection>Science Database (Alumni Edition)</collection><collection>Telecommunications (Alumni Edition)</collection><collection>Computing Database (Alumni Edition)</collection><collection>ProQuest SciTech Collection</collection><collection>ProQuest Technology Collection</collection><collection>Hospital Premium Collection</collection><collection>Hospital Premium Collection (Alumni Edition)</collection><collection>ProQuest Central (Alumni) (purchase pre-March 2016)</collection><collection>ABI/INFORM Collection (Alumni Edition)</collection><collection>Research Library (Alumni Edition)</collection><collection>Materials Science & Engineering Collection</collection><collection>ProQuest Central (Alumni Edition)</collection><collection>ProQuest Central UK/Ireland</collection><collection>Advanced Technologies & Aerospace Collection</collection><collection>ProQuest Central Essentials</collection><collection>ProQuest Central</collection><collection>Business Premium Collection</collection><collection>Technology Collection</collection><collection>ProQuest One Community College</collection><collection>ProQuest Central Korea</collection><collection>Business Premium Collection (Alumni)</collection><collection>Health Research Premium Collection</collection><collection>ABI/INFORM Global (Corporate)</collection><collection>Health Research Premium Collection (Alumni)</collection><collection>ProQuest Central Student</collection><collection>Research Library Prep</collection><collection>SciTech Premium Collection</collection><collection>ProQuest Computer Science Collection</collection><collection>ProQuest Business Collection (Alumni Edition)</collection><collection>ProQuest Business Collection</collection><collection>Computer Science Database</collection><collection>ProQuest Health & Medical Complete (Alumni)</collection><collection>ABI/INFORM Professional Advanced</collection><collection>ProQuest Engineering Collection</collection><collection>ABI/INFORM Global</collection><collection>Computing Database</collection><collection>Health & Medical Collection (Alumni Edition)</collection><collection>Medical Database</collection><collection>Military Database</collection><collection>Research Library</collection><collection>Science Database</collection><collection>Telecommunications Database</collection><collection>Engineering Database</collection><collection>Research Library (Corporate)</collection><collection>Advanced Technologies & Aerospace Database</collection><collection>ProQuest Advanced Technologies & Aerospace Collection</collection><collection>ProQuest One Business</collection><collection>ProQuest One Business (Alumni)</collection><collection>ProQuest One Academic Eastern Edition (DO NOT USE)</collection><collection>ProQuest One Academic</collection><collection>ProQuest One Academic UKI Edition</collection><collection>Engineering Collection</collection><collection>ProQuest Central Basic</collection><collection>Technology Research Database</collection><collection>Aerospace Database</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts</collection><collection>Computer and Information Systems Abstracts Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><jtitle>IEEE transactions on software engineering</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Yau, S.S.</au><au>Nicholl, R.A.</au><au>Tsai, J.J.-P.</au><au>Liu, S.-S.</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>An integrated life-cycle model for software maintenance</atitle><jtitle>IEEE transactions on software engineering</jtitle><stitle>TSE</stitle><date>1988-08-01</date><risdate>1988</risdate><volume>14</volume><issue>8</issue><spage>1128</spage><epage>1144</epage><pages>1128-1144</pages><issn>0098-5589</issn><eissn>1939-3520</eissn><coden>IESEDJ</coden><abstract>An integrated life-cycle model is presented for use in a software maintenance environment. The model represents information about the development and maintenance of software systems, emphasizing relationships between different phases of the software life cycle. It provides the basis for automated tools to assist maintenance personnel in making changes to existing software systems. The model is independent of particular specification, design, and programming languages because it represents only certain 'basic' semantic properties of software systems: control flow, data flow, and data structure. The software development processes by which one phase of the software life cycle is derived from another are represented by graph rewriting rules, which indicate how various components of a software system have been implemented. This approach permits analysis of the basic properties of a software system throughout the software life cycle. Examples are given to illustrate the integrated software life-cycle model during evolution.< ></abstract><cop>New York</cop><pub>IEEE</pub><doi>10.1109/32.7624</doi><tpages>17</tpages></addata></record> |
fulltext | fulltext_linktorsrc |
identifier | ISSN: 0098-5589 |
ispartof | IEEE transactions on software engineering, 1988-08, Vol.14 (8), p.1128-1144 |
issn | 0098-5589 1939-3520 |
language | eng |
recordid | cdi_proquest_journals_195579561 |
source | IEEE Electronic Library (IEL) |
subjects | Computer engineering Computer languages Computer programming Computer science Control system synthesis Costs Electrical engineering Graphs Integrated Integrated software Life cycles Personnel Programming languages Proposals Repair & maintenance Software Software development Software maintenance Software systems Software tools Systems development |
title | An integrated life-cycle model for software maintenance |
url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-01-05T04%3A44%3A47IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest_RIE&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=An%20integrated%20life-cycle%20model%20for%20software%20maintenance&rft.jtitle=IEEE%20transactions%20on%20software%20engineering&rft.au=Yau,%20S.S.&rft.date=1988-08-01&rft.volume=14&rft.issue=8&rft.spage=1128&rft.epage=1144&rft.pages=1128-1144&rft.issn=0098-5589&rft.eissn=1939-3520&rft.coden=IESEDJ&rft_id=info:doi/10.1109/32.7624&rft_dat=%3Cproquest_RIE%3E24928358%3C/proquest_RIE%3E%3Curl%3E%3C/url%3E&disable_directlink=true&sfx.directlink=off&sfx.report_link=0&rft_id=info:oai/&rft_pqid=195579561&rft_id=info:pmid/&rft_ieee_id=7624&rfr_iscdi=true |