<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:rdf="http://www.w3.org/1999/02/22-rdf-syntax-ns#" xmlns:taxo="http://purl.org/rss/1.0/modules/taxonomy/" version="2.0">
  <channel>
    <title>topic Re: basci steps to write technical spec from functional specs in Application Development and Automation Discussions</title>
    <link>https://community.sap.com/t5/application-development-and-automation-discussions/basci-steps-to-write-technical-spec-from-functional-specs/m-p/3401210#M816651</link>
    <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Every organization may have diff template , you may require to follow the template . In TS you have to write clearly in technical term but dont do any copy pase from the code , which not at all sound good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Find the below steps.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.In 1st page you may require to give heading and company logo also at the RHS.&lt;/P&gt;&lt;P&gt;2.Give title of the document , SAP Module Name, Specification Type (Giv ein a tabular format)&lt;/P&gt;&lt;P&gt;3.Revision History in Tabluar Format including Author , Description , Date , Version ( Version management very imp try to maintain it)&lt;/P&gt;&lt;P&gt;4.Requirement Description : Enter in detail wat is u r reqmt.&lt;/P&gt;&lt;P&gt;5.U may add Process flow diagram using visio etc. &lt;/P&gt;&lt;P&gt;6.Outstanding issues&lt;/P&gt;&lt;P&gt;7.Prerequisites&lt;/P&gt;&lt;P&gt;8.Input Parameter Details &lt;/P&gt;&lt;P&gt;9.Processign logic Details&lt;/P&gt;&lt;P&gt;10.Out Put Details (if Report Output Format)&lt;/P&gt;&lt;P&gt;11.The few unit testing scripts also u can include&lt;/P&gt;&lt;P&gt;12.Proper file name , in header &amp;amp; Footer&lt;/P&gt;&lt;P&gt;13. Always try to keep track changes on for version management. If u need to create new version try to accept previous version then keep track for curren tchanges.&lt;/P&gt;&lt;P&gt;14. Maintain index &amp;amp; Page no in table content .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eg..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Below are the standards for Tech specs&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.1 Development Attributes&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Program Name:&lt;/P&gt;&lt;P&gt;Title:&lt;/P&gt;&lt;P&gt;Application:&lt;/P&gt;&lt;P&gt;Development Class:&lt;/P&gt;&lt;P&gt;Message Class:&lt;/P&gt;&lt;P&gt;Program Type:&lt;/P&gt;&lt;P&gt;Execution Mode:&lt;/P&gt;&lt;P&gt;Schedule Frequency:&lt;/P&gt;&lt;P&gt;Variant:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.2 Program Functionality&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.3 Output Fields&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Output Label &lt;/P&gt;&lt;P&gt;Related SAP table-field (if any) &lt;/P&gt;&lt;P&gt;Length &lt;/P&gt;&lt;P&gt;Output Characteristics&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.4 Proposed Solutions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.5 Solution to be implemented&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.6 Reasons of selection/rejection&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.7 Pseudo-Code / Flow Logic of the selected solution&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.8 Selection Screen &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.9 Database Tables Used&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Table Name &lt;/P&gt;&lt;P&gt;Table Description &lt;/P&gt;&lt;P&gt;How the table is used in the program&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.10 External Files Used &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.10.1 External File Layout &amp;lt;file name&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.11 Components External to Program Used&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.12 Error Conditions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.13 Key Technical Test Conditions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.14 Sample Test Data&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.15 Assumptions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.16 Comments&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
    <pubDate>Wed, 20 Feb 2008 05:24:56 GMT</pubDate>
    <dc:creator>Former Member</dc:creator>
    <dc:date>2008-02-20T05:24:56Z</dc:date>
    <item>
      <title>basci steps to write technical spec from functional specs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/basci-steps-to-write-technical-spec-from-functional-specs/m-p/3401208#M816649</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;hi gurus,&lt;/P&gt;&lt;P&gt;  &lt;/P&gt;&lt;P&gt;      what are the steps to take for writing technical spec's.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;regards,&lt;/P&gt;&lt;P&gt;praveen&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Feb 2008 04:35:25 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/basci-steps-to-write-technical-spec-from-functional-specs/m-p/3401208#M816649</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-20T04:35:25Z</dc:date>
    </item>
    <item>
      <title>Re: basci steps to write technical spec from functional specs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/basci-steps-to-write-technical-spec-from-functional-specs/m-p/3401209#M816650</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;every project/company has its own Template for FS, TS etc...&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Take the TS template, u can see many contents in that. &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;FS in the Functionality of the requirement.&lt;/P&gt;&lt;P&gt;TS is the Technical solution for that requirement.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;u need to write the Pseudocode in the TS, how can you implement the technical solution for the requirement into its corr. content or paragraph.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;generally any TS consists of the foll: as its content:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;(this is an example for a report)&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1. DETAIL DESIGN SPECIFICATIONS OVERVIEW &lt;/P&gt;&lt;P&gt;a. BUSINESS FUNCTIONALITY &lt;/P&gt;&lt;P&gt;b .MAJOR FEATURES &lt;/P&gt;&lt;P&gt;USER PROCEDURES &lt;/P&gt;&lt;P&gt;CHECK LISTS &lt;/P&gt;&lt;P&gt;ASSUMPTIONS: &lt;/P&gt;&lt;P&gt;CONSTRAINTS: &lt;/P&gt;&lt;P&gt;SECURITY CONSIDERATIONS &lt;/P&gt;&lt;P&gt;OBJECTS: &lt;/P&gt;&lt;P&gt;LTS SECURITY REQUIREMENTS: &lt;/P&gt;&lt;P&gt;RESTART/RECOVERY STRATEGY &lt;/P&gt;&lt;P&gt;PERFORMANCE CONSIDERATIONS &lt;/P&gt;&lt;P&gt;PROGRAM &amp;amp; DATA FLOW INTERACTION &lt;/P&gt;&lt;P&gt;PICTORIAL VIEW &lt;/P&gt;&lt;P&gt;INPUT DATA &lt;/P&gt;&lt;P&gt;COMMENTS &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;2. DETAILED PROGRAM DESIGN SPECIFICATIONS &lt;/P&gt;&lt;P&gt;PROGRAM DESCRIPTION &lt;/P&gt;&lt;P&gt;EXECUTION METHOD &lt;/P&gt;&lt;P&gt;PROGRAM TYPE &lt;/P&gt;&lt;P&gt;COMMON SUBROUTINES &lt;/P&gt;&lt;P&gt;EXCEPTIONS TO PROGRAMMING STANDARDS &lt;/P&gt;&lt;P&gt;LIST OF OBJECTS IMPACTED &lt;/P&gt;&lt;P&gt;INPUTS / OUTPUTS &lt;/P&gt;&lt;P&gt;ERROR MESSAGES AND CLASSES &lt;/P&gt;&lt;P&gt;BDC SESSIONS &lt;/P&gt;&lt;P&gt;STRUCTURES &lt;/P&gt;&lt;P&gt;DETAILED LOGIC &lt;/P&gt;&lt;P&gt;3. DETAILED REPORT DESIGN SPECIFICATIONS &lt;/P&gt;&lt;P&gt;(REPORT PROGRAM NAME) &lt;/P&gt;&lt;P&gt;REPORT DESCRIPTION &lt;/P&gt;&lt;P&gt;REPORT INVOCATION METHOD &lt;/P&gt;&lt;P&gt;REPORT APPLICATION &lt;/P&gt;&lt;P&gt;REPORT TYPE &lt;/P&gt;&lt;P&gt;REPORT CLASSIFICATION &lt;/P&gt;&lt;P&gt;REPORT MEDIUM &lt;/P&gt;&lt;P&gt;REPORT FREQUENCY &lt;/P&gt;&lt;P&gt;REPORT REQUEST METHOD &lt;/P&gt;&lt;P&gt;REPORT TIMING &lt;/P&gt;&lt;P&gt;REPORT ORIGINATOR &lt;/P&gt;&lt;P&gt;REPORT RECIPIENTS &lt;/P&gt;&lt;P&gt;REPORT PROCESSING ENVIRONMENT &lt;/P&gt;&lt;P&gt;REPORT LAYOUT &lt;/P&gt;&lt;P&gt;REPORT LAYOUT DESCRIPTION &lt;/P&gt;&lt;P&gt;REPORT SORT INFORMATION &lt;/P&gt;&lt;P&gt;REPORT CONTROL BREAKS &lt;/P&gt;&lt;P&gt;REPORT PAGE BREAKS &lt;/P&gt;&lt;P&gt;REPORT SUMMARY STATISTICS &lt;/P&gt;&lt;P&gt;REPORT MESSAGES &lt;/P&gt;&lt;P&gt;REPORT NUMBER OF PAGES / LINES / COPIES &lt;/P&gt;&lt;P&gt;REPORT PRINTING INFORMATION&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Check this thread..It may be useful.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_thread" href="https://community.sap.com/" __jive_macro_name="thread" modifiedtitle="true" __default_attr="429163"&gt;&lt;/A&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Regards.&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Feb 2008 05:11:18 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/basci-steps-to-write-technical-spec-from-functional-specs/m-p/3401209#M816650</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-20T05:11:18Z</dc:date>
    </item>
    <item>
      <title>Re: basci steps to write technical spec from functional specs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/basci-steps-to-write-technical-spec-from-functional-specs/m-p/3401210#M816651</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Every organization may have diff template , you may require to follow the template . In TS you have to write clearly in technical term but dont do any copy pase from the code , which not at all sound good.&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Find the below steps.&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.In 1st page you may require to give heading and company logo also at the RHS.&lt;/P&gt;&lt;P&gt;2.Give title of the document , SAP Module Name, Specification Type (Giv ein a tabular format)&lt;/P&gt;&lt;P&gt;3.Revision History in Tabluar Format including Author , Description , Date , Version ( Version management very imp try to maintain it)&lt;/P&gt;&lt;P&gt;4.Requirement Description : Enter in detail wat is u r reqmt.&lt;/P&gt;&lt;P&gt;5.U may add Process flow diagram using visio etc. &lt;/P&gt;&lt;P&gt;6.Outstanding issues&lt;/P&gt;&lt;P&gt;7.Prerequisites&lt;/P&gt;&lt;P&gt;8.Input Parameter Details &lt;/P&gt;&lt;P&gt;9.Processign logic Details&lt;/P&gt;&lt;P&gt;10.Out Put Details (if Report Output Format)&lt;/P&gt;&lt;P&gt;11.The few unit testing scripts also u can include&lt;/P&gt;&lt;P&gt;12.Proper file name , in header &amp;amp; Footer&lt;/P&gt;&lt;P&gt;13. Always try to keep track changes on for version management. If u need to create new version try to accept previous version then keep track for curren tchanges.&lt;/P&gt;&lt;P&gt;14. Maintain index &amp;amp; Page no in table content .&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Eg..&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;Below are the standards for Tech specs&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.1 Development Attributes&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;Program Name:&lt;/P&gt;&lt;P&gt;Title:&lt;/P&gt;&lt;P&gt;Application:&lt;/P&gt;&lt;P&gt;Development Class:&lt;/P&gt;&lt;P&gt;Message Class:&lt;/P&gt;&lt;P&gt;Program Type:&lt;/P&gt;&lt;P&gt;Execution Mode:&lt;/P&gt;&lt;P&gt;Schedule Frequency:&lt;/P&gt;&lt;P&gt;Variant:&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.2 Program Functionality&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.3 Output Fields&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Output Label &lt;/P&gt;&lt;P&gt;Related SAP table-field (if any) &lt;/P&gt;&lt;P&gt;Length &lt;/P&gt;&lt;P&gt;Output Characteristics&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.4 Proposed Solutions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.5 Solution to be implemented&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.6 Reasons of selection/rejection&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.7 Pseudo-Code / Flow Logic of the selected solution&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.8 Selection Screen &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;&lt;STRONG&gt;1.9 Database Tables Used&lt;/STRONG&gt;&lt;/P&gt;&lt;P&gt;Table Name &lt;/P&gt;&lt;P&gt;Table Description &lt;/P&gt;&lt;P&gt;How the table is used in the program&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.10 External Files Used &lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.10.1 External File Layout &amp;lt;file name&amp;gt;&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.11 Components External to Program Used&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.12 Error Conditions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.13 Key Technical Test Conditions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.14 Sample Test Data&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.15 Assumptions&lt;/P&gt;&lt;P&gt;&lt;/P&gt;&lt;P&gt;1.16 Comments&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Feb 2008 05:24:56 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/basci-steps-to-write-technical-spec-from-functional-specs/m-p/3401210#M816651</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-20T05:24:56Z</dc:date>
    </item>
    <item>
      <title>Re: basci steps to write technical spec from functional specs</title>
      <link>https://community.sap.com/t5/application-development-and-automation-discussions/basci-steps-to-write-technical-spec-from-functional-specs/m-p/3401211#M816652</link>
      <description>&lt;HTML&gt;&lt;HEAD&gt;&lt;/HEAD&gt;&lt;BODY&gt;&lt;P&gt;Also check this thread..u have smaple TS&lt;/P&gt;&lt;P&gt;&lt;A class="jive_macro jive_macro_message" href="https://community.sap.com/" __jive_macro_name="message" modifiedtitle="true" __default_attr="1876285"&gt;&lt;/A&gt;&lt;/P&gt;&lt;/BODY&gt;&lt;/HTML&gt;</description>
      <pubDate>Wed, 20 Feb 2008 05:26:51 GMT</pubDate>
      <guid>https://community.sap.com/t5/application-development-and-automation-discussions/basci-steps-to-write-technical-spec-from-functional-specs/m-p/3401211#M816652</guid>
      <dc:creator>Former Member</dc:creator>
      <dc:date>2008-02-20T05:26:51Z</dc:date>
    </item>
  </channel>
</rss>

