BIT 286: Web Applications Software Design Documents.

Slides:



Advertisements
Similar presentations
Logical and Physical Design of an Information System
Advertisements

System Development Life Cycle (SDLC)
Executional Architecture
Presentation by Prabhjot Singh
Software Modeling SWE5441 Lecture 3 Eng. Mohammed Timraz
Information Systems Analysis and Design
INFO 425 Week 31 INFO 425 Design Problem I Week 3 – SDS Improvements Glenn Booker.
Introduction To System Analysis and Design
1 SYSTEM and MODULE DESIGN Elements and Definitions.
Lecture 13 Revision IMS Systems Analysis and Design.
Analysis Stage (Phase I) The goal: understanding the customer's requirements for a software system. n involves technical staff working with customers n.
Requirements (recap)‏
Computers: Tools for an Information Age
9 1 Chapter 9 Database Design Database Systems: Design, Implementation, and Management, Seventh Edition, Rob and Coronel.
SE 555 Software Requirements & Specification Requirements Analysis.
Gregor v. Bochmann, University of Ottawa Based on Powerpoint slides by Gunter Mussbacher (2009) with material from: IEEE Standard, Daniel Amyot.
Object Oriented Analysis and Design Using the UML
Software Documentation Written By: Ian Sommerville Presentation By: Stephen Lopez-Couto.
Welcome to CMPE003 Personal Computer Concepts: Hardware and Software Winter 2003 UC Santa Cruz Instructor: Guy Cox.
Copyright © 2003 by Prentice Hall Computers: Tools for an Information Age Chapter 14 Systems Analysis and Design: The Big Picture.
Systems Analysis and Design: The Big Picture
CS 8532: Adv. Software Eng. – Spring 2007 Dr. Hisham Haddad Tuesday Class will start momentarily. Please Stand By … CS 8532: Advanced Software.
Chapter 10 Architectural Design
Lesson 7 Guide for Software Design Description (SDD)
Typical Software Documents with an emphasis on writing proposals.
Modelling information systems
Managing the development and purchase of information systems (Part 1)
System models Abstract descriptions of systems whose requirements are being analysed Abstract descriptions of systems whose requirements are being analysed.
SOFTWARE DESIGN DOCUMENT (SDD)
Copyright © 2013 Curt Hill The Zachman Framework What is it all about?
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management Dave Salisbury ( )
CS 3610: Software Engineering – Spring 2009 Dr. Hisham Haddad – CSIS Dept. Class Project OO Design Document Here is what you need to do for your class.
Introduction To System Analysis and Design
Chapter 9 Moving to Design
CS12420 Sequence Diagrams – a UML notation for modelling bahaviour Lynda Thomas Images from Wikipedia unless credited or mine.
SE: CHAPTER 7 Writing The Program
CS 4310: Software Engineering Lecture 4 System Modeling The Analysis Stage.
Systems Analysis and Design in a Changing World, 3rd Edition
The Systems Development Life Cycle
Requirements as Usecases Capturing the REQUIREMENT ANALYSIS DESIGN IMPLEMENTATION TEST.
Requirements Capture. Four Steps of requirements capture List candidate requirements Understand system context Capture functional requirements Capture.
CS 4850: Senior Project Fall 2014 Object-Oriented Design.
1 CS Tutorial 5 Frid. Oct 23, 2009 Design Document Tutorial.
Introduction to Computing Systems CT101 – Computing Systems.
1 Web Servers (Chapter 21 – Pages( ) Outline 21.1 Introduction 21.2 HTTP Request Types 21.3 System Architecture.
Systems Development Life Cycle
Connecting with Computer Science2 Objectives Learn how software engineering is used to create applications Learn some of the different software engineering.
Design Methods Instructor: Dr. Jerry Gao. Software Design Methods Design --> as a multistep process in which we design: a) data structureb) program structure.
Architecture View Models A model is a complete, simplified description of a system from a particular perspective or viewpoint. There is no single view.
Architectural Design Introduction Design has been described as a multistep process in which representations of data and program structure,
Irwin/McGraw-Hill Copyright © 2000 The McGraw-Hill Companies. All Rights reserved Whitten Bentley DittmanSYSTEMS ANALYSIS AND DESIGN METHODS5th Edition.
UML - Development Process 1 Software Development Process Using UML.
21/1/ Analysis - Model of real-world situation - What ? System Design - Overall architecture (sub-systems) Object Design - Refinement of Design.
Class Diagrams. Terms and Concepts A class diagram is a diagram that shows a set of classes, interfaces, and collaborations and their relationships.
CSIS 4850: CS Senior Project – Spring 2009 CSIS 4850: Senior Project Spring 2009 Object-Oriented Design.
1 SYS366 Week 1 - Lecture 1 Introduction to Systems.
Use Case, Component and Deployment Diagrams University of Sunderland.
NAVSEA Liaison Scott Huseth Faculty Advisor Dr. Jiang Guo Team Members Areg Abcarians David Ballardo Niteen Borge Daniel Flores Constance Jiang June 3,
Architectural Complexity  A useful technique for assessing the overall complexity of a proposed architecture is to consider dependencies between components.
Software Engineering Lecture 4 System Modeling The Analysis Stage.
UML Diagrams By Daniel Damaris Novarianto S..
Database System Concepts and Architecture
Physical Data Model – step-by-step instructions and template
UML Diagrams Jung Woo.
System Modeling Chapter 4
Object-Oriented Design
Software Design Lecture : 15.
How to manage Requirements?
MIS 385/MBA 664 Systems Implementation with DBMS/ Database Management
Presentation transcript:

