Log in

Relevant bibliographies by topics / Software design / Journal articles

Journal articles on the topic 'Software design'

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

Author: Grafiati

Published: 4 June 2021

Last updated: 1 August 2024

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

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

Tharmaseelan, Janani. "Cohesive Software Design." International Journal of Trend in Scientific Research and Development Volume-3, Issue-3 (April 30, 2019): 955–57. http://dx.doi.org/10.31142/ijtsrd22900.

Full text

APA, Harvard, Vancouver, ISO, and other styles

2

Early, M. "Relating software requirements to software design." ACM SIGSOFT Software Engineering Notes 11, no. 3 (July 1986): 37–39. http://dx.doi.org/10.1145/12923.12924.

Full text

APA, Harvard, Vancouver, ISO, and other styles

3

Shapiro, Stuart. "Software by Design." Information Society 12, no. 2 (June 1996): 205–6. http://dx.doi.org/10.1080/713856148.

Full text

APA, Harvard, Vancouver, ISO, and other styles

4

Stevens, P. "Software design patterns." Computing & Control Engineering Journal 11, no. 4 (August 1, 2000): 160–62. http://dx.doi.org/10.1049/cce:20000403.

Full text

APA, Harvard, Vancouver, ISO, and other styles

5

Willhoft, Blaine, and Rob Willhoft. "Decoding Software Design." Computing in Science & Engineering 19, no. 3 (May 2017): 86–87. http://dx.doi.org/10.1109/mcse.2017.41.

Full text

APA, Harvard, Vancouver, ISO, and other styles

6

Savage, Neil. "Optical design software." Nature Photonics 1, no. 10 (October 2007): 598–99. http://dx.doi.org/10.1038/nphoton.2007.190.

Full text

APA, Harvard, Vancouver, ISO, and other styles

7

Intergraph (Great Britain) Ltd. "Plant design software." Computer-Aided Design 17, no. 5 (June 1985): 251. http://dx.doi.org/10.1016/0010-4485(85)90106-x.

Full text

APA, Harvard, Vancouver, ISO, and other styles

8

Mukherjee, Debagish. "Software by Design." Information Processing & Management 31, no. 2 (March 1995): 264–65. http://dx.doi.org/10.1016/0306-4573(95)80053-v.

Full text

APA, Harvard, Vancouver, ISO, and other styles

9

Viana, Elizandra Biá, Taís Arriero Shinma Galbetti, Marcus Vinicius Galbetti, Vinícius de Oliveira Ribeiro, and Jonailce Oliveira Diodato. "AltBlock - Design Storms Software." Terr Plural 16 (2022): 1–12. http://dx.doi.org/10.5212/terraplural.v.16.2220175.036.

Full text

Abstract:

A design storm can be defined as a precipitation pattern used to determine indirectly the design flood, which is an important data in many hydrologic design projects. Due to difficult to obtain historical data on precipitation, it has become common to construct design storms using general characteristics of precipitation in the surrounding region, represented by intensity-duration-frequency (IDF) relationships. In addition, it’s also necessary specify design return period, storm duration and the temporal distribution. For this purpose, is used the Alternating Block Method. In the view of software development applied to hydrology and to make more practical using this Alternating Block Method, this article intended to develop the AltBlock, a software able to calculate design storms automatically. Using Visual Studio .NET and the programming language Visual Studio .NET it was sought to build a graphical user-friendly interface. The AltBlock is applicable to any location and it’s useful for educational uses, engineering projects and hydrological studies.

APA, Harvard, Vancouver, ISO, and other styles

10

Tang, Antony, and Hans van Vliet. "Design Strategy and Software Design Effectiveness." IEEE Software 29, no. 1 (January 2012): 51–55. http://dx.doi.org/10.1109/ms.2011.130.

Full text

APA, Harvard, Vancouver, ISO, and other styles

11

Budgen, David. "‘Design models’ from software design methods." Design Studies 16, no. 3 (July 1995): 293–325. http://dx.doi.org/10.1016/0142-694x(95)00001-8.

Full text

APA, Harvard, Vancouver, ISO, and other styles

12

Aggarwal, K. K., Yogesh Singh, Arvinder Kaur, and Ruchika Malhotra. "Software Design Metrics for Object-Oriented Software." Journal of Object Technology 6, no. 1 (2007): 121. http://dx.doi.org/10.5381/jot.2007.6.1.a4.

Full text

APA, Harvard, Vancouver, ISO, and other styles

13

CEPERO GARCÍA, MARÍA TERESA, LUIS GERARDO MONTANE JIMENEZ, GUADALUPE TOLEDO TOLEDO, EDGARD IVAN BENITEZ GUERRERO, and CARMEN MEZURA GODOY. "HEURISTICS FOR COLLABORATIVE SOFTWARE DESIGN." DYNA 96, no. 4 (July 1, 2021): 346. http://dx.doi.org/10.6036/10172.

