How to Write Software Design Descriptions

Plain English version of IEEE 1016


Author: David Tuffley
eBook
Pages: 23
Language: English
Publication date: 22.04.2011
1.95 €
VAT included
Instant download after purchase
Adobe PDF format Adobe PDF format
MS Word text format MS Word text format
Practical guide for software development project managers and staff
I N T R O D U C T I O N

The task of developing comprehensive Software Design Descriptions (SDDs) is greatly assisted by this document. Written for project personnel, it is basically a plain-English, simplified version of the IEEE Std 1016 Recommended Practice for Software Design Descriptions. While it infringes no copyright, it still embodies the essential detail of IEEE 1016.

It describes the:

Software development context in which an SDD should be created,
Minimum requirements for SDD format and content and,
Qualities of a good SDD.
Who is this document for? The SDD is created by the System Architect or designer and is the major deliverable from the detailed design process.

What are the Prerequisites? The prerequisite document required for an SDD varies according to the size and complexity of the software product to be developed. For large systems the prerequisite is the System Architecture Specification. In this context the SDD represents a further refinement of the design entities described in the SAS. An SDD may provide descriptions of one or more design entities. For small systems, the SDD prerequisite is a Software Requirements Specification. In this context it is the single source of design solutions to problems stated in the SRS.

Who uses the SDD? The SDD is the primary reference for code development. As such, it must contain all the information required by a programmer to write code.

Contribution to IS Quality A structured and comprehensive approach to software design is known to be a major factor contributing to Information Systems Quality. Adequate design is however often not performed, contributing to a higher number of software defects which impact the real and perceived quality of the software, as well as leading to time and expense being spent on rework and higher maintenance costs.

How to Write Software Design Descriptions is a plain-English, procedural guide to developing high quality SDDs that are both systematic and comprehensive. It contains detailed instructions and templates on the following test documentation.
El vendedor asume toda la responsabilidad de esta entrada.
Dr. David Tuffley is a Senior Lecturer in Applied Ethics and SocioTechnical Studies at Griffith University’s School of ICT. A regular contributor to mainstream media on the social impact of technology, David is a recognized expert in his field. Before academia David worked as an IT Consultant in Australia and the United Kingdom, a role he continues to perform when not educating the next generation of IT professionals. David is an engaging science communicator of many years experience, David was a guest panelist in the 2017 World Science Festival and a wide variety of high profile public events.

David's academic background includes fields as diverse as Psychology, Anthropology, Classical Rhetoric and English literature at the University of Queensland. David is an engaging professional speaker and forum moderator of many years experience.

David's formal qualifications include a PhD (Software Engineering), Master of Philosophy (Information Systems), Grad Cert in Higher Education (all from Griffith University), Bachelor of Arts majoring in Psychology, English Literature, Anthropology (University of Queensland)

If you like this ebook, you might also like:

© 2019 XinXii - GD Publishing Ltd. & Co. KG. Imprint | Terms of Use | Privacy Policy
€ Euro
International sites: German (main) | English | Spanish | French | Italian | Dutch | Portuguese | Russian