Relevant bibliographies by topics / Software systems

Contents

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

Academic literature on the topic 'Software systems'

Author: Grafiati
Published: 4 June 2021
Last updated: 20 February 2023

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.'

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"

1

Spinellis, Diomidis. "Systems Software." IEEE Software 30, no. 3 (May 2013): 18–19. http://dx.doi.org/10.1109/ms.2013.61.

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

Silva, Dilma M. da, and Fabio Kon. "Adaptive software systems." Journal of the Brazilian Computer Society 10, no. 1 (July 2004): 3–4. http://dx.doi.org/10.1590/s0104-65002004000200001.

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

Ebert, Christof, Divith Bajaj, and Michael Weyrich. "Testing Software Systems." IEEE Software 39, no. 4 (July 2022): 8–17. http://dx.doi.org/10.1109/ms.2022.3166755.

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

Vogelsang, Andreas. "Explainable software systems." it - Information Technology 61, no. 4 (August 27, 2019): 193–96. http://dx.doi.org/10.1515/itit-2019-0015.

Full text
Abstract:
Abstract Software and software-controlled technical systems play an increasing role in our daily lives. In cyber-physical systems, which connect the physical and the digital world, software does not only influence how we perceive and interact with our environment but software also makes decisions that influence our behavior. Therefore, the ability of software systems to explain their behavior and decisions will become an important property that will be crucial for their acceptance in our society. We call software systems with this ability explainable software systems. In the past, we have worked on methods and tools to design explainable software systems. In this article, we highlight some of our work on how to design explainable software systems. More specifically, we describe an architectural framework for designing self-explainable software systems, which is based on the MAPE-loop for self-adaptive systems. Afterward, we show that explainability is also important for tools that are used by engineers during the development of software systems. We show examples from the area of requirements engineering where we use techniques from natural language processing and neural networks to help engineers comprehend the complex information structures embedded in system requirements.
APA, Harvard, Vancouver, ISO, and other styles
5

Suhler, P. A., N. Bagherzadeh, M. Malek, and N. Iscoe. "Software Authorization Systems." IEEE Software 3, no. 5 (September 1986): 34–41. http://dx.doi.org/10.1109/ms.1986.234396.

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

Del Ra, William. "Software systems architecture." ACM SIGSOFT Software Engineering Notes 37, no. 2 (April 3, 2012): 36. http://dx.doi.org/10.1145/2108144.2108171.

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

Becker, Steffen, Wilhelm Hasselbring, Alexandra Paul, Marko Boskovic, Heiko Koziolek, Jan Ploski, Abhishek Dhama, et al. "Trustworthy software systems." ACM SIGSOFT Software Engineering Notes 31, no. 6 (November 2006): 1–18. http://dx.doi.org/10.1145/1218776.1218781.

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

Del Ra, William. "Software build systems." ACM SIGSOFT Software Engineering Notes 36, no. 4 (August 4, 2011): 33–34. http://dx.doi.org/10.1145/1988997.1989005.

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

Jones, Russell. "Supporting systems software." Data Processing 27, no. 5 (June 1985): 19–21. http://dx.doi.org/10.1016/0011-684x(85)90131-5.

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

da Silva, Dilma M., and Fabio Kon. "Adaptive software systems." Journal of the Brazilian Computer Society 10, no. 1 (February 2004): 3–4. http://dx.doi.org/10.1007/bf03192349.

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

Dissertations / Theses on the topic "Software systems"

1

Rodrigues, Filho Roberto Vito. "Emergent software systems." Thesis, Lancaster University, 2018. http://eprints.lancs.ac.uk/126944/.