Full text

Abstract:

Collaborative software (groupware) provides the means for a group of people to develop team activities. These systems provide information that helps people understand events beyond their current tasks, e.g., understanding who is participating, where they are, what they are saying, and what they are doing.

APA, Harvard, Vancouver, ISO, and other styles

14

Del Fiol, Guilherme, Haley Hanseler, Barbara Crouch, Mollie Cummins, and Scott Nelson. "Software prototyping." Applied Clinical Informatics 07, no. 01 (January 2016): 22–32. http://dx.doi.org/10.4338/aci-2015-07-cr-0091.

Full text

Abstract:

SummaryHealth information exchange (HIE) between Poison Control Centers (PCCs) and Emergency Departments (EDs) could improve care of poisoned patients. However, PCC information systems are not designed to facilitate HIE with EDs; therefore, we are developing specialized software to support HIE within the normal workflow of the PCC using user-centered design and rapid prototyping.To describe the design of an HIE dashboard and the refinement of user requirements through rapid prototyping.Using previously elicited user requirements, we designed low-fidelity sketches of designs on paper with iterative refinement. Next, we designed an interactive high-fidelity prototype and conducted scenario-based usability tests with end users. Users were asked to think aloud while accomplishing tasks related to a case vignette. After testing, the users provided feedback and evaluated the prototype using the System Usability Scale (SUS).Survey results from three users provided useful feedback that was then incorporated into the design. After achieving a stable design, we used the prototype itself as the specification for development of the actual software. Benefits of prototyping included having 1) subject-matter experts heavily involved with the design; 2) flexibility to make rapid changes, 3) the ability to minimize software development efforts early in the design stage; 4) rapid finalization of requirements; 5) early visualization of designs; 6) and a powerful vehicle for communication of the design to the programmers. Challenges included 1) time and effort to develop the prototypes and case scenarios; 2) no simulation of system performance; 3) not having all proposed functionality available in the final product; and 4) missing needed data elements in the PCC information system.

APA, Harvard, Vancouver, ISO, and other styles

15

余, 子文. "Optimization of 3D Software Interface Design Based on Eye Tracking Testing." Design 08, no. 02 (2023): 313–24. http://dx.doi.org/10.12677/design.2023.82044.

Full text

APA, Harvard, Vancouver, ISO, and other styles

16

Oja, M., B. Tamm, and K. Taveter. "AGENT-BASED SOFTWARE DESIGN." Proceedings of the Estonian Academy of Sciences. Engineering 7, no. 1 (2001): 5. http://dx.doi.org/10.3176/eng.2001.1.02.

Full text

APA, Harvard, Vancouver, ISO, and other styles

17

Cleaveland, Rance. "Formality and software design." ACM Computing Surveys 28, no. 4es (December 1996): 117. http://dx.doi.org/10.1145/242224.242376.

Full text

APA, Harvard, Vancouver, ISO, and other styles

18

Bentley, J. L., and J. A. Dallen. "Exercises in Software Design." IEEE Transactions on Software Engineering SE-13, no. 11 (November 1987): 1164–69. http://dx.doi.org/10.1109/tse.1987.232865.

Full text

APA, Harvard, Vancouver, ISO, and other styles

19

Carvajal, Laura, Ana M. Moreno, Maria-Isabel Sanchez-Segura, and Ahmed Seffah. "Usability through Software Design." IEEE Transactions on Software Engineering 39, no. 11 (November 2013): 1582–96. http://dx.doi.org/10.1109/tse.2013.29.

Full text

APA, Harvard, Vancouver, ISO, and other styles

20

Mills, Mike, and Greg Peterson. "Hardware/software co-design." ACM SIGAda Ada Letters XVIII, no. 6 (November 1998): 18–27. http://dx.doi.org/10.1145/301687.289528.

Full text

APA, Harvard, Vancouver, ISO, and other styles

21

Glass, Robert L. "CREATIVITY AND SOFTWARE DESIGN." Information Systems Management 9, no. 3 (January 1992): 38–43. http://dx.doi.org/10.1080/10580539208906880.

Full text

APA, Harvard, Vancouver, ISO, and other styles

22

Feathers, M. "Before clarity [software design]." IEEE Software 21, no. 6 (November 2004): 86–88. http://dx.doi.org/10.1109/ms.2004.37.

Full text

APA, Harvard, Vancouver, ISO, and other styles

23

Krauskopf, J. "Elemental concerns (software design)." IEEE Potentials 9, no. 1 (February 1990): 13–15. http://dx.doi.org/10.1109/45.46811.

Full text

APA, Harvard, Vancouver, ISO, and other styles

24

