Your question above seems to be somewhat vague, but would like to see
if we can flush that out a bit.  A solution document "may" be a
"Solution Engineering", "Solution Architecture", "Solution
Integration", "Technical Solution", "Solution Design", or "Solution
Build" document.  These are a few of the names that I've seen used in
the past across my various projects.

The main Solutions documents can be divided as either being more
Technical or more Business-oriented.  The contents will differ based
on the purpose of the doc and the audience who will be reading it.
The best way that I can easily describe it is that a Biz Solutions
document will be the "WHAT" explained; where as the Tech Solutions doc
will contain the "HOW".

For example, your Biz doc will include: Current/Future state biz
process flows (BMP diagrams, flowcharts), business rules, UI wire-
frames, testing strategy, etc.  Whereas the Tech Solutions document
may include: Infrastructure diagrams, Interface components, component
design, pseudo code, UML, etc. The tech may also include App/Database/
Web Server information specific to the project.

What is commonly shared between the two will be sections like
Introduction, Purpose, Audience, Approvals, Supplemental references,
etc.

With regards to websites, you may want to check out some of the
following (more tech than biz):
http://www.omg.org/technology/documents/bms_spec_catalog.htm
http://www.uml.org/
http://www.opengroup.org/architecture/togaf8-doc/arch/

Hope this helps!
-Chris

On Jun 10, 7:34 am, vickeybird <viveksisod...@gmail.com> wrote: