Log in

Relevant bibliographies by topics / Software systems / Journal articles

To see the other types of publications on this topic, follow the link: Software systems.

Journal articles 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 top 50 journal articles for your research 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.

Browse journal articles on a wide variety of disciplines and organise your bibliography correctly.

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

11

Conn, Richard. "Software Systems Requirements." Journal on Educational Resources in Computing 2, no. 4 (December 2002): 1. http://dx.doi.org/10.1145/949257.949258.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

&NA;. "INFORMATION SYSTEMS SOFTWARE." Nursing Management (Springhouse) 31, no. 9 (September 2000): 44. http://dx.doi.org/10.1097/00006247-200009000-00028.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

Boasson, M. "Control systems software." IEEE Transactions on Automatic Control 38, no. 7 (July 1993): 1094–106. http://dx.doi.org/10.1109/9.231463.

Full text

APA, Harvard, Vancouver, ISO, and other styles

14

Bernstein, Larry. "Trustworthy software systems." ACM SIGSOFT Software Engineering Notes 30, no. 1 (January 2005): 4–5. http://dx.doi.org/10.1145/1039174.1039176.

Full text

APA, Harvard, Vancouver, ISO, and other styles

15

Leu, M. C. "Robotics software systems." Robotics and Computer-Integrated Manufacturing 2, no. 1 (January 1985): 1–12. http://dx.doi.org/10.1016/0736-5845(85)90002-x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

Sherer, Susan A. "Purchasing software systems." Information & Management 24, no. 5 (January 1993): 257–66. http://dx.doi.org/10.1016/0378-7206(93)90003-c.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Korablin, Y. P., and A. A. Shipov. "Questions of verification in distributed software systems." Contemporary problems of social work 1, no. 2 (June 30, 2015): 102–6. http://dx.doi.org/10.17922/2412-5466-2015-1-2-102-106.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

ARAI, Tamio. "Software systems for assembly." Journal of the Japan Society for Precision Engineering 57, no. 2 (1991): 221–23. http://dx.doi.org/10.2493/jjspe.57.221.

Full text

APA, Harvard, Vancouver, ISO, and other styles

19

USHIDA, Hirohide, and Hiroshi NAKAJIMA. "Software Systems with Emotion." Journal of Japan Society for Fuzzy Theory and Systems 12, no. 6 (2000): 762–69. http://dx.doi.org/10.3156/jfuzzy.12.6_44.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Lenin, R. B., S. Ramaswamy, Liguo Yu, and R. B. Govindan. "Open Source Software Systems." International Journal of Open Source Software and Processes 2, no. 4 (October 2010): 28–47. http://dx.doi.org/10.4018/ijossp.2010100103.

Full text

Abstract:

Complex software systems and the huge amounts of data they produce are becoming an integral part of our organizations. We are also becoming increasingly dependent on high quality software products in our everyday lives. These systems ‘evolve’ as we identify and correct existing defects, provide new functionalities, or increase their nonfunctional qualities - such as security, maintainability, performance, etc. Simultaneously, more software development projects are distributed over multiple locations (often globally) and are often several millions of dollars in development costs. Consequently, as the Internet continually eliminates geographic boundaries, the concept of doing business within a single country has given way to companies focusing on competing in an international marketplace. The digitalization of work and the reorganization of work processes across many organizations have resulted in routine and/or commodity components being outsourced.

APA, Harvard, Vancouver, ISO, and other styles

21

Mössinger, Jürgen. "Software in Automotive Systems." IEEE Software 27, no. 2 (March 2010): 92–94. http://dx.doi.org/10.1109/ms.2010.55.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

Collings, Patti B. "Fathom: Dynamic Systems Software." American Statistician 55, no. 3 (August 2001): 258–59. http://dx.doi.org/10.1198/tas.2001.s123.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

Wing, Jeannette M., and Mandana Vaziri-Farahani. "Model checking software systems." ACM SIGSOFT Software Engineering Notes 20, no. 4 (October 1995): 128–39. http://dx.doi.org/10.1145/222132.222148.

Full text

APA, Harvard, Vancouver, ISO, and other styles