Full text
Abstract:
Contemporary software systems often have millions of lines of code that interact over complex infrastructures. The development of such systems is very challenging due to the increasing complexity of services and the high level of dynamism of current operating environments. In order to support the development and management of such systems, autonomic computing concepts have gained significant importance. The majority of autonomic computing approaches show significant levels of expert dependency in designing adaptive solutions. These approaches usually rely on human-made models and policies to support and guide software adaptation at runtime. These approaches mainly suffer from: i) a significant upfront effort demanded to create such solutions, which adds to the complexity of creating autonomous systems, and ii) unreliability given the high levels of uncertainty in current operating environments, leading the system to degraded performance and error states when subjected to unpredicted operating conditions and unexpected software interactions. Motivated by the problems and limitations of state-of-the-art autonomic computing solutions, this thesis introduces the concept of Emergent Software Systems. These systems are autonomously composed at runtime from discovered components, and are autonomously optimised based on the operating conditions, being able to build their own understanding of their environment and constituent parts. This thesis defines Emergent Software Systems, presenting the challenges of implementing such approach, and presents a fully functioning emergent systems framework that demonstrates this concept in real-world, fully functioning datacentre-based software.
APA, Harvard, Vancouver, ISO, and other styles
2

Nasir, Muhammad-Iftikhar, and Rizwan Iqbal. "Evolvability of Software Systems." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2008. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-4053.

Full text
Abstract:
Software evolvability, meeting the future requirements of the customer is one of the emerging challenges which software industry is facing nowadays. Software evolvability is the ability of software system to accommodate future requirements. Studies have shown that software evolvability has large economic benefits but at the same time it’s difficult to assess. Over the time many methods have been derived to assess the software evolvability. Software evolvability depends upon various characteristics of the software system. In this paper we will discuss different characteristics of the software systems on which software evolvability depends. We will also have a look on hierarchy of these characteristics based on their role in the evolvability of software system. Moreover we will find out that what level of qualifications is appropriate for an expert to assess the software evolvability of a software system
Software evolvability plays an important role in the software life cycle. It is ease with which software system can be modified for future requirements. There are different methods for assessing the software evolvability. Mainly, structural measures; expert assessment and combined approach. Structural approach focus on the class level measures i.e. inheritance, modularity, coupling etc. Whereas, the expert assessment approach utilizes experts opinion regarding the software system i.e. how much it is evolvable? Combined approach is a combination of structural measures and expert assessment. According to David E. Peercy software evolvability depends upon six factors i.e. modularity, descriptiveness, consistency, simplicity, expandability and instrumentation. However, David A. Sunday considered five factors which are modularity, descriptiveness, consistency, testability and changeability. Moreover, there are other factors which also influence the software evolvability i.e. skills and qualification of the maintainer, organizational support to evolvability and characteristics of the methods being used for maintenance. The importance of research methodology can't be neglected because it gives us thought about our research before start. It has a positive impact on research. We are able to understand the structure of our work and have rough idea about research procedure. Our research methodology on theme evolvability of software systems is consistent of few steps. These steps are literature review, informal discussions and then development of a questionnaire. Subsequently questionnaire is distributed to the subjects and conclusions are drawn, based on their feedback and analysis of results. We visited different software houses and discussed all the factors related to the survey. Experienced and qualified professionals were selected as subjects. To get the survey feedback we made phone calls, email reminders and personal meetings. Which result in high survey response i.e. 75%. Questionnaire was designed into three parts namely as personal information, characteristics of software evolvability and qualifications required for an expert. Pre-test was also designed to assure that the questions for the survey were properly defined and participants had no difficulty in understanding them. Participants of the survey included software developers, team leads, software testers and research students. Special consideration was given to the ethical issues in design and conduction of survey. We discussed about the response behavior of the participants analysis of the data we collected from survey. Analysis was conducted by different means like standard deviation, mean, medium, mode and variance in survey results. First part of the analysis is about what characteristics of the software which effect software evolvability and their priority. In this part we concluded that there are total eleven characteristics of the software evolvability out of which design and architecture is highly prioritized while technical platform and comments are least prioritized characteristics. In the second part of the analysis we concluded that technical training and quality assurance management experience are most important criteria for an expert while development experience and testing experience is least important In the last part of the thesis we discussed the research work, validity assessment of results and answers to the questions. We used A Lincoln‘s and Cuba’s criterion for validation assessment to support the validity of results. Validity is judged by four aspects credibility, transferability, dependability and conformability.
APA, Harvard, Vancouver, ISO, and other styles
3

