Relevant bibliographies by topics / Software/systems development

Contents

  1. Journal articles
  2. Dissertations / Theses
  3. Books
  4. Book chapters
  5. Conference papers
  6. Reports

Academic literature on the topic 'Software/systems development'

Author: Grafiati
Published: 4 June 2021
Last updated: 1 February 2022

Create a spot-on reference in APA, MLA, Chicago, Harvard, and other styles

Select a source type:

Consult the lists of relevant articles, books, theses, conference reports, and other scholarly sources on the topic 'Software/systems development.'

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/systems development"

1

Dudkin, M. V., A. I. Kaz'min, A. A. Menn, and V. N. Popolitov. "FMS Software Development Systems." IFAC Proceedings Volumes 19, no. 2 (April 1986): 131–35. http://dx.doi.org/10.1016/s1474-6670(17)64110-7.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Bull, G. M. "Software Development for Distributed Systems." IFAC Proceedings Volumes 19, no. 6 (May 1986): 37–46. http://dx.doi.org/10.1016/s1474-6670(17)59722-0.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Ortolano, Leonard, and Catherine D. Perman. "Software for Expert Systems Development." Journal of Computing in Civil Engineering 1, no. 4 (October 1987): 225–40. http://dx.doi.org/10.1061/(asce)0887-3801(1987)1:4(225).

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Aoyama, M. "Concurrent development of software systems." ACM SIGSOFT Software Engineering Notes 12, no. 3 (July 1987): 20–24. http://dx.doi.org/10.1145/29934.29937.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

SATAKE, Toshifumi, Shinya HARAMAKI, Mikio FUJIO, and Akihiro HAYASHI. "Development of Software-Toolkit for Reconfigurable Software Applications for Manufacturing Systems(Advanced Manufacturing,Session: MP2-D)." Abstracts of the international conference on advanced mechatronics : toward evolutionary fusion of IT and mechatronics : ICAM 2004.4 (2004): 36. http://dx.doi.org/10.1299/jsmeicam.2004.4.36_3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Lind, M. R., and J. M. Sulek. "Undersizing software systems: third versus fourth generation software development." European Journal of Information Systems 7, no. 4 (1998): 261–68. http://dx.doi.org/10.1038/sj.ejis.3000308.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Lind, M. R., and J. M. Sulek. "Undersizing software systems: third versus fourth generation software development." European Journal of Information Systems 7, no. 4 (December 1998): 261–68. http://dx.doi.org/10.1057/palgrave.ejis.3000308.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Calisi, Daniele, Francesco Fedi, Alberto Leo, and Daniele Nardi. "Software Development for Networked Robot Systems." IFAC Proceedings Volumes 43, no. 16 (2010): 605–10. http://dx.doi.org/10.3182/20100906-3-it-2019.00104.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Piltsov, M. V., and S. M. Khantaeva. "DEVELOPMENT OF SOFTWARE FOR CCTV SYSTEMS." Scientific Papers Collection of the Angarsk State Technical University 1, no. 1 (June 12, 2019): 16–20. http://dx.doi.org/10.36629/2686-7788-2019-1-1-16-20.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Rannanjärvi, Leila, and Tapio Heikkilä. "Software development for holonic manufacturing systems." Computers in Industry 37, no. 3 (November 1998): 233–53. http://dx.doi.org/10.1016/s0166-3615(98)00101-8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Dissertations / Theses on the topic "Software/systems development"

1

Cao, Lan. "Modeling Dynamics in Agile Software Development." Digital Archive @ GSU, 2005. http://digitalarchive.gsu.edu/cis_diss/4.

