I have to clean it up a lot, but I can post something.
For now, my very basic document falls into this format:
- Abstract (Executive Summary)
- Details
- More overview
- Proposed technologies
- Module Description
- Desired Output
- Input
- Business Rules, behaviors, etc.
- Test Cases (if applicable)
- ...
I'm taking little steps right now. I wanted something to use for TDD in the
long run. I'm going to keep the document evolving.
I'll post more detail over the weekend. It is based upon a more formal
software spec. document.
Russel
> - Introduced "proper" application design to the department manager.
> Before now the developers here have just produced requirement
> documents that were vague or incomplete. I have introduced the need
> for formally defining the desired output and the user input.
>
> Russel
>
> Can you share with me what you shared with your department? Or what
> you can without breaking any rules you are unwilling to break. I have
> been trying to pass this same message to the group I work with. But I
> am neither senior enough to demand it. Nor am I knowledge enough in
> HOW. I just know mostly WHY one should, not HOW one actually does
> this.
>
> I would be most appreciative of any templates or such on how one
> documents the formal definition of output and user input, especially
> with an eye to intranet applications.
>
> TIA
>
> --------------
> Ian Skinner
> Web Programmer
> BloodSource
> www.BloodSource.org
> Sacramento, CA
>
> ---------
> | 1 | |
> --------- Binary Soduko
> | | |
> ---------
>
> "C code. C code run. Run code run. Please!"
> - Cynthia Dunning
>
> Confidentiality Notice: This message including any
> attachments is for the sole use of the intended
> recipient(s) and may contain confidential and privileged
> information. Any unauthorized review, use, disclosure or
> distribution is prohibited. If you are not the
> intended recipient, please contact the sender and
> delete any copies of this message.
>
>
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~|
Introducing the Fusion Authority Quarterly Update. 80 pages of hard-hitting,
up-to-date ColdFusion information by your peers, delivered to your door four
times a year.
http://www.fusionauthority.com/quarterly
Archive:
http://www.houseoffusion.com/groups/CF-Community/message.cfm/messageid:217027
Subscription: http://www.houseoffusion.com/groups/CF-Community/subscribe.cfm
Unsubscribe: http://www.houseoffusion.com/cf_lists/unsubscribe.cfm?user=89.70.5
