Variations in software development practices
Research on over 18 years of software projects reveals that developing large systems involves substantially more activities and a greater variety of specialized personnel than developing smaller systems. Perhaps the most significant observation is that good quality control is the best overall indica...
Gespeichert in:
| Veröffentlicht in: | IEEE software 2003-11, Vol.20 (6), p.22-27 |
|---|---|
| 1. Verfasser: | |
| 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 | 27 |
|---|---|
| container_issue | 6 |
| container_start_page | 22 |
| container_title | IEEE software |
| container_volume | 20 |
| creator | Jones, C. |
| description | Research on over 18 years of software projects reveals that developing large systems involves substantially more activities and a greater variety of specialized personnel than developing smaller systems. Perhaps the most significant observation is that good quality control is the best overall indicator of a successful project. Schedule delays and cost overruns most often occur when you discover during testing that the application has so many bugs that it doesn't work. Projects using QA teams, formal design and code inspections, and pretest defect tracking always had shorter testing cycles and therefore were more likely to be deliverable on schedule. |
| doi_str_mv | 10.1109/MS.2003.1241362 |
| format | Article |
| fullrecord | <record><control><sourceid>proquest_RIE</sourceid><recordid>TN_cdi_proquest_miscellaneous_28820680</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><ieee_id>1241362</ieee_id><sourcerecordid>901677436</sourcerecordid><originalsourceid>FETCH-LOGICAL-c395t-2191063cceaf63e61d8ae53cd4cddecb78f2d8a22b9062289e2e79f9752fb8883</originalsourceid><addsrcrecordid>eNp9kMtLw0AQhxdRsFbPHrwED3ox7ewj-zhK8QUtHqpel-1mAitpEndTxf_elBYED54GZr7fMPMRck5hQimY6WI5YQB8QpmgXLIDMqKGq1xQIw7JCJSAXInCHJOTlN4BoKAcRuTmzcXg-tA2KQtNltqq_3IRsxI_sW67NTZ91kXn--AxnZKjytUJz_Z1TF7v715mj_n8-eFpdjvPPTdFnzNqKEjuPbpKcpS01A4L7kvhyxL9SumKDS3GVgYkY9ogQ2UqowpWrbTWfEyud3u72H5sMPV2HZLHunYNtptkDVCplOByIK_-JZnWDKSGAbz8A763m9gMX1hGCy2Gm4sBmu4gH9uUIla2i2Ht4relYLeS7WJpt5LtXvKQuNglAiL-0vvpD5u_doU</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>215842195</pqid></control><display><type>article</type><title>Variations in software development practices</title><source>IEEE Electronic Library (IEL)</source><creator>Jones, C.</creator><creatorcontrib>Jones, C.</creatorcontrib><description>Research on over 18 years of software projects reveals that developing large systems involves substantially more activities and a greater variety of specialized personnel than developing smaller systems. Perhaps the most significant observation is that good quality control is the best overall indicator of a successful project. Schedule delays and cost overruns most often occur when you discover during testing that the application has so many bugs that it doesn't work. Projects using QA teams, formal design and code inspections, and pretest defect tracking always had shorter testing cycles and therefore were more likely to be deliverable on schedule.</description><identifier>ISSN: 0740-7459</identifier><identifier>EISSN: 1937-4194</identifier><identifier>DOI: 10.1109/MS.2003.1241362</identifier><identifier>CODEN: IESOEG</identifier><language>eng</language><publisher>Los Alamitos: IEEE</publisher><subject>Accounting ; Accounting systems ; Alliances ; Application software ; Architecture ; Benchmarks ; Buildings ; Business ; Companies ; Computer programs ; Computers ; Delay ; Design engineering ; Failure ; Inspection ; Management information systems ; Marine vehicles ; Military standards ; Occupations ; Personal computers ; Personnel ; Processes ; Productivity ; Programming ; Schedules ; Software ; Software development ; Success ; Telephony ; Tracking</subject><ispartof>IEEE software, 2003-11, Vol.20 (6), p.22-27</ispartof><rights>Copyright Institute of Electrical and Electronics Engineers, Inc. (IEEE) Nov/Dec 2003</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed><citedby>FETCH-LOGICAL-c395t-2191063cceaf63e61d8ae53cd4cddecb78f2d8a22b9062289e2e79f9752fb8883</citedby></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktohtml>$$Uhttps://ieeexplore.ieee.org/document/1241362$$EHTML$$P50$$Gieee$$H</linktohtml><link.rule.ids>314,776,780,792,27901,27902,54733</link.rule.ids><linktorsrc>$$Uhttps://ieeexplore.ieee.org/document/1241362$$EView_record_in_IEEE$$FView_record_in_$$GIEEE</linktorsrc></links><search><creatorcontrib>Jones, C.</creatorcontrib><title>Variations in software development practices</title><title>IEEE software</title><addtitle>S-M</addtitle><description>Research on over 18 years of software projects reveals that developing large systems involves substantially more activities and a greater variety of specialized personnel than developing smaller systems. Perhaps the most significant observation is that good quality control is the best overall indicator of a successful project. Schedule delays and cost overruns most often occur when you discover during testing that the application has so many bugs that it doesn't work. Projects using QA teams, formal design and code inspections, and pretest defect tracking always had shorter testing cycles and therefore were more likely to be deliverable on schedule.</description><subject>Accounting</subject><subject>Accounting systems</subject><subject>Alliances</subject><subject>Application software</subject><subject>Architecture</subject><subject>Benchmarks</subject><subject>Buildings</subject><subject>Business</subject><subject>Companies</subject><subject>Computer programs</subject><subject>Computers</subject><subject>Delay</subject><subject>Design engineering</subject><subject>Failure</subject><subject>Inspection</subject><subject>Management information systems</subject><subject>Marine vehicles</subject><subject>Military standards</subject><subject>Occupations</subject><subject>Personal computers</subject><subject>Personnel</subject><subject>Processes</subject><subject>Productivity</subject><subject>Programming</subject><subject>Schedules</subject><subject>Software</subject><subject>Software development</subject><subject>Success</subject><subject>Telephony</subject><subject>Tracking</subject><issn>0740-7459</issn><issn>1937-4194</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2003</creationdate><recordtype>article</recordtype><sourceid>RIE</sourceid><sourceid>8G5</sourceid><sourceid>BENPR</sourceid><sourceid>GUQSH</sourceid><sourceid>M2O</sourceid><recordid>eNp9kMtLw0AQhxdRsFbPHrwED3ox7ewj-zhK8QUtHqpel-1mAitpEndTxf_elBYED54GZr7fMPMRck5hQimY6WI5YQB8QpmgXLIDMqKGq1xQIw7JCJSAXInCHJOTlN4BoKAcRuTmzcXg-tA2KQtNltqq_3IRsxI_sW67NTZ91kXn--AxnZKjytUJz_Z1TF7v715mj_n8-eFpdjvPPTdFnzNqKEjuPbpKcpS01A4L7kvhyxL9SumKDS3GVgYkY9ogQ2UqowpWrbTWfEyud3u72H5sMPV2HZLHunYNtptkDVCplOByIK_-JZnWDKSGAbz8A763m9gMX1hGCy2Gm4sBmu4gH9uUIla2i2Ht4relYLeS7WJpt5LtXvKQuNglAiL-0vvpD5u_doU</recordid><startdate>20031101</startdate><enddate>20031101</enddate><creator>Jones, C.</creator><general>IEEE</general><general>IEEE Computer Society</general><scope>RIA</scope><scope>RIE</scope><scope>AAYXX</scope><scope>CITATION</scope><scope>3V.</scope><scope>7WY</scope><scope>7WZ</scope><scope>7XB</scope><scope>87Z</scope><scope>88F</scope><scope>88I</scope><scope>88K</scope><scope>8AL</scope><scope>8FE</scope><scope>8FG</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>F~G</scope><scope>GNUQQ</scope><scope>GUQSH</scope><scope>HCIFZ</scope><scope>JQ2</scope><scope>K60</scope><scope>K6~</scope><scope>K7-</scope><scope>L.-</scope><scope>L6V</scope><scope>M0C</scope><scope>M0N</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>PRINS</scope><scope>PTHSS</scope><scope>Q9U</scope><scope>7SC</scope><scope>8FD</scope><scope>L7M</scope><scope>L~C</scope><scope>L~D</scope><scope>7SP</scope><scope>F28</scope><scope>FR3</scope></search><sort><creationdate>20031101</creationdate><title>Variations in software development practices</title><author>Jones, C.</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-LOGICAL-c395t-2191063cceaf63e61d8ae53cd4cddecb78f2d8a22b9062289e2e79f9752fb8883</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2003</creationdate><topic>Accounting</topic><topic>Accounting systems</topic><topic>Alliances</topic><topic>Application software</topic><topic>Architecture</topic><topic>Benchmarks</topic><topic>Buildings</topic><topic>Business</topic><topic>Companies</topic><topic>Computer programs</topic><topic>Computers</topic><topic>Delay</topic><topic>Design engineering</topic><topic>Failure</topic><topic>Inspection</topic><topic>Management information systems</topic><topic>Marine vehicles</topic><topic>Military standards</topic><topic>Occupations</topic><topic>Personal computers</topic><topic>Personnel</topic><topic>Processes</topic><topic>Productivity</topic><topic>Programming</topic><topic>Schedules</topic><topic>Software</topic><topic>Software development</topic><topic>Success</topic><topic>Telephony</topic><topic>Tracking</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>Jones, C.</creatorcontrib><collection>IEEE All-Society Periodicals Package (ASPP) 1998-Present</collection><collection>IEEE Electronic Library (IEL)</collection><collection>CrossRef</collection><collection>ProQuest Central (Corporate)</collection><collection>ABI/INFORM Collection</collection><collection>ABI/INFORM Global (PDF only)</collection><collection>ProQuest Central (purchase pre-March 2016)</collection><collection>ABI/INFORM Global (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>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>ABI/INFORM Global (Corporate)</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>ABI/INFORM Professional Advanced</collection><collection>ProQuest Engineering Collection</collection><collection>ABI/INFORM Global</collection><collection>Computing 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>ProQuest Central China</collection><collection>Engineering Collection</collection><collection>ProQuest Central Basic</collection><collection>Computer and Information Systems Abstracts</collection><collection>Technology Research Database</collection><collection>Advanced Technologies Database with Aerospace</collection><collection>Computer and Information Systems Abstracts Academic</collection><collection>Computer and Information Systems Abstracts Professional</collection><collection>Electronics & Communications Abstracts</collection><collection>ANTE: Abstracts in New Technology & Engineering</collection><collection>Engineering Research Database</collection><jtitle>IEEE software</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext_linktorsrc</fulltext></delivery><addata><au>Jones, C.</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Variations in software development practices</atitle><jtitle>IEEE software</jtitle><stitle>S-M</stitle><date>2003-11-01</date><risdate>2003</risdate><volume>20</volume><issue>6</issue><spage>22</spage><epage>27</epage><pages>22-27</pages><issn>0740-7459</issn><eissn>1937-4194</eissn><coden>IESOEG</coden><abstract>Research on over 18 years of software projects reveals that developing large systems involves substantially more activities and a greater variety of specialized personnel than developing smaller systems. Perhaps the most significant observation is that good quality control is the best overall indicator of a successful project. Schedule delays and cost overruns most often occur when you discover during testing that the application has so many bugs that it doesn't work. Projects using QA teams, formal design and code inspections, and pretest defect tracking always had shorter testing cycles and therefore were more likely to be deliverable on schedule.</abstract><cop>Los Alamitos</cop><pub>IEEE</pub><doi>10.1109/MS.2003.1241362</doi><tpages>6</tpages></addata></record> |
| fulltext | fulltext_linktorsrc |
| identifier | ISSN: 0740-7459 |
| ispartof | IEEE software, 2003-11, Vol.20 (6), p.22-27 |
| issn | 0740-7459 1937-4194 |
| language | eng |
| recordid | cdi_proquest_miscellaneous_28820680 |
| source | IEEE Electronic Library (IEL) |
| subjects | Accounting Accounting systems Alliances Application software Architecture Benchmarks Buildings Business Companies Computer programs Computers Delay Design engineering Failure Inspection Management information systems Marine vehicles Military standards Occupations Personal computers Personnel Processes Productivity Programming Schedules Software Software development Success Telephony Tracking |
| title | Variations in software development practices |
| url | https://sfx.bib-bvb.de/sfx_tum?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-02-02T14%3A31%3A22IST&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=Variations%20in%20software%20development%20practices&rft.jtitle=IEEE%20software&rft.au=Jones,%20C.&rft.date=2003-11-01&rft.volume=20&rft.issue=6&rft.spage=22&rft.epage=27&rft.pages=22-27&rft.issn=0740-7459&rft.eissn=1937-4194&rft.coden=IESOEG&rft_id=info:doi/10.1109/MS.2003.1241362&rft_dat=%3Cproquest_RIE%3E901677436%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=215842195&rft_id=info:pmid/&rft_ieee_id=1241362&rfr_iscdi=true |