De Michell, G., and R. K. Gupta. "Hardware/software co-design." Proceedings of the IEEE 85, no. 3 (March 1997): 349–65. http://dx.doi.org/10.1109/5.558708.

Full text

APA, Harvard, Vancouver, ISO, and other styles

25

Sommerville, I. "Describing Software Design Methodologies." Computer Journal 30, no. 2 (February 1, 1987): 128–33. http://dx.doi.org/10.1093/comjnl/30.2.128.

Full text

APA, Harvard, Vancouver, ISO, and other styles

26

Fowler, M. "Avoiding repetition [software design]." IEEE Software 18, no. 1 (2001): 97–99. http://dx.doi.org/10.1109/52.903175.

Full text

APA, Harvard, Vancouver, ISO, and other styles

27

Berry, Daniel M. "Software requirements and design." ACM SIGSOFT Software Engineering Notes 36, no. 2 (March 14, 2011): 39–40. http://dx.doi.org/10.1145/1943371.1943379.

Full text

APA, Harvard, Vancouver, ISO, and other styles

28

Kearsley, Greg, and Rachelle Heller. "Teaching instructional software design." ACM SIGCSE Bulletin 24, no. 3 (September 1992): 24–28. http://dx.doi.org/10.1145/142040.142059.

Full text

APA, Harvard, Vancouver, ISO, and other styles

29

Sparagen, Susan L., and Amnon Riback. "Flexible Software Interface Design." Ergonomics in Design: The Quarterly of Human Factors Applications 7, no. 4 (October 1999): 4–8. http://dx.doi.org/10.1177/106480469900700402.

Full text

APA, Harvard, Vancouver, ISO, and other styles

30

Dikananda, Arif Rinaldi, Achmad Daengs GS, Dahlan Abdullah, and Cut Ita Erliana. "Chess Game Software Design." Journal of Physics: Conference Series 1364 (December 2019): 012023. http://dx.doi.org/10.1088/1742-6596/1364/1/012023.

Full text

APA, Harvard, Vancouver, ISO, and other styles

31

Vanacken, J., Li Liang, K. Rosseel, W. Boon, and F. Herlach. "Pulsed magnet design software." Physica B: Condensed Matter 294-295 (January 2001): 674–78. http://dx.doi.org/10.1016/s0921-4526(00)00742-0.

Full text

APA, Harvard, Vancouver, ISO, and other styles

32

O'Donnell, Hugh. "Negotiating CALL software design." Language Learning Journal 1, no. 1 (1990): 55–57. http://dx.doi.org/10.1080/09571739085200181.

Full text

APA, Harvard, Vancouver, ISO, and other styles

33

Rahmani, M. "Software modeling & design." ACM SIGSOFT Software Engineering Notes 36, no. 4 (August 4, 2011): 35. http://dx.doi.org/10.1145/1988997.1989008.

Full text

APA, Harvard, Vancouver, ISO, and other styles

34

Jackson, Daniel. "Dependable Software by Design." Scientific American 294, no. 6 (June 2006): 68–75. http://dx.doi.org/10.1038/scientificamerican0606-68.

Full text

APA, Harvard, Vancouver, ISO, and other styles

35

Pandey, R. K. "Managing software design complexity." ACM SIGSOFT Software Engineering Notes 34, no. 1 (January 31, 2009): 1–4. http://dx.doi.org/10.1145/1457516.1457526.

Full text

APA, Harvard, Vancouver, ISO, and other styles

36

Akhil, Soma, and Soma Anvesh. "Software Engineering Design Issues." International Journal of Engineering Trends and Technology 18, no. 4 (December 25, 2014): 184–86. http://dx.doi.org/10.14445/22315381/ijett-v18p237.

Full text

APA, Harvard, Vancouver, ISO, and other styles

37

Kalyanov, G. N. "Case: Software design technologies." Cybernetics and Systems Analysis 29, no. 5 (1994): 760–70. http://dx.doi.org/10.1007/bf01125806.

Full text

APA, Harvard, Vancouver, ISO, and other styles

38

Palmer, ThomasC. "Software and system design." Journal of Molecular Graphics 10, no. 1 (March 1992): 42–43. http://dx.doi.org/10.1016/0263-7855(92)80020-e.

Full text

APA, Harvard, Vancouver, ISO, and other styles

39

Comer, James R., Herb C. Conn, and Kurt A. Schember. "Software design and development." ACM SIGCSE Bulletin 17, no. 1 (March 1985): 335–41. http://dx.doi.org/10.1145/323275.323403.

Full text

APA, Harvard, Vancouver, ISO, and other styles

40

Littlewood, Bev, Peter Popov, and Lorenzo Strigini. "Modeling software design diversity." ACM Computing Surveys 33, no. 2 (June 2001): 177–208. http://dx.doi.org/10.1145/384192.384195.