24

Gardner, Philippa. "Verified trustworthy software systems." Philosophical Transactions of the Royal Society A: Mathematical, Physical and Engineering Sciences 375, no. 2104 (September 4, 2017): 20150408. http://dx.doi.org/10.1098/rsta.2015.0408.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

Rice, J. R. "Future scientific software systems." IEEE Computational Science and Engineering 4, no. 2 (1997): 44–48. http://dx.doi.org/10.1109/99.609831.

Full text

APA, Harvard, Vancouver, ISO, and other styles

26

Lane, Chris. "Systems software integrity assurance." ACM SIGAda Ada Letters 30, no. 3 (November 5, 2010): 11–12. http://dx.doi.org/10.1145/1879097.1879071.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

Hamlet, Dick. "Continuity in software systems." ACM SIGSOFT Software Engineering Notes 27, no. 4 (July 2002): 196–200. http://dx.doi.org/10.1145/566171.566203.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Pruett, G., A. Abbondanzio, J. Bielski, T. D. Fadale, A. E. Merkin, Z. Rafalovich, L. A. Riedle, and J. W. Simpson. "BladeCenter systems management software." IBM Journal of Research and Development 49, no. 6 (November 2005): 963–75. http://dx.doi.org/10.1147/rd.496.0963.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Crnkovic, Ivica, and Judith Stafford. "Embedded Systems Software Architecture." Journal of Systems Architecture 59, no. 10 (November 2013): 1013–14. http://dx.doi.org/10.1016/j.sysarc.2013.11.005.

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

Müllerburg, M. "Software intensive embedded systems." Information and Software Technology 41, no. 14 (November 1999): 979–84. http://dx.doi.org/10.1016/s0950-5849(99)00072-5.

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

Limebeer, David J. N. "Control systems software reviews." Automatica 30, no. 4 (April 1994): 563. http://dx.doi.org/10.1016/0005-1098(94)90140-6.

Full text

APA, Harvard, Vancouver, ISO, and other styles

32

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

33

OHTAKE, HISAO, TOSHIO TSUJI, and HIROYUKI KURATA. "Software of Living Systems." KAGAKU KOGAKU RONBUNSHU 25, no. 2 (1999): 169–76. http://dx.doi.org/10.1252/kakoronbunshu.25.169.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

Chen, I. R. "High Assurance Software Systems." Computer Journal 49, no. 5 (February 17, 2006): 507–8. http://dx.doi.org/10.1093/comjnl/bxl040.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Hasselbring, W., and R. Reussner. "Toward Trustworthy Software Systems." Computer 39, no. 4 (April 2006): 91–92. http://dx.doi.org/10.1109/mc.2006.142.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Rechtin, Eberhardt. "Software systems architecting (abstract)." ACM SIGSOFT Software Engineering Notes 21, no. 6 (November 1996): 1. http://dx.doi.org/10.1145/250707.239102.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Ritter, Norbert. "Engineering adaptive software systems." it – Information Technology 56, no. 1 (January 28, 2014): 1–3. http://dx.doi.org/10.1515/itit-2014-9001.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Murphy, E. E., and J. Voelcker. "Technology '90: systems software." IEEE Spectrum 27, no. 1 (1990): 38–40. http://dx.doi.org/10.1109/6.45053.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Buffet, Pierre. "Telecommunication systems and software." World Patent Information 14, no. 1 (February 1992): 13–16. http://dx.doi.org/10.1016/0172-2190(92)90144-8.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Atamtürk, Alper, and Martin W. P. Savelsbergh. "Integer-Programming Software Systems." Annals of Operations Research 140, no. 1 (November 2005): 67–124. http://dx.doi.org/10.1007/s10479-005-3968-2.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Jackson, Daniel, Martyn Thomas, Lynette I. Millett, and Trace Baker. "Software For Dependable Systems." INSIGHT 11, no. 2 (April 2008): 62–63. http://dx.doi.org/10.1002/inst.200811262.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Суханова, Наталия, Nataliya Sukhanova, Юрий Соломенцев, Yuriy Solomentsev, Сергей Шептунов, Sergey Sheptunov, Илья Кабак, and Ilya Kabak. "Automation software reliability assessment software for control systems." Bulletin of Bryansk state technical university 2015, no. 3 (September 30, 2015): 157–60. http://dx.doi.org/10.12737/23018.

