Bibliographies thématiques / Software engineering

Littérature scientifique sur le sujet « Software engineering »

Auteur : Grafiati
Publié le 4 juin 2021
Mis à jour le 22 juin 2024

Créez une référence correcte selon les styles APA, MLA, Chicago, Harvard et plusieurs autres

Choisissez une source :

Sommaire

Consultez les listes thématiques d’articles de revues, de livres, de thèses, de rapports de conférences et d’autres sources académiques sur le sujet « Software engineering ».

À côté de chaque source dans la liste de références il y a un bouton « Ajouter à la bibliographie ». Cliquez sur ce bouton, et nous générerons automatiquement la référence bibliographique pour la source choisie selon votre style de citation préféré : APA, MLA, Harvard, Vancouver, Chicago, etc.

Vous pouvez aussi télécharger le texte intégral de la publication scolaire au format pdf et consulter son résumé en ligne lorsque ces informations sont inclues dans les métadonnées.

Articles de revues sur le sujet "Software engineering"

1

Anand, Prabhjot Singh, Deepak Chahal et Latika Kharb. « Tools for Software Re-Engineering ». International Journal of Trend in Scientific Research and Development Volume-3, Issue-1 (31 décembre 2018) : 600–603. http://dx.doi.org/10.31142/ijtsrd19032.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
2

Sharad, Prof Sushmitha. « The need for Software Engineering ». Global Journal For Research Analysis 3, no 1 (15 juin 2012) : 45. http://dx.doi.org/10.15373/22778160/january2014/72.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
3

Notkin, David. « Software, Software Engineering and Software Engineering Research : Some Unconventional Thoughts ». Journal of Computer Science and Technology 24, no 2 (mars 2009) : 189–97. http://dx.doi.org/10.1007/s11390-009-9217-4.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
4

Rine, David. « A note on software engineering, software systems engineering and software design ». ACM SIGSOFT Software Engineering Notes 18, no 4 (octobre 1993) : 16–18. http://dx.doi.org/10.1145/163626.163629.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
5

Denert, Ernst. « Software Engineering ». Informatik Spektrum 44, no 2 (10 février 2021) : 122–25. http://dx.doi.org/10.1007/s00287-021-01338-y.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
6

Parnas, David Lorge. « Software engineering ». Communications of the ACM 40, no 9 (septembre 1997) : 128. http://dx.doi.org/10.1145/260750.260784.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
7

Christiaanse, Vance. « Software engineering ». 3C ON-LINE 4, no 3 (juillet 1997) : 12–13. http://dx.doi.org/10.1145/270877.270881.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
8

Loka, Raghavendra Rao. « Software engineering ». ACM SIGSOFT Software Engineering Notes 17, no 3 (juillet 1992) : 34–38. http://dx.doi.org/10.1145/140938.140941.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
9

Ellis, Heidi. « Software engineering ». ACM SIGSOFT Software Engineering Notes 32, no 1 (janvier 2007) : 4. http://dx.doi.org/10.1145/1226816.1226822.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
10

Kazman, Rick. « Software Engineering ». Computer 50, no 7 (2017) : 10–11. http://dx.doi.org/10.1109/mc.2017.184.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
Plus de sources

Thèses sur le sujet "Software engineering"

1

Le, Gal Thierry. « Re-engineering software for integration using computer aided software engineering ». Thesis, This resource online, 1992. http://scholar.lib.vt.edu/theses/available/etd-06232009-063016/.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
2

CHRISTOPH, ROBERTO DE HOLANDA. « SOFTWARE ENGINEERING FOR OPEN SOURCE SOFTWARE ». PONTIFÍCIA UNIVERSIDADE CATÓLICA DO RIO DE JANEIRO, 2004. http://www.maxwell.vrac.puc-rio.br/Busca_etds.php?strSecao=resultado&nrSeq=4854@1.