Full text

APA, Harvard, Vancouver, ISO, and other styles

41

Bubenik, R., and W. Zwaenepoel. "Optimistic make (software design)." IEEE Transactions on Computers 41, no. 2 (1992): 207–17. http://dx.doi.org/10.1109/12.123396.

Full text

APA, Harvard, Vancouver, ISO, and other styles

42

Coplien, J. O. "Software patterns: Design utilities." Computer 29, no. 10 (October 1996): 48. http://dx.doi.org/10.1109/mc.1996.539721.

Full text

APA, Harvard, Vancouver, ISO, and other styles

43

Campbell, A. "Computer-aided software design." Information and Software Technology 33, no. 3 (April 1991): 246–47. http://dx.doi.org/10.1016/0950-5849(91)90146-3.

Full text

APA, Harvard, Vancouver, ISO, and other styles

44

Card, D. N., and W. W. Agresti. "Measuring software design complexity." Journal of Systems and Software 8, no. 3 (June 1988): 185–97. http://dx.doi.org/10.1016/0164-1212(88)90021-0.

Full text

APA, Harvard, Vancouver, ISO, and other styles

45

Vogt, Peter. "Patterns in software design." Landscape Ecology 34, no. 9 (March 28, 2019): 2083–89. http://dx.doi.org/10.1007/s10980-019-00797-9.

Full text

APA, Harvard, Vancouver, ISO, and other styles

46

Sandusky, Robert J. "Bringing design to software." Journal of the American Society for Information Science 48, no. 12 (December 1997): 1149–50. http://dx.doi.org/10.1002/(sici)1097-4571(199712)48:12<1149::aid-asi10>3.0.co;2-0.

Full text

APA, Harvard, Vancouver, ISO, and other styles

47

Suvorov, Anatoliy Sergeevich, Oleg Fedorovich Sevriukov, Evgeniy Mikhailovich Sokov, Mikhail Borisovich Salin, Svetlana Georgievna Zaitseva, and Varvara Alekseevna Sharagina. "Software for Acoustic Design." Journal of Applied Mathematics and Physics 11, no. 08 (2023): 2515–22. http://dx.doi.org/10.4236/jamp.2023.118162.

Full text

APA, Harvard, Vancouver, ISO, and other styles

48

Jolak, Rodi, Maxime Savary-Leblanc, Manuela Dalibor, Andreas Wortmann, Regina Hebig, Juraj Vincur, Ivan Polasek, Xavier Le Pallec, Sébastien Gérard, and Michel R. V. Chaudron. "Software engineering whispers: The effect of textual vs. graphical software design descriptions on software design communication." Empirical Software Engineering 25, no. 6 (September 10, 2020): 4427–71. http://dx.doi.org/10.1007/s10664-020-09835-6.

Full text

Abstract:

Abstract Context Software engineering is a social and collaborative activity. Communicating and sharing knowledge between software developers requires much effort. Hence, the quality of communication plays an important role in influencing project success. To better understand the effect of communication on project success, more in-depth empirical studies investigating this phenomenon are needed. Objective We investigate the effect of using a graphical versus textual design description on co-located software design communication. Method Therefore, we conducted a family of experiments involving a mix of 240 software engineering students from four universities. We examined how different design representations (i.e., graphical vs. textual) affect the ability to Explain, Understand, Recall, and Actively Communicate knowledge. Results We found that the graphical design description is better than the textual in promoting Active Discussion between developers and improving the Recall of design details. Furthermore, compared to its unaltered version, a well-organized and motivated textual design description–that is used for the same amount of time–enhances the recall of design details and increases the amount of active discussions at the cost of reducing the perceived quality of explaining.

APA, Harvard, Vancouver, ISO, and other styles

49

Luo, Ning, and Yue Xiong. "Enhanced Software Design for Boosted Continuous Software Delivery." International Journal of Software Engineering & Applications 13, no. 02 (March 31, 2022): 23–31. http://dx.doi.org/10.5121/ijsea.2022.13202.

Full text

Abstract:

Engineering efficiency in continuous software delivery can be impacted by multiple factors. In this paper, citing one ultra-large-scale software - Intel Media Driver as an example, we analyse the hotspots impacting the engineering efficiency in continuous software delivery, their challenges to our software design and the experiences on software delivery efficiency boost against the targeted design enhancements. We expect the identified hotspots can help more researchers to form the corresponding research agendas and the experiences shared can help following practitioners to apply similar enhancements.

APA, Harvard, Vancouver, ISO, and other styles

50

French, Allen C. "Software engineering applied to programmable controller software design." ISA Transactions 29, no. 2 (January 1990): 23–32. http://dx.doi.org/10.1016/0019-0578(90)90060-x.

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!