Academic literature on the topic 'Software design'

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

Journal articles on the topic "Software design"

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

Dissertations / Theses on the topic "Software design"

1

Loomes, Martin James. "Software engineering curriculum design." Thesis, University of Surrey, 1991. http://epubs.surrey.ac.uk/844417/.

Full text
Abstract:
Software engineering design is a vital component of modern industry, unfortunately, the processes involved are still poorly understood. This poses a major problem for teachers of the subject, who are under constant pressure to improve the quality of education, but are unsure how to bring this about, or even how to detect such improvement. This thesis attempts to start the process of clarifying what we mean by "software engineering design", and apply the insights gained to the activity of curriculum design. First, we establish a method for the research, by constructing a framework to constrain and guide the process of seeking new insights. This leads to a decidedly eclectic approach to the problem, as software engineering design is viewed, and reviewed, from a number of different perspectives. Next, these views are synthesised into a model of the software engineering design process, and new insights are sought to refine the model. The central theme of this model is the idea that the design process can be considered as a one of theory building. Finally, we bring this model into direct contact with the task of curriculum design, both in a general sense, and also by providing illustrations of some of the consequences of its use.
APA, Harvard, Vancouver, ISO, and other styles
2

Love, Randall James. "Predictive software design measures." Thesis, This resource online, 1994. http://scholar.lib.vt.edu/theses/available/etd-06112009-063248/.

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

Wirell, Cecilia. "Software." Thesis, Konstfack, Textil, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:konstfack:diva-6784.

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

Ström, David. "Purposes of Software Architecture Design." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2005. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2830.

Full text
Abstract:
Software architecture design as an engineering field has evolved greatly during the last 15 years, which is evident by the number of methods, styles, patterns, and guidelines available for its practitioners in industry. This paper takes a closer look at the purposes behind this field to reveal the level of discrepancy in pursued purposes between industrial practitioners and published methods for software architecture design. In our research surveys of architecture design methods and of purposes at a number of industrial practitioners resulted in two sets of purposes which were eventually compared and the level of discrepancy identified.
Mjukvarudesign är ett område inom mjukvaruindustrin som utvecklats omfattande under de senaste 15 åren, vilket synliggjorts av de nya metoder, designstilar, designmönster och paradigmer som gjorts tillgängliga för mjukvaruutvecklare idag. Den här uppsatsen gör en djupgranskning av syftena bakom detta arbetsområde för att upptäcka eventuella skillnader mellan de syften som framhålls av befintliga arkitekturmetoder och de syften som åtsträvas av utövare inom mjukvaruindustrin.
APA, Harvard, Vancouver, ISO, and other styles
5

Cronje, Johannes Jacobus. "Software architecture design of a software defined radio system." Thesis, Stellenbosch : Stellenbosch University, 2004. http://hdl.handle.net/10019.1/50095.

Full text
Abstract:
Thesis (MScEng)--University of Stellenbosch, 2004.
ENGLISH ABSTRACT: The high pace of technological advancement enables the realisation of ever more advanced mobile communications standards with more functionality than simple voice communications. The hardware that is used to implement the radio sections of these systems generally require long design cycles, much longer than the design cycles of the other components of a communications system. Another problem is that, once new communications standards are introduced, the current hardware platforms used in the terminal equipment becomes obsolete because they can generally not be used with the new standards. This has serious cost implications for both the service provider and the consumer, because both parties have to acquire new equipment to be able to use the new standards. An elegant solution to the above issues is to use software-defined radio sections to replace the hardware radio components. New communications standards can then be supported by simply loading new software onto the equipment, provided the maximum processing capacity of the processor(s) that the software runs on can accommodate the bandwidth requirements of that specific standard. This thesis investigates the ideas behind software defined radio and also describes the design and implementation of a software architecture that can be used to implement software defined radios on general-purpose platforms such as personal computers.
AFRIKAANSE OPSOMMING: Die hoë tempo van tegnologiese vordering maak dit moontlik om baie gevorderde mobiele kommunikasie standaarde te implementeer wat meer funksionaliteit bied as blote spraakkommunikasie. Die hardeware wat gebruik word om die radios van sulke stelsels te implementeer neem gewoonlik langer om te ontwikkel as die ander komponente van die stelsels. Die ander probleem is dat hierdie hardeware gewoonlik nie hergebruik kan word wanneer nuwe kommunikasie standaarde in gebruik geneem word nie omdat die standaarde nie versoenbaar is nie. Dit het tot gevolg dat beide die verbruiker en die diensverskaffer groot bedrae geld moet spandeer om die nuwe tegnologie te kan gebruik. 'n Elegante oplossing vir hierdie probleme is om gebruik te maak van radios waarvan die funksionaliteit in sagteware gedefiniëer word. Nuwe kommunikasie standaarde kan dan gebruik word deur slegs die nodige sagteware op die toerusting te laai, solank die verwerkingskapasiteit van die mikroverwerkers in die stelsel die benodigde bandwydte kan akkommodeer. Hierdie tesis ondersoek die konsepte van sagteware-gedefiniëerde radio en beskryf die ontwerp en implementering van 'n sagteware argitektuur vir die implementering van sagteware-gedefiniëerde radios op veeldoelige platforms soos persoonlike rekenaars.
APA, Harvard, Vancouver, ISO, and other styles
6

