cancel
Showing results for 
Search instead for 
Did you mean: 

regarding to technical specification

Former Member
0 Kudos

Hi everybody....!

What should we mention in technical specification of XI scenario? People with how many years of exp will create technical specification?

Thanking you in advance...

Accepted Solutions (0)

Answers (4)

Answers (4)

Former Member
0 Kudos

What should we mention in technical specification of XI scenario?

1) INTRODUCTION

PURPOSE

OPEN ISSUES

ASSUMPTIONS AND LIMITATIONS

DOCUMENT REFERENCES

2. DETAILED TECHNICAL SPECIFICATION 6

PROCESS OVERVIEW

PROCESS FLOW

. DETAIL DESIGN STEPS

. EXCEPTION SITUATIONS

. LIST OF DELIVERABLES

. PROCESSING ATTRIBUTES

. PERFORMANCE / TRANSACTION VOLUME

. SECURITY, INTEGRITY AND CONTROLS

3. SYSTEM LANDSCAPE DIRECTORY

DETAILS OF TECHNICAL AND BUSINESS SYSTEMS

Application 1 Sender

Application 2 Receiver

4. INTEGRATION REPOSITORY DESIGN OBJECTS

CROSS COMPONENT BUSINESS PROCESS MANAGEMENT

5. CONFIGURATION AND IMPLEMENTATION

6. ERROR HANDLING

7. APPENDIX

People with how many years of exp will create technical specification?

NO exp is required u need to know wat information is required in TS.

chirag

Former Member
0 Kudos

Thanks Gohil...!

I have gotten th information. Still i have a question regading to that. For how much experienced proffessionals the Technical Design task will be assigned?

Former Member
0 Kudos

Basically technical specification is designed by expertise people. But if team members are comfortable with technology then they can also make Technical specification.

Technical Specification is nothing but a documentation of an interface that later you or some one else is going to Develop.

Thanks

Farooq

Former Member
0 Kudos

Hi Farook...!

Thank You for the reply.

Can i have any sample technical specifications for overview of a scenario?

Former Member
0 Kudos

Hi,

Technical specs are varying from organization to organization.

It contains the information about Document Owner, Reviwer,

Sender System details, Receiver System details, Process flow according to Functional spec.

And also contains Integration Repository objects (DT,MT,MI,MM,IM) information and Integration Directory Objects like Business System or Service, Communciton Channel Parameters, Interface Determination, Receiver Agreement and Sender Agrement details.

Go through the following link you can get more information.

Regards,

Sridhar Goli

JaganMohan
Participant
0 Kudos

Dear Praveen,

Please go through the following link. Hope this will answer your question.

Regards,

Jagan.

Former Member
0 Kudos

this depends from project to project.

Generally it should describe the technical approach to solving the functional requirement. So mode of transport, data structures, mapping, comm channel parameters, security if applicable etc etc. Just everything that you can think of that will make a developers life easier to make things happen.

With regard to experience it really doesn't have a year limit on it but you obviously have to know what our doing to write one