Full text

Abstract:

Software is complex and expensive product. As to the automation systems are applied the high wants, included reliability of software. To realize projects in the field of automation of technolo-gy processes it is necessary to construct the new software and to improve, adapt and transfer existing software. The field of investigations and trial of software reliability was not automated yet, the instrumental tools are absent, witch can allow to estimate reliability indexes at all stages of software life cycle. In the article it is developed the structure of automation system for soft-ware reliability monitoring.

APA, Harvard, Vancouver, ISO, and other styles

43

Petkov, Doncho, Denis Edgar-Nevill, Raymond Madachy, and Rory O’Connor. "Information Systems, Software Engineering, and Systems Thinking." International Journal of Information Technologies and Systems Approach 1, no. 1 (January 2008): 62–78. http://dx.doi.org/10.4018/jitsa.2008010105.

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

Carithers, W. R. "Systems software: An introduction to systems programming." Proceedings of the IEEE 75, no. 3 (1987): 431. http://dx.doi.org/10.1109/proc.1987.13750.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

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

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Akyildiz, Ian F., Pu Wang, and Shih-Chun Lin. "SoftWater: Software-defined networking for next-generation underwater communication systems." Ad Hoc Networks 46 (August 2016): 1–11. http://dx.doi.org/10.1016/j.adhoc.2016.02.016.

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

Barsiienko, Vladyslav, and Oksana Lashko. "Software System of Decoding Light Codes." Advances in Cyber-Physical Systems 6, no. 1 (January 23, 2021): 1–7. http://dx.doi.org/10.23939/acps2021.01.001.

Full text

Abstract:

The paper presents the stages of creating a software system for decoding light codes and examines the effectiveness of its operation. The relevance of the development is due to the need to combine the speed and distance of information delivery for the further development of wireless communication systems. The authors’ attention is focused on considering the basic components of the designed system. The main algorithms of operation have been presented and the effectiveness of their development has been proved. A comparison with existing means has been made and the prospects for the development of cable free optical communication systems have been emphasized.

APA, Harvard, Vancouver, ISO, and other styles

48

Steinbrückner, Frank, and Claus Lewerentz. "Understanding software evolution with software cities." Information Visualization 12, no. 2 (March 19, 2012): 200–216. http://dx.doi.org/10.1177/1473871612438785.

Full text

Abstract:

Software cities are visualizations of software systems in the form of virtual cities. They are used as platforms to integrate a large variety of product- and process-related analysis data. Their usability, however, for real-world software development often suffers from their inability to appropriately deal with software changes. Even small structural changes can disrupt the overall structure of the city, which in turn corrupts the mental maps of its users. In this article we describe a systematic approach to utilize the city metaphor for the visualization of evolving software systems as growing software cities. The main contribution is a new layout approach which explicitly takes the development history of software systems into account. The approach has two important effects: first, it creates a stable gestalt of software cities even when the underlying software systems evolve; thus, by preserving its users’ mental maps these cities are especially suitable for use during ongoing system development. Second, it makes history directly visible in the city layouts, which allows for supporting novel analysis scenarios. We illustrate such scenarios by presenting several thematic cities’ maps, each capturing specific development history aspects.

APA, Harvard, Vancouver, ISO, and other styles

49

WANG, Bei-Yang, and Jin-Hu LÜ. "Software Networks Nodes Impact Analysis of Complex Software Systems." Journal of Software 24, no. 12 (January 17, 2014): 2814–29. http://dx.doi.org/10.3724/sp.j.1001.2013.04397.

Full text

APA, Harvard, Vancouver, ISO, and other styles

50

Kemp, A. "Requirements capture. Getting better software and software-based systems." Engineering Management Journal 6, no. 3 (1996): 149. http://dx.doi.org/10.1049/em:19960314.

Full text

APA, Harvard, Vancouver, ISO, and other styles

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!