Software Design
Arthur Tatnall · Encyclopedia of Education and Information Technologies · 2020
Cited by 0
Read the abstract, see who wrote it and who cites it, and get the citation in APA, MLA, Chicago or Harvard.
About 10,000 papers for “software design”
Arthur Tatnall · Encyclopedia of Education and Information Technologies · 2020
Cited by 0
2005
Cited by 0
Rachita Misra, Chhabi Rani Panigrahi, Bijayalaxmi Panda et al. · Advances in systems analysis, software engineering, and high performance computing book series · 2015
This chapter on “Software Design” emphasizes the role of modeling, prototyping, and simulation in software design. The chapter introduces the principles of software design, issues and challenges. Modeling techniques used in procedural and object oriented methodologies is presented along with the Unified Modeling Language (UML). The suitability of prototyping, as a design artifact and a simulation method is briefly discussed. Software processes such as Rapid Application Development (RAD), Rational Unified Process (RUP) and Agile methodologies which influence the design process have been discussed and recommended. The chapter then deals with Design Metrics for Quality Analysis, Software Risk Analysis and Threat Modeling for design of secure software. Finally, some of the recent research topics such as Model Driven Architecture (MDA), Model Driven Development (MDD), Meta Object Facility (MOF), and Model Driven Testing (MDT) have been covered.
Cited by 0
Bo Fu (200894), Mark C. Pitter (200895), Noah A. Russell (200896) · Figshare · 2015
<p>Example schematic of the software. The arrows show data flow from producer loops (P) to consumer loops (C). Solid loops represent lossless data process while dotted loops represent lossy process. For example, commands from the user are processed by the Graphical User Interface (GUI) producer loop before being passed, without loss, to the Acquisition consumer loop. Note that loops can be both producers and consumers (e.g. Acquisition). The line thickness of the loop represents its running priority. Thicker lines indicate higher priority tasks.</p>
Cited by 0Open access
Roberto Minelli, Roberto Minelli · 2012
Cited by 0
NASA Technical Reports Server (NASA)
A NASA contractor and Small Business Innovation Research (SBIR) participant has converted its research into commercial software products for auto design, structural analysis and other applications. ViGYAN, Inc., utilizing the aeronautical research principle of computational fluid dynamics, has created - with VGRID3D and VPLOT3D - an easier alternative to conventional structured grids for fluid dynamic calculations.
Cited by 0Open access
James Derry · Apress eBooks · 2025
In this chapter, we learn about the top-down design (TDD) methodology for organizing code in large programming projects. Then we learn how to implement that methodology using Python functions. Implemented thus, they act as subroutines and the main routine of a program. Also implemented thus, we can put our subroutines in one text file (module) and invoke them from the main routine in another text file (module). Organizing our code in this way emphasizes its modularity.
Cited by 0
2006
This chapter contains sections titled: Software Design Concepts Software Architecture Software Design Quality Analysis and Evaluation Software Design Notations and Documentation Software Design Strategies and Methods Human Factors in Software Design Software and System Safety
Cited by 0
Elsevier eBooks · 1995
Cited by 0
Francisco Burgos-Flórez (12055176), Alexander Rodríguez (2631949), Eliana Cervera (12055179) et al. · Figshare · 2022
Cited by 0Open access
Stuart Ball · Elsevier eBooks · 2002
Cited by 0
2000
Cited by 0
2012
Cited by 0
Anne L. C. Runehov, Lluís Oviedo · 2013
Cited by 0
Keith R. Wehmeyer · 2021
Cited by 0
Suely Oliveira, David E. Stewart · Cambridge University Press eBooks · 2006
Software engineering is about the task of designing and implementing software. It is not about the specific algorithms or techniques to be programmed, but about how to organize both the software and the people who develop it. While many programmers have the attitude “Just do it!” and can cope with small programs just fine, large programs and, indeed, any programs that you expect other people to use, need careful attention and design.
Cited by 0
Ebrisa Savina Mastrodicasa, Tommaso Dal Sasso, Ebrisa Savina Mastrodicasa et al. · 2014
Cited by 0
Auerbach Publications eBooks · 2012
Cited by 0
Kevin Lano, José Luiz Fiadeiro, Luís Andrade · 2002
This chapter describes the role of design in the software development process, and gives some desirable properties of software designs. It introduces three examples: a restaurant management system, an on-line football game, and a bank account management system, and describes what the design process consists of for these systems.KeywordsCurrent AccountSoftware DesignClass DiagramSequence DiagramInteraction DiagramThese keywords were added by machine and not by the authors. This process is experimental and the keywords may be updated as the learning algorithm improves.
Cited by 0
Kevin Sullivan · 1996
Many software engineering principles and concepts that are critical to reasoning about problems in software design (of which software architecture is an important special case) remain ad hoc, idiosyncratic and poorly integrated. I argue that this is due to our lack of a clean theory about how to make software design decisions. In this paper I propose that we should view software design as a process of deciding how to make irreversible capital investment in software assets of uncertain value, and that financial options theory provides a firm, unifying, simplifying and well developed basis for such decision-making. To support this view, I interpret software architecture and other related concepts in options theoretic terms.
Cited by 32Open access