Meta tags:

Headings (most frequently used words):

edit, maintenance, software, of, navigation, tools, contents, history, importance, planning, processes, categories, factors, debt, see, also, references, further, reading, external, links, menu, personal, namespaces, views, search, contribute, print, export, in, other, projects, languages,

Text of the page (most frequently used words):
the (114), #software (113), #maintenance (84), and (81), management (21), this (20), tools (19), engineering (19), for (19), with (17), model (17), system (17), that (17), articles (16), edit (14), development (14), information (13), from (13), standards (13), systems (13), process (13), code (13), ieee (12), analysis (12), computer (11), computing (11), modification (11), iso (10), quality (10), change (10), are (10), wikipedia (9), data (9), design (9), computational (9), new (9), factors (9), which (9), product (9), other (8), all (8), application (8), time (8), isbn (8), processes (8), delivery (8), after (8), may (7), page (7), help (7), references (7), programming (7), language (7), network (7), can (7), problem (7), over (7), article (6), search (6), 2015 (6), issues (6), iec (6), control (6), 14764 (6), also (6), science (6), requirements (6), security (6), complexity (6), performance (6), lehman (6), evolution (6), debt (6), such (6), measurements (6), high (6), impact (6), key (6), during (6), additional (5), learn (5), more (5), not (5), categories (5), retrieved (5), org (5), libraries (5), configuration (5), modeling (5), research (5), learning (5), theory (5), environment (5), automation (5), very (5), template (5), 978 (5), 2006 (5), life (5), swanson (5), any (5), defect (5), error (5), costs (5), request (5), how (5), citation (5), about (4), organization (4), use (4), commons (4), was (4), links (4), languages (4), pdf (4), book (4), identifiers (4), january (4), unsourced (4), 2010 (4), category (4), 802 (4), architecture (4), formal (4), testing (4), deployment (4), artificial (4), intelligence (4), knowledge (4), hardware (4), source (4), team (4), external (4), york (4), practices (4), pigoski (4), thomas (4), cycle (4), bug (4), test (4), implementation (4), maintainability (4), cost (4), solution (4), must (4), has (4), value (4), problems (4), specialists (4), y2k (4), example (4), they (4), improve (4), corrective (4), used (4), activities (4), should (4), part (4), years (4), when (4), remove (4), view (3), last (3), 2022 (3), special (3), pages (3), file (3), current (3), navigation (3), history (3), talk (3), statements (3), needing (3), wikiproject (3), september (3), description (3), series (3), see (3), 1219 (3), project (3), object (3), agile (3), service (3), verification (3), validation (3), enterprise (3), methods (3), document (3), technology (3), processing (3), electronic (3), publishing (3), digital (3), social (3), mathematics (3), reality (3), graphics (3), machine (3), distributed (3), automated (3), planning (3), services (3), world (3), web (3), platform (3), library (3), support (3), components (3), acm (3), 1980 (3), practical (3), effective (3), wiley (3), swebok (3), john (3), doi (3), reading (3), estdale (3), international (3), 2013 (3), first (3), lientz (3), does (3), report (3), reporting (3), functionality (3), too (3), become (3), user (3), poor (3), training (3), desk (3), tracking (3), level (3), prone (3), modules (3), range (3), order (3), some (3), experience (3), base (3), there (3), who (3), correct (3), faults (3), fixing (3), these (3), maintainers (3), will (3), work (3), modifications (3), plan (3), users (3), needed (3), studies (3), message (3), statistics (2), contact (2), privacy (2), policy (2), available (2), terms (2), apply (2), using (2), site (2), you (2), non (2), wikimedia (2), inc (2), version (2), disable (2), creator (2), wikidata (2), upload (2), related (2), changes (2), what (2), recent (2), portal (2), contents (2), main (2), hidden (2), specifically (2), marked (2), weasel (2), worded (2), phrases (2), multiple (2), covered (2), wikify (2), cleanup (2), short (2), https (2), software_maintenance (2), 42010 (2), 29148 (2), 27000 (2), 20000 (2), 15926 (2), 12207 (2), 11941 (2), 11073 (2), 238 (2), 9001 (2), 1073 (2), 500 (2), standard (2), number (2), 754 (2), 1985 (2), superseded (2), original (2), 1076 (2), 1016 (2), fields (2), uml (2), cmmi (2), waterfall (2), spiral (2), scrum (2), rad (2), incremental (2), models (2), orientation (2), structured (2), assurance (2), methodology (2), archaeology (2), paradigm (2), concepts (2), devops (2), outline (2), image (2), virtual (2), task (2), scheduling (2), interaction (2), detection (2), decision (2), storage (2), theoretical (2), mathematical (2), algorithm (2), algorithms (2), computation (2), construction (2), integrated (2), domain (2), specific (2), compiler (2), operating (2), middleware (2), evaluation (2), embedded (2), large (2), circuit (2), 2012 (2), journal (2), press (2), academic (2), program (2), grubb (2), penny (2), takang (2), armstrong (2), 2003 (2), scientific (2), ramesh (2), alain (2), 471 (2), further (2), 2019 (2), twenty (2), june (2), s2cid (2), proceedings (2), conference (2), practice (2), laws (2), 1997 (2), your (2), 2020 (2), 106344 (2), efficient (2), feature (2), maintainer (2), long (2), term (2), retirement (2), make (2), unmaintainable (2), production (2), including (2), run (2), transfer (2), archive (2), etc (2), platforms (2), build (2), only (2), often (2), overall (2), modified (2), less (2), business (2), needs (2), have (2), happens (2), sum (2), unpaid (2), overtime (2), satisfaction (2), morale (2), productivity (2), reverse (2), annual (2), restructuring (2), inexperience (2), line (2), regression (2), inspections (2), response (2), ease (2), mass (2), update (2), low (2), engines (2), staff (2), variables (2), adjustment (2), sorted (2), maximum (2), many (2), complex (2), common (2), situation (2), lack (2), excellent (2), pre (2), release (2), things (2), includes (2), goals (2), resources (2), perfective (2), adaptive (2), performed (2), identified (2), handling (2), transition (2), include (2), occur (2), finally (2), daily (2), migration (2), its (2), preparation (2), addressed (2), customer (2), correction (2), enhancements (2), capabilities (2), because (2), technical (2), understanding (2), importance (2), survey (2), effort (2), suggest (2), show (2), his (2), evolve (2), study (2), perception (2), please (2), sources (2), citations (2), style (2), jump (2), sep (2), cookie, statement, developers, mobile, disclaimers, text, under, agree, registered, trademark, profit, foundation, creative, attribution, sharealike, license, edited, july, utc, tiếng, việt, українська, türkçe, தமிழ், српски, srpski, shqip, русский, português, polski, 日本語, македонски, עברית, italiano, hrvatski, հայերեն, 한국어, galego, français, فارسی, español, eesti, deutsch, català, العربية, projects, printable, download, print, export, item, cite, permanent, link, here, community, contribute, donate, random, events, read, views, english, namespaces, log, create, account, contributions, logged, personal, menu, lccn, j9u, gnd, bnf, october, 2018, matches, index, php, title, oldid, 1096946531, united, states, israel, germany, france, authority, national, 80000, 56000, 55000, 50001, 45001, 40500, 38500, 37001, 32000, 31000, 30170, 30000, 29500, 29199, 29110, 28000, 27729, 27006, 27005, 27002, 27001, 26324, 26300, 26262, 26000, 25964, 25178, 24707, 24617, 24613, 24517, 23360, 23271, 23270, 23090, 22395, 22300, 22000, 21827, 21500, 21047, 21000, 20802, 20400, 20121, 20022, 29999, 19831, 19794, 19775, 19770, 19757, 19752, 19600, 19510, 19509, 19508, 19507, 19506, 19505, 19503, 19502, 19501, 19500, 19439, 19407, 19136, 19125, 19115, 19114, 19092, 19011, 19005, 18916, 18629, 18245, 18014, 18004, 18000, 17799, 17506, 17442, 17369, 17203, 17100, 17025, 17024, 16949, 16750, 16612, 16485, 16355, 16262, 16023, 15930, wip, 15924, 15919, 15897, 15707, 15706, 15693, 15686, 15511, 15504, 15438, 15445, 15444, 15408, 15398, 15292, 15291, 15288, 15189, 15022, 14971, 14882, 14698, 14651, 14649, 14644, 14617, 14496, 14443, 14396, 14289, 14224, 14031, 14000, 13816, 13616, 13584, 13568, 13567, 13490, 13485, 13450, 13406, 13399, 13250, 13216, 13211, 12620, 12234, 12182, 12006, 11992, 11940, 11898, 11889, 11801, 11785, 11784, 11783, 11544, 11404, 11179, 11170, 10967, 10962, 10957, 10861, 10746, 10664, 10646, 10628, 10589, 10585, 10487, 10383, 10303, 10218, 10206, 10179, 10165, 10161, 10160, 10118, 10116, 10007, 10006, 10005, 10000, 19999, 9995, 9985, 9984, 9945, 9899, 9897, 9797, 9660, 9594, 9592, 9593, 9564, 9529, 9506, 9496, 9407, 9362, 9314, 9293, 9241, 9227, 9141, 9126, 9075, 9036, 9000, 8879, 8859, 8820, 8807, 8805, 8806, 8691, 8652, 8651, 8632, 8613, 8601, 8583, 8571, 8501, 8373, 8217, 8178, 8093, 8000, 7942, 7816, 7813, 7812, 7811, 7810, 7736, 7637, 7498, 7200, 7185, 7098, 7064, 7027, 7010, 7002, 7001, 6943, 6709, 6523, 6438, 6429, 6425, 6385, 6346, 6344, 6166, 5964, 5807, 5800, 5776, 5775, 5725, 5428, 5427, 5426, 5218, 4909, 4217, 4165, 4157, 4031, 3977, 3950, 3901, 3864, 3602, 3601, 3307, 3297, 3166, 3103, 3029, 2852, 2848, 2788, 2720, 2711, 2709, 2533, 2281, 2240, 2146, 2145, 2108, 2047, 2033, 2014, 1989, 1745, 1629, 1538, 1413, 1155, 1007, 1004, 1000, 999, 965, 898, 860, 843, 838, 764, 732, 704, 690, 668, 657, 646, 639, 519, 518, 428, 361, 306, 302, 262, 261, 259, 233, 228, 226, 217, 216, 128, 9999, list, romanizations, association, 1471, 1364, 1362, 1233, 830, p1906, p1823, p1699, p1619, p1363, proposed, legacy, mode, 1983, qay, qat, qav, 16326, 16085, 2050, 2030, 1905, 1904, 1902, 1901, 1900, 1850, 1815, 1801, 1800, 1733, 1722, 1685, 1675, 1667, 1666, 1613, 1603, 1596, 1588, 1584, 1547, 1541, 1516, 1497, 1451, 1394, 1355, 1284, 1278, 1275, 1164, 1154, 1149, 1014, 1003, 896, 829, 828, 854, revision, 730, 488, risk, sysml, usl, idef, metamodeling, function, spice, prototype, iterative, executable, eup, developmental, sdlc, ontology, aspect, oriented, orientations, essential, functional, specification, reliability, educational, operations, word, video, games, voting, cyberwarfare, art, healthcare, biology, chemistry, physics, commerce, applied, solid, compression, mixed, unit, manipulation, rendering, animation, cross, multi, reinforcement, unsupervised, supervised, philosophy, method, vision, representation, reasoning, natural, multiprocessing, multithreading, parallel, concurrent, concurrency, accessibility, visualization, ubiquitous, human, intrusion, cryptography, retrieval, wide, marketing, mining, multimedia, geographic, database, numerical, probability, discrete, geometry, randomized, algorithmic, efficiency, semantics, logic, computability, automata, open, variable, repository, framework, notations, interpreter, scheduler, protocol, networks, dependability, real, acceleration, energy, consumption, green, chip, socs, scale, integration, peripheral, printed, board, note, roughly, follows, classification, jones, meilir, yourdon, 917072, guide, belady, london, 442441, jersey, 981, 425, gopalaswamy, bhattiprolu, delhi, tata, mcgraw, hill, 048345, geographically, environments, april, abran, 2008, 470, 14707, area, 1996, sons, 17001, 7381, 4960, 1109, ieeestd, 235774, std, november, chapter, 106, delaying, prove, fatal, khan, marchbank, georgiadou, linecar, ross, staples, southampton, solent, university, 9996549, proc, xxvii, experiences, initiatives, archived, economics, century, status, 1998, tompkins, 1978, 466, 14950091, 1145, 359511, 359522, communications, burt, dimensions, 2nd, san, francisco, 1976, 492, 497, company, cycles, 1060, addison, wesley, eick, graves, karr, marron, mockus, 2001, decay, assessing, evidence, transactions, best, managing, investment, pub, soleimani, neysiani, behzad, babamir, seyed, morteza, aritsugi, masayoshi, 219733047, infsof, 126, extraction, improvement, duplicate, triage, 2011, based, complete, disappearance, component, could, rebuildable, imminently, availability, relevant, skills, house, marketplace, course, arising, applications, sharing, interworking, question, bought, invocable, separately, acquired, packages, dbms, comms, standby, disaster, recovery, facilities, wider, ecosystem, job, replicated, backup, single, sign, execute, above, selection, execution, editing, compilation, defines, gap, between, state, ideal, fully, maintained, supported, recognized, dependent, continuing, obtainability, sorts, suppliers, owner, then, discover, longer, literally, dramatically, take, much, solve, alternative, found, suddenly, crashed, paper, 27th, introduced, generated, dependence, obsolescent, continues, department, forgets, liability, focussing, urgent, elsewhere, accumulates, silently, eating, away, asset, eventually, something, makes, unavoidable, reengineering, manual, minus, negative, troublesome, but, degrade, quite, difficult, maintain, safely, degrades, suitable, below, describe, spaghetti, 503, days, table, driven, plus, positive, notion, good, lower, total, ownership, like, compliance, coding, coupling, cohesion, attainment, supportability, sae, ja1004, ja1005, ja1006, institutions, carrying, out, quantify, ongoing, due, documents, comprehension, multiply, approx, where, detect, latent, before, preventive, keep, usable, changed, changing, reactive, discovered, automatic, initially, three, since, been, updated, presents, p14764, prioritize, route, requests, receive, slas, specialized, contracts, negotiated, agreements, controlled, coordinated, sequence, transferred, progressively, developer, ideally, typical, hand, unique, event, basis, piece, exceptional, tasks, ported, another, without, likely, assigned, acceptance, confirming, individual, submitted, sure, provided, considering, itself, executed, once, responsibility, group, programmer, analyze, each, confirm, reproducing, check, validity, investigate, propose, proposal, obtain, required, authorizations, contains, conception, creation, follow, section, describes, six, integral, requires, accurate, constructed, specify, budget, resource, estimates, every, objectives, even, decades, calls, address, scope, tailoring, post, designation, provide, estimate, done, operation, considered, purpose, preserve, enhanced, expanding, meeting, becoming, easier, employing, newer, span, whereas, broad, activity, deletion, obsolete, optimization, inevitable, mechanisms, developed, controlling, making, both, managerial, alignment, priorities, staffing, estimating, limited, measurement, showed, around, two, types, consumed, subsequent, similar, magnitude, contribution, end, crucial, requirement, gathering, cause, important, consumes, lifecycle, inability, quickly, reliably, means, opportunities, lost, 1969, period, led, formulation, findings, conclude, really, evolutionary, decisions, aided, demonstrated, continue, grow, unless, action, taken, reduce, late, 1970s, famous, widely, cited, exposed, fraction, were, being, expended, refactoring, meir, merely, involves, however, one, indicated, actions, perpetuated, submitting, reports, put, proportion, closer, defects, attributes, outlines, electrical, electronics, glossaries, ireb, itil, pmbok, babok, bodies, infrastructure, ide, gui, designer, profiler, debugger, tdd, stand, sbe, ddd, cco, bdd, atdd, documentation, supporting, disciplines, openup, tsp, semat, safe, rup, psp, msf, mdd, lean, kanban, iid, fdd, dsdm, dad, asd, frameworks, methodologies, prototyping, cleanroom, paradigms, debugging, core, discuss, material, challenged, removed, jstor, scholar, books, newspapers, news, find, adding, reliable, made, clearer, different, consistent, footnoting, unclear, messages, free, encyclopedia, 490, add, wayback, http, 20221002181330, wiki, timestamps, capture, fail, success, 2023, 2021, nov, oct, aug, 2004, 2026, 982, captures,

