topic Technical specifications in Application Development and Automation Discussions

Technical specifications

Former Member — Tue, 31 Oct 2006 11:10:41 GMT

why are technical specifications needed........what are the rules to write technical specifications

Re: Technical specifications

Former Member — Tue, 31 Oct 2006 11:13:14 GMT

Hi,

in future if some body wants to modify the object , then it will guide him, and it will give the idea about the object,

there is no specific rules, it all varies from company to company.

Regards

vijay

Re: Technical specifications

Former Member — Tue, 31 Oct 2006 11:26:27 GMT

Techical specifications should be structured document which will give someone information about how exactly particular object is developed, so it should contain at least:

Why the requirement exists

What the requirement was agreed at after initial analysis

Agreement that the requirement is an accurate reflection of the user's wishes

What you are doing technically to satisfy this requirement

Any assumptions made / items which were considered 'out of scope'

Agreement that the development covers the requirement to the satisfaction of the key users / stakeholder.

I hope it gives you some idea.

Best Regards,

Vibha

*Please mark all the helpful answers

Re: Technical specifications

Former Member — Wed, 01 Nov 2006 04:58:49 GMT

what is the difference between technical specifications and functional specifications

Re: Technical specifications

Former Member — Wed, 01 Nov 2006 05:24:45 GMT

Hi,

1) Functional specification is developed by Functional in general.

Technical specification is developed by technical person. Some times functional does this if he/she is technically sound.

2) Functional mainly concentrate on business requirement in words. (What is to be done?)

Technical specification concentrates on requirements in technical terms.(How to be done ?)

3) In general,

Developer will get functional specification first. Then he/she will prepare technical specification and start with development.

This is some common difference. This varies project to project.

Re: Technical specifications

Former Member — Wed, 01 Nov 2006 06:52:48 GMT

Technical Specification provides an overview of the following attributes in order to make a clear view of the program and its requirements to a third person.

1. Before starting the development,

the abaper plans what to do,

and what he/she will create.

eg. what will be the programname

what will be the Z tables created, if any,

what logic he will use

etc.

2. the general format is somewhat like this

Below are the standards for Tech specs

1.1 Development Attributes

Program Name:

Title:

Application:

Development Class:

Message Class:

Program Type:

Execution Mode:

Schedule Frequency:

Variant:

1.2 Program Functionality

1.3 Output Fields

Output Label

Related SAP table-field (if any)

Length

Output Characteristics

1.4 Proposed Solutions

1.5 Solution to be implemented

1.6 Reasons of selection/rejection

1.7 Pseudo-Code / Flow Logic of the selected solution

1.8 Selection Screen

1.9 Database Tables Used

Table Name

Table Description

How the table is used in the program

1.10 External Files Used

1.10.1 External File Layout <file name>

1.11 Components External to Program Used

1.12 Error Conditions

1.13 Key Technical Test Conditions

1.14 Sample Test Data

1.15 Assumptions

1.16 Comments

Functional Specification is basically created by the functional consultant which will tel u the requirements like material shud b used frm table MARA where the condition ERNAM = 'B%' shud b met i hope this gives a basic picture.

regards,

Seema.