Texte intégral
Résumé :
Software livres têm despertado bastante atenção, não apenas devido a popularidade obtida por alguns destes como o Linux e o Apache, mas também pela forma singular como estes sistemas são desenvolvidos e sua quantidade de adeptos. No entanto, em alguns projetos de software livre, a documentação existente dificulta a entrada de novos participantes, já que devido a informalidade do processo de desenvolvimento deste tipo de software, é comum que a documentação do sistema não receba muita atenção. Este trabalho colabora para um melhor entendimento do desenvolvimento de software livres, relacionando-o com as questões de evolução de software. Será apresentada uma proposta utilizada no software livre C e L para documentar em termos da aplicação o código do sistema, utilizando-se do conceito de cenários. Será mostrado através de um protótipo que um software seguindo esse padrão proposto pode produzir uma documentação que torna mais fácil seu entendimento para novos participantes do projeto.
This thesis presents an introduction on the use of the thermal desorption technique that is based on the direct heating of the soil, for the remediation of contaminated areas. Heat propagation through soils can be mathematically simulated using coupled heat-moisture transfer theories. In order to make this simulation possible it is necessary to identify the required parameters: hydraulic conductivity as a function of volumetric water content, thermal conductivity as a function of volumetric water content, volumetric heat capacity, and soil-water characteristic curve. One technical description of such parameters is presented. Two different kinds of soils were used, one clay- sand (CH) and one sandclay (SC). A study physico-chemical was done talking into consideration the temperature effect on the soils with X-Ray, electron microscopic investigation, CTC, Atterberg Limits and at the particle size distribution. The study was done on pre-heated soils with temperatures ranging from 20 Celsius Degrees to 300 Celsius Degrees. Equipments and methodologies have been especially developed for the study of the thermo-hydraulics proprieties. The laboratory tests program consisted of hydraulic conductivity, retention curves and deformability, taking into account the temperature effects. During the tests it was observed that all parameters were temperature dependent. The thermal parameters, thermal conductivity and heat capacity were studied for both soils.
Styles APA, Harvard, Vancouver, ISO, etc.
3

Bondesson, Tobias. « Software Engineering Education Improvement : An Assessment of a Software Engineering Programme ». Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-5891.

Texte intégral
Résumé :
An assessment of a software engineering program has been carried out by reviewing state-of-the-art literature pertaining to software engineering education. Six surveys have been adopted and the result implies that the balance of the curriculum should be revised, and that software engineering education ought to expand the technical oriented knowledge areas somewhat. Relevant curriculum data have been derived hereby, which also confirms other studies in the area. This data, along with a benchmark of the software engineering program to the Software Engineering Body of Knowledge (SWEBOK), is very constructive to universities as it assists educators, trainers, and software engineering practitioners in evaluating, designing, and recommending existing and proposed curricula.
This is the final revision of the thesis. Author may be contacted on +464458038. See also paper at the 18th Conference on Software Engineering Education and Training (CSEE&T), Ottawa, Canada.
Styles APA, Harvard, Vancouver, ISO, etc.
4

Riehle, Richard D. « An engineering context for software engineering ». Monterey, Calif. : Naval Postgraduate School, 2008. http://edocs.nps.edu/npspubs/scholarly/theses/2008/Sept/08Sep%5FRiehle%5FPhD.pdf.

Texte intégral
Résumé :
Dissertation (Ph.D. in Software Engineering)--Naval Postgraduate School, September 2008.
Dissertation Supervisor(s): Michael, J. Bret. "September 2008." Description based on title screen as viewed on November 4, 2008. Includes bibliographical references (p. 111-120). Also available in print.
Styles APA, Harvard, Vancouver, ISO, etc.
5

Lim, Edwin C. « Software metrics for monitoring software engineering projects ». Thesis, Edith Cowan University, Research Online, Perth, Western Australia, 1994. https://ro.ecu.edu.au/theses/1100.