BIT 286: Web Applications Software Design Documents

Info Needed To Plan a Software Project  From What is a software design?What is a software design? 1.“a description of the business requirements or needs” 2.“a description of how these requirements will map to a set of features and how the features will work from the perspective of the customer” 3. “a description of how these features will be implemented and the work list breakdown for implementing them” 4.“a description of how the implementation will be validated.” [I.e., testing]  We’ve merged #1 & #2 into the SRS  #3 is called a “ software design document ”  We’ll put the work breakdown structure off till next week (along with Gantt charts) 2

SDD (or ‘design doc’)  “ A design document is a way for you to communicate to others what your design decisions are and why your decisions are good decisions. Don’t worry if your design is not UML compliant and don’t worry if you didn’t use a special modeling tool to create it. The biggest factor that determines if your design document is good is whether or not it clearly explains your intentions.” – Scott HackettScott Hackett  How the software will be structured, sure, but also:  Peer Dev: “make sure that your ideas are valid and that your approach works with what others are doing.”  Manager: “[list] what the main entities of the system are, what the benefits are and, most importantly, what the risks are” 3

 For each decision write down:  why it’s necessary (based on the requirements)  Benefit  Risks  – Scott HackettScott Hackett 4

What is typically included?  Wikipedia (surprisingly short read) Wikipedia 1.The data design describes structures that reside within the software. Attributes and relationships between data objects dictate the choice of data structures.data designdata objectsdata structures 2.The architecture design uses information flowing characteristics, and maps them into the program structure. The transformation mapping method is applied to exhibit distinct boundaries between incoming and outgoing data. The data flow diagrams allocate control input, processing and output along three separate modules.architecture design 3.The interface design describes internal and external program interfaces, as well as the design of human interface. Internal and external interface designs are based on the information obtained from the analysis model.interface design 4.The procedural design describes structured programming concepts using graphical, tabular and textual notations. These design mediums enable the designer to represent procedural detail, that facilitates translation to code. This blueprint for implementation forms the basis for all subsequent software engineering worked.procedural design 5

What is typically included? 1.System overview  May be copied from SRS 2.System Architecture  What are the big ‘areas’ of your program, what do they do, and how do they interact? 3.Data Design  Database schema, interconnections amongst tables 4.Component Design Details  Detailed, step-by-step explanation of how stuff works for programmers  Can be done in pseudocode 5.Human Interface Design  Show how the user will use the system  Include images – hand-drawn, Paint.Net, Photoshop, or mock-ups in HTML (show the browser’s rendering)  Goal is to explain functionality – the ‘look and feel’ can/will be changed as you go 6.Requirements Matrix  For each component listed above write out which requirement (in your SRS) it satisfies  From 6

What should we include? 1.System overview 2.System Architecture 3.Data Design 4.Component Design Details 5.Human Interface Design 6.Requirements Matrix 7 Are these applicable to ASP.Net WebForms programs? Try this – list a couple of requirements & where they’re addressed and then let’s see if it’s actually useful for us

 Mockups:  ‘map’ page of thumbnails with clear, simple abbreviations  Individual ‘here’s a page’ images, with additional explanation as needed  Also show ‘work flows’  start at page X, do stuff X  then go to page Y, do stuff Y  then end on page Z  One workflow per requirement? 8

How to edit.PDF files  Google for ‘Pdf to Word’  There’s a couple of options  I personally don’t like the idea of installing software to do this…  …But I’m ok with handing out my address for the conversion 9