<div>
<div class="content wysiwyg-content">
I am asked to write a Technical Requirement Document against the Functional Requirement Document based on the project i have completed.<br />
I have the following questions:<br />
1. When is a Technical Spec required. Is it at the end of the project or at the begining of the project? And who is the audiance of this document?<br />
2. What other documents can be prepaired after the Functional Specs and Technical Specs are produced. For example, What documents are prepaired by testers to start work on test cases.<br />
3. What is the scope of this document? In the document i have prepaired, I have supported the technical specs with Use Cases, ERD diagrams, Data Flow Diagrams,. To sum it all up, it contains the detail architectural design of the system where the user interaction with web page is supported by Use Cases, the database design is supported by ERD, and details of data flow is supported by DFD. What is the level of depth required in this document. Do i provide code peaces also?
</div>
</div>


I am asked to write a Technical Requirement Document against the Functional Requirement Document based on the project i have completed.
I have the following questions:
1. When is a Technical Spec required. Is it at the end of the project or at the begining of the project? And who is the audiance of this document?
2. What other documents can be prepaired after the Functional Specs and Technical Specs are produced. For example, What documents are prepaired by testers to start work on test cases.
3. What is the scope of this document? In the document i have prepaired, I have supported the technical specs with Use Cases, ERD diagrams, Data Flow Diagrams,. To sum it all up, it contains the detail architectural design of the system where the user interaction with web page is supported by Use Cases, the database design is supported by ERD, and details of data flow is supported by DFD. What is the level of depth required in this document. Do i provide code peaces also?

Writing Technical Requirement Specs Against Functional Requirement Specs

Software is any set of instructions that directs a computer to perform specific tasks or operations. Computer software consists of programs, libraries and related non-executable data (such as documentation). Computer software is non-tangible, contrasted with computer hardware, which is the physical component of computers. Software written in a machine language is known as "machine code". However, in practice, software is usually written in high-level programming languages than machine language. High-level languages are translated into machine language using a compiler or interpreter or a combination of the two.

Software

Programming includes both the specifics of the language you’re using, like Visual Basic, .NET, Java and others, but also the best practices in user experience and interfaces and the management of projects, version control and development. Other programming topics are related to web and cloud development and system and hardware programming.

Programming

Project management is the discipline of carefully projecting or planning, organizing, motivating and controlling resources to achieve specific goals and meet specific success criteria. A project is a temporary endeavor designed to produce a unique product, service or result with a defined beginning and end (usually time-constrained, and often constrained by funding or deliverables) undertaken to meet unique goals and objectives, typically to bring about beneficial change or added value.