Jong, Hayco Alexander de. "Flexible heterogeneous software systems." [S.l : Amsterdam : s.n.] ; Universiteit van Amsterdam [Host], 2007. http://dare.uva.nl/document/39606.

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

Caffall, Dale Scott. "Developing dependable software for a system-of-systems." Diss., Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2005. http://library.nps.navy.mil/uhtbin/hyperion/05Mar%5FCaffall.pdf.

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

Caffall, Dale Scott. "Conceptual framework approach for system-of-systems software developments." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 2003. http://library.nps.navy.mil/uhtbin/hyperion-image/03Mar%5FCaffall.pdf.

Full text
Abstract:
Thesis (M.S. in Software Engineering)--Naval Postgraduate School, March 2003.
Thesis advisor(s): James Bret Michael, Man-Tak Shing. Includes bibliographical references (p. 83-84). Also available online.
APA, Harvard, Vancouver, ISO, and other styles
6

Saks, Craig Sheldon. "Expanding software process improvement models beyond the software process itself." Master's thesis, University of Cape Town, 1999. http://hdl.handle.net/11427/16844.

Full text
Abstract:
Bibliography: pages 182-188.
The problems besetting software development and maintenance are well recorded and numerous strategies have been adopted over the years to overcome the so-called "software crisis". One increasingly popular strategy focuses on managing the processes by which software is built, maintained and managed. As such, many software organisations see software process improvement initiatives as an important strategy to help them improve their software development and maintenance performance. Two of the more popular software process improvement (SPI) models used by the software industry to help them in this endeavour are the Capability Maturity Model for Software (SW-CMM) from the Software Engineering Institute and the Software Process Improvement and Capability determination (SPICE) model from the International Standards Organisation. This research begins with the supposition that, although these SPI models have added significant value to many organisations, they have a potential shortcoming in that they tend to focus almost exclusively on the software process itself and seem to neglect other organisational aspects that could contribute to improved software development and maintenance performance. This research is concerned with exploring this potential shortcoming and identifying complementary improvement areas that the SW -CMM and SPICE models fail to address adequately. A theoretical framework for extending the SW-CMM and SPICE models is proposed. Thereafter complementary improvement areas are identified and integrated with the SW-CMM and SPICE models to develop an Extended SPI Model. This Extended SPI Model adopts a systemic view of software process and IS organisational improvement by addressing a wide range of complementary improvement considerations. A case study of an SPI project is described, with the specific objective of testing and refining the Extended SPI Model. The results seem to indicate that the framework and Extended SPI Model are largely valid, although a few changes were made in light of the findings of the case study. Finally, the implications of the research for both theory and practice are discussed.
APA, Harvard, Vancouver, ISO, and other styles
7

Inada, Kenichiro. "Analysis of Japanese Software Business." Thesis, Massachusetts Institute of Technology, 2010. http://hdl.handle.net/1721.1/59244.

Full text
Abstract:
Thesis (S.M. in System Design and Management)--Massachusetts Institute of Technology, Engineering Systems Division, System Design and Management Program, 2010.
Cataloged from PDF version of thesis.
Includes bibliographical references (p. 94-96).
Today, our society is surrounded by information system, computers, and software. It is no exaggeration to say that our daily life depends on software and its function. Accordingly, the business of software has made miraculous growth in the last two decades and is playing a significant role in various industries. In accordance with the growing business needs for effective software and information systems, various firms in various countries have entered the business of software seeking for prosperity. Some have succeeded, some have failed. What distinguishes these firms is its ability to manage and deliver quality products on demand, on time, at a low cost. To achieve such goal, software firms have thought out different methods and tools striving to establish its practice. Nevertheless, many software firms around the globe are struggling to satisfy its clients to achieve business success. With no exception, Japanese software firms are facing difficulties of managing software projects. While its ability to deliver high quality product is well acknowledged among software industry, its high cost structure and schedule delays are thought of as serious problems. Moreover, some of the transitions in the industry are forcing Japanese software firms to seek new opportunities. Therefore, it is important for Japanese software firms to establish more productive ways of developing software products and effective business strategies. Primal objective of this paper is to analyze the present conditions of Japanese software firms and to derive some recommendations which could enhance its current situation. It will also include the discussion of software development practices in US and India firms to better understand strength and weaknesses of Japanese firms and capture some important concepts which can be applied to improve current practice.
by Kenichiro Inada.
S.M.in System Design and Management
APA, Harvard, Vancouver, ISO, and other styles
8