Full text
Abstract:
Agile software development challenges the traditional way of software development and project management. In rapidly changing environments, changing requirements and tight schedule constraints require software developers to take a different approach toward the process of software development. However, beyond a few case studies, surveys and studies focused on specific practices such as pair programming, the effectiveness and applicability of agile methods have not been established adequately. The objective of my research is to improve the understanding of and gain insights into these issues. For this purpose, I develop a system dynamic simulation model that considers the complex interdependencies among the variety of practices used in agile development. The model is developed on the basis of an extensive review of the literature as well as quantitative and qualitative data collected from real projects in seven organizations. The development of the model was guided by dynamic hypotheses on customer involvement, refactoring and quality of design. The model was refined and validated using data from independent projects. The model helps in answering important questions on the impact of customer behavior, cost of making changes and economics of pair programming. Experimentation with the model suggests that the cost of change is not constant; instead, its value changes cyclically and increases towards the later phase of development. Also, the results of simulation show that with no pair programming, fewer tasks are delivered and it costs more to deliver a task when compared to development with pair programming. Further, customer behavior has a major impact on project performance. The quality of customer feedback is found to be very critical to the successful of an agile software development project. The primary contribution of this research is the simulation model of agile software development that can be used a tool to examine the impact of agile practices and management policies on critical project variables including project scope, schedule, and cost. This research provides a mechanism to study agile development as a dynamic system of practices rather than using a static view and in isolation. The results from this study are expected to be of significant interest to practitioners of agile methods by providing them a simulation environment to examine the impact of their practices, procedures and management policies.
APA, Harvard, Vancouver, ISO, and other styles
2

Minich, Matthias Ernst. "Industrialising software development in systems integration." Thesis, University of Plymouth, 2013. http://hdl.handle.net/10026.1/2772.

Full text
Abstract:
Compared to other disciplines, software engineering as of today is still dependent on craftsmanship of highly-skilled workers. However, with constantly increasing complexity and efforts, existing software engineering approaches appear more and more inefficient. A paradigm shift towards industrial production methods seems inevitable. Recent advances in academia and practice have lead to the availability of industrial key principles in software development as well. Specialization is represented in software product lines, standardization and systematic reuse are available with component-based development, and automation has become accessible through model-driven engineering. While each of the above is well researched in theory, only few cases of successful implementation in the industry are known. This becomes even more evident in specialized areas of software engineering such as systems integration. Today’s IT systems need to quickly adapt to new business requirements due to mergers and acquisitions and cooperations between enterprises. This certainly leads to integration efforts, i.e. joining different subsystems into a cohesive whole in order to provide new functionality. In such an environment. the application of industrial methods for software development seems even more important. Unfortunately, software development in this field is a highly complex and heterogeneous undertaking, as IT environments differ from customer to customer. In such settings, existing industrialization concepts would never break even due to one-time projects and thus insufficient economies of scale and scope. This present thesis, therefore, describes a novel approach for a more efficient implementation of prior key principles while considering the characteristics of software development for systems integration. After identifying the characteristics of the field and their affects on currently-known industrialization concepts, an organizational model for industrialized systems integration has thus been developed. It takes software product lines and adapts them in a way feasible for a systems integrator active in several business domains. The result is a three-tiered model consolidating recurring activities and reducing the efforts for individual product lines. For the implementation of component-based development, the present thesis assesses current component approaches and applies an integration metamodel to the most suitable one. This ensures a common understanding of systems integration across different product lines and thus alleviates component reuse, even across product line boundaries. The approach is furthermore aligned with the organizational model to depict in which way component-based development may be applied in industrialized systems integration. Automating software development in systems integration with model-driven engineering was found to be insufficient in its current state. The reason herefore lies in insufficient tool chains and a lack of modelling standards. As an alternative, an XML-based configuration of products within a software product line has been developed. It models a product line and its products with the help of a domain-specific language and utilizes stylesheet transformations to generate compliable artefacts. The approach has been tested for its feasibility within an exemplarily implementation following a real-world scenario. As not all aspects of industrialized systems integration could be simulated in a laboratory environment, the concept was furthermore validated during several expert interviews with industry representatives. Here, it was also possible to assess cultural and economic aspects. The thesis concludes with a detailed summary of the contributions to the field and suggests further areas of research in the context of industrialized systems integration.
APA, Harvard, Vancouver, ISO, and other styles
3

