Note: The Detailed Design Document cannot be generalized for all the projects. This is a guide only document. Marking may be dependent upon other factors including the nature of the project etc. and may not be restricted to this guide. Team Name: Marker: Document: SDD (Software Design Document) Criteria and Description Comment Mark General (15 marks) Purpose and scope • Objectives and goals • Stakeholders • Document scope and Product scope (5 marks) Description and Justification • User characteristics and chosen methodology for project, including development environment/languages. • Relevant benefits- a framework for satisfying requirements, technical basis for design, managerial basis for cost estimation & process management and an effective basis for reuse. • Evidence of appropriate LLD (Low-Level Design) processes from the relevant HLD (High-Level Design) models/diagrams- in identifying the sub-systems making up a system (decomposition) and the framework for sub-system (control and communication). • Represents the link between specifications and design processes (High-Level to Low-Level) (10 marks) Architectural Design Overview (15 marks) • Inclusion of Architectural styles and element- • Component, connector, and interfaces • Constraints on interactions, behavioural and concurrency. • Other constraints relevant to project • Static and Dynamic Aspects of the system • Functional and non-functional aspects of the system • High-Level Design (HLD) models of Interfaces- Hardware (if any), Software, Communication and control • Preliminary defined Colour maps, fonts, button layouts, menu design, etc. • Design-specific Context and Use Case diagrams (incorporating design decisions) • High-Level distribution models- e.g. 3 tiered architecture, client server, etc.- Discuss limitations/constraints; mention portability and other qualities (non-functional requirements) and how they are addressed in the design. (15 marks) Detailed Design (50 marks) • Updated description of data and processing (relevant to the system design as appropriate) • e.g., Data dictionary, file formats, data structures. Appropriate diagrams might include Normalised E-R Diagrams and Schema, Description of objects, Flow Diagrams, Event diagrams, Sequence diagrams, Interaction diagrams, state diagrams, Implementation diagrams etc. as relevant to the methodology chosen. • Detailed decomposition of system - using structure charts and module decomposition (Structured Approach), design class diagrams, updated/detailed storyboards for multimedia etc. • Programme/code-specific design specifications (coding patterns, algorithms/pseudo-codes etc.), implementation-specific database design specifications (queries etc.), design specifications related to the non-functional requirements. • Detailed storyboards (multimedia)/GUI design/Screen and Report layouts. • Design-specific well-defined Colours, Fonts, Button layouts, menu design, etc. • Games Design- inclusion of detailed technical specifications o Describe the engine to be used for development and context of interactions with other inputs (e.g. data file, user inputs). o Define input file formats and game mechanics. Provide all programming design information and standards as relevant. o Detailed description of models, may include memory usage and limitations of requirements (e.g. memory card limits). For each model/scene state polygon count, textures (mipmaps), visual effects, lighting, colour maps etc. (50 marks) Others (20 marks) • Research, Initiative and Creativity- Evidence of appropriate research and initiative on the ‘project-specific’ design aspects and inclusion of new and creative design views in relevance. (10 marks) • Layout and Presentation- Table of contents, referencing, appropriateness of document to this particular project. (5 marks) • Overall quality (5 marks) Total Mark: /100 Scaled: /10 General Comments (if any): Summary- Software Design Document (SDD) 10% This should include the Architectural Design and expansion of the architecture into the Detailed Design, and will ensure that the system will work when all sub parts are put together. This document will be important for the future maintenance of the system also and should be given to the client. Please note that the presentation (invigilated) will outline a team’s design also and so contributes to the assessment of the chosen design. The Software Design Document (SDD) must contain the architectural design scheme plus more detail regarding the breakdown of the system and detailed diagrams outlining the design. Game designs should be detailed including technical specifications: Describe the engine to be used for development and context of interactions with other inputs (e.g. data file, user inputs). Define input file formats and game mechanics. Provide all programming design information and standards as relevant. Detailed description of models, particularly stating memory usage and limitations of requirements (e.g. memory card limits). For each model/scene state polygon count, textures (mipmaps), visual effects, lighting, colour maps etc. In short, the Architectural Design part should have the High Level design (HLD) specifications/models/diagrams and the Detailed Design part should have the Low Level Design (LLD) specifications/models/diagrams. These should answer all the questions that may arise during programming and should provide enough detail that it could be given to a group of programmers to code from. If you answer yes to those, then it is probably worth very high marks.