Factbites
 Where results make sense
About us   |   Why use us?   |   Reviews   |   PR   |   Contact us  

Topic: Design document


Related Topics

In the News (Tue 29 Dec 09)

  
  Gamasutra - Features - "The Anatomy of a Design Document, Part 1" [10.19.99]
A design document is a bible from which the producer preaches the goal, through which the designers champion their ideas, and from which the artists and programmers get their instructions and express their expertise.
Unfortunately, design documents are sometimes ignored or fall short of their purpose, failing the producers, designers, artists, or programmers in one way or another.
The lead designer is the principle author of all the documentation with the exception of the technical specification, which is written by the senior programmer or technical director.
www.gamasutra.com /features/19991019/ryan_01.htm   (878 words)

  
 Design document - Wikipedia, the free encyclopedia
A design document is a 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.
A design document is practically required to coordinate a large team under a single vision.
A design document needs to be stable reference, and outline all parts of the software and how they will work.
en.wikipedia.org /wiki/Design_document   (330 words)

  
 Design Documents - Game Design Documents
This design document is very precise and to the point.
This design document is a incomplete transscript of the original Doom Design Bible.
It is not an example of a good design document, but quite the opposite.
www.ihfsoft.com /designdocuments.htm   (328 words)

  
 Gamasutra - Features "Creating a Great Design Document" [09.12.97]
The original designer may be an integral part of the team, but in many cases - especially in large companies - the designer ends up as a kind of outside consultant.
Without question, the design document is where the original parent of the project exercises the most influence on how this little baby is going to grow up.
The challenge is to create a design document that will allow your project to tolerate surprise adaptations without losing the integrity of its original direction and scope.
www.gamasutra.com /features/19970912/design_doc.htm   (3132 words)

  
 Game design - Wikipedia, the free encyclopedia
A document which describes a game's design maybe used during development (often called a design document), although this is not the only way to design a game.
Iterative design tends to be more suitable for core game mechnics (or gameplay) where the emergent properties of the design can be very hard to predict.
Because of the demands of the market, designers are often required to design games based on licensed properties or IPs—some of which may place very stringent and difficult to negotiate constraints upon the design.
en.wikipedia.org /wiki/Game_design   (1328 words)

  
 A Software Design Specification Template
The design document used for high-level design is a "living document" in that it gradually evolves to include low-level design details (although perhaps the "Detailed Design" section may not yet be appropriate at the high-level design phase).
Frequently, one of the best ways to document a project's design is to keep a detailed project journal, log, or diary of issues as they are mulled over and bandied about and to record the decisions made (and the reasons why) in the journal.
For the remaining sections of this document, it is conceivable (and perhaps even desirable) that one or more of the section topics are discussed in a separate design document within the project.
www.cmcrossroads.com /bradapp/docs/sdd.html   (2815 words)

  
 Xalan-J 2.0 Design
This document presents the basic design for Xalan-J 2.0, which is a refactoring and redesign of the Xalan-J 1.x processor.
Please note that the diagrams in this design document are meant to be useful abstractions, and may not always be exact.
An important part of the XPath design in both Xalan 1 and Xalan 2, is to enable database connections to be used as drivers directly to the XPath LocationPath handling.
xml.apache.org /xalan-j/design/design2_0_0.html   (2911 words)

  
 Writing a Design Document for Computer Science 51
Writing design documents develops and hones your ability to think through a design and reduce the number of costly and unplanned changes to your software program.
The design document is designed to get you to think about the details of each project in advance and to practice communicating succinctly about what you are doing.
Design documents are due far before the problem set is due.
www.fas.harvard.edu /~lib51/files/design_doc/index.html   (1770 words)

  
 Design Document Fundamentals -- Part 1
Because there are just as many ways to produce a design document as there are ways to write a book, for the purposes of this article, I will take you through the format I've personally used.
Also, before the actual design document drafting begins, you need to have had creative meetings and a pooling of all the best ideas, design notes, and diagrams that will make up the game play and look of the product.
From the designer’s standpoint it becomes very useful in helping him or her see how all of the subjects in the design flow into the overall structure of the product design.
www.gignews.com /andersondesigner2.htm   (2198 words)

  
 Detailed Design Document   (Site not responding. Last check: 2007-10-14)
The Design Document (DD) is an EPRI requirement only for software with commercial potential outside of EPRI.
Typically, the Design Document consists of tables and diagrams that translate the functional specification into data structures, data flows, and algorithms.
The designer's goal is to develop a model that achieves the functional requirements while operating within key constraints, such as performance goals and hardware.
www.epri.com /eprisoftware/processguide/ddd.html   (310 words)

  
 Amazon.com: Dynamics in Document Design: Creating Text for Readers: Books: Karen A. Schriver   (Site not responding. Last check: 2007-10-14)