Ramos, Marcelo Augusto. "Bridging software engineering gaps towards system of systems development." Universidade de São Paulo, 2014. http://www.teses.usp.br/teses/disponiveis/55/55134/tde-13082014-103931/.

Full text
Abstract:
While there is a growing recognition of the importance of System of Systems (SoS), there is still little agreement on just what they are or on by what principles they should be constructed. Actually, there are numerous SoS definitions in the literature. The difficulty in specifying what are the constituent systems, what they are supposed to do, and how they are going to do it frequently lead SoS initiatives to complete failures. Guided by a sample SoS that comprises all the distinguishing SoS characteristics and a generic SoS Engineering (SoSE) process, this thesis explores the SoS development from different Software Engineering (SE) perspectives that include requirements, analysis, design, and reengineering. For the Requirements Engineering (RE), we propose a scene-based RE approach to describe the SoS progressively as an arrangement of elementary but meaningful related behaviors named scenes. The objective is making easier the description and the understanding of the SoS dynamism. For the analysis, we propose extensions to statecharts to visually improve the modeling of systems interactions. They are symbolic notations that result from an analogy with multi-layer Printed Circuit Boards (PCB). The resulting diagrams are named PCBstatecharts. For the design, we propose an extension to the conventional SPLE process in such a way that SPL can become a natural source of SoS members. Domain engineering is extended to deliver components able to share abilities in SoS environments. Then, application engineers can design families of products that comply with different SoS requirements and still improve their products using the abilities of other SoS members. For the reengineering, we propose an approach extension to evolve legacy systems to SPL and then to SoS members. We demonstrate that when legacy systems are reengineered properly, they can share useful abilities, work cooperatively, and compose SoS
Apesar do crescente reconheciimento da importância de Sistemas de Sistemas (SoS) ainda não há um consenso sobre o que eles são um para que princípios devem ser construídos. De fato, existem várias definições de SoS na literatura. A dificuldade de especificar quais são os sistemas constituintes, as suas tarefas e como eles irão realizá-las frequentemente conduzem iniciativas de SoS ao completo fracasso. Guiados por um exemplo que inclui todas as características distintas de um SoS e um processo genérico de engenharia de SoS (SoSE), esta tese explora o desenvolvimento de SoS a partir de diferentes perspectivas da engenharia de software (SE), que incluem requisitos, análise, projeto e reengenharia. Para a engenharia de requisitos (RE) é proposta uma abordagem para descrever progressivamente um SoS como um arranjo de comportamentos mais simples, porém significativos, denominados \'cenas\'. O objetivo é facilitar a descrição e o entendimento do SoS e seu dinamismo. Para a análise, propõe-se as extensões de statecharts para melhorar a modelagem das interações entre sistemas. Elas são notações simbólicas que resultam de uma analogia com placas de circuito impresso multi camadas (PCB). Os diagramas resultantes são denominados PCB-statecharts. Para o projeto, é proposta uma extensão para o processo convencional de engenharia de linha de produtos (SPLE), de tal forma que linhas de produto (SPL) possam se tornar uma fonte natural de membros para SoS. A engenharia de domínio é estendida para prover componentes capazes de compartilhar habilidades em ambientes de SoS. Desta forma, engenheiros de aplicação podem projetar famílias de produtos complacentes com diferentes requisitos de SoS e ainda melhorar seus produtos usando habilidades de outros membros de um SoS. Para a reengenharia propõe-se extensão de uma abordagem existente para evoluir legados para SPL e depois para membros de um SoS. O objetivo é demonstrar que quando sistemas legados são tratados apropriadamente, eles podem compartilhar habilidades úteis, trabalhar de maneira cooperativa e compor SoS
APA, Harvard, Vancouver, ISO, and other styles
4

Kortetjärvi, Fredrik, and Rohullah Khorami. "Software development of visualizationsystem." Thesis, Högskolan i Halmstad, Akademin för informationsteknologi, 2021. http://urn.kb.se/resolve?urn=urn:nbn:se:hh:diva-44789.

