views:

24

answers:

4

We have a bunch of requirements documents and class diagrams, but are missing the document that brings it all together.

What is the correct term for a document that gives an overview of what a system does? Or what is the best way to present an overall picture of what is going on.

Something that starts with a high level picture of what’s going on, describes what the system provides, who it interacts with, and any dependencies, etc ?

A: 

What about a nice Domain model?

AidanO
That sounds too much like a description of an object representation of our system.
Nix
A: 

You said it yourself: System Overview.

BernardMarx
A: 

Back in the 2167A and MIL-498 days we called it a Software Product Specification (or SPS).

If that isn't quite what you are looking for, try surfing around Simon's MIL-498 document website and see if one looks like what you need. You (probably) don't have to follow any of them exactly, but they make good templates.

T.E.D.
Maybe software design description http://homepage.mac.com/simon.j.wright/pushface.org/mil_498/sdd-did.htm#scope
Nix
A: 

Sounds like an architecture document to me. http://en.wikipedia.org/wiki/Software_architecture

Mike