on 08-08-2008 11:34 AM
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...
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
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
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
81 | |
24 | |
11 | |
9 | |
7 | |
5 | |
5 | |
5 | |
4 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.