CSE1IS Information Systems Week 11 Lecture 1 System Design Specification

S.C.&R. Ch. 8, pp. 396-398

1. System Design Specification:

or, System Design Document , contains the complete design for the new system.
Content depends on whether you are developing from scratch or installing a package, or somewhere inbetween.
A full development should consist of something like (pp. 396-397):

• Executive Summary:
  • brief overview
  • outline what is completed so far
  • current status
  • summarise antipated costs of development and implementation
  • cost benefit analysis
• System Components:
  • DFDs/UML diagrams including logic behind processes
  • ER diagram and database file structure
  • menu hierarchy
  • screen designs, including logic behind events (buttons)
  • report designs, including examples (based on realistic data)
  • backup and recovery procedures
• System Environment:
  • required new hardware and/or operating system
  • requirements for interfacing with current hardware/software
  • networking requirements
  • security procedures
  • other information like processing schedules, reporting deadlines and online response time
• Implementation Requirements:
  • data conversion and initial processing
  • user training
  • test plans
• Time and Cost Estimates:
  • detailed schedule of implementation (gantt chart)
  • should be able to break down the development into screen-by-screen and report-by-report
  • cost estimates for each
  • costs to date
  • overall cost estimates for remainder of project (development, implemenation and maintenance)
• Appendices:
  • copies of actual reports, interview records etc.

References:

• Shelly, Cashman & Rosenblatt, Systems Analysis and Design, 6th Edition,  Course Technology, 2006.

NOTE: this webpage has not been brought up to WCAG 1.0 standard nor does it contain validated HTML