Full text
Abstract:
Today wireless technologies are increasing in the automation systems used in homes and buildings. More electrical devices are used in a house to save time, money, and energy because they are relatively inexpensive and easy to install; these devices even allow smart components such as mobile tablets and computer connectivity. To connect all these devices for data transmission purposes and easy access, the KNX is the best choice. The KNX standard is an open standard for home and building automation. KNX standard supports different communication media such as Twisted pairs, Power line, Radio Frequency, and tunnelling IP. KNX system is a bus system for building control, making all electrical and smart devices in a KNX system use the same transmission method and exchange telegrams via a shared bus network. To check and control all the electrical devices in a home or an apartment takes time; that is why there is a massive need for applications to make every room’s controlling process much easier and take a much shorter time. This project is about designing and implementing a visualization application for windows and .NET for managing and comparing input data with the actual data. This application is equipped with a KNX bus driver to communicate with hardware in a building. The practical part of the application is to take some raw data and then sort them in a specific way to minimize the time of controlling the process of the KNX devices in a building.
APA, Harvard, Vancouver, ISO, and other styles
5

Quezada, Gomez Juan Manuel. "Model-based guidelines for automotive electronic systems software development." Thesis, Massachusetts Institute of Technology, 2015. http://hdl.handle.net/1721.1/100383.

Full text
Abstract:
Thesis: S.M. in Engineering and Management, Massachusetts Institute of Technology, Engineering Systems Division, System Design and Management Program, 2015.
Cataloged from PDF version of thesis.
Includes bibliographical references (pages 96-98).
The automobile innovation transformed the human life style ever since its introduction to the public, and for over the last one hundred years incumbent technologies have been adopted to improve its performance characteristics. Yet, we need a holistic approach to understand that automobiles shifted from being a mere assembly of mechanical parts to a multidisciplinary system that form the modern automobile. Thanks to the increased use of electronics and software in automobiles, consumers benefit from better gas mileage, more amenities and features, such as comfort, driving assistance, and entertainment. At the same time, stability and performance of automobiles as systems have been facing deterioration, and eventually vehicle owners are finding that features and functions become inoperative over time, causing frustration, loss of time and money. Reports of problems experienced by vehicle owners have stem from casual factors of system defects that model-based systems engineering can reduce or eliminate. This research presents a model-based systems engineering approach to an automobile electronic system design. The work is founded on a comprehensive OPM model and engineering guidelines for electronic control module software design. The purpose of the framework developed in this study is to support development of complex vehicle software that allows flexibility for changing features and creating new ones, and enables software developers to pinpoint systemic faults quicker and at earlier lifecycle phases, reducing rework, increasing safety, and providing for more effective resolution of such problems.
by Juan Manuel Quezada Gomez.
S.M. in Engineering and Management
APA, Harvard, Vancouver, ISO, and other styles
6

Webster, David D. "Hardware, software, firmware allocation of functions in systems development." Diss., Virginia Polytechnic Institute and State University, 1987. http://hdl.handle.net/10919/49907.

Full text
Abstract:
The top-down development methodology is, for the most part, a well defined subject. There is, however, one area of top-down development that lacks structure and definition. The undefined topic is the hardware, software, and firmware allocation of functions. This research addresses this deficiency in top-down system development. The key objective is the restructuring of the hardware, software, and firmware process from a subjective, qualitative decision process to a structured, quantitative one. Factors that affect the hardware, software, and firmware allocation process are identified. Qualitative data on the influence of the factors on the allocation process are systematized into quantitative information. This information is used to develop a model to provide a recommendation for implementing a function in hardware, software, or firmware. The model applies three analytical methods: 1) the analytic hierarchy process, 2) the general linear model, and 3) the second order regression technique. These three methods are applied to the quantified information of the hardware, software, firmware allocation process. A computer-based software tool is developed by this research to aid in the evaluation of the hardware, software, and firmware allocation process. The software support tool assists in data collection. Future application of the support tool will enable the capture and documentation of expert knowledge on the hardware, software, and firmware allocation process. The improved knowledge base can be used to improve the model which in tum will improve the system development process, and resulting system.
Ph. D.
incomplete_metadata
APA, Harvard, Vancouver, ISO, and other styles
7