Scott, Randall C. "Reengineering real-time software systems." Thesis, Monterey, Calif. : Springfield, Va. : Naval Postgraduate School ; Available from National Technical Information Service, 1993. http://handle.dtic.mil/100.2/ADA273408.

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

Frid, Jonas. "Security Critical Systems in Software." Thesis, Linköpings universitet, Informationskodning, 2010. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-61588.

Full text
Abstract:
Sectra Communications is today developing cryptographic products for high assurance environments with rigorous requirements on separation between encrypted and un-encrypted data. This separation has traditionally been achieved through the use of physically distinct hardware components, leading to larger products which require more power and cost more to produce compared to systems where lower assurance is required. An alternative to hardware separation has emerged thanks to a new class of operating systems based on the "separation kernel" concept, which offers verifiable separation between software components running on the same processor comparable to that of physical separation. The purpose of this thesis was to investigate the feasibility in developing a product based on a separation kernel and which possibilities and problems with security evaluation would arise. In the thesis, a literature study was performed covering publications on the separation kernel from a historical and technical perspective, and the development and current status on the subject of software evaluation. Additionally, a software crypto demonstrator was partly implemented in the separation kernel based Green Hills Integrity operating system. The thesis shows that the separation kernel concept has matured significantly and it is indeed feasible to begin using this class of operating systems within a near future. Aside from the obvious advantages with smaller amounts of hardware, it would give greater flexibility in development and potential for more fine-grained division of functions. On the other hand, it puts new demands on developers and there is also a need for additional research about some evaluation aspects, failure resistance and performance.
Sectra Communications utvecklar idag kryptoprodukter med högt ställda krav på separation mellan krypterad och okrypterad data. Traditionellt har denna separation gjorts i hårdvara med fysiskt åtskilda komponenter, vilket lett till större produkter, högre energiförbrukning och högre tillverkningskostnader än motsvarande system för lägre säkerhetsnivåer. Ett alternativ till hårdvaruseparation har framkommit tack vare en ny typ av operativsystem baserat på ett koncept kallat "separationskärna", som erbjuder verifierbar separation mellan mjukvarukomponenter på en processor likvärdig med fysisk separation. Syftet med examensarbetet var att undersöka möjligheten att basera en produkt på ett sådant system samt vilka ytterligare möjligheter och problem med säkerhetsevaluering av produkten som uppstår. I examensarbetet utfördes en litteraturstudie av publikationer om separationskärnan ur ett historiskt och tekniskt perspektiv, samt den historiska utvecklingen inom säkerhetsevaluering av mjukvara och dess nuvarande status. Dessutom implementerades delar av ett mjukvarukrypto som en demonstrationsenhet baserad på Integrity från Green Hills Software, vilket är ett realtidsoperativsystem byggt kring en separationskärna. Arbetet visade att separationskärnan som koncept har nått en hög mognadsgrad och att det är rimligt att börja använda denna typ av operativsystem till produkter med mycket högt ställda säkerhetskrav inom en snar framtid. Det skulle förutom uppenbara vinster med minskad mängd hårdvara även ge större flexibilitet vid utvecklingen och möjlighet till exaktare uppdelning av funktioner. Samtidigt ställer det andra krav på utvecklarna och det behövs ytterligare utredning om vissa aspekter av hur evalueringsförfarandet påverkas, systemens feltolerans samt prestanda.
APA, Harvard, Vancouver, ISO, and other styles
10