Waqas, Ahmad, and Fawad Kamal. "Modeling Patterns in Software Design." Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2007. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2350.

Full text
Abstract:
Software patterns provide solutions to recurring design problems, provide a way to reason about the quality attributes, and support stakeholders in understanding the system. Naturally, the use of software patterns emerges from the requirements of the software. Use Cases have been a traditional and authentic approach to document these requirements. We propose a way to mine these patterns by sing use cases and advocate their significance in saving resources and time. For this purpose, an open-source system is discussed and four design patterns are mined with the help of use cases elicited from the documentation and literature available for the selected system. Patterns mined in this system are then document in GOF format.Furthermore, the consequences of few patterns on quality attributes are studied and an additional design pattern is proposed to improve the quality of the system.
Folkspark Vägan 15:11 ,372 40 Ronneby ,Sweden
APA, Harvard, Vancouver, ISO, and other styles
7

Lesage, Pierre-Yves. "Numerical computation and software design." Thesis, Cranfield University, 1999. http://dspace.lib.cranfield.ac.uk/handle/1826/11134.

Full text
Abstract:
The development of simulation tools is becoming an important area in industry, recently fostered by the tremendous improvements in computer hardware. Many physical problems can be simulated by being modelled by mathematical equations which can then be solved numerically. This thesis is concerned with the development of a Finite Difference solver for time dependent partial differential equations. The development involves a number of challenging requirements that the solver must meet: to have the capacity of solving conservation and non-conservation laws (using several numerical techniques), to be robust, efficient and to have a modular and extendible design. Firstly, we focus on the architecture of the program and how an original design approach was used in order to carry out its development. A combination of Object- Oriented Design and Structured Design was adopted.
APA, Harvard, Vancouver, ISO, and other styles
8

Ralph, David Paul. "Fundamentals of software design science." Thesis, University of British Columbia, 2010. http://hdl.handle.net/2429/29536.

Full text
Abstract:
This dissertation comprises three essays on software design science, the philosophical, theoretical and empirical study of software creation and modification including its phenomenology, methodology and causality. The essays consider three limitations evident in the software design science literature: 1) lack of a precisely-defined, well-understood vocabulary; 2) difficulties surrounding empirical research; 3) lack of theory concerning the design process’s structure and organization. The first essay presents an extensive review of definitions of design, revealing nontrivial disagreements regarding its nature and scope. Following this, a formal definition of design and a conceptual model of design projects are constructed. The definition incorporates seven elements – agent, object, environment, goals, primitives, requirements and constraints. The conceptual model views design projects as temporal trajectories of work systems, in which human agents design systems for stakeholders, using resources and tools. This provides a detailed, defensible basis for theoretical and empirical software design science research. The second essay addresses the difficulties of empirical software design science research by elucidating a broad, bipolar conflict in design literature between two incompatible beliefs: 1) the belief that design is an innately cognitive, approximately rational, plan-centered activity (Reason-Centric Perspective); 2) the belief that design is an emergent phenomenon, improvised through continual interaction between agents and environments (Action-Centric Perspective). Each perspective is operationalized through a software design process theory: the Function-Behavior-Structure Framework (chosen for the Reason-Centric Perspective) and the Sensemaking-Coevolution-Implementation Framework (proposed for the Action-Centric Perspective). The third essay presents a survey study comparing these perspectives and theories. Responses from 1384 software development professionals in 65 countries indicate that the Sensemaking-Coevolution-Implementation Framework more accurately describes the structure and organization of their design processes than the Function-Behavior-Structure Framework. Gender, education, experience, nationality, occupation, team size, project duration, firm size, methodologies in use, and the nature of the software had no measurable effect on this finding. This supports a theory of the design process’s structure and organization and facilitates several streams of empirical research including studies of design project success.
APA, Harvard, Vancouver, ISO, and other styles
9