Ramanath, Ana Maria. "The role of information systems development methods in interorganisational systems development." Thesis, Brunel University, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.289900.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Hui, S. C. "Software development of real-time distributed systems." Thesis, University of Sussex, 1987. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.375841.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Kelanti, M. (Markus). "Stakeholder analysis in software-intensive systems development." Doctoral thesis, Oulun yliopisto, 2016. http://urn.fi/urn:isbn:9789526213682.

Full text
Abstract:
Abstract A stakeholder analysis is commonly a part of the requirements engineering process in the development of software systems. It contributes to identifying, analysing, negotiating and validating requirements from multiple stakeholder viewpoints that do not necessary share the same views on a system under development and do not necessary express themselves using a similar language. Stakeholder analysis is often integrated into a used development method or practice and doesn’t necessarily appear as a separate process. The increase in software size, availability and use in different appliances, however, requires more from the stakeholder analysis than has been recognized in Software Engineering literature. The increasing scale of software systems and connections to other systems increase the number of involved stakeholders complicating the stakeholder analysis. In addition, how the actual stakeholder analysis should be implemented in large scale software development and how it supports the development effort is problematic in practice. The purpose of this thesis is to study the role and purpose of a stakeholder analysis in a large-scale software-intensive systems development. In this thesis, an empirical approach is taken to study the large-scale software-intensive systems development as phenomena in order to observe it as a whole. This approach allows this thesis to analyse the phenomena from different perspectives in order to identify and describe the nature and purpose of a stakeholder analysis in large-scale software-intensive systems development. The contribution of this thesis is the following. First, the thesis contributes to both the practical and scientific community by describing the role of stakeholder analysis in the software-intensive systems development process. Secondly, it demonstrates how a stakeholder analysis can be implemented in a large-scale software-intensive systems development process
Tiivistelmä Sidosryhmäanalyysi on yleensä osa vaatimusmäärittelyprosessia ohjelmistojärjestelmien kehityksessä. Se edesauttaa vaatimusten tunnistamista, analysointia, sopimista ja vahvistamista useiden eri sidosryhmien näkökulmasta tilanteissa, missä eri sidosryhmät eivät välttämättä jaa samaa näkökulmaa kehitettävään järjestelmään ja eivät välttämättä käytä samaa kieltä ilmaistakseen itseään. Sidosryhmäanalyysi on usein integroitu suoraan käytettyyn kehitysmenetelmään tai käytäntöön ja ei välttämättä ilmene erillisenä prosessina. Ohjelmiston koon kasvaessa ja yhteyksien lisääntyminen yhä useampiin laitteisiin on johtanut tilanteeseen, missä sidosryhmäanalyysilta vaaditaan yhä enemmän kuin kirjallisuudessa on aiemmin tunnistettu. Ohjelmistojärjestelmien alati kasvava koko ja yhteyksien lisääntyminen muihin järjestelmiin kasvattaa sidosryhmien määrää vaikeuttaen sidosryhmäanalyysin tekemistä. Lisäksi on ongelmallista, että miten sidosryhmäanalyysin tulisi tukea suuren mittakaavan ohjelmistotuotantoa ja miten se käytännössä toteutetaan tällaisessa ympäristössä. Tämän väitöskirjan tavoitteena on tutkia sidosryhmän roolia ja tarkoitusta suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotannossa. Tutkimus on toteutettu empiirisellä lähestymistavalla tarkkailemalla suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotantoa kokonaisuutena. Tämä lähestymistapa mahdollistaa kokonaisuuden analysoinnin eri näkökulmista, jotta sidosryhmäanalyysin luonne ja tarkoitus voidaan tunnistaa ja kuvata suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotannossa. Väitöskirjan tulosten kontribuutio jakautuu kahteen osaan. Ensimmäiseksi väitöskirjan tulokset auttavat sekä tiedeyhteisöä ja käytännön työtä tekeviä kuvaamalla sidosryhmäanalyysin suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotannossa. Toiseksi tulokset havainnollistavat miten sidosryhmäanalyysi voidaan toteuttaa suuren mittakaavan ohjelmistointensiivisten järjestelmien tuotekehitysprosessissa
APA, Harvard, Vancouver, ISO, and other styles
10

