IT:AD:Documentation:Questions

• (UP)

  • IT - Documentation - Specification
    • IT:PM:Docs/Specifications/IO
  • IT/AD/Documentation:Briefing Paper
  • IT::AD:Documentation:Examples
    • frd (WIN-QNKB1B7TQET's conflicted copy 2016-09-15)
    • IT::AD:Documentation:Examples:1
  • IT:AD:Documentation:Architecture Description Document (ADD)
  • IT:AD:Documentation:BRD
    • home (WIN-QNKB1B7TQET's conflicted copy 2016-09-15)
  • IT:AD:Documentation:Business Canvas
  • IT:AD:Documentation:Closure Report (CR)
  • IT:AD:Documentation:Decision Paper
  • IT:AD:Documentation:Defect Report Document
  • IT:AD:Documentation:Deployment
    • document
  • IT:AD:Documentation:Discussion Document
  • IT:AD:Documentation:DP (Deployment Plan)
  • IT:AD:Documentation:Fact Sheet
  • IT:AD:Documentation:Green Paper
  • IT:AD:Documentation:HowTo
    • IT:AD:Documentation:HowTo:Abstract, Summary, Introduction, Etc.
    • IT:AD:Documentation:HowTo:Standard Document Structure
    • IT:AD:Documentation:HowTo:Common Enterprise Editing Tips
  • IT:AD:Documentation:Information Paper
  • IT:AD:Documentation:Issue Paper
  • IT:AD:Documentation:Meetings
    • IT:AD:Documentation:Meeting:Minutes
    • IT:AD:Documentation:Meetings:Agenda
  • IT:AD:Documentation:Onboarding Document
  • IT:AD:Documentation:Options Paper
  • IT:AD:Documentation:Project Brief
  • IT:AD:Documentation:Request for Information (RFI)
  • IT:AD:Documentation:RFC:Request for Change
  • IT:AD:Documentation:RFP (Request for Proposal)
  • IT:AD:Documentation:RFQ
  • it:ad:documentation:scientific_paper:Home
  • IT:AD:Documentation:SDD (Solution/Application Design Document)
    • home (WIN-QNKB1B7TQET's conflicted copy 2016-09-15)
  • IT:AD:Documentation:Software Requirements Specification (SRS) Document
  • IT:AD:Documentation:Solution Architecture Description (SAD) Document
    • IT:AD:Documentation:SAD:Examples
    • IT:AD:Documentation:SAD:Rozanski and Woods (RaW)
  • IT:AD:Documentation:SOW
    • home (WIN-QNKB1B7TQET's conflicted copy 2016-09-15)
  • IT:AD:Documentation:TDD
    • home (WIN-QNKB1B7TQET's conflicted copy 2016-09-15)
  • IT:AD:Documentation:Terms of Reference (TOR)
  • IT:AD:Documentation:Test Summary Report (TSR)
  • IT:AD:Documentation:URD
    • home (WIN-QNKB1B7TQET's conflicted copy 2016-09-15)
  • IT:AD:Documentation:Vision Document (VD)
  • IT:AD:Documentation:White Paper
  • IT:PM:Documentation:Diagrams
    • Overall
  • NFRD
    • home (WIN-QNKB1B7TQET's conflicted copy 2016-09-15)
  • Options Summary
  • Resources
  • home (WIN-QNKB1B7TQET's conflicted copy 2016-09-15)
  • IT:AD:Documentation:Design
  • IT:AD:Documentation:Implementation
  • IT:AD:Documentation:Options Statement
  • IT:AD:Documentation:Project Charter
  • IT:AD:Documentation:Questions
  • IT:AD:Documentation:Static Analysis Report
• RFP:
  • Characteristics:

    • Length for a mid size website?

    * RFI:

  • Characteristics:

    • Length for a mid size website?

Note that i have the following nagging questions as it's not my primary domain:

• What goes in the UAT?
  • Scope: a BRD, I believe to be usually succinct, describing the functional reason to undertake the development of the solution. Is a URD similarly short?
  • Am I correct in thinking it's a pre-contract doc?
• Functional Specs is such a loose term.

  • As such, I think that this company is putting in there Functional and SRS…getting too close to the solution specifics. Would you agree?

  * SRS:It's obviously not able to well produced by a developer, as they don't understand the concept of traceability. It's obviously not the domain of a BA, as it's switched from a Business Domain to a Technical Domain, and is therefore out of the competance of a BA.

  • Are there such roles as Technical Anaylysts who's job is to …?

In summary – if the diagram is correct and complete….how would you say we fit our company's documents over the above? Are we using funcitonal specs as a free for all? FRD + SRS?