Industry standard to represent technical specification of forms,conf objetc

Hello Everyone,
I am in a process of creating design document for a Sun IdM project. I was wondering, is there any way to represent Form, taskdefinition etc in the document as we represent in JAVA, sth like Class diagram.
Is there any industry standard to represent technical specification for these things.
Any pointers would be of great help.
Thanks,
Saurabh

No as you have phrased the question. WebEx provides this functionality and that is the route you should be taking if this is a feature requirement.
If you are opposed to WebEx or require an on-premise solution, you may want to evaluate Cisco Unified Video Conferencing Manger (CUVC Manager) and it's desktop solution.

Similar Messages

Industry Standard documentation for Technical Information related to Netweaver Portals

Hi.
I was hoping someone could point me in the right direction.
I want to create documentation related to our Netweaver Portals, but I want the documentation to be based on Industry Standards related to Netweaver Portals.
Information which I will include in this document, will include the following, but not limited to:
Naming Conventions
Folder Logic
Roles (How to create and use them)
Pages
Worksets
iViews
etc..
Does someone know of a template which I can use and alter to fit my requirements?

Hi Juandre,
There is not such template called Industry standard for NW portals.
Each firm have there own format and contents required by them .Objective of such documentation is to cover all the data points which can enable Technical support to provide necessary support for Portal environments.
Normally we include System landscape, URL details, OS details, Hardware details, DB details, SAP Portal technical details like version and patch level.
Business point of contacts,
SOP to start and stop systems
Known problems and resolutions
You may work out template based on above inputs.
Hope this helps.
Regards,
Deepak Kori

Technical Specification for Enterprise Portal

Our EP consultant left without delivering Technical Specification. Now, we need to prepare this document mainly for handover to support team. Coming from BW background, I have little knowledge on what is expected in the document.
What I can think of at the moment are that we need to document the followings:
1. Portal Content structure
2. iViews Configuration
3. Portal Display
Is there anything else missing? Or can someone share with me the structure of a complete Enterprise Portal Technical Specification?
Thank you very much!

Hi M. Syuhair,
That's a rather unfortunate situation that you have walked into where the implementer has left without documentation.
I would start the document with a blueprint diagram of the platform landscape, with each of the logical instances purposes described. You should include the OS and DB versions and any specifics on security zoning you may have. Then move into a diagram for transport flows and description of the purpose of the Portal. i.e. used for BI and ESS/MSS scenarios.
Also I would describe the integration with the solution, how security is provided, what other components are integrated (i.e. document repositories), how transports are performed (CTS, NWDI etc) and what systems are connected and SLD connectivity. Also mention UWL and Adobe services if they are deployed and anything else that represents significant usage.
After this point you can dig deeper into the detail and provide a description of the details of the business packages with versions you have deployed to the portal (use the NWA to look up package versions if you donu2019t know this already) along with the name spaces and PCD hierarchy that has been chosen to ensure standards are followed during maintenance by the support team.
Remember your support staff should be starting with at a minimum a basic understanding of standard SAP Portal implementations so getting to the detail of how each iView is configured would be taking the document too far.
Your purpose of the document is in providing the framework for support to be able to know what standards they should follow and how to quickly find out the implementation specific details. This should be your objective.
Starting this from scratch without any portal experience is not advisable, I would suggest you engage another Portal consultant to perform the task as familiarity with the core solution is really a must.
Regards
Daniel

What are the contents in technical specifications

What are the contents in technical specifications
could u plz explain clearly

hi rajeshreddy,
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
regards,
amit m.

Technical specification

Hello all,
I have to prepare a technical specification for my project. I have a high-level technical design document and a functional specification. Do I need an existing technical specification template or do I need to create one using the above documents I have?
If I have to make one, does anyone have sample technical specification templates?
Please help.
Thanks very much.
Ramesh.

Hi,
Technical specification should include details such as Source, Target systems, Mapping involved, structures (data types) involved, which sender/receiver adapter is used, the technical details which need to be filed in them.....inshort it should have the details of all the objects that are created in Integration repository and Directory.
High-level technical design document and a functional specification will form the base for your technical specification document.
If this is not the first XI project in your company then you can find related documents from other Xi projects.
Regards,
Abhishek.
Edited by: abhishek salvi on Oct 6, 2008 4:56 PM

Industry standard Manufacturing

Hi,
I want to know how the SD process differ in a manufacturing industry and IS Retail. Can IS- Retail be used in a manufacturing industry? Or do they follow a different industry standard. I am not able to understand the industry standards by going thru help.sap... Can anybody please help?
Thanks,
SV

hi,
there is no IS specific for plastic but there is one for CHEMICAL as you can see in the following link.
http://help.sap.com/bestpractices/BBLibrary/bblibrary_start.htm

Industry Standard for Adobe LiveCycle Users/Groups on AIX environments.