Kalfoglou, I. "Deploying ontologies in software design." Thesis, University of Edinburgh, 2000. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.653180.

Full text
Abstract:
1). After presenting an in depth analysis of the field of ontologies and software testing as conceived and implemented by the software engineering and artificial intelligence communities (chapter 2), we discuss an approach which enabled us to deploy ontologies in the early phases of software development (i.e.: specifications) in order to detect conceptual errors (chapter 3). It is based on the provision of ontological axioms which are used to verify conformance of specification constructs to the underpinning ontology. To facilitate the integration of ontology with applications that adopt it we developed an architecture and built tools to implement the this form of conceptual errors check (chapter 4). We apply and evaluate the architecture on a variety of contexts to identify potential uses (chapter 5). An implication of this method for deploying ontologies to reason about the correctness of applications is to raise our trust in given ontologies. However, when these are erroneous we might fail to reveal pernicious discrepancies. To cope with this problem we extended the architecture in a multi-layer form (chapter 4) which gives us the ability to check for correctness the ontologies themselves. We apply this multi-layer architecture to capture errors founded in a complex ontologies lattice (chapter 6). We further elaborate on the weaknesses in ontology evaluation methods and employed a technique stemming form software engineering, that of experience management, to facilitate ontology testing and deployment. (chapter 7). The work presented in this thesis aims to improve ontology exercise and identify areas to which ontologies could be of benefits other than the advocated ones of knowledge sharing and reuse (chapter 8).
APA, Harvard, Vancouver, ISO, and other styles
10

Kamal, Muhammad. "Software design methods and errors." Thesis, University of Liverpool, 1991. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.317143.

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

Books on the topic "Software design"

1

Budgen, David. Software Design. Third edition. | Boca Raton : CRC Press, 2021. | Series: Chapman & Hall/CRC innovations in software engineering: Chapman and Hall/CRC, 2020. http://dx.doi.org/10.1201/b21883.

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

Budgen, D. Software design. Wokingham, England: Addison-Wesley Pub. Co., 1994.

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

Gagarina, Larisa, Elena Akimova, Anton Garaschenko, Ilona Kapitanova, Martin Tihonov, and Larisa Gagarina. Software design. ru: INFRA-M Academic Publishing LLC., 2023. http://dx.doi.org/10.12737/1893880.

Full text
Abstract:
The basic concepts and definitions, classification of software, stages of software product creation within the life cycle are considered, the current state of software product development technologies is highlighted. The existing approaches to assessing the quality of software creation processes are described, requirements analysis and definition of software specifications are performed. Much attention is paid to the issues of software design, its reliability, and collective development using modern version control systems. The theoretical material is accompanied by a workshop in the form of laboratory work on the stated topic. Meets the requirements of the federal state educational standards of higher education of the latest generation. For students and teachers of higher educational institutions of technical profile, as well as for specialists of any subject area who have shown interest in the current state of programming methods and tools.
APA, Harvard, Vancouver, ISO, and other styles
4

Beningo, Jacob. Embedded Software Design. Berkeley, CA: Apress, 2022. http://dx.doi.org/10.1007/978-1-4842-8279-3.

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