Rathor, Shekhar. "Facilitators for Software Development Agility." FIU Digital Commons, 2016. http://digitalcommons.fiu.edu/etd/3059.

Full text
Abstract:
Software development methodologies provide guidelines and practices for developing information systems. They have evolved over time from traditional plan-driven methodologies to incremental and iterative software development methodologies. The Agile Manifesto was released in 2001, which provides values and principles for agile software development. Over the last few years, agile software development has become popular because its values and principles focus on addressing the needs of contemporary software development. IT and Business teams need agility to deal with changes that can emerge during software development due to changing business needs. Agile software development practices claim to provide the ability to deal with such changes. Various research studies have identified many factors/variables that are important for agile software development such as team autonomy, communication, and organizational culture. Most of these empirical studies on agile software development focus on just a few variables. The relationships among the variables is still not understood. The dimensions of agility and the relationship between agility and other variables have not been studied quantitatively in the literature. Also, there is no comprehensive framework to explain agile software development. This research study addresses these research gaps. This study analyzed a comprehensive research model that included antecedent variables (team autonomy, team competence), process variables (collaborative decision making, iterative development, communication), delivery capability, agility, and project outcomes (change satisfaction, customer satisfaction). It presents key dimensions of agility and quantitatively analyzes the relationship between agility and other variables. The PLS analysis of one hundred and sixty survey responses show that process variables mediate the relationship between antecedent variables and delivery capability and agility. The findings show that the delivery capability of the teams contributes to agility, antecedents and process variables contribute to agility, and delivery capability for better customer satisfaction. These results will help IS practitioners to understand the variables that are necessary to achieve agility for better project outcomes. Also, these quantitative findings provide better conceptual clarity about the relationship between various key variables related to agile software development.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software/systems development"

1

Morris, Daniel C. Relational Systems Development. New York: McGraw-Hill, 1989.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
2

Hamilton, Marc. Software development: Building reliable systems. Upper Saddle River, NJ: Prentice Hall PTR, 1999.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
3

Rosen, Clive. Guide to Software Systems Development. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-39730-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Corporation, Intel. Development systems handbook: Software, tools, and systems. Santa Clara, CA: Intel, 1986.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
5

Camille, Amadio, ed. Systems development projects. New York: Mitchell/McGraw-Hill, 1990.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
6

Daniela, Rus, ed. Systems methodology for software. Singapore: World Scientific, 1993.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
7

Software and systems traceability. New York: Springer, 2012.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
8

Winkler, Dietmar, Stefan Biffl, and Johannes Bergsmann, eds. Software Quality. The Future of Systems- and Software Development. Cham: Springer International Publishing, 2016. http://dx.doi.org/10.1007/978-3-319-27033-3.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Winkler, Dietmar, Stefan Biffl, and Johannes Bergsmann, eds. Software Quality. Increasing Value in Software and Systems Development. Berlin, Heidelberg: Springer Berlin Heidelberg, 2013. http://dx.doi.org/10.1007/978-3-642-35702-2.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Peterson, Robert O. Managing the systems development function. New York: Van Nostrand Reinhold, 1987.

Find full text
APA, Harvard, Vancouver, ISO, and other styles
More sources

Book chapters on the topic "Software/systems development"

1