Schmidgall, Ralf. "Automotive embedded systems software reprogramming." Thesis, Brunel University, 2012. http://bura.brunel.ac.uk/handle/2438/7070.

Full text
Abstract:
The exponential growth of computer power is no longer limited to stand alone computing systems but applies to all areas of commercial embedded computing systems. The ongoing rapid growth in intelligent embedded systems is visible in the commercial automotive area, where a modern car today implements up to 80 different electronic control units (ECUs) and their total memory size has been increased to several hundreds of megabyte. This growth in the commercial mass production world has led to new challenges, even within the automotive industry but also in other business areas where cost pressure is high. The need to drive cost down means that every cent spent on recurring engineering costs needs to be justified. A conflict between functional requirements (functionality, system reliability, production and manufacturing aspects etc.), testing and maintainability aspects is given. Software reprogramming, as a key issue within the automotive industry, solve that given conflict partly in the past. Software Reprogramming for in-field service and maintenance in the after sales markets provides a strong method to fix previously not identified software errors. But the increasing software sizes and therefore the increasing software reprogramming times will reduce the benefits. Especially if ECU’s software size growth faster than vehicle’s onboard infrastructure can be adjusted. The thesis result enables cost prediction of embedded systems’ software reprogramming by generating an effective and reliable model for reprogramming time for different existing and new technologies. This model and additional research results contribute to a timeline for short term, mid term and long term solutions which will solve the currently given problems as well as future challenges, especially for the automotive industry but also for all other business areas where cost pressure is high and software reprogramming is a key issue during products life cycle.
APA, Harvard, Vancouver, ISO, and other styles
More sources

Books on the topic "Software systems"

1

Vybihal, Joseph. Software Systems. Dubuque, IA: Kendall Hunt Pub., 2008.

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

Danielle, Azar, ed. Software Systems. Dubuque, IA: Kendall Hunt Pub., 2008.

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