H, Packard Michael, Ziemianski Tom, and United States. National Aeronautics and Space Administration., eds. Software design improvements. [Washington, D.C: National Aeronautics and Space Administration, 1997.

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

Collins, Rip. Software by design. Beaverton, Or: Dilithium Press, 1985.

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

Hong, Zhu. Software design methodology. Amsterdam: Elsevier Butterworth-Heinemann, 2005.

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

Charles, Thies, ed. Secure software design. Burlington, Mass: Jones & Bartlett Learning, 2013.

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

1955-, Lowry Michael R., and McCartney Robert D, eds. Automating software design. Menlo Park: AAAI Press, 1991.

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

Terry, Winograd, ed. Bringing design to software. New York, N.Y: ACM Press, 1996.

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

Book chapters on the topic "Software design"

1

Sølvberg, Arne, and David Chenho Kung. "Software Design." In Information Systems Engineering, 81–143. Berlin, Heidelberg: Springer Berlin Heidelberg, 1993. http://dx.doi.org/10.1007/978-3-642-78001-1_3.

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

Lano, Kevin, José Luiz Fiadeiro, and Luís Andrade. "Software Design." In Software Design Using Java 2, 1–24. London: Macmillan Education UK, 2002. http://dx.doi.org/10.1007/978-1-4039-1466-8_1.

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

Arya, Ali. "Software Design." In Anyone Can Code, 533–41. First edition. | Boca Raton : CRC Press, 2020.: Chapman and Hall/CRC, 2020. http://dx.doi.org/10.1201/9780429244421-20.

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

Rao, Natti S. "Design Software." In Diagnostics of Extrusion Processes, 79–88. München: Carl Hanser Verlag GmbH & Co. KG, 2014. http://dx.doi.org/10.3139/9781569905692.005.

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

Manns, Tom, and Michael Coleman. "Software Design." In Software Quality Assurance, 176–82. London: Macmillan Education UK, 1996. http://dx.doi.org/10.1007/978-1-349-13285-0_10.

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

Weston, Joseph. "Software Design." In Springer Theses, 51–66. Cham: Springer International Publishing, 2017. http://dx.doi.org/10.1007/978-3-319-63691-7_4.

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

Wheat, Dale. "Software Design." In Arduino Internals, 255–80. Berkeley, CA: Apress, 2011. http://dx.doi.org/10.1007/978-1-4302-3883-6_11.

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

Morshed, Bashir I. "Software Design." In Embedded Systems – A Hardware-Software Co-Design Approach, 101–66. Cham: Springer International Publishing, 2021. http://dx.doi.org/10.1007/978-3-030-66808-2_4.

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

Rettig, Alexander. "Software Design." In Engineering Haptic Devices, 387–429. Berlin, Heidelberg: Springer Berlin Heidelberg, 2009. http://dx.doi.org/10.1007/978-3-540-88248-0_13.

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

Rao, Natti S. "Design Software." In Diagnostics of Extrusion Processes, 79–88. München, Germany: Carl Hanser Verlag GmbH & Co. KG, 2014. http://dx.doi.org/10.1007/978-1-56990-569-2_5.

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

Conference papers on the topic "Software design"

1

Ernst, Neil A., and John Mylopoulos. "Tracing software evolution history with design goals." In Third International IEEE Workshop on Software Evolvability 2007. IEEE, 2007. http://dx.doi.org/10.1109/software-evolvability.2007.19.

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

Arcelli, Francesca, and Luca Christina. "Enhancing Software Evolution through Design Pattern Detection." In Third International IEEE Workshop on Software Evolvability 2007. IEEE, 2007. http://dx.doi.org/10.1109/software-evolvability.2007.7.

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

Sullivan, Kevin J. "Software design." In Joint proceedings of the second international software architecture workshop (ISAW-2) and international workshop on multiple perspectives in software development (Viewpoints '96). New York, New York, USA: ACM Press, 1996. http://dx.doi.org/10.1145/243327.243338.

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

Broadfoot, G. "Analytical software design case: MagLev Stage software design." In Embedded Systems Conference ESS2005 Incorporating the IEE FPGA Developers Forum. IEE, 2005. http://dx.doi.org/10.1049/ic:20050678.

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

Capilla, Rafael, Francisco Nava, and Antony Tang. "Attributes for Characterizing the Evolution of Architectural Design Decisions." In Third International IEEE Workshop on Software Evolvability 2007. IEEE, 2007. http://dx.doi.org/10.1109/software-evolvability.2007.3.

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

de Haan, Geert. "Software design and media design." In the 29th Annual European Conference. New York, New York, USA: ACM Press, 2011. http://dx.doi.org/10.1145/2074712.2074778.

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

Bass, Len. "Software Architecture Design." In 2009 22nd Conference on Software Engineering Education and Training. IEEE, 2009. http://dx.doi.org/10.1109/cseet.2009.50.

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

Robillard, Martin P. "Sustainable software design." In FSE'16: 24nd ACM SIGSOFT International Symposium on the Foundations of Software Engineering. New York, NY, USA: ACM, 2016. http://dx.doi.org/10.1145/2950290.2983983.

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

van Dooren, Maikel, and Bart Zevenhoven. "WTF design software." In IABSE Congress, Ghent 2021: Structural Engineering for Future Societal Needs. Zurich, Switzerland: International Association for Bridge and Structural Engineering (IABSE), 2021. http://dx.doi.org/10.2749/ghent.2021.1471.

Full text
Abstract:
<p>Over the past years the demand for wind farms in the Netherlands on both land and sea has considerably grown. Three years ago, the Dutch contractor Dura Vermeer has decided to expand its activities with the realization of wind farms on land. A part of this activity is the design of Wind Turbine Foundations (WTFs). Where a wind farm can vary from 6 to 90+ wind turbines, the amount of WTF designs that must be considered in one project can be large for an object that is relatively standard. This especially because the interaction between soil and WTF must be considered for every specific location. The process of designing can be very time consuming. Both due to the amount of repetitive actions and the use of standard design software the question may be asked if, when following the traditional designing route, an optimal design is obtained. Dura Vermeer decided to perform the designing work with help of parametric design.</p><p>Together with a software developer, Dura Vermeer developed a web application in which structural and geotechnical calculation models are coupled. The calculation models are centrally controlled in an online interface in which a set of variables (e.g. dimensions, soil parameters, structural load etc.) can be controlled by the user. The coupling between the structural and geotechnical models works in an iterative manner, making it possible to design with structural parameters that correspond very accurate to the geotechnical results. By making use of the link between these calculation models the risk of human mistakes is reduced and the time required for the design is drastically shortened. With the built-in optimization tool, it is furthermore possible to obtain an efficient design with a small amount of effort and due to the parametric approach, it is possible to generate standard design documents.</p>
APA, Harvard, Vancouver, ISO, and other styles
10

Duell, Michael, John Goodsen, and Linda Rising. "Non-software examples of software design patterns." In Addendum to the 1997 ACM SIGPLAN conference. New York, New York, USA: ACM Press, 1997. http://dx.doi.org/10.1145/274567.274592.

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

Reports on the topic "Software design"

1

Seyfarth, Benjamin R., Jerry L. Bickham, and Germana Peggion. Glenda Software Design. Fort Belvoir, VA: Defense Technical Information Center, February 1995. http://dx.doi.org/10.21236/ada292537.

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

Aleman, S. E., G. P. Flach, L. L. Hamm, S. Y. Lee, and F. G. III Smith. FLOWTRAN-TF software design. Office of Scientific and Technical Information (OSTI), February 1993. http://dx.doi.org/10.2172/10151616.

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

Aleman, S. E., G. P. Flach, L. L. Hamm, S. Y. Lee, and F. G. III Smith. FLOWTRAN-TF software design. Office of Scientific and Technical Information (OSTI), February 1993. http://dx.doi.org/10.2172/6538896.

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

Budgen, David. Introduction to Software Design. Fort Belvoir, VA: Defense Technical Information Center, January 1989. http://dx.doi.org/10.21236/ada236118.

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

Long, John P., William G. Wood, and David P. Wood. Classifying Software Design Methods. Fort Belvoir, VA: Defense Technical Information Center, August 1989. http://dx.doi.org/10.21236/ada226696.

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

El-Kady, Ihab. MIRaGE: Design Software for Metamaterials. Office of Scientific and Technical Information (OSTI), August 2020. http://dx.doi.org/10.2172/1648194.

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

Gaugush, Robert F. Sampling Design Software User's Manual. Fort Belvoir, VA: Defense Technical Information Center, February 1993. http://dx.doi.org/10.21236/ada262632.

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

Drayna, Travis, Laura Lang, Louie Long, and Henry Stam. CrossLink - Software Design and Methods. Office of Scientific and Technical Information (OSTI), January 2023. http://dx.doi.org/10.2172/1922002.

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

Bachmann, Felix, Len Bass, and Mark Klein. Preliminary Design of ArchE: A Software Architecture Design Assistant. Fort Belvoir, VA: Defense Technical Information Center, September 2003. http://dx.doi.org/10.21236/ada421618.

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

Lawrence, J. D., and G. G. Preckshot. Design factors for safety-critical software. Office of Scientific and Technical Information (OSTI), December 1994. http://dx.doi.org/10.2172/10196677.

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!

To the bibliography