Academic literature on the topic 'Software development environment'
Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles
Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software development environment.'
Next to every source in the list of references, there is an 'Add to bibliography' button. Press on it, and we will generate automatically the bibliographic reference to the chosen work in the citation style you need: APA, MLA, Harvard, Chicago, Vancouver, etc.
You can also download the full text of the academic publication as pdf and read online its abstract whenever available in the metadata.
Journal articles on the topic "Software development environment"
de Oliveira, Káthia Marçal, Fábio Zlot, Ana Regina Rocha, Guilherme Horta Travassos, Cátia Galotta, and Crediné Silva de Menezes. "Domain-oriented software development environment." Journal of Systems and Software 72, no. 2 (July 2004): 145–61. http://dx.doi.org/10.1016/s0164-1212(03)00233-4.
Full textSoupos, R., S. Goutas, D. Christodoulakis, and C. Zaroliagis. "A software development environment database." ACM SIGSOFT Software Engineering Notes 12, no. 1 (January 1987): 63. http://dx.doi.org/10.1145/24574.24585.
Full textINOUE, Kuniko, and Yoshitaka MIYAZAKI. "Special Issue on Environment for FA Software Development. FA Software Development and Language Environment." Journal of the Japan Society for Precision Engineering 58, no. 10 (1992): 1629–32. http://dx.doi.org/10.2493/jjspe.58.1629.
Full textFujigaki, Yuko. "Software Development Environment and Work-density." Japanese journal of ergonomics 26, Supplement (1990): 136–37. http://dx.doi.org/10.5100/jje.26.supplement_136.
Full textKroon, J. G. M. "The software development environment at Rijkswaterstaat." Microprocessing and Microprogramming 34, no. 1-5 (February 1992): 3–6. http://dx.doi.org/10.1016/0165-6074(92)90089-p.
Full textSugiyama, Yasuhiro, and Ellis Horowitz. "Building your own software development environment." Software Engineering Journal 6, no. 5 (1991): 317. http://dx.doi.org/10.1049/sej.1991.0033.
Full textMarovac, Nenad. "Software development environment based on HyperNet." ACM SIGSOFT Software Engineering Notes 22, no. 2 (March 1997): 68–71. http://dx.doi.org/10.1145/251880.251954.
Full textCoptcoat, B. W., G. N. Turner, I. R. Ibbitson, C. S. Hall, and R. A. Bull. "An integrated test software development environment." Computer-Aided Engineering Journal 4, no. 1 (1987): 39. http://dx.doi.org/10.1049/cae.1987.0009.
Full textKtari, Béchir, Hamido Fujita, Mohamed Mejri, and Daniel Godbout. "Toward a new software development environment." Knowledge-Based Systems 20, no. 7 (October 2007): 683–93. http://dx.doi.org/10.1016/j.knosys.2007.05.006.
Full textHeinicke, Peter, Tom Nicinski, Penelope Constanta-Fanourakis, Donald Petravick, Ruth Pordes, David Ritchie, and Vicky White. "A Multiple Node Software Development Environment." IEEE Transactions on Nuclear Science 34, no. 4 (1987): 884–89. http://dx.doi.org/10.1109/tns.1987.4334757.
Full textDissertations / Theses on the topic "Software development environment"
Norman, Michael John. "SSDE : structured software development environment." Master's thesis, University of Cape Town, 1990. http://hdl.handle.net/11427/15899.
Full textSoftware engineers have identified many problem areas regarding the development of software. There is a need for improving system and program quality at design level, ensuring that design costs remain within the budget, and increasing the productivity of designers. Structured Software Development Environment (SSDE) provides the system designer with an interactive menu-driven environment, and a framework within which he can conveniently express and manipulate his proposed solution. This representation is in terms of both a conceptual model and a detailed software logic definition. Thus SSDE provides tools for both high-level (or logical) and low-level (or physical) design. It allows a user to follow his own preferred methodology rather than restricting him to one specific strategy. SSDE builds and maintains databases that record all design decisions. It provides the system designer with a mechanism whereby systems can easily be modified and new systems can evolve from similar existing systems. There are several auxiliary facilities as productivity aids. SSDE generates PASCAL code for low-level design constructs, ·full documentation of both the high- and low-level designs for inclusion in the project file, as well as a skeleton manual. The system was evaluated by a number of independent users. This exercise clearly demonstrated its success as an aid in expressing, understanding, manipulating and solving software development problems.
Konuralp, Zeynep. "Software Process Improvement In A Software Development Environment." Master's thesis, METU, 2007. http://etd.lib.metu.edu.tr/upload/12609059/index.pdf.
Full textrkiye (XCOM) is studied and the static software development metrics based on a recent proposal have been evaluated. The static software metrics based improvement suggestions and the author&rsquo
s improvement suggestions discussed with the senior staff are compared. An improved peer review process is proposed. The static software development metrics have been evaluated on the improved process to see the impacts of the improvements. The improved process has been already implemented at XCOM and preliminary results have been obtained.
Christensen, Olga. "Software Development Environment : the DevOps perspective." Thesis, Linnéuniversitetet, Institutionen för datavetenskap och medieteknik (DM), 2020. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-97568.
Full textKasu, Velangani Deepak Reddy. "Programmer Difficulties within a Software Development Environment." University of Cincinnati / OhioLINK, 2018. http://rave.ohiolink.edu/etdc/view?acc_num=ucin1544002452972811.
Full textStoll, Pia. "Exploring Sustainable Industrial Software System Development : within the Software Architecture Environment." Licentiate thesis, Mälardalen University, School of Innovation, Design and Engineering, 2009. http://urn.kb.se/resolve?urn=urn:nbn:se:mdh:diva-6672.
Full textThis thesis describes how sustainable development definitions can be transposed to the software architecture environment for the industrial software system domain. In a case study, sustainable development concerns from three companies are investigated for their influence on the dimensions of sustainable development: economical, environmental, and social sustainability. Classifying the case study’s concerns, in the thesis’s Software Engineering taxonomy, shows that the software development concerns are in majority and the software architecture concerns surprisingly few. The economical sustainability concerns dominate followed by social sustainability concerns, including both concerns successfully met and concerns to be met.
Sustainable industrial software system development is in the thesis defined as: “Sustainable industrial software system development meets current stakeholders’ needs without compromising the software development organization’s ability to meet the needs of future stakeholders”. Understanding current and future stakeholders concerns is necessary for the formulation of sustainability goals and metrics. Clarifying the interrelationships among stakeholders’ concerns’ impact on business goals and software qualities, in the thesis’s Influencing Factors method, proves to help stakeholders understand their future needs.
Trust is found to be critical for sustainable development. For the establishing of trust between system and system users, the usability quality is vital. To implement usability support in the architecture in the early design phase, reusable architectural responsibilities are created. The reusable architectural responsibilities are integrated into an experience factory and used by the product line system architects, resulting in a return of investment of 25:2.
Pasas- Analyzing the enterprise-, system-, and software architecture impact of stakeholders’ concerns for profitable industrial software systems
Ghali, Nagi. "Managing software development knowledge: A conceptually-oriented software engineering environment (COSEE)." Thesis, University of Ottawa (Canada), 1993. http://hdl.handle.net/10393/6565.
Full textSherwood, Patricia Ann. "Inspections : software development process for building defect free software applied in a small-scale software development environment /." Online version of thesis, 1990. http://hdl.handle.net/1850/10598.
Full textBortz, Kent. "Coverage testing in a production software development environment." [Denver, Colo.] : Regis University, 2006. http://165.236.235.140/lib/KBortz2006.pdf.
Full textJoubert, Anton Francois. "Development of a software defined radar environment simulator." Thesis, Stellenbosch : Stellenbosch University, 2005. http://hdl.handle.net/10019.1/50318.
Full textENGLISH ABSTRACT: The development of a radar system is a complex process, requiring a substantial amount of testing. In general, these tests are performed using field trials. Such trials are expensive, and their exact conditions can never be repeated. A radar environment simulator allows for repeatable testing of the majority of a radar's functionality; however, most commercial products are not cost effective. In this thesis we investigate the various approaches to modelling targets and the littoral environment, and then develop a low-cost, largely software defined simulator. This simulator is capable of generating real-time video signals for a monopulse doppler tracking radar. The core simulation routines reside in an extensible software framework which is populated with simple target and clutter models for a prototype simulator. Closed loop tracking tests verify the operation of the prototype simulator.
AFRIKAANSE OPSOMMING: Die ontwikkeling van 'n radarstelsel is a ingewikkelde proses wat verskeie stelseltoetse benodig. Veldtoetse, wat gewoonlik gebruik word, is 'n duur proses, en die toestande is nooit presies dieselfde nie. 'n Radar-omgewingsimulator kan 'n groot deel van 'n radar se funksionaliteit herhaaldelik toets. Daar is egter weinig koste-effektiewe kommersile produkte vir hierdie doel beskikbaar. Hierdie tesis ondersoek verskeie teiken- en omgewingsmodelle, waarna 'n lae-koste, meestal sagteware-gedefinieerde simulator ontwikkel word. Hierdie simulator genereer intydse videoseine vir 'n enkelpuls-dopplervolgingsradar. Die kernfunksionaliteit van die simulator is in sagteware gesetel, en basiese teiken- en omgewingsmodelle is geïmplementeer. Die prototipe-simulator word getoets deur dit aan die radar self te koppel, en dan die teiken-opsporing en -volging te verifieer.
Fouladi, Amir Hossein, and Khorvaj Omid Zafari. "TryMyLanguage : An Extensible, Web-based Software Development Environment." Thesis, Linköpings universitet, Programvara och system, 2014. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-109673.
Full textBooks on the topic "Software development environment"
Reiss, Steven P. The Field Programming Environment: A Friendly Integrated Environment for Learning and Development. Boston, MA: Springer US, 1995.
Find full textInternational Workshop on Software Engineering Environment (1986 Beijing, China). Software engineering environment: Proceedings of the International Workshop on Software Engineering Environment, August 18-20, 1986, Beijing, China. Beijing: China Academic Publishers, 1986.
Find full textMark, Hammond, and Abrams Brad, eds. Programming in the . NET environment. Boston: Addison-Wesley, 2003.
Find full textWallace, Dolores R. Study of a prototype software engineering environment. Gaithersburg, MD: U.S. Dept. of Commerce, National Bureau of Standards, 1986.
Find full textWallace, Dolores R. Study of a prototype software engineering environment. Gaithersburg, MD: U.S. Dept. of Commerce, National Bureau of Standards, 1986.
Find full textReiss, Steven P. The field programming environment: A friendly integrated environment for learning and development. Boston: Kluwer Academic Publishers, 1995.
Find full textStone, John A. Developing software applications in a changing IT environment: Management strategies and techniques. New York: McGraw-Hill, 1997.
Find full textOracle's cooperative development environment: A reference and user's guide. Boston: Butterworth-Heinemann, 1995.
Find full textJohn, Watkins. Agile testing: How to succeed in an extreme testing environment. Cambridge: Cambridge University Press, 2009.
Find full textBook chapters on the topic "Software development environment"
Sloane, Anthony M., Matthew Roberts, Scott Buckley, and Shaun Muscat. "Monto: A Disintegrated Development Environment." In Software Language Engineering, 211–20. Cham: Springer International Publishing, 2014. http://dx.doi.org/10.1007/978-3-319-11245-9_12.
Full textLiu, Shaoying. "Intelligent Software Engineering Environment." In Formal Engineering for Industrial Software Development, 371–81. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-662-07287-5_20.
Full textGouveia, Jo∼ao, Georgios Koutsoukos, Michel Wermelinger, Luís Andrade, and José Luiz Fiadeiro. "The Coordination Development Environment." In Fundamental Approaches to Software Engineering, 323–26. Berlin, Heidelberg: Springer Berlin Heidelberg, 2002. http://dx.doi.org/10.1007/3-540-45923-5_22.
Full textBischofberger, Walter R., and Gustav Pomberger. "The TOPOS Exploratory Programming Environment." In Prototyping-Oriented Software Development, 152–77. Berlin, Heidelberg: Springer Berlin Heidelberg, 1992. http://dx.doi.org/10.1007/978-3-642-84760-8_9.
Full textSouquières, Jeanine, and Nicole Lévy. "Proplane: A specification development environment." In Algebraic Methodology and Software Technology, 612–15. Berlin, Heidelberg: Springer Berlin Heidelberg, 1996. http://dx.doi.org/10.1007/bfb0014355.
Full textBischofberger, Walter R., and Gustav Pomberger. "The TOPOS User Interface Prototyping Environment DICE." In Prototyping-Oriented Software Development, 137–51. Berlin, Heidelberg: Springer Berlin Heidelberg, 1992. http://dx.doi.org/10.1007/978-3-642-84760-8_8.
Full textChang, Shi-Kuo. "Pragmatics: Tools for a Multimedia Development Environment." In Multimedia Software Engineering, 101–16. Boston, MA: Springer US, 2000. http://dx.doi.org/10.1007/978-1-4615-4435-7_7.
Full textRedmond, James A., and Kevin T. Ryan. "Designing a Method Driven Software Development Environment." In Automating Systems Development, 441–52. Boston, MA: Springer US, 1988. http://dx.doi.org/10.1007/978-1-4613-1033-4_36.
Full textCho, Jeonghun. "Software Development Environment for Automotive SoC." In Algorithm & SoC Design for Automotive Vision Systems, 231–61. Dordrecht: Springer Netherlands, 2014. http://dx.doi.org/10.1007/978-94-017-9075-8_9.
Full textCleaveland, Ranee, Philip M. Lewis, Scott A. Smolka, and Oleg Sokolsky. "The Concurrency Factory software development environment." In Tools and Algorithms for the Construction and Analysis of Systems, 391–95. Berlin, Heidelberg: Springer Berlin Heidelberg, 1996. http://dx.doi.org/10.1007/3-540-61042-1_56.
Full textConference papers on the topic "Software development environment"
Globa, L. S., and T. N. Kot. "Integrated software environment development." In Telecommunication Technology" (CriMiCo 2008). IEEE, 2008. http://dx.doi.org/10.1109/crmico.2008.4676424.
Full textLazic, Ljubomir, and Stevan A. Milinkovic. "Software environment for optimal software quality development." In 2012 20th Telecommunications Forum Telfor (TELFOR). IEEE, 2012. http://dx.doi.org/10.1109/telfor.2012.6419552.
Full textLeelanupab, Teerapong, and Tiwipab Meephruek. "CodeBuddy (Collaborative Software Development Environment)." In SIGCSE '19: The 50th ACM Technical Symposium on Computer Science Education. New York, NY, USA: ACM, 2019. http://dx.doi.org/10.1145/3287324.3293750.
Full textHussein, Mahmoud, Reda Nouacer, and Ansgar Radermacher. "Towards a Safe Software Development Environment." In 2017 Euromicro Conference on Digital System Design (DSD). IEEE, 2017. http://dx.doi.org/10.1109/dsd.2017.13.
Full textHattori, Lile, and Michele Lanza. "An environment for synchronous software development." In 2009 31st International Conference on Software Engineering - Companion Volume. IEEE, 2009. http://dx.doi.org/10.1109/icse-companion.2009.5070987.
Full textSimec, Alen, Bruno Drzanic, and Davor Lozic. "Isolated Environment Tools for Software Development." In 2018 International Conference on Applied Mathematics & Computer Science (ICAMCS). IEEE, 2018. http://dx.doi.org/10.1109/icamcs46079.2018.00016.
Full text"COMPONENT-BASED SOFTWARE DEVELOPMENT ENVIRONMENT (CBDE)." In 6th International Conference on Enterprise Information Systems. SciTePress - Science and and Technology Publications, 2004. http://dx.doi.org/10.5220/0002638303380343.
Full textEpstein, Geoffrey N., Marc P. Nobile, and Anthony Sacramone. "Multisensor Algorithm And Software Development Environment." In 1988 Robotics Conferences, edited by Paul S. Schenker. SPIE, 1989. http://dx.doi.org/10.1117/12.948946.
Full textJamsek, Damir A., and Minsoo Suk. "An Environment For Software System Development." In 1988 Technical Symposium on Optics, Electro-Optics, and Sensors, edited by Mohan M. Trivedi. SPIE, 1988. http://dx.doi.org/10.1117/12.946967.
Full textPilatti, Leonardo, Jorge Luis Nicolas Audy, and Rafael Prikladnicki. "Software configuration management over a global software development environment." In the 2006 international workshop. New York, New York, USA: ACM Press, 2006. http://dx.doi.org/10.1145/1138506.1138517.
Full textReports on the topic "Software development environment"
Heinicke, P., Tom Nicinski, P. Constanta-Fanourakis, D. Petravick, Ruth Pordes, D. Ritchie, and V. White. A Multiple Node Software Development Environment. Office of Scientific and Technical Information (OSTI), June 1987. http://dx.doi.org/10.2172/1151463.
Full textBrown, Alan W., Peter H. Feiler, and Kurt C. Wallnau. Understanding Integration in a Software Development Environment. Fort Belvoir, VA: Defense Technical Information Center, January 1992. http://dx.doi.org/10.21236/ada248119.
Full textDossick, Stephen E., and Gail E. Kaiser. CHIME: A Metadata-Based Distributed Software Development Environment. Fort Belvoir, VA: Defense Technical Information Center, January 2005. http://dx.doi.org/10.21236/ada437472.
Full textTran, N. T., and R. H. Mumm. Environment/Tool Integrator for Software Development. Version 1.1. Fort Belvoir, VA: Defense Technical Information Center, August 1992. http://dx.doi.org/10.21236/ada257607.
Full textMcCoy, Annette L., and Susan K. Schnipke. Development Manual for 3D World Virtual Environment Software. Fort Belvoir, VA: Defense Technical Information Center, December 1999. http://dx.doi.org/10.21236/ada378892.
Full textDoak, J. Case study on selecting an environment for software development. Office of Scientific and Technical Information (OSTI), May 1997. http://dx.doi.org/10.2172/481846.
Full textDandekar, Kapil, James Templeman, Linda Sibert, and Robert Page. The Hobbes Software Architecture for Virtual Environment Interface Development. Fort Belvoir, VA: Defense Technical Information Center, April 1998. http://dx.doi.org/10.21236/ada341960.
Full textGamalel-Din, Shehab A., and Leon J. Osterweil. ORBIT: A Prototype Software Maintenance/Development Process Programming Meta-Environment. Fort Belvoir, VA: Defense Technical Information Center, October 1989. http://dx.doi.org/10.21236/ada606428.
Full textGamalel-Din, Shehab A., and Leon J. Osterweil. ORBIT -- A Prototype Software Maintenance/Development Process Programming Meta-Environment. Fort Belvoir, VA: Defense Technical Information Center, October 1989. http://dx.doi.org/10.21236/ada456865.
Full textBrenner, Neal J., Daniel D. Galorath, David G. Lawrence, and Judy C. Rampton. A Plan for Collecting Ada Software Development Cost, Schedule, and Environment Data. Fort Belvoir, VA: Defense Technical Information Center, April 1987. http://dx.doi.org/10.21236/ada185905.
Full text