CSE784 - Software Studio
Lecture #2 - Specification Attributes, Good and Bad
Revised: 07 September 2008
Software Project Survival Guide
Steve McConnell's Top 10 Reading List
This lecture starts with a continuation our discussion of Specifications, moves on to testing, and provides links for
a discussion of design. We probably won't get to design until next week.
Describes topics to be covered,
reading material for you to digest before coming to class, and due dates
for the assigned projects.
Creating SQL Server DB Programmatically
Dusan Palider found this link and we think it may be useful for Project #1.
Product Model Scope
Breaking Down/Building Up
Much of the discussion in this lecture involves specifying and testing modules. If you need a refresher about modules,
then look here.
Concept Development: Project Center - Final Project, Fall 04
Initial project concept development occurs before, or concurrently with, B-Level requirements development. Use Cases Are
a key part of the concept development process. Here we show use cases prepared for the Final Project, Fall 04.
Project Center Packages
Project Center Use Cases
Developing Use Cases is part of the project concept definition that is completed before beginning development of specifications.
This presentation was developed for the Final Project, Fall 04.
The purpose of testing is to demonstrate that specifications are satisfied.
Specification and Architecture
In this lecture we finish the specification topic by discussing C-Level specs, e.g., design documents.
SRS Quality Measures
Discusses what makes a specification good or bad.
Help for Project #1
Project #1 requires you to develop a DataLayer providing an object to relational mapping for all information stored in SQL Server. These notes will help you
with that implementation.
Discusses design attributes and how to judge their quality.
Basic Design Issues
Truely Awful Interface Design