Document design is a relatively new field of study, so the comprehensive timeline of its development is a gold mine, especially since no author has attempted it before.
And her research spans several decades, which is invaluable for tracking the evolution of document design.
Later chapters presenting the results of various reader response studies are interesting enough, but surely we could move more quickly to the results and their relevance to document design without spending so much time with dry narration of the actual empirical testing.
www.amazon.com /Dynamics-Document-Design-Creating-Readers/dp/0471306363   (1943 words)

  
 fish user documentation   (Site not responding. Last check: 2007-10-14)
This is a description of the design principles that have been used to design fish.
This design rule is different than the others, since it describes how one should go about designing new features, not what the features should be.
A program should be designed to make its features as easy as possible to discover for the user.
roo.no-ip.org /fish/user_doc/design.html   (1218 words)

  
 MONDO Design Document
The MONDO Design document is currently in draft form.
The PDF version is available as the whole MONDO Design Document or divided into chapters.
Later, these will either become part of the Design document or they may be placed into a new, seperate document.
www.chimu.com /projects/mondo/design/index.html   (228 words)

  
 XQEngine: Design Document   (Site not responding. Last check: 2007-10-14)
This document briefly details some of the more important architectural components of XQEngine and how they work.
As XQEngine's SAX parser encounters element, attribute, and text nodes during indexing, a two-part key and other information is appended to the end of the current NodeTree to represent the node, and the tree is grown as needed.
Text in element content that's encountered during indexing is concatenated in an element-text StringBuffer maintained by the NodeTree for that document, and pointers to the start and stop locations of each text node are stored in the tree.
xqengine.sourceforge.net /design.html   (1096 words)

  
 Design Document Skeleton
For a long time now I’ve been getting lots of emails from readers of GIGnews design articles asking for advice on how to setup a good design document, what subject they need to add, and in which order.
In answer to those questions, I am making available the design document skeleton that I’ve used for many years in one form or another.
He was also responsible for the original gameplay design for Abe's Oddysee for the Sony Playstation.
www.gignews.com /andersondesigndoc.htm   (198 words)

  
 SPECweb2005 Benchmark Design Document
It is designed to measure a system's ability to act as a web server servicing static and dynamic page requests.
This phase is designed to ramp up user activity rather than beginning the benchmark run with an immediate and full-load spike in requests.
And though SPECweb2005 is not designed as a capacity planning tool, by exposing more benchmark tuning flexibility in the configuration files and making it easier to add custom workloads, SPECweb2005 further extends its potential usefulness in capacity planning.
www.spec.org /web2005/docs/designdocument.html   (3096 words)

  
 design document concept from the Object Oriented Software Engineering knowledge base   (Site not responding. Last check: 2007-10-14)
includes the rationale for the design which allows the reader to better understand the design, helps reviewers to determine whether good decisions were made, and helps the maintainers determine how to change the design
Those who will be implementing the design, i.e.
details in a design document that would be better placed as comments in the code
www.site.uottawa.ca:4321 /oose/designdocument.html   (338 words)

  
 Document Design Online Journal
Document Design Online Journal served a purpose in the early internet days when the web was just taking shape, documenting some of the changes that were coming down the pike.
All that is history, now, as the web has matured into a shape that ever morphs into something else, often bigger, buggier, and less user friendly, especially to those of us who prefer to use something tried, true, and rarely destructive to our stable operating systems.
One of Whiskey Creek Document Design's vintage etchings.
www.wcdd.com /dd/ddindex.html   (503 words)

  
 BibDesk 2.0 Design Document - BibDeskWiki   (Site not responding. Last check: 2007-10-14)
Annotations should be able to be made directly on PDFs, and be portable with that PDF, but still indexed and presentable as part of the metadata of a document, for example, being accessible for HTML export.
A major goal is to be maximally flexible with what configurations the code can support, while not forcing the user to choose between a ton of choices that are no more different than various 'skins'.
We should present UI options for viewing, organizing and editing by the task they were designed to support.
bibdesk.sourceforge.net /wiki/index.php/BibDesk_2.0_Design_Document   (3295 words)

  
 Software Design Document – MIPS Simulator   (Site not responding. Last check: 2007-10-14)
The data design specifies how the data of the program is going to be stored.
The architectural design of a software project is simply the design of the entire software system.
A good architectural design will create a clear and fair balance between cohesion (each module has only one distinct purpose), coupling (no two modules depend completely on each other), abstraction (seeing modules in full and not in detail), hierarchy (logical modules stem from others) and partitioning (logically grouping modules together) of the software modules.
www.csc.calpoly.edu /~abenamou/csc405/dd.html   (607 words)

  
 SPECjAppServer2004 Design Document