Text of the page (random words):
ble add this page to your book show book 490 pages suggest pages software maintenance from wikipedia the free encyclopedia jump to navigation jump to search modification of a software product after delivery this article has multiple issues please help improve it or discuss these issues on the talk page learn how and when to remove these template messages this article has an unclear citation style the references used may be made clearer with a different or consistent style of citation and footnoting september 2010 learn how and when to remove this template message this article needs additional citations for verification please help improve this article by adding citations to reliable sources unsourced material may be challenged and removed find sources software maintenance news newspapers books scholar jstor january 2015 learn how and when to remove this template message learn how and when to remove this template message part of a series on software development core activities processes requirements design construction engineering testing debugging deployment maintenance paradigms and models software engineering agile cleanroom incremental prototyping spiral v model waterfall methodologies and frameworks asd devops dad dsdm fdd iid kanban lean sd less mdd msf psp rad rup safe scrum semat tsp openup up xp supporting disciplines configuration management documentation software quality assurance project management user experience practices atdd bdd cco ci cd ddd pp sbe stand up tdd tools compiler debugger profiler gui designer modeling ide build automation release automation infrastructure as code standards and bodies of knowledge babok cmmi ieee standards iso 9001 iso iec standards pmbok swebok itil ireb glossaries artificial intelligence computer science electrical and electronics engineering outlines outline of software development v t e software maintenance in software engineering is the modification of a software product after delivery to correct faults to improve performance or other attributes 1 2 a common perception of maintenance is that it merely involves fixing defects however one study indicated that over 80 of maintenance effort is used for non corrective actions 3 this perception is perpetuated by users submitting problem reports that in reality are functionality enhancements to the system citation needed more recent studies put the bug fixing proportion closer to 21 4 contents 1 history 2 importance of software maintenance 3 software maintenance planning 4 software maintenance processes 5 categories of software maintenance 6 maintenance factors 7 maintenance debt 8 see also 9 references 10 further reading 11 external links history edit software maintenance and evolution of systems was first addressed by meir m lehman in 1969 over a period of twenty years his research led to the formulation of lehman s laws lehman 1997 key findings of his research conclude that maintenance is really evolutionary development and that maintenance decisions are aided by understanding what happens to systems and software over time lehman demonstrated that systems continue to evolve over time as they evolve they grow more complex unless some action such as code refactoring is taken to reduce the complexity in the late 1970s a famous and widely cited survey study by lientz and swanson exposed the very high fraction of life cycle costs that were being expended on maintenance the survey showed that around 75 of the maintenance effort was on the first two types and error correction consumed about 21 many subsequent studies suggest a similar problem magnitude studies show that contribution of end users is crucial during the new requirement data gathering and analysis this is the main cause of any problem during software evolution and maintenance software maintenance is important because it consumes a large part of the overall lifecycle costs and also the inability to change software quickly and reliably means that business opportunities are lost 5 6 7 importance of software maintenance edit the key software maintenance issues are both managerial and technical key management issues are alignment with customer priorities staffing which organization does maintenance estimating costs key technical issues are limited understanding impact analysis testing maintainability measurement software maintenance is a very broad activity that includes error correction enhancements of capabilities deletion of obsolete capabilities and optimization because change is inevitable mechanisms must be developed for evaluation controlling and making modifications so any work done to change the software after it is in operation is considered to be maintenance work the purpose is to preserve the value of software over the time the value can be enhanced by expanding the customer base meeting additional requirements becoming easier to use more efficient and employing newer technology maintenance may span for 20 years citation needed whereas development may be 1 2 years citation needed software maintenance planning edit an integral part of software is maintenance which requires an accurate maintenance plan to be constructed during the software development it should specify how users will request modifications or report problems the budget should include resource and cost estimates and a new decision should be addressed for the development of every new system feature and its quality objectives the software maintenance which can last for 5 years or even decades after the development process calls for an effective plan which can address the scope of software maintenance the tailoring of the post delivery deployment process the designation of who will provide maintenance and an estimate of the life cycle costs software maintenance processes edit this section describes the six software maintenance processes as the implementation process contains software preparation and transition activities such as the conception and creation of the maintenance plan the preparation for handling problems identified during development and the follow up on product configuration management the problem and modification analysis process which is executed once the application has become the responsibility of the maintenance group the maintenance programmer must analyze each request confirm it by reproducing the situation and check its validity investigate it and propose a solution document the request and the solution proposal and finally obtain all the required authorizations to apply the modifications the process considering the implementation of the modification itself the process acceptance of the modification by confirming the modified work with the individual who submitted the request in order to make sure the modification provided a solution the migration process platform migration for example is exceptional and is not part of daily maintenance tasks if the software must be ported to another platform without any change in functionality this process will be used and a maintenance project team is likely to be assigned to this task finally the last maintenance process also an event which does not occur on a daily basis is the retirement of a piece of software there are a number of processes activities and practices that are unique to maintainers for example transition a controlled and coordinated sequence of activities during which a system is transferred progressively from the developer to the maintainer ideally it should include a knowledge transfer kt to occur during a typical hand over service level agreements slas and specialized domain specific maintenance contracts negotiated by maintainers modification request and problem report help desk a problem handling process used by maintainers to prioritize document and route the requests they receive categories of software maintenance edit e b swanson initially identified three categories of maintenance corrective adaptive and perfective 8 the ieee 1219 standard was superseded in june 2010 by p14764 9 these have since been updated and iso iec 14764 presents corrective maintenance reactive modification of a software product performed after delivery to correct discovered problems corrective maintenance can be automated with automatic bug fixing adaptive maintenance modification of a software product performed after delivery to keep a software product usable in a changed or changing environment perfective maintenance modification of a software product after delivery to improve performance or maintainability preventive maintenance modification of a software product after delivery to detect and correct latent faults in the software product before they become effective faults there is also a notion of pre delivery pre release maintenance which is all the good things you do to lower the total cost of ownership of the software things like compliance with coding standards that includes software maintainability goals the management of coupling and cohesion of the software the attainment of software supportability goals sae ja1004 ja1005 and ja1006 for example some academic institutions who are carrying out research to quantify the cost to ongoing software maintenance due to the lack of resources such as design documents and system software comprehension training and resources multiply costs by approx 1 5 2 0 where there is no design data available maintenance factors edit impact of key adjustment factors on maintenance sorted in order of maximum positive impact maintenance factors plus range maintenance specialists 35 high staff experience 34 table driven variables and data 33 low complexity of base code 32 y2k and special search engines 30 code restructuring tools 29 re engineering tools 27 high level programming languages 25 reverse engineering tools 23 complexity analysis tools 20 defect tracking tools 20 y2k mass update specialists 20 automated change control tools 18 unpaid overtime 18 quality measurements 16 formal base code inspections 15 regression test libraries 15 excellent response time 12 annual training of 10 days 12 high management experience 12 help desk automation 12 no error prone modules 10 on line defect reporting 10 productivity measurements 8 excellent ease of use 7 user satisfaction measurements 5 high team morale 5 sum 503 not only are error prone modules troublesome but many other factors can degrade performance too for example very complex spaghetti code is quite difficult to maintain safely a very common situation which often degrades performance is lack of suitable maintenance tools such as defect tracking software change management software and test library software below describe some of the factors and the range of impact on software maintenance impact of key adjustment factors on maintenance sorted in order of maximum negative impact maintenance factors minus range error prone modules 50 embedded variables and data 45 staff inexperience 40 high code complexity 30 no y2k of special search engines 28 manual change control methods 27 low level programming languages 25 no defect tracking tools 24 no y2k mass update specialists 22 poor ease of use 18 no quality measurements 18 no maintenance specialists 18 poor response time 16 no code inspections 15 no regression test libraries 15 no help desk automation 15 no on line defect reporting 12 management inexperience 15 no code restructuring tools 10 no annual training 10 no reengineering tools 10 no reverse engineering tools 10 no complexity analysis tools 10 no productivity measurements 7 poor team morale 6 no user satisfaction measurements 4 no unpaid overtime 0 sum 500 10 maintenance debt edit in a paper for the 27th international conference on software quality management in 2019 11 john estdale introduced the term maintenance debt for maintenance needs generated by an implementation s dependence on external it factors such as libraries platforms and tools that have become obsolescent 12 the application continues to run and the it department forgets this theoretical liability focussing on more urgent requirements and problems elsewhere such debt accumulates over time silently eating away at the value of the software asset eventually something happens that makes system change unavoidable the owner may then discover that the system can no longer be modified it is literally unmaintainable less dramatically it may take too long or cost too much for maintenance to solve the business problem and an alternative solution must be found the software has suddenly crashed to 0 value estdale defines maintenance debt 12 as the gap between the current implementation state of an application and the ideal using only functionality of external components that is fully maintained and supported this debt is often hidden or not recognized an application s overall maintainability is dependent on the continuing obtainability of components of all sorts from other suppliers including development tools source editing configuration management compilation and build testing tools test selection execution verification reporting platforms to execute the above hardware operating system and other services production environment and any standby disaster recovery facilities including the source code language s run time support environment and the wider ecosystem of job scheduling file transfer replicated storage backup and archive single sign on etc etc separately acquired packages eg dbms graphics comms middleware bought in source code object code libraries and other invocable services any requirements arising from other applications sharing the production environment or interworking with the application in question and of course the availability of relevant skills in house or in the marketplace the complete disappearance of a component could make the application un rebuildable or imminently unmaintainable see also edit application retirement journal of software maintenance and evolution research and practice long term support search based software engineering software archaeology software maintainer software development references edit 13 iso iec 14764 2006 software engineering software life cycle processes maintenance iso org 2011 12 17 retrieved 2013 12 02 soleimani neysiani behzad babamir seyed morteza aritsugi masayoshi 2020 10 01 efficient feature extraction model for validation performance improvement of duplicate bug report detection in software bug triage systems information and software technology 126 106344 doi 10 1016 j infsof 2020 106344 s2cid 219733047 pigoski thomas m 1997 practical software maintenance best practices for managing your software investment wiley computer pub new york eick s graves t karr a marron j and mockus a 2001 does code decay assessing evidence from change management data ieee transactions on software engineering 27 1 1 12 lientz b swanson e 1980 software maintenance management addison wesley reading ma lehman m m 1980 program life cycles and the laws of software e...