I wanted to know if there is an industry standard in creating users/groups for Adobe LiveCycle in *NIX environments.
What’s the usual set of users/groups created in most of the Installations.
wasadmin (Intended for WebSphere specifically),
adbadmin (Intended for adobe specifically),
cmadmin (Intended for correspondence management specifically)
etc.

Adobe Acrobat X Pro build 10.0.1
Adobe Livecycle Designer ES2 build 9.0.0.2.20101008.1.734229
I also have this issue.
thanks
WoWRonin

Code Review in Technical Specifications

What is the Code Review in the technical Specification document.

Hi,
Code review is done by the other member of the team member or by the onsite guy from the clien side or by team SQA.
Each company is having their own way of coding standards and naming conventions. the client always send one template for the same when the project starts.
The developer can not review his object and the third person like SQA of the team will review it and it will done in document which will be kept for reference.
if any changes or comments made by the SQA, then the developer will change the same again.
hope this will help you.
Thanks
Shiva

FUNCTIONAL SPECIFICATION AND TECHNICAL SPECIFICATION

hi Experts,
how does a functional specification looks and a technical specification looks.
can i have these requirements with samples..
or any helpful link wher i can get in template form.
thanks i advance

Functional Specification:
The Functional Specification describes the features of the desired functinality.. It describes the product's features as seen by the stake holders,and contains the technical information and the data needed for the design and developement.
The Functional Specification defines what the functionality will be of a particulat area that is to be precise a transaction in SAP terminology.
The Functional Specification document to create a detailed design document that explains in detail how the software will be designed and developed.
Technical Specification
Technical Specification is the document prepared by the Technical consultants. These documents are prepared basing on the Functional Specification given by the Functional consultants. The Technical Specification contains the following;
GENERAL INFORMATION
DEVELOPMENT INFORMATION
BUSINESS REQUIREMENTS
DATA EXTRACTION
AVAILABLE CUSTOMISING TABLES
AVAILABLE TEXTS WITH THEIR CODING CONVENTIONS
Check the below links for useful content on Technical and Functional specs:
/thread/409073 [original link is broken]
http://www.epri.com/eprisoftware/processguide/funcspec.html
http://www.mojofat.com/tutorial/
http://searchsoftwarequality.techtarget.com/sDefinition/0,,sid92_gci212169,00.html
http://www.devshed.com/c/a/Practices/Writing-A-Functional-Specification/
http://www.softwarereality.com/lifecycle/FunctionalSpecStandard.doc
http://www.webopedia.com/TERM/F/functional_specification.html
Reward Points if useful.

When will we write Technical Specifications ?

I am new to ABAP and i would like to know about technical specifications....i:e when will we write Technical Specifications that is before Developing the Object or After developing the object. And what is in it ?
Regards
Moved to a more appropriate forum.
Edited by: kishan P on Feb 15, 2012 10:46 AM

Actually agree with Lukas.
A good functional spec should be written up front and should not normally change. The initial technical specs will often change and need to be updated after full testing and acceptance.
The problem is many folks think the functional spec should be written to the level of a technical spec. In some places they become, (or are), one and the same.
The functional spec should represent the goal. While the technical spec should be the actual steps or plan used to accomplish that. There are often many ways to reach the same goal, some better than others.
FF

Technical Specification Interfaces PI

Hi, first of all, thank you very much for the support I can provide.
I have developed a set of interfaces, but now I need to make the documentation of the technical specification of the interfaces developed. If there is not a standard in the IP documentation I can provide for the technical specification.
thank you very much.
Daniel

As many SDN'ers have suggested here. The format of tech spec is different for every project and clients.
Typically, these formats are decided before the build phase starts.
However, following information is most certainly available in most of the formats:
Section I: Initial Information Requirements
General Information
Involved Systems, Message Communication and Interfaces
Involved Systems
Message Communication
Interfaces
Section II: Technical Development Concept
General Information
Overall Process Description
Enterprise Service Repository Objects
Data Types
Message Types
External Definition
Imported Archive
Imported Objects
Service Interfaces
Java Archive
Message Mappings
Function Library
Operation Mappings
Integration Process
Integration Scenario
BPM Processing Details
Container Variables
Integration Directory
Sender Configuration
Receiver Configuration
Receiver Determination
Interface Determination
Sender Agreement
Receiver Agreement
Direct Connections
Integrated Configurations (AAE)
File Archiving Mechanism
Security & Authorization Configurations
IDoc Port Configurations (for IDoc Inbound/Outbound scenarios)
COMMON Services
PI PatTERNS IDENTIFIED
Section III: Operational Support
Monitoring
Other Configurations
Error Handling within PI
Test Cycle u2013 Unit Test
Transport Number(s)
Cutover Activities
Contacts to Solution Owner
Outstanding Issues
**Apart from this make sure you have the PI standards and naming convention guide specific for your project before you start working on build and TD.
Edited by: Puneet Singhal on Oct 5, 2011 8:26 AM

Industry Standards for the Retail Industry

