Software design is a process of problem-solving and planning for a
softwaresolution. After the purpose and specifications of software are determined, software developers will designor employ designers to develop a plan for a solution. It includes low-level component and algorithm implementation issues as well as the architectural view.
software requirements analysis(SRA) step of a software development processyields specificationsthat are used in software engineering. If the software is "semiautomated" or user centered, software design may involve user experience designyielding a story boardto help determine those specifications. If the software is completely automated (meaning no useror user interface), a software design may be as simple as a flow chartor text describing a planned sequence of events. There are also semi-standard methods like Unified Modeling Languageand Fundamental modeling concepts. In either case some documentationof the plan is usually the product of the design.
Software design topics
There are many aspects to consider in the design of a piece of software. The importance of each should reflect the goals the software is trying to achieve. Some of these aspects are:
* Compatibility - The software is able to operate with other products that are designed for interoperability with another product. For example, a piece of software may be backward-compatible with an older version of itself.
* Extensibility - New capabilities can be added to the software without major changes to the underlying architecture.
* Fault-tolerance - The software is resistant to and able to recover from component failure.
* Maintainability - The software can be restored to a specified condition within a specified period of time. For example, antivirus software may include the ability to periodically receive virus definition updates in order to maintain the software's effectiveness.
* Marketability - If the software is to be mass marketed, there must be a market for the software. Research must be conducted to determine the
target marketand its needs.
* Modularity - the resulting software comprises well defined, independent components. That leads to better maintainability. The components could be then implemented and tested in isolation before being integrated to form a desired software system. This allows division of work in a software development project.
* Packaging - Printed material such as the box and manuals should match the style designated for the target market and should enhance usability. All compatibility information should be visible on the outside of the package. All components required for use should be included in the package or specified as a requirement on the outside of the package.
* Reliability - The software is able to perform a required function under stated conditions for a specified period of time.
* Reusability - the modular components designed should capture the essence of the functionality expected out of them and no more or less. This single-minded purpose renders the components reusable wherever there are similar needs in other designs.
* Robustness - The software is able to operate under stress or tolerate unpredictable or invalid input. For example, it can be designed with a resilience to low memory conditions.
* Security - The software is able to withstand hostile acts and influences.
* Usability - The software
user interfacemust be intuitive (and often aesthetically pleasing) to its target user/audience. In many cases, online helpshould be included and also carefully designed.
Design methodologies aim to provide a template process or a framework for the actual design of a system. They aim to simplify the actual process of designing a system and aim to enforce some standard design principles which improve the quality of a design. One of the earlier design methodologies is the Responsibility Driven Design (RDD) pioneered by Rebecca Wirth et al. It forms the basis of the URDAD, the Use Case, Responsibility-Driven Analysis and Design method which aims to generate a technology neutral design which is then mapped onto one's choice of implementation architecture and technologies.
A software designer or architect may identify a design problem which has been solved by others before. A template or pattern describing a solution to a common problem is known as a design pattern. The reuse of such patterns can speed up the software development process, having been tested and proved in the past.
design documentation may be reviewed or presented to allow constraints, specifications and even requirements to be adjusted prior to programming. Redesign may occur after review of a programmed simulationor prototype. It is possible to design software in the process of programming, without a plan or requirement analysis, but for more complex projects this would not be considered a professional approach. A separate design prior to programming allows for multidisciplinarydesigners and Subject Matter Experts (SMEs) to collaborate with highly-skilled programmers for software that is both useful and technically sound.
Aspect-oriented software development
Common layers in an information system logical architecture
Search Based Software Engineering
Software Design Description(IEEE 1016)
Wikimedia Foundation. 2010.
Look at other dictionaries:
Software design pattern — In software engineering, a design pattern is a general reusable solution to a commonly occurring problem within a given context in software design. A design pattern is not a finished design that can be transformed directly into code. It is a… … Wikipedia
Software design document — A software design document (SDD) is a written description of a software product, that a software designer writes in order to give a software development team an overall guidance of the architecture of the software project. An SDD usually… … Wikipedia
Software Design Description — Definitionen von IEEE SQAP – Software Quality Assurance Plan IEEE 730 SCMP – Software Configuration Management Plan IEEE 828 STD – Software Test Documentation IEEE 829 SRS – Software Requirements Specification IEEE 830 SVVP – Software Validation… … Deutsch Wikipedia
Software Design Description — IEEE 1016 1998, also known as the 1016 Standard for Software Design Description is an IEEE standard that specifies the form of the document used to specify system architecture and application design in a software related project.The Document… … Wikipedia
Software design & management — Capgemini sd m AG Unternehmensform Aktiengesellschaft … Deutsch Wikipedia
Nintendo Software Design & Development — Nintendo SDD Software Design Development Type R D Branch and Subsidiary of Nintendo Industry Video games F … Wikipedia
Virtuality (software design) — Virtuality is a term used by Ted Nelson for what he considers the central issues of software design. Virtuality refers to the seeming of anything, as opposed to its reality. (This has been the dictionary meaning of virtuality since at least the… … Wikipedia
Berkeley Software Design — Inc. (BSDI or, later, BSDi) was a corporation which developed, sold licences to, and supported BSD/OS (previously known as BSD/386), a commercial and partially proprietary variant of the BSD Unix operating system for PC compatible computer… … Wikipedia
Feature (software design) — The Institute of Electrical and Electronics Engineers defines the term feature in IEEE 829 as A distinguishing characteristic of a software item (e.g., performance, portability, or functionality). [… … Wikipedia
Catalysis software design method — Catalysis™ is a method for the specification and design of component based computer systems originally developed by Desmond D’Souza and Alan Cameron Wills in their 1999 book [ Objects, Components and Frameworks with UML: The Catalysis Approach ,… … Wikipedia