Texte intégral
Résumé :
As part of the undergraduate course offered by Edith Cowan University, the Department of Computer Science has (as part of a year's study) a software engineering group project. The structure of this project was divided into two units, Software Engineering l and Software Engineering 2. ln Software Engineering 1, students were given the group project where they had to complete and submit the Functional Requirement and Detail System Design documentation. In Software Engineering 2, students commenced with the implementation of the software, testing and documentation. The software was then submitted for assessment and presented to the client. To aid the students with the development of the software, the department had adopted EXECOM's APT methodology as its standard guideline. Furthermore, the students were divided into groups of 4 to 5, each group working on the same problem. A staff adviser was assigned to each project group. The purpose of this research exercise was to fulfil two objectives. The first objective was to ascertain whether there is a need to improve the final year software engineering project for future students by enhancing any aspect that may be regarded as deficient. The second objective was to ascertain the factors that have the most impact on the quality of the delivered software. The quality of the delivered software was measured using a variety of software metrics. Measurement of software has mostly been ignored until recently or used without true understanding of its purpose. A subsidiary objective was to gain an understanding of the worth of software measurement in the student environment One of the conclusions derived from the study suggests that teams who spent more time on software design and testing, tended to produce better quality software with less defects. The study also showed that adherence to the APT methodology led to the project being on schedule and general team satisfaction with the project management. One of the recommendations made to the project co-ordinator was that staff advisers should have sufficient knowledge of the software engineering process.
Styles APA, Harvard, Vancouver, ISO, etc.
6

Sezer, Bulent. « Software Engineering Process Improvement ». Master's thesis, METU, 2007. http://etd.lib.metu.edu.tr/upload/12608338/index.pdf.

Texte intégral
Résumé :
This thesis presents a software engineering process improvement study. The literature on software process improvement is reviewed. Then the current design verification process at one of the Software Engineering Departments of the X Company, Ankara, Tü
rkiye (SED) is analyzed. Static software development process metrics have been calculated for the SED based on a recently proposed approach. Some improvement suggestions have been made based on the metric values calculated according to the proposals of that study. Besides, the author'
s improvement suggestions have been discussed with the senior staff at the department and then final version of the improvements has been gathered. Then, a discussion has been made comparing these two approaches. Finally, a new software design verification process model has been proposed. Some of the suggestions have already been applied and preliminary results have been obtained.
Styles APA, Harvard, Vancouver, ISO, etc.
7

Boriani, Dario V. « Software engineering for control ». Thesis, University of Oxford, 1989. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.253293.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
8

Arciniegas-Mendez, Maryi. « Regulation in Software Engineering ». Thesis, Proceedings of the Eighth International Workshop on Cooperative and Human Aspects of Software Engineering, 2015. http://hdl.handle.net/1828/7524.

Texte intégral
Résumé :
Collaboration has become an integral part of software engineering. The widespread availability and adoption of social channels has led to a culture where developers participate and collaborate more frequently with one another. While collaboration in software engineering has been studied extensively, models and frameworks do not adequately capture how development team members “regulate” themselves, one another, and their projects. I borrow the term “regulate” from the learning sciences to refer to mindful processes developers engage in to determine what tasks they need to complete and who should be involved, what their goals are relative to those tasks, how they should meet their goals, what domain knowledge needs to be manipulated, and why they use a particular approach or tool. This research starts by borrowing constructs from the theory of regulated learning in the learning science domain, adapting and extending them as a model of collaboration for software engineering: the Model of Regulation. This model was composed to capture how individuals self-regulate their tasks, knowledge and motivation, how they regulate one another, and how they achieve a shared understanding of project goals and required tasks. The model provides a vocabulary for comparing and analyzing collaboration tools and processes. In this thesis, I present the Model of Regulation as a new and complementary theoretical model of collaboration for software engineering and showcase its potential by using the model to analyze features of a collaborative tool, gain insights into an open-source software development community and to create an instrument that investigates about collaboration practices and tool support in units of collaboration (e.g., group, project, community).
Graduate
Styles APA, Harvard, Vancouver, ISO, etc.
9

Loomes, Martin James. « Software engineering curriculum design ». Thesis, University of Surrey, 1991. http://epubs.surrey.ac.uk/844417/.

Texte intégral
Résumé :
Software engineering design is a vital component of modern industry, unfortunately, the processes involved are still poorly understood. This poses a major problem for teachers of the subject, who are under constant pressure to improve the quality of education, but are unsure how to bring this about, or even how to detect such improvement. This thesis attempts to start the process of clarifying what we mean by "software engineering design", and apply the insights gained to the activity of curriculum design. First, we establish a method for the research, by constructing a framework to constrain and guide the process of seeking new insights. This leads to a decidedly eclectic approach to the problem, as software engineering design is viewed, and reviewed, from a number of different perspectives. Next, these views are synthesised into a model of the software engineering design process, and new insights are sought to refine the model. The central theme of this model is the idea that the design process can be considered as a one of theory building. Finally, we bring this model into direct contact with the task of curriculum design, both in a general sense, and also by providing illustrations of some of the consequences of its use.
Styles APA, Harvard, Vancouver, ISO, etc.
10

Alrabghi, Leenah O. « QFD IN SOFTWARE ENGINEERING ». Kent State University / OhioLINK, 2014. http://rave.ohiolink.edu/etdc/view?acc_num=kent1385046526.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
Plus de sources

Livres sur le sujet "Software engineering"

1

Bjørner, D. Software engineering. Berlin : Springer, 2006.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
2

Schach, Stephen R. Software engineering. 2e éd. Homewood, IL : Aksen Associates, 1993.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
3

Pomberger, Gustav, et Wolfgang Pree. Software Engineering. München : Carl Hanser Verlag GmbH & ; Co. KG, 2004. http://dx.doi.org/10.3139/9783446227880.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
4

Sommerville, Ian. Software engineering. 7e éd. Harlow, Essex : Pearson/Addison-Wesley, 2004.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
5

Sommerville, Ian. Software engineering. 2e éd. Wokingham, Eng : Addison-Wesley, 1985.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
6

Sommerville, Ian. Software engineering. 4e éd. Wokingham, England : Addison-Wesley Pub. Co., 1992.

Trouver le texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
7

Rau, Karl-Heinz, et Eberhard Stickel. Software Engineering. Wiesbaden : Gabler Verlag, 1991. http://dx.doi.org/10.1007/978-3-322-86223-5.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
8

Meyer, Bertrand, et Martin Nordio, dir. Software Engineering. Cham : Springer International Publishing, 2015. http://dx.doi.org/10.1007/978-3-319-28406-4.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
9

Dumke, Reiner. Software Engineering. Wiesbaden : Vieweg+Teubner Verlag, 2000. http://dx.doi.org/10.1007/978-3-322-93944-9.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
10

Kahlbrandt, Bernd. Software Engineering. Berlin, Heidelberg : Springer Berlin Heidelberg, 1998. http://dx.doi.org/10.1007/978-3-662-00034-2.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
Plus de sources

Chapitres de livres sur le sujet "Software engineering"

1

Rombach, Dieter. « Engineering Software & ; Software Engineering ». Dans SOFSEM’ 98 : Theory and Practice of Informatics, 240–43. Berlin, Heidelberg : Springer Berlin Heidelberg, 1998. http://dx.doi.org/10.1007/3-540-49477-4_16.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
2

O’Regan, Gerard. « Software Engineering Tools Software Engineering Tools ». Dans Introduction to Software Quality, 271–87. Cham : Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-06106-1_16.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
3

Heimgärtner, Rüdiger. « Software Engineering ». Dans Human–Computer Interaction Series, 49–71. Cham : Springer International Publishing, 2019. http://dx.doi.org/10.1007/978-3-030-17427-9_3.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
4

Denert, Ernst. « Software Engineering ». Dans Ernst Denert Award for Software Engineering 2019, 11–17. Cham : Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-58617-1_2.

Texte intégral
Résumé :
Abstract“A Passion for Software-Engineering.” This was the headline of a 2015 newspaper article about Ernst Denert. And they were absolutely right. Ernst Denert is really passionate about developing software with excellent quality in a predictable and systematic style. Furthermore, he is very much interested in encouraging young people to study computer science or at least to learn how programming and digitalization works, as well as computer science students to focus on software engineering principles and software development. This chapter is a personal view of Ernst Denert on the software engineering discipline.
Styles APA, Harvard, Vancouver, ISO, etc.
5

Hering, Ekbert, Jürgen Gutekunst et Ulrich Dyllong. « Software-Engineering ». Dans Handbuch der praktischen und technischen Informatik, 195–355. Berlin, Heidelberg : Springer Berlin Heidelberg, 2000. http://dx.doi.org/10.1007/978-3-642-57287-6_4.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
6

Hering, Ekbert, Jürgen Gutekunst et Ulrich Dyllong. « Software-Engineering ». Dans Informatik für Ingenieure, 195–355. Berlin, Heidelberg : Springer Berlin Heidelberg, 1995. http://dx.doi.org/10.1007/978-3-662-00518-7_4.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
7

Koranne, Sandeep. « Software Engineering ». Dans Handbook of Open Source Tools, 47–104. Boston, MA : Springer US, 2010. http://dx.doi.org/10.1007/978-1-4419-7719-9_3.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
8

Harel, David, et Yishai Feldman. « Software Engineering ». Dans Algorithmics, 383–404. Berlin, Heidelberg : Springer Berlin Heidelberg, 1987. http://dx.doi.org/10.1007/978-3-642-27266-0_13.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
9

O’Regan, Gerard. « Software Engineering ». Dans Introduction to Software Quality, 35–57. Cham : Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-06106-1_2.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
10

O’Regan, Gerard. « Software Engineering ». Dans Mathematics in Computing, 71–87. London : Springer London, 2012. http://dx.doi.org/10.1007/978-1-4471-4534-9_4.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.

Actes de conférences sur le sujet "Software engineering"

1

Baxter, R. « Software engineering is software engineering ». Dans "Software Engineering for High Performance Computing System (HPCS) Applications" W3S Workshop - 26th International Conference on Software Engineering. IEE, 2004. http://dx.doi.org/10.1049/ic:20040411.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
2

Dillon, T. S., E. Chang et P. Wongthongtham. « Ontology-Based Software Engineering- Software Engineering 2.0 ». Dans 2008 19th Australian Conference on Software Engineering ASWEC. IEEE, 2008. http://dx.doi.org/10.1109/aswec.2008.4483185.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
3

Harman, Mark. « Software engineering ». Dans Proceeding of the fifteenth annual conference companion. New York, New York, USA : ACM Press, 2013. http://dx.doi.org/10.1145/2464576.2480770.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
4

« Software engineering ». Dans 8th International Multitopic Conference, 2004. Proceedings of INMIC 2004. IEEE, 2004. http://dx.doi.org/10.1109/inmic.2004.1492909.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
5

« Software engineering ». Dans Education (ICCSE). IEEE, 2009. http://dx.doi.org/10.1109/iccse.2009.5228168.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
6

Finkelstein, Anthony, et Jeff Kramer. « Software engineering ». Dans the conference. New York, New York, USA : ACM Press, 2000. http://dx.doi.org/10.1145/336512.336519.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
7

Gruszczynski, Robert. « Software Engineering as Engineering ». Dans SAE 2000 World Congress. 400 Commonwealth Drive, Warrendale, PA, United States : SAE International, 2000. http://dx.doi.org/10.4271/2000-01-0713.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
8

Wagstrom, Patrick. « Engineering software engineering teams ». Dans the 4th international workshop. New York, New York, USA : ACM Press, 2011. http://dx.doi.org/10.1145/2024645.2024654.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
9

Petkovic, Dragutin, Gary Thompson et Rainer Todtenhoefer. « Teaching practical software engineering and global software engineering ». Dans the 11th annual SIGCSE conference. New York, New York, USA : ACM Press, 2006. http://dx.doi.org/10.1145/1140124.1140202.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
10

Murphy, Gail C. « Is software engineering research addressing software engineering problems ? » Dans ASE '20 : 35th IEEE/ACM International Conference on Automated Software Engineering. New York, NY, USA : ACM, 2020. http://dx.doi.org/10.1145/3324884.3417103.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.

Rapports d'organisations sur le sujet "Software engineering"

1

Ardis, Mark, et Gary Ford. SEI (Software Engineering Institute) Report on Graduate Software Engineering Education, 1989. Fort Belvoir, VA : Defense Technical Information Center, juin 1989. http://dx.doi.org/10.21236/ada219018.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
2

Eslinger, S. Software Acquisition and Software Engineering Best Practices. Fort Belvoir, VA : Defense Technical Information Center, novembre 1999. http://dx.doi.org/10.21236/ada371477.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
3

Johnson, Albert L. Software Engineering Education Directory. Fort Belvoir, VA : Defense Technical Information Center, janvier 1988. http://dx.doi.org/10.21236/ada200630.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
4

McSteen, Bill, et Mark Schmick. Software Engineering Education Directory. Fort Belvoir, VA : Defense Technical Information Center, février 1989. http://dx.doi.org/10.21236/ada207545.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
5

Schultz, Herman P. Software Engineering Exercise Guidelines. Fort Belvoir, VA : Defense Technical Information Center, juillet 1989. http://dx.doi.org/10.21236/ada212510.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
6

Cohen, Herbert E. Software Engineering in Ada. Fort Belvoir, VA : Defense Technical Information Center, mars 1988. http://dx.doi.org/10.21236/ada286826.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
7

Murphy, Carl. Parallel Software Engineering Assessment. Fort Belvoir, VA : Defense Technical Information Center, juillet 1995. http://dx.doi.org/10.21236/ada303034.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
8

Basili, Victor R., Richard W. Selby, Hutchens Jr. et David H. Experimentation in Software Engineering,. Fort Belvoir, VA : Defense Technical Information Center, novembre 1985. http://dx.doi.org/10.21236/ada170840.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
9

McSteen, Bill, Brian Gottier et Mark Schmick. Software Engineering Education Directory. Fort Belvoir, VA : Defense Technical Information Center, avril 1990. http://dx.doi.org/10.21236/ada223740.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
10

Basili, Victor R., Jr Selby, Hutchens Richard W. et David H. Experimentation in Software Engineering. Fort Belvoir, VA : Defense Technical Information Center, novembre 1985. http://dx.doi.org/10.21236/ada226830.

Texte intégral
Styles APA, Harvard, Vancouver, ISO, etc.
Vous pouvez également être intéressé par les bibliographies sur le sujet « Software engineering » pour d’autres types de sources :
Articles de revues Thèses Livres
Nous offrons des réductions sur tous les plans premium pour les auteurs dont les œuvres sont incluses dans des sélections littéraires thématiques. Contactez-nous pour obtenir un code promo unique!

Vers la bibliographie