I want to know " SAP recommends which of these Industry Standards for the Retail Industry?
1.GS1
2.ANSI ASC X12
3.eCOM
4.GSMP
5.EPCglobal
6.GDSN
7.GCI
8.VICS

SAP has avoided making any recommendations. I specifically asked one of their architects a similar question a couple of weeks ago.
In general the X12 and EDIFACT standards are king within the retail industry. Within the United States X12 has been the default standard for many years and is used by all the giants. Within the European Union EDIFACT is the default standard and is used by the vast majority of retailers. However the UK has a standard which is called Tradacoms. In my experience UK retailers have, when pushed, also offered EDIFACT messaging. It should be noted that these formats are not XML. However many XML convertors exist for them. X12, EDIFACT and Tradacoms are what are commonly referred to as Traditional EDI.
The GS1 standard called eCOM is being increasingly adopted. I do know that Accenture and CapGemini have recently been heavily involved in promoting GS1 and eCOM. This is because eCOM standard is realistically the most heavily backed replacement for the Traditional EDI standards. The several of the largest US and European retailers and manufactures are now throwing their weight behind eCOM.

Industry Standards - What are they?

Hi everyone,
I need to know what industry standards usually are when it comes to video. I know that Audio is usually 48 Kh with a frame rate of 29.97 for broadcast and 24 for film. However, what I don't know are compression settings that will help me keep my videos in great quality. Is there an industry standard when it comes to compression? From what I've read on the boards, i know that DVD's use MPEG-2 video, but is this the same standard that professionals use? If so, what is a good guide for my settings?
Also, I've read on the boards that if I were to use Compressor on my videos to fit them on a DVD I would need to use the MPEG-2 DVD setting, however I do not have an MPEG-2 setting that specifically says MPEG-2 DVD. I have numerous MPEG-2 presets, and each has a drop down box that lists DVD PCM Audio, but I just don't know enough to make heads or tails of it and the manual doesn't really seem to explain what any of these settings are/do. Thusfar, I have used DVD Studio Pro for my videos, and it compresses everything to DVD. It's taking videos that are arond 45 minutes long and 10 Gigs and sizing them down to around 1.2 gigs. Is this good? Should my files be sized down THAT much?
If anyone could help me out with this or at least point me in a good direction to get insight on this, I would appreciate it. I realize this is quite a few questions and they probably make no sense. I am a stickler for quality, though, and I want to make sure I'm doing all this RIGHT, not just doing it.
Thanks.

Well, I can qualify it with my experience, and I can explain it with facts. It is my experience and that of most people I hear from that it is the highest quality - for shorter work.
CBR uses one datarate throughout the program - no matter whether it's fast-moving action or black screen. So data is "wasted" on the black frames but the highest quality possible (within the parameters you set) is used everywhere.
VBR uses lower datarate where it thinks it can get away with it. That saves space on the disk, but even in the data-hungry parts it is limited to the parameters you set.
Unfortunately Compressor and friends just don't generally do a good job deciding where to save space. Except perhaps in truly expert hands.
As far as I know the only reason to ever uuse VBR is if you're trying to max out disc capacity. Which is a perfectly good reason.
But there's no reason to get into that if you're just getting your feet wet and/or you have projects less than 60 or even 90 minutes.

Standard warning messages in Vendor Request Form

Hi All,
Please let us know, how are the standard warning messages in Vendor Request Form while creation/search are displayed.
For example, I am getting an soft warning message text, at vendor creation which says "Some of the records were not found; for more information, check the log".
Here we don't have any log traces to be checked for, and we have verified the back end record resultset count which is same, irrelevant of the warning message being shown.
These messages are displayed only at two places:
1) The search navigation page, where all the searched record results are displayed and we continue further for creation of vendor workflow.
2) When the workflow of vendor creation is completed, along with the "Workflow has been completed" success message, this warning message is also shown.
I want to know, from where these messages are being populated and how to suppress these messages.
Kindly suggest.
Thanks in advance!
Message was edited by: Oxana Noa Zubarev

Hi All,
Attaching the screen shot for refernce:
After we click on "continue with create/edit" button, after few details have been entered, the work flow completes.
There are we are getting these error message as highlighted above.
Let me know if any info from my end would help in getting the root cause.
Thanks in advance.

I have destroyed the motherboard of a Mid 2009 MacBook Pro. How do I find out the technical specifications so I can give accurate information to someone who buys it for parts?

I recently had an unfortunate incident with a glass of water and a mid 2009-MacBook Pro. 13 inch screen.
According to the techs at the genius bar, the screen, keyboard, chassis and hard drive (160g) were still all good - as were all components other than the Motherboard.
I just completed the complete erasure of the hard drive, but don't have the technical specifications at my disposal.
Does anyone know how I can get them - the guy at apple said he didn't think he could help?
Serial No. Is available.
Thanks-

http://www.everymac.com/

Industry standard to represent technical specification of forms,conf objetc

Similar Messages

Maybe you are looking for