Killisperger, Peter, Georg Peters, Markus Stumptner, and Beate Nothhelfer-Kolb. "Automating Software Processes." In Information Systems Development, 1059–68. Boston, MA: Springer US, 2008. http://dx.doi.org/10.1007/978-0-387-78578-3_37.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Radice, Ronald A. "Large Systems Software Implementation." In Application Development Systems, 354–74. Tokyo: Springer Japan, 1986. http://dx.doi.org/10.1007/978-4-431-68051-2_18.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Graf, Susanne, and Jozef Hooman. "Correct Development of Embedded Systems." In Software Architecture, 241–49. Berlin, Heidelberg: Springer Berlin Heidelberg, 2004. http://dx.doi.org/10.1007/978-3-540-24769-2_21.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Lunn, Ken. "Systems Analysis." In Software Development with UML, 194–221. London: Macmillan Education UK, 2003. http://dx.doi.org/10.1007/978-0-230-80419-7_12.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

Gorrod, Martin. "The software development lifecycle." In Risk Management Systems, 93–120. London: Palgrave Macmillan UK, 2004. http://dx.doi.org/10.1057/9780230510296_4.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Hammouda, Imed, Markku Hakala, Mika Pussinen, Mika Katara, and Tommi Mikkonen. "Concern-Based Development of Pattern Systems." In Software Architecture, 113–29. Berlin, Heidelberg: Springer Berlin Heidelberg, 2005. http://dx.doi.org/10.1007/11494713_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Fitsilis, P., A. Kameas, and L. Anthopoulos. "Classification of Software Projects’ Complexity." In Information Systems Development, 149–59. New York, NY: Springer New York, 2010. http://dx.doi.org/10.1007/978-1-4419-7355-9_13.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Apine, Baiba. "Software Development Risk Management Survey." In Information Systems Development, 241–51. Boston, MA: Springer US, 2002. http://dx.doi.org/10.1007/978-1-4615-0167-1_22.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Boehm, Barry, Jo Ann Lane, Supannika Koolmanojwong, and Richard Turner. "Architected Agile Solutions for Software-Reliant Systems." In Agile Software Development, 165–84. Berlin, Heidelberg: Springer Berlin Heidelberg, 2010. http://dx.doi.org/10.1007/978-3-642-12575-1_8.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Mylopoulos, John. "Agent Oriented Software Development." In Object-Oriented Information Systems, 1. Berlin, Heidelberg: Springer Berlin Heidelberg, 2003. http://dx.doi.org/10.1007/978-3-540-45242-3_1.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software/systems development"

1

Foustok, Mohamad. "Experiences in Large-Scale, Component Based, Model-Driven Software Development." In 2007 1st Annual IEEE Systems Conference. IEEE, 2007. http://dx.doi.org/10.1109/systems.2007.374657.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Isselhorst, Armin, and Nico Rackemann. "euces Software Development." In International Conference On Environmental Systems. 400 Commonwealth Drive, Warrendale, PA, United States: SAE International, 2008. http://dx.doi.org/10.4271/2008-01-2072.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Velikov, Valentin Petrov, and Ivaylo Kamenov Kamenarov. "Software development aid systems." In 2014 Information Technology Based Higher Education and Training (ITHET). IEEE, 2014. http://dx.doi.org/10.1109/ithet.2014.7155668.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

Jovicic, Bojan, Vladan Devedzic, Dragan Djuric, and Ramo Sendelj. "Agile ERP systems development." In the 5th India Software Engineering Conference. New York, New York, USA: ACM Press, 2012. http://dx.doi.org/10.1145/2134254.2134266.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

"Software Project Management in Distributed Software Development Context." In 15th International Conference on Enterprise Information Systems. SciTePress - Science and and Technology Publications, 2013. http://dx.doi.org/10.5220/0004442402160222.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Siddiqui, M. S., and S. J. Hussain. "Comprehensive software development model." In 2006 IEEE International Conference on Computer Systems and Applications. IEEE, 2006. http://dx.doi.org/10.1109/aiccsa.2006.205113.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Venolia, Gina. "Session details: Software development." In CHI '09: CHI Conference on Human Factors in Computing Systems. New York, NY, USA: ACM, 2009. http://dx.doi.org/10.1145/3256991.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Ellison, R. J. "Trends in software development environments for large software systems." In COMPCON Spring 88. IEEE, 1988. http://dx.doi.org/10.1109/cmpcon.1988.4870.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Joshi, Rajive, Arnab Bose, and Scott Breneman. "Software Development Platforms for Autonomous Systems." In AIAA Modeling and Simulation Technologies Conference and Exhibit. Reston, Virigina: American Institute of Aeronautics and Astronautics, 2002. http://dx.doi.org/10.2514/6.2002-4484.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Borcsok, Josef, and Sebastian Schaefer. "Software development for safety-related systems." In Second International Conference on Systems (ICONS'07). IEEE, 2007. http://dx.doi.org/10.1109/icons.2007.50.