Comment: While separated from the main text for readability, comments are a part of the design specification, and are meant to provide further clarification on the specific section.
By leaving the wording in the document, it is easier to expand the workload in future versions.
It communicates with the SUT by sending and receiving XML documents via a HTTP connection that conforms to the HTTP 1.1 protocol.
www.spec.org /jAppServer2004/docs/DesignDocument.html   (7458 words)

  
 Comp 410: Netmaintain Design Document   (Site not responding. Last check: 2007-10-14)
The purpose of this document is to provide a detailed description of the system leading to actual implementation.
The netmaintain system is designed for tracking and taking inventory of networked workstations, and the software provides a user-friendly interface to collect, analyze and store the relevant information.
The design of the client application with embedded SQL is described in the later sections.
www.owlnet.rice.edu /~comp410/design.html   (2174 words)

  
 R.S. Pressman & Associates, Inc.
Attributes of the overall software design (including data structures, OS features, I/O, and interoperable systems) that constrain the design of this sub-component are presented.
Special design issues which impact the design or implementation of the software are noted here.
A description of all design metrics to be used during the design activity is noted here.
www.rspa.com /docs/Designspec.html   (695 words)

  
 Design Document
The design to this point is sufficient to simulate the kidney forever.
However, a few have not been entirely prototyped, so the design of these dialog boxes will be explained a thoroughly as possible without visual reference.
Other dialogs are provided by MFC and, therefore, do not require extended discussion of there design other than that of there existence in the menu.
people.msoe.edu /~barnicks/courses/cs400/19967/renal/desdoc.htm   (3848 words)

  
 CUL Web Design Document
The "CUL WWW Design Guidelines" should be considered a document under continual review.
Use of any and all images, designs and text copied from other sources (including WWW sites) must adhere to copyright and licensing guidelines.
Provide visual consistency across related documents by using a style sheet or template.
www.library.cornell.edu /design/dsigndoc.html   (1130 words)

  
 Electronic Document Management Software: with Electronic Form Design, Document Archiving, and Automated Document Fax ...
EZeDocs is a powerful, yet affordable, form design and document delivery system that enables organizations to automate the exchange of critical business documents between customers, business partners, and suppliers.
Cut postage and document delivery costs while improving response times.
Design contemporary full-color business documents using EZDesigner, a simple, yet feature-rich GUI design tool.
www.acom.com /document_management   (259 words)

  
 MDC:Design Document - MDC
This section of the design document is intended to describe the information architecture that we wish to expose to users through navigation systems, internal nomenclature, and implicit ontologies (yes, yes, despite the fact that ontologies are overrated).
This information architecture proposes that any document ("content") can be classified (as a "content-type") and categorized in order to provide multiple navigation and organizational schemes.
Design elements should be reused so that to a casual user, the difference between wiki and weblog is minimal.
developer.mozilla.org /en/docs/Devmo:Design_Document   (1111 words)

  
 Document Output Management Software: Visually design document templates
EZDesigner is EZeDocs' innovative GUI document design tool that allows you to create sophisticated and professional looking business documents.
Create professional, color documents with ease; no extensive technical knowledge or custom programming is required.
Intuitive and familiar design tools will make what had been a chore almost fun.
www.acom.com /document_management/document_design.html   (283 words)

  
 Design Document
This report is the initial draft, based on one month of activity, of a design document intended to identify detailed technology integration opportunities for ALP and CoABS.
An ALP cluster is essentially a generalized agent shell, designed to provide a convenient way to define agents for individual organizations, and specialize them with/for their distinct functions.
The approach is to use graphical component composition (as in Visual Basic) to select a type of wiring, wizards to identify domain components, document object model, animated displays of control flow and data flow, and the single environment view for agents that actually operate in a distributed fashion.
www.objs.com /agility/tech-reports/9902-COABS-ALP-design-doc-1.html   (7600 words)

  
 Design Document
The website is designed to allow students to select topics of interest in the order of their choosing.
The trend of consistency continues with the layout of the page which is purposefully maintained from topic to topic, allowing the user to become familiar with the design.
The page design of my site is representative of the information architecture and the goal of interactivity.
homepages.nyu.edu /~jrc363/DesignDocument.html   (1737 words)

Try your search on: Qwika (all wikis)

Factbites
  About us   |   Why use us?   |   Reviews   |   Press   |   Contact us  
Copyright © 2005-2007 www.factbites.com Usage implies agreement with terms.