Germany) NATO Advanced Study Institute on Software Systems Safety (2013 Marktoberdorf. Software systems safety. Amsterdam: IOS Press, 2014.

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

Biggerstaff, Ted J. Systems software tools. Englewood Cliffs, N.J: Prentice-Hall, 1986.

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

Biggerstaff, Ted J. Systems software tools. Englewood Cliffs: Prentice / Hall International, 1986.

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

Chen, M. J., M. Buamud, and D. M. Grant. Generation Systems Software. Boston, MA: Springer US, 1996. http://dx.doi.org/10.1007/978-1-4613-1191-1.

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

Denzer, Ralf, Gerald Schimak, and David Russell, eds. Environmental Software Systems. Boston, MA: Springer US, 1996. http://dx.doi.org/10.1007/978-0-387-34951-0.

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

Zeng, Deze, Lin Gu, Shengli Pan, and Song Guo. Software Defined Systems. Cham: Springer International Publishing, 2020. http://dx.doi.org/10.1007/978-3-030-32942-6.

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

Mason, J. C., and M. G. Cox, eds. Scientific Software Systems. Dordrecht: Springer Netherlands, 1989. http://dx.doi.org/10.1007/978-94-009-0841-3.

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

Denzer, Ralf, David A. Swayne, Martin Purvis, and Gerald Schimak, eds. Environmental Software Systems. Boston, MA: Springer US, 2000. http://dx.doi.org/10.1007/978-0-387-35503-0.

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

Book chapters on the topic "Software systems"

1

Eisner, Howard. "Software." In Systems Architecting, 55–60. Boca Raton, FL : CRC Press/Taylor & Francis Group, 2019.: CRC Press, 2019. http://dx.doi.org/10.1201/9780429327810-10.

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

Jorgensen, Paul C., and Byron DeVries. "Testing Systems of Systems." In Software Testing, 373–90. 5th ed. Boca Raton: Auerbach Publications, 2021. http://dx.doi.org/10.1201/9781003168447-19.

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

Taylor, G. "Software Systems." In Work Out Computer Studies for First Examinations, 168–89. London: Macmillan Education UK, 1986. http://dx.doi.org/10.1007/978-1-349-18143-8_9.

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

Taylor, G. "Software Systems." In Work Out Computer Studies GCSE, 170–92. London: Macmillan Education UK, 1987. http://dx.doi.org/10.1007/978-1-349-09458-5_9.

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

Mett, Percy. "Systems Software." In Introduction to Computing, 275–312. London: Macmillan Education UK, 1990. http://dx.doi.org/10.1007/978-1-349-08039-7_10.

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

Burrell, Mark. "Systems Software." In Fundamentals of Computer Architecture, 231–45. London: Macmillan Education UK, 2004. http://dx.doi.org/10.1007/978-1-137-11313-9_14.

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

Hartley, M. G., M. Healey, and P. G. Depledge. "Software Systems." In Mini and Microcomputer Systems, 203–41. London: Macmillan Education UK, 1988. http://dx.doi.org/10.1007/978-1-349-19315-8_8.

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

Alber, Antone F. "Software." In Interactive Computer Systems, 201–23. Boston, MA: Springer US, 1993. http://dx.doi.org/10.1007/978-1-4615-2888-3_8.

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

Eisner, Howard. "Software Engineering." In Systems Engineering: Building Successful Systems, 90–95. Cham: Springer International Publishing, 2011. http://dx.doi.org/10.1007/978-3-031-79336-3_23.

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

Marwedel, Peter. "System Software." In Embedded Systems, 203–37. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-60910-8_4.

Full text
Abstract:
AbstractIn order to cope with the complexity of applications of embedded systems, reuse of components is a key technique. As pointed out by Sangiovanni-Vincentelli (The context for platform-based design. IEEE Design and Test of Computers, 2002), software and hardware components must be reused in the platform-based design methosdology (see p. 296). These components comprise knowledge from earlier design efforts and constitute intellectual property (IP). Standard software components that can be reused include system software components such as embedded operating systems (OSs) and middleware. The last term denotes software that provides an intermediate layer between the OS and application software. This chapter starts with a description of general requirements for embedded operating systems. This includes real-time capabilities as well as adaptation techniques to provide just the required functionality. Mutually exclusive access to resources can result in priority inversion, which is a serious problem for real-time systems. Priority inversion can be circumvented with resource access protocols. We will present three such protocols: the priority inheritance, priority ceiling, and stack resource protocols. A separate section covers the ERIKA real-time system kernel. Furthermore, we will explain how Linux can be adapted to systems with tight resource constraints. Finally, we will provide pointers for additional reusable software components, like hardware abstraction layers (HALs), communication software, and real-time data bases. Our description of embedded operating systems and of middleware in this chapter is consistent with the overall design flow.
APA, Harvard, Vancouver, ISO, and other styles

Conference papers on the topic "Software systems"

1

Hen-Geul Yeh and Paul Ingerson. "Software-defined radio for OFDM transceivers." In 2010 4th Annual IEEE Systems Conference. IEEE, 2010. http://dx.doi.org/10.1109/systems.2010.5482434.

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

Menon, Catherine, and Tim Kelly. "Eliciting software safety requirements in complex systems." In 2010 4th Annual IEEE Systems Conference. IEEE, 2010. http://dx.doi.org/10.1109/systems.2010.5482343.

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

Boxer, Philip J. "Building organizational agility into large-scale software-reliant environments." In 2009 3rd Annual IEEE Systems Conference. IEEE, 2009. http://dx.doi.org/10.1109/systems.2009.4815830.

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

Kumar, Ashok, Sujana Shruthi Mudhole, and Blake Lemoine. "A smart sensor-based software system for driver evaluation." In 2010 4th Annual IEEE Systems Conference. IEEE, 2010. http://dx.doi.org/10.1109/systems.2010.5482437.

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

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
6

Turner, Richard, Arthur Pyster, and Michael Pennotti. "Developing and validating a framework for integrating systems and software engineering." In 2009 3rd Annual IEEE Systems Conference. IEEE, 2009. http://dx.doi.org/10.1109/systems.2009.4815836.

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

Boutayeb, M. "A decentralized software sensor based approach for large-scale dynamical systems." In 2010 4th Annual IEEE Systems Conference. IEEE, 2010. http://dx.doi.org/10.1109/systems.2010.5482344.

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

Oberndorf, Patricia, and Carol A. Sledge. "Evolution of a software engineer in a SoS system engineering world." In 2010 4th Annual IEEE Systems Conference. IEEE, 2010. http://dx.doi.org/10.1109/systems.2010.5482478.

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

van de Laar, Piërre, Sjir van Loo, Gerrit Muller, Teade Punter, David Watts, Pierre America, and Joland Rutgers. "The Darwin Project: Evolvability of Software-Intensive Systems." In Third International IEEE Workshop on Software Evolvability 2007. IEEE, 2007. http://dx.doi.org/10.1109/software-evolvability.2007.14.

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

Croll, Paul R. "System and software assurance — rationalizing governance, engineering practice, and engineering economics." In 2010 4th Annual IEEE Systems Conference. IEEE, 2010. http://dx.doi.org/10.1109/systems.2010.5482470.

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

Reports on the topic "Software systems"

1

Robey, Robert W. Software Build and Delivery Systems. Office of Scientific and Technical Information (OSTI), July 2016. http://dx.doi.org/10.2172/1261804.

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

Olson, Thomas J., Frank Z. Brill, Glenn S. Wasson, Jennifer A. Wong, and Ari S. Rapkin. Software for Advanced Vision Systems. Fort Belvoir, VA: Defense Technical Information Center, April 1995. http://dx.doi.org/10.21236/ada293507.

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

Olson, T. J. Software for Advanced Vision Systems. Fort Belvoir, VA: Defense Technical Information Center, July 1995. http://dx.doi.org/10.21236/ada306666.

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

Rosenthal, Lynne S. Integrated software for microcomputer systems. Gaithersburg, MD: National Bureau of Standards, 1986. http://dx.doi.org/10.6028/nbs.sp.500-135.

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

Chandrasekaran, B., and Bruce Weide. Functional Representation of Software Systems and Component-Based Software Technology. Fort Belvoir, VA: Defense Technical Information Center, February 1998. http://dx.doi.org/10.21236/ada341742.

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

Leibee, A. Nuclear Software Systems Division (NSSD) software testing and validation guidelines. Office of Scientific and Technical Information (OSTI), July 1987. http://dx.doi.org/10.2172/6676291.

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

Hoting, S. K., and R. J. Costello. Computer Systems Division Software System Metrics Approach, Revision 1. Fort Belvoir, VA: Defense Technical Information Center, September 1996. http://dx.doi.org/10.21236/ada328410.

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

Vo, C. V. Computer systems and software description for gas characterization system. Office of Scientific and Technical Information (OSTI), April 1997. http://dx.doi.org/10.2172/16922.

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

Moore, Tamra K. Information Systems Criteria for Applying Software Reengineering: Guidelines for Identifying Information Systems for Software Reengineering. Fort Belvoir, VA: Defense Technical Information Center, May 1993. http://dx.doi.org/10.21236/ada274699.

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

Turner, C. R., Alfonso Fuggetta, and Alexander L. Wolf. Toward Feature Engineering of Software Systems. Fort Belvoir, VA: Defense Technical Information Center, February 1997. http://dx.doi.org/10.21236/ada445868.

Full text
APA, Harvard, Vancouver, ISO, and other styles
You might also be interested in the extended bibliographies on the topic 'Software systems' 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