Инжењеринг софтвера — разлика између измена

С Википедије, слободне енциклопедије
Садржај обрисан Садржај додат
Спашавам 1 извора и означавам 1 мртвим.) #IABot (v2.0.8.5
.
Ред 1: Ред 1:
{{short description|Рачунарска дисциплина}}
{{Развојни циклус софтвера}}
{{Развојни циклус софтвера}}

'''Инжењеринг софтвера''' је поддисциплина [[рачунарство|рачунарства]], настала као потреба за проналажење рјешења све више сложенијих, обимнијих и структурно компликованијих [[инжењерство|инжењерских]] задатака, приликом дизајна, имплементације и одржавања [[софтвер]]а (рачунарских програма), која често захтијевају тимове програмера различитих профила и специјализације, као и вријеме које се све чешће мјери годинама. Развој сложених софтверских рјешења, као што је на примјер, [[оперативни систем]], се третира као инжењерски подухват са сличним потешкоћама као што је изградња неког [[архитектура|архитектонског]] објекта, али и са сличним пажљивим планирањем израде, али и планирањем одржавања крајњег софтверског производа.
'''Инжењеринг софтвера''' је поддисциплина [[рачунарство|рачунарства]], настала као потреба за проналажење рјешења све више сложенијих, обимнијих и структурно компликованијих [[инжењерство|инжењерских]] задатака,<ref name="BoDu04">{{harvnb |Abran |Moore |Bourque| Dupuis |2004 |pp=1–1}}</ref><ref name="ACM 2020">{{cite web |last=ACM |year=2007 |url=http://computingcareers.acm.org/?page_id=12|title=Computing Degrees & Careers |publisher=ACM |access-date=2010-11-23}}</ref><ref name="Laplante 2007">{{cite book |last=Laplante |first=Phillip |title=What Every Engineer Should Know about Software Engineering |publisher=CRC |location=Boca Raton |year=2007 |isbn=978-0-8493-7228-5 |url=https://books.google.com/books?id=pFHYk0KWAEgC&q=What%20Every%20Engineer%20Should%20Know%20about%20Software%20Engineering.&pg=PA1 |access-date=2011-01-21 }}</ref> приликом дизајна, имплементације и одржавања [[софтвер]]а (рачунарских програма), која често захтијевају тимове програмера различитих профила и специјализације, као и вријеме које се све чешће мјери годинама. Развој сложених софтверских рјешења, као што је на примјер, [[оперативни систем]], се третира као инжењерски подухват са сличним потешкоћама као што је изградња неког [[архитектура|архитектонског]] објекта, али и са сличним пажљивим планирањем израде, али и планирањем одржавања крајњег софтверског производа.


Процес инжењеринга софтвера се обично састоји из више фаза, дефинисаних на различите начине, али у основи уопштено сљедећих:
Процес инжењеринга софтвера се обично састоји из више фаза, дефинисаних на различите начине, али у основи уопштено сљедећих:
Ред 9: Ред 11:
# тестирање софтверског рјешења у реалном окружење, и на крају
# тестирање софтверског рјешења у реалном окружење, и на крају
# одржавање софтвера.
# одржавање софтвера.

== Историја ==
{{Main|Историја софтверског инжењерства}}
{{рут}}
Beginning in the 1960s, software engineering was seen as its own type of [[engineering]]. Additionally, the development of software engineering was seen as a struggle. It was difficult to keep up with the hardware which caused many problems for software engineers. Problems included software that was over budget, exceeded deadlines, required extensive [[Debugging|de-bugging]] and maintenance, and unsuccessfully met the needs of consumers or was never even completed. In 1968 [[NATO]] held the first Software Engineering conference where issues related to software were addressed: guidelines and best practices for the development of software were established. <ref>{{Cite web|title=The history of coding and software engineering|url=https://www.hackreactor.com/blog/the-history-of-coding-and-software-engineering|access-date=2021-05-06|website=www.hackreactor.com|language=en-US}}</ref>

The origins of the term "software engineering" have been attributed to various sources. The term "software engineering" appeared in a list of services offered by companies in the June 1965 issue of [http://www.bitsavers.org/magazines/Computers_And_Automation/196506.pdf COMPUTERS and AUTOMATION] and was used more formally in the August 1966 issue of Communications of the ACM (Volume 9, number 8) “letter to the ACM membership” by the ACM President Anthony A. Oettinger,<ref>{{cite journal |last=Oettinger|first=A. G.|title=President's Letter to the ACM Membership|year =1966| publisher = Association for Computing Machinery| volume = 9| number = 8|issn = 0001-0782| doi = 10.1145/365758.3291288| journal = Commun. ACM|pages = 545–546|s2cid=53432801|doi-access = free}}</ref><ref>{{cite web
| url = https://bertrandmeyer.com/2013/04/04/the-origin-of-software-engineering/
| title = The origin of "software engineering"
| access-date = 17 November 2017}}</ref> it is also associated with the title of a NATO conference in 1968 by Professor [[Friedrich L. Bauer]], the first conference on software engineering.<ref>{{cite web
| url = http://homepages.cs.ncl.ac.uk/brian.randell/NATO/NATOReports/
| title = The 1968/69 NATO Software Engineering Reports
| last = Randall | first = Brian
| access-date = 17 November 2017}}</ref> Independently, [[Margaret Hamilton (software engineer)|Margaret Hamilton]] named the discipline "software engineering" during the Apollo missions to give what they were doing legitimacy.<ref>{{cite web |url=https://publications.computer.org/software-magazine/2018/06/08/margaret-hamilton-software-engineering-pioneer-apollo-11/ |title=What to Know About the Scientist who Invented the Term "Software Engineering" |author=Software Magazine | access-date = February 12, 2019 | archive-url = https://web.archive.org/web/20181124103748/https://publications.computer.org/software-magazine/2018/06/08/margaret-hamilton-software-engineering-pioneer-apollo-11/ | archive-date = November 24, 2018 | url-status = live |author-link=Software Magazine }}</ref> At the time there was perceived to be a "[[software crisis]]".<ref>{{harvnb|Sommerville|2008|p=26}}</ref><ref>{{cite conference|author-first1=Naur|author-last1=Peter|author-first2=Brian |author-last2=Randell|author-link2=Brian Randell| title = Software Engineering: Report of a conference sponsored by the NATO Science Committee| publisher = Scientific Affairs Division, NATO| date = 7–11 October 1968| location = Garmisch, Germany| url = http://homepages.cs.ncl.ac.uk/brian.randell/NATO/nato1968.PDF| access-date = 2008-12-26}}</ref><ref>{{cite web | url = http://homepages.cs.ncl.ac.uk/brian.randell/NATO/NATOReports/index.html| title = The 1968/69 NATO Software Engineering Reports| access-date = 2008-10-11 | last = Randell | first = Brian | author-link = Brian Randell|date = 10 August 2001| work = Brian Randell's University Homepage| publisher = The School of the Computer Sciences, Newcastle University| quote = The idea for the first NATO Software Engineering Conference, and in particular that of adopting the then practically unknown term "software engineering" as its (deliberately provocative) title, I believe came originally from Professor [[Friedrich L. Bauer|Fritz Bauer]].}}</ref> The 40th International Conference on Software Engineering (ICSE 2018) celebrates 50 years of "Software Engineering" with the Plenary Sessions' keynotes of [[Frederick Brooks]]<ref>{{cite web
| url = https://www.youtube.com/watch?v=StN49re9Nq8&t=67s | title = ICSE 2018 – Plenary Sessions – Fred Brooks | author = 2018 International Conference on Software Engineering celebrating its 40th anniversary, and 50 years of Software engineering | access-date = 9 August 2018}}</ref> and [[Margaret Hamilton (scientist)|Margaret Hamilton]].<ref>{{cite web
| url = https://www.youtube.com/watch?v=ZbVOF0Uk5lU | title = ICSE 2018 – Plenary Sessions – Margaret Hamilton | author = 2018 International Conference on Software Engineering celebrating its 40th anniversary, and 50 years of Software engineering | access-date = 9 August 2018}}</ref>

In 1984, the [[Software Engineering Institute]] (SEI) was established as a federally funded research and development center headquartered on the campus of Carnegie Mellon University in Pittsburgh, Pennsylvania, United States. [[Watts Humphrey]] founded the SEI Software Process Program, aimed at understanding and managing the software engineering process. The Process Maturity Levels introduced would become the Capability Maturity Model Integration for Development(CMMI-DEV), which has defined how the US Government evaluates the abilities of a software development team.

Modern, generally accepted best-practices for software engineering have been collected by the [[ISO/IEC JTC 1/SC 7]] subcommittee and published as the [[Software Engineering Body of Knowledge]] (SWEBOK).<ref>{{cite web |url=http://www.iso.org/iso/iso_catalogue/catalogue_tc/catalogue_detail.htm?csnumber=33897|title=ISO/IEC TR 19759:2005|access-date=2012-04-01}}</ref> Software engineering is considered one of major [[computing]] disciplines.<ref>{{Cite web|date=2014-10-21|title=The Joint Task Force for Computing Curricula 2005|url=http://www.acm.org/education/curric_vols/CC2005-March06Final.pdf|url-status=live|archive-url=https://web.archive.org/web/20141021153204/http://www.acm.org/education/curric_vols/CC2005-March06Final.pdf|archive-date=2014-10-21|access-date=2020-04-16}}</ref>

== Референце ==
{{Reflist|}}


== Литература ==
== Литература ==
{{refbegin|2}}
{{refbegin|30em}}
* {{Cite book | ref= harv|first=Alain |last=Abran |first2=James W. |last2=Moore |first3=Pierre |last3=Bourque |first4=Robert |last4=Dupuis |first5=Leonard L. |last5=Tripp |title=Guide to the Software Engineering Body of Knowledge |year=2004 |publisher=IEEE |isbn=978-0-7695-2330-9 }}
* {{Cite book | ref= harv|first=Alain |last=Abran |first2=James W. |last2=Moore |first3=Pierre |last3=Bourque |first4=Robert |last4=Dupuis |first5=Leonard L. |last5=Tripp |title=Guide to the Software Engineering Body of Knowledge |year=2004 |publisher=IEEE |isbn=978-0-7695-2330-9 }}
* {{Cite book | ref= harv|last=Sommerville |first=Ian |title=Software Engineering |edition=7 |url=https://books.google.com/books?id=PqsWaBkFh1wC |accessdate = 10. 1. 2013. |year=2008 |publisher=Pearson Education |isbn=978-81-7758-530-8}}
* {{Cite book | ref= harv|last=Sommerville |first=Ian |title=Software Engineering |edition=7 |url=https://books.google.com/books?id=PqsWaBkFh1wC |accessdate = 10. 1. 2013. |year=2008 |publisher=Pearson Education |isbn=978-81-7758-530-8}}
* {{Cite book | ref= harv|last= Ghezzi|first=Carlo | title = Fundamentals of Software Engineering| url= https://archive.org/details/fundamentalsofso0000ghez_t0y0|origyear = 1991 | edition = 2nd (International) |year=2003| publisher = Pearson Education @ Prentice-Hall | author2=Mehdi Jazayeri, Dino Mandrioli}}
* {{Cite book | ref= harv|last= Ghezzi|first=Carlo | title = Fundamentals of Software Engineering| url= https://archive.org/details/fundamentalsofso0000ghez_t0y0|origyear = 1991 | edition = 2nd (International) |year=2003| publisher = Pearson Education @ Prentice-Hall | author2=Mehdi Jazayeri, Dino Mandrioli}}
* {{Cite book |ref=harv |last=Jalote |first=Pankaj |title=An Integrated Approach to Software Engineering |origyear=1991 |url=http://www.springer.com/east/home?SGWisbn=5-102-22-52090005-0&changeHeader=true |edition=3rd |year=2005 |publisher=Springer |location= |isbn=978-0-387-20881-7 }}{{Мртва веза}}
* {{Cite book |ref=harv |last=Jalote |first=Pankaj |title=An Integrated Approach to Software Engineering |origyear=1991 |url= https://dl.acm.org/doi/10.5555/1098691 |edition=3rd |year=2005 |publisher=Springer |location= |isbn=978-0-387-20881-7 }}
* {{Cite book | ref= harv|last= Pressman|first=Roger S | title = Software Engineering: A Practitioner's Approach | url= https://archive.org/details/softwareengineer0000roge|origyear = | edition = 6th |year=2005| publisher = McGraw-Hill | location = Boston, Mass|isbn=978-0-07-285318-6}}
* {{Cite book | ref= harv|last= Pressman|first=Roger S | title = Software Engineering: A Practitioner's Approach | url= https://archive.org/details/softwareengineer0000roge|origyear = | edition = 6th |year=2005| publisher = McGraw-Hill | location = Boston, Mass|isbn=978-0-07-285318-6}}
* {{Cite book | ref= harv|last= Sommerville|first=Ian | title = Software Engineering|origyear = 1982 |url=http://www.pearsoned.co.uk/HigherEducation/Booksby/Sommerville/ | edition = 8th |year=2007| publisher = Pearson Education | location = Harlow, England |isbn=978-0-321-31379-9 }}
* {{Cite book | ref= harv|last= Sommerville|first=Ian | title = Software Engineering|origyear = 1982 |url=http://www.pearsoned.co.uk/HigherEducation/Booksby/Sommerville/ | edition = 8th |year=2007| publisher = Pearson Education | location = Harlow, England |isbn=978-0-321-31379-9 }}
* {{Cite book|last1=Bruegge|first1=Bernd|author-link1=Bernd Bruegge|last2=Dutoit|first2=Allen|edition=3rd|year=2009|title=Object-oriented software engineering : using UML, patterns, and Java|publisher=Prentice Hall|isbn=978-0-13-606125-0|url-access=registration|url=https://archive.org/details/objectorientedso0000brue}}
*{{cite book |last1=Oshana |first1=Robert |title=Software engineering for embedded systems : methods, practical techniques, and applications |publisher=Kidlington, Oxford, United Kingdom |isbn=978-0-12-809433-4 |edition=Second|date=2019-06-21 }}
*''About Face: The Essentials of User Interface Design'' by [[Alan Cooper]], about user interface design. {{ISBN|0-7645-2641-3}}
*''The Capability Maturity Model'' by [[Watts Humphrey]]. Written for the [[Software Engineering Institute]], emphasizing management and process. (See ''Managing the Software Process'' {{ISBN|0-201-18095-2}})
*''[[The Cathedral and the Bazaar]]'' by [[Eric S. Raymond|Eric Raymond]] about open source development.
*''The Decline and Fall of the American Programmer'' by [[Ed Yourdon]] predicts the end of software development in the U.S. {{ISBN|0-13-191958-X}}
*''[[Design Patterns (book)|Design Patterns]]'' by [[Erich Gamma]], [[Richard Helm]], [[Ralph Johnson (computer scientist)|Ralph Johnson]], and [[John Vlissides]]. {{ISBN|0-201-63361-2}}
*''Extreme Programming Explained'' by [[Kent Beck]] {{ISBN|0-321-27865-8}}
*"[https://web.archive.org/web/20070703050443/http://www.acm.org/classics/oct95/ Go To Statement Considered Harmful]" by [[Edsger Dijkstra]].
*"Internet, Innovation and Open Source:Actors in the Network" — ''[[First Monday (journal)|First Monday]]'' article by [[Ilkka Tuomi]] (2000) [http://www.firstmonday.org/issues/issue6_1/tuomi/#t9 source]
*''[[The Mythical Man-Month]]'' by [[Fred Brooks]], about project management. {{ISBN|0-201-83595-9}}
*''Object-oriented Analysis and Design'' by [[Grady Booch]]. {{ISBN|0-8053-5340-2}}
*''[[Peopleware]]'' by [[Tom DeMarco]] and Tim Lister. {{ISBN|0-932633-43-9}}
*''The pragmatic engineer versus the scientific designer'' by [[Edsger Wybe Dijkstra|E. W. Dijkstra]] [https://www.cs.utexas.edu/users/EWD/transcriptions/EWD06xx/EWD690.html]
*''Principles of Software Engineering Management'' by [[Tom Gilb]] about evolutionary processes. {{ISBN|0-201-19246-2}}
*''The Psychology of Computer Programming'' by [[Gerald Weinberg]]. Written as an independent consultant, partly about his years at IBM. {{ISBN|0-932633-42-0}}
*''Refactoring: Improving the Design of Existing Code'' by [[Martin Fowler (software engineer)|Martin Fowler]], [[Kent Beck]], John Brant, [[William Opdyke]], and Don Roberts. {{ISBN|0-201-48567-2}}
*''[http://www.pragmaticprogrammer.com The Pragmatic Programmer: from journeyman to master]'' by [[Andy Hunt (author)|Andrew Hunt]], and [[Dave Thomas (programmer)|David Thomas]]. {{ISBN|0-201-61622-X}}
*''[[Software Engineering Body of Knowledge]] (SWEBOK)'' ISO/IEC TR 19759
* {{cite book|editor-last=Laplante|editor-first=Phillip|title=Great papers in computer science|year=1996|publisher=IEEE Press|location=New York|isbn=978-0-314-06365-6}}
* [[Brian Randell|Randell, Brian]] (ed). (1982). ''The Origins of Digital Computers: Selected Papers.'' 3rd ed. Berlin: Springer-Verlag. {{ISBN|0-387-11319-3}}.
* Turning Points in Computing: 1962–1999, Special Issue, ''IBM Systems Journal, 38'' (2/3),1999.
* [[Ed Yourdon|Yourdon, Edward]] (ed.) (1979) ''Classics in Software Engineering.'' New York: Yourdon Press. {{ISBN|0-917072-14-6}}
* {{cite journal | title = No Silver Bullet&nbsp;— Essence and Accidents of Software Engineering | last = Brooks | first = Fred P. | author-link = Fred Brooks | author-mask = 1 | journal = [[Computer (magazine)|IEEE Computer]] | volume = 20 | issue = 4 | date = April 1987 | pages = 10–19 | ref = Brooks, IEEE Computer| doi = 10.1109/MC.1987.1663532 | citeseerx = 10.1.1.117.315 | s2cid = 372277 }}
* {{cite book|last1=Wilkinson|first1=J. H.|author-link=James H. Wilkinson |first2=C. |last2=Reinsch |title=Linear algebra, volume II of Handbook for Automatic Computation|year=1971|publisher=Springer|isbn=978-0-387-05414-8}}
* {{Citation | last1 = Golub | first1 = Gene H. |author-link=Gene H. Golub | last2 = van Loan | first2 = Charles F. |author2-link=Charles F. Van Loan | title = Matrix Computations, 3rd edition | publisher = Johns Hopkins University Press | year = 1996 |orig-year=1983 | isbn = 978-0-8018-5414-9}}
* {{Cite journal | first = Lawrence R. | last = Rabiner | author-link = Lawrence Rabiner | title = A tutorial on hidden Markov models and selected applications in speech recognition | journal = [[Proceedings of the IEEE]] | volume = 77 | issue = 2 | pages = 257–286 | year = 1989 | doi=10.1109/5.18626 | citeseerx = 10.1.1.381.3454 }}
*{{Cite journal | first = Eric | last = Brill | author-link = Eric Brill | title = Transformation-based error-driven learning and natural language processing: A case study in part-of-speech tagging | journal = [[Computational Linguistics (journal)|Computational Linguistics]] | volume = 21 | issue = 4 | pages = 543–566 | year = 1995
}}

{{refend}}
{{refend}}

== Спољашње везе ==
== Спољашње везе ==
{{Commonscat|Software engineering}}
{{Commonscat|Software engineering}}
Ред 24: Ред 80:
* [http://www.bls.gov/oco/ocos267.htm -{Computer Software Engineers] {{Wayback|url=http://www.bls.gov/oco/ocos267.htm |date=20100327215644 }} - Definition and statistics from the U.S. Bureau of Labor Statistics}-
* [http://www.bls.gov/oco/ocos267.htm -{Computer Software Engineers] {{Wayback|url=http://www.bls.gov/oco/ocos267.htm |date=20100327215644 }} - Definition and statistics from the U.S. Bureau of Labor Statistics}-
* [https://web.archive.org/web/20190616143329/http://www.studentprojectguide.info/ -{A Student's Guide to Software Engineering Projects] - a free online guide for students taking SE project courses}-
* [https://web.archive.org/web/20190616143329/http://www.studentprojectguide.info/ -{A Student's Guide to Software Engineering Projects] - a free online guide for students taking SE project courses}-
* [http://opensdlc.org/ The Open Systems Engineering and Software Development Life Cycle Framework] OpenSDLC.org the integrated Creative Commons SDLC
* [http://www.sei.cmu.edu/ Software Engineering Institute] Carnegie Mellon


{{Технологија}}
{{Технологија}}

Верзија на датум 15. јануар 2022. у 06:53

Инжењеринг софтвера је поддисциплина рачунарства, настала као потреба за проналажење рјешења све више сложенијих, обимнијих и структурно компликованијих инжењерских задатака,[1][2][3] приликом дизајна, имплементације и одржавања софтвера (рачунарских програма), која често захтијевају тимове програмера различитих профила и специјализације, као и вријеме које се све чешће мјери годинама. Развој сложених софтверских рјешења, као што је на примјер, оперативни систем, се третира као инжењерски подухват са сличним потешкоћама као што је изградња неког архитектонског објекта, али и са сличним пажљивим планирањем израде, али и планирањем одржавања крајњег софтверског производа.

Процес инжењеринга софтвера се обично састоји из више фаза, дефинисаних на различите начине, али у основи уопштено сљедећих:

  1. идентификовање и анализа потреба и захтјева корисника,
  2. анализа, дизајн и развој спецификација система (хардвера и софтвера),
  3. дизајн софтвера (који се обично састоји од више међусобно повезаних задатака, као што је на примјер, дизајн одговарајућих алгоритама, корисничког интерфејса, итд.),
  4. имплементација (писање кода и неопходне документације за софтвер),
  5. тестирање софтверског рјешења у реалном окружење, и на крају
  6. одржавање софтвера.

Историја

Beginning in the 1960s, software engineering was seen as its own type of engineering. Additionally, the development of software engineering was seen as a struggle. It was difficult to keep up with the hardware which caused many problems for software engineers. Problems included software that was over budget, exceeded deadlines, required extensive de-bugging and maintenance, and unsuccessfully met the needs of consumers or was never even completed. In 1968 NATO held the first Software Engineering conference where issues related to software were addressed: guidelines and best practices for the development of software were established. [4]

The origins of the term "software engineering" have been attributed to various sources. The term "software engineering" appeared in a list of services offered by companies in the June 1965 issue of COMPUTERS and AUTOMATION and was used more formally in the August 1966 issue of Communications of the ACM (Volume 9, number 8) “letter to the ACM membership” by the ACM President Anthony A. Oettinger,[5][6] it is also associated with the title of a NATO conference in 1968 by Professor Friedrich L. Bauer, the first conference on software engineering.[7] Independently, Margaret Hamilton named the discipline "software engineering" during the Apollo missions to give what they were doing legitimacy.[8] At the time there was perceived to be a "software crisis".[9][10][11] The 40th International Conference on Software Engineering (ICSE 2018) celebrates 50 years of "Software Engineering" with the Plenary Sessions' keynotes of Frederick Brooks[12] and Margaret Hamilton.[13]

In 1984, the Software Engineering Institute (SEI) was established as a federally funded research and development center headquartered on the campus of Carnegie Mellon University in Pittsburgh, Pennsylvania, United States. Watts Humphrey founded the SEI Software Process Program, aimed at understanding and managing the software engineering process. The Process Maturity Levels introduced would become the Capability Maturity Model Integration for Development(CMMI-DEV), which has defined how the US Government evaluates the abilities of a software development team.

Modern, generally accepted best-practices for software engineering have been collected by the ISO/IEC JTC 1/SC 7 subcommittee and published as the Software Engineering Body of Knowledge (SWEBOK).[14] Software engineering is considered one of major computing disciplines.[15]

Референце

  1. ^ Abran et al. 2004, стр. 1–1
  2. ^ ACM (2007). „Computing Degrees & Careers”. ACM. Приступљено 2010-11-23. 
  3. ^ Laplante, Phillip (2007). What Every Engineer Should Know about Software Engineering. Boca Raton: CRC. ISBN 978-0-8493-7228-5. Приступљено 2011-01-21. 
  4. ^ „The history of coding and software engineering”. www.hackreactor.com (на језику: енглески). Приступљено 2021-05-06. 
  5. ^ Oettinger, A. G. (1966). „President's Letter to the ACM Membership”. Commun. ACM. Association for Computing Machinery. 9 (8): 545—546. ISSN 0001-0782. S2CID 53432801. doi:10.1145/365758.3291288Слободан приступ. 
  6. ^ „The origin of "software engineering". Приступљено 17. 11. 2017. 
  7. ^ Randall, Brian. „The 1968/69 NATO Software Engineering Reports”. Приступљено 17. 11. 2017. 
  8. ^ Software Magazine. „What to Know About the Scientist who Invented the Term "Software Engineering". Архивирано из оригинала 24. 11. 2018. г. Приступљено 12. 2. 2019. 
  9. ^ Sommerville 2008, стр. 26
  10. ^ Peter, Naur; Randell, Brian (7—11. 10. 1968). Software Engineering: Report of a conference sponsored by the NATO Science Committee (PDF). Garmisch, Germany: Scientific Affairs Division, NATO. Приступљено 2008-12-26. 
  11. ^ Randell, Brian (10. 8. 2001). „The 1968/69 NATO Software Engineering Reports”. Brian Randell's University Homepage. The School of the Computer Sciences, Newcastle University. Приступљено 2008-10-11. „The idea for the first NATO Software Engineering Conference, and in particular that of adopting the then practically unknown term "software engineering" as its (deliberately provocative) title, I believe came originally from Professor Fritz Bauer. 
  12. ^ 2018 International Conference on Software Engineering celebrating its 40th anniversary, and 50 years of Software engineering. „ICSE 2018 – Plenary Sessions – Fred Brooks”. Приступљено 9. 8. 2018. 
  13. ^ 2018 International Conference on Software Engineering celebrating its 40th anniversary, and 50 years of Software engineering. „ICSE 2018 – Plenary Sessions – Margaret Hamilton”. Приступљено 9. 8. 2018. 
  14. ^ „ISO/IEC TR 19759:2005”. Приступљено 2012-04-01. 
  15. ^ „The Joint Task Force for Computing Curricula 2005” (PDF). 2014-10-21. Архивирано (PDF) из оригинала 2014-10-21. г. Приступљено 2020-04-16. 

Литература

Спољашње везе