Full text
APA, Harvard, Vancouver, ISO, and other styles

Reports on the topic "Software/systems development"

1

Baca, L. S., J. F. Bouchard, E. W. Collins, M. Eisenhour, D. D. Neidigk, M. J. Shortencarier, and P. A. Trellue. Software development methodology for high consequence systems. Office of Scientific and Technical Information (OSTI), October 1997. http://dx.doi.org/10.2172/541928.

Full text
APA, Harvard, Vancouver, ISO, and other styles
2

Garlan, David, and Mary Shaw. Architectures for Software Systems: A Curriculum Development Proposal in Undergraduate Software Engineering. Fort Belvoir, VA: Defense Technical Information Center, May 1993. http://dx.doi.org/10.21236/ada266703.

Full text
APA, Harvard, Vancouver, ISO, and other styles
3

Yau, Stephen S., Doc-Hwan Bae, Pranshu K. Gupta, Sun I. Paek, and Thaddeus J. Thigpen. A Software Development Methodology for Parallel Processing Systems. Fort Belvoir, VA: Defense Technical Information Center, October 1995. http://dx.doi.org/10.21236/ada303063.

Full text
APA, Harvard, Vancouver, ISO, and other styles
4

AIR FORCE SPACE COMMAND SPACE MISSILE SYS CTR. Space and Missile Systems Center Standard: Software Development. Fort Belvoir, VA: Defense Technical Information Center, January 2015. http://dx.doi.org/10.21236/ada619900.

Full text
APA, Harvard, Vancouver, ISO, and other styles
5

SOFTWARE OPTIONS INC CAMBRIDGE MA. Improving Productivity in the Development of Large Software Systems. Fort Belvoir, VA: Defense Technical Information Center, February 1994. http://dx.doi.org/10.21236/ada282270.

Full text
APA, Harvard, Vancouver, ISO, and other styles
6

Bui, James, and Neang I. Om. Estimating Software Development Costs and Schedules for Space Systems. Fort Belvoir, VA: Defense Technical Information Center, May 1994. http://dx.doi.org/10.21236/ada283661.

Full text
APA, Harvard, Vancouver, ISO, and other styles
7

Yau, Stephen S., Changju Gao, Debin Jia, Jun Wang, and Jiazheng Wu. Automated Object-Oriented Software Development for Parallel Processing Systems. Fort Belvoir, VA: Defense Technical Information Center, February 1998. http://dx.doi.org/10.21236/ada341223.

Full text
APA, Harvard, Vancouver, ISO, and other styles
8

Williams, L. G. Formal methods in the development of safety critical software systems. Office of Scientific and Technical Information (OSTI), November 1991. http://dx.doi.org/10.2172/10146119.

Full text
APA, Harvard, Vancouver, ISO, and other styles
9

Constable, Robert, and Christoph Kreitz. A Computation Infrastructure for Knowledge-Based Development of Reliable Software Systems. Fort Belvoir, VA: Defense Technical Information Center, November 2006. http://dx.doi.org/10.21236/ada462900.

Full text
APA, Harvard, Vancouver, ISO, and other styles
10

Lavappa, Priya D. Guidelines for planning and development of software for buildings and building systems. Gaithersburg, MD: National Institute of Standards and Technology, 2008. http://dx.doi.org/10.6028/nist.ir.7499.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software/systems development' for particular source types:
Journal articles Dissertations / Theses Books
We offer discounts on all premium plans for authors whose works are included in thematic literature selections. Contact us to get a unique promo code!

To the bibliography