Development of Technical Specification for WDA

Hi,
I've not seen any new information on a Technical Specification template specifically for WDA.
Has there been any new developments on this since last year?
Where can I download the T.S. if it is available?
Thanks.

Index:
DOCUMENT INFORMATION
ACCEPTANCE     
STAKEHOLDERS     
BUSINESS KEY STAKEHOLDERS     
OTHER KEY ROLES AND RESPONSIBILITIES     
1.    CONFIGURATION FOR PROJECT     
2.     DATA STRUCTURES     
2.1     APPLICATION DATA STRUCTURE MODEL     
2.2     DATA ACCESS OBJECTS     
3.     SYSTEM INTERFACE PROCESSES     
3.1     SYSTEM CONNECTIVITY MODEL     
3.2     SYSTEM INTERFACE DEFINITIONS     
3.2.1     Interface Definition:     
<Name of the interface e.g.  BAPI/RFC, Webservice, Bean etc >     
<Name of the interface e.g.  BAPI/RFC, Webservice, Bean etc >     
3.2.2     <BAPI/RFC, Webservice, Bean >Definition:     
<Name of the interface e.g.  BAPI/RFC, Webservice, Bean etc >     
4.     OBJECT DESIGN     
4.1     WEB DYNPRO COMPONENT MODEL     
4.1.1     Views used in the WD Component     
4.1.2     External Components used in the WD Component     
4.1.3     Interface Controller used in the WD Component     
4.1.4     Custom Controllers used in WD component     
4.1.5     Events, Actions and Methods     
4.1.6     Context Elements Defined in WD Components     
4.1.7     Context Binding/Mapping in WD Components     
4.2     ABAP RFCS     
4.2.1     RFC Summary:     
5.     USER INTERFACE SCREEN DESIGNS     
5.1     VIEW ARRANGEMENT (WINDOWS DIAGRAM)     
5.2     NAVIGATION MODELING     
5.3     WEBDYNPRO VIEW DETAILS     
5.3.1     <View Name>: <This view shows information related to view including screen shots.>     
INPUT DATA:     
OUTPUT DATA:     
6.     APPENDIX A u2013 OUTSTANDING ISSUES

Similar Messages

  • Technical specifications for ECC 6.0

    Technical Specifications for ECC 6.0  
    Posted: Oct 8, 2007 7:49 AM         Reply      E-mail this post 
    Hi,
    I am planning to buy a laptop & install ECC 6.0 for the trainings, just wanted to know what technical specifications & additional system components , accessories services should I look for?
    Kindly help asap...
    Points will be rewarded!!!!
    Regards,
    Poornima

    Hi Poornima,
    Check the similar thread on the system requiremement specifications for ECC6.0:
    Hardware requirements for SAP ERP 2005 using ECC 6.0
    Regards,
    Subhasha

  • A technical specification for MC007ZE/A

    Hello!
    Let me know can I get a technical specification for MC007ZE/A. Our organization is going to buy a big batch of these displays. For this we need a technical specification. I've found out this document http://manuals.info.apple.com/MANUALS/1000/MA1554/en_US/LED_Cinema_Display_27-in ch_UG.pdf but it does't containt the number 'MC007ZE/A'. This paper formality associated with the features of our supplier.

    Click here for information; the ZE and LL are country codes which don't affect the model's specifications.
    (106313)

  • Product Specification or Technical Specification for a HP G6000 laptop?

    Does anyone have or know where I might find the Product Specification or Technical Specification for a HP G6000 laptop? I'm particularly interested in the hard drive installed. My daughters laptop HD has crashed so I can't even boot it up to find the HD spec., and although I have removed it, I find it is a Toshiba HDD2D62 120GB Sata 2.5". I can't find a similar one anywhere or a website that provides a suitable compatible HD. Any suggestions anyone?
    This question was solved.
    View Solution.

    Hi,
    The laptop is probably a SATA I one so SATA (not SATA II)  hard drives should work on the laptop. I believe that any SATA hdd up to 160GB should work.
    Dv6-7000 /Full HD/Core i5-3360M/GF 650M/Corsair 8GB/Intel 7260AC/Samsung Pro 256GB
    Testing - HP 15-p000
    HP Touchpad provided by HP
    Currently on Debian Wheeze
    *Please, help other users with the same issue by marking your solved topics as "Accept as Solution"*

  • 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

  • Technical specifications for adding a field in screengroup

    Hi ,
    I have a view profile say FL .  In the activity and layout view I have added a Tab say "85" -Additional data 3- . Now I have made tab active and used 150 ans screen group "150-USER data"
    I want developer to add a new cusom filed in screen group 150-user data .
    Specification for field is ready .
    Question is
    1) How to know which table this screen group 150-user data belongs to so that developer can add it there ? Or is there any other method of specification .
    2)I wil be using this field in equipment also . However in equipment I would like to control data orgin from FL or  individual maintenance . How to enable this feature in custom fields of equipment master data .
    NPB

    NPB,
    Normally the user defined fields are filled through the user exit and the user exit documentaion would help you in identifying which core table needs to be extended to include the custom fields.Have a look at the same for help.
    1) In your case the custom fields needs to included to EQUI or IFLOT or EQUZ or ILOA depending upon your business needs.Have a look at the user exit (ITOB0001 )help for detailed documentation.
    2). It would probably require additional coding to accomplish this requirement(Visibility of transfer or individual maintenance for these custom fields), but it should be possible through the same user exit and or save user exit (IEQM0003 Additional checks before updating equipment).
    Regards
    Narasimhan

  • Technical specification template for WebDynpro development required

    Dear All,
    Can you please provide any pointer to SAP provided technical specification templates for WebDynpro development.
    Thanks and regards,
    Sudhir

    Hi Sudhir
    Does that mean you got the documents you were looking for?
    I too am looking for sample documents and/or templates for Technical Specification for WebDynpro (Java) Application but was not able to find any.
    If you have them will you please forward them to me?
    If you can share a tech spec done for a real project (or even a sample one) along with any such documents, I'd much appreciate it as I'm new to the technology. I still have to find my way around these..... :o)
    Thanks in advance.

  • Urgently need a Technical Specification Document for any java development

    hi friends,
    I urgently need a tech spec doc for any java developments , wanted to refer for creating templates for a product . Please help its very urgent.
    Thanks

    Here are a couple of hundred technical specifications for a wide variety of Java development projects:
    http://jcp.org/en/jsr/all

  • Technical specifications needed for ECC 6.0

    Technical Specifications for ECC 6.0  
    Posted: Oct 8, 2007 7:49 AM         Reply      E-mail this post 
    Hi,
    I am planning to buy a laptop & install ECC 6.0 for the trainings, just wanted to know what technical specifications & additional system components , accessories services should I look for?
    Points will be rewarded!!!!
    Regards,
    Poornima

    Dear Poornima,
    As per my experience,better to go for above 160GB hard drive(250GB will be
    good) and 2 GB RAM is required for Laptop's.
    All the best.
    Regards
    Mangal

  • 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.

  • 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.

  • 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

  • RE: BI functional and Technical Specification

    Hi,
    Can anybody share BI Functional and Technical Specification for SAP R/3 data extraction for modules FI/CO, SD, MM, WM/MM.
    Thanks.

    Hi Hitesh
    Bi Functional Specification is like this where you get the details of what is the report they are looking for and what does that do in detail explanation from the key user of that particular area.
    and also you will receive an document saying that the particular tables and fields ...
    After receiving that then you will be starting an work by preparing an Design document of what are the objects you are going to use in the system and what type of Data Source your are  using and Targets etc.. This is nothing but an Technical Specification... and this also contains what type of the load is it...
    Hope this helps you..
    Thanks

  • WebDynpro Development Technical Specification Document

    I am developing some custom screens using WebDynpro for our Project.  I am looking for a template for Technical Specification document for WD development.  I searched in SDN an Service market but could not find any.  I only found a naming convention document.  Can any one who has been developing suggest what should be the table of contents
    Ex:-
    Landscape
    NWDI
    Development Components
    Views
         -- Methods
         -- Actions
    Model Objects
        - RFC
    Any template would be greatly helpful.
    Thanks

    Hi,
    Template -Technical Specification document for WD development, should ideally include following topics and we are using document which has got same sections
    a) Development Component
             Name
             Used Development Components
             Public Parts
             External files used
    b) Web Dynrpo Components
            i) Web Dynpro Component
            ii) Used Components 
            iii) Methods of Component - Each method explained separately
            iv)Message Pool
            v) Views - Each view explained separately with methods written, plugs, events
             vi) Windows
            vii) Component Controller interfaces
            viii) Any models used
             ix) Application
             x) Custom controllers
      c) Dictionaries
      d) Models
      e) Web Dynpro Component Interfaces
    The above part covers 90% what development activity involved, order can be changed to convenience
    Reagrds,
    Ganga
    Edited by: Gangadharayya Virupakshayya Hiremat on May 12, 2009 6:21 AM

  • Specifications for development

    hi gurus      
    how to give thje specifications for development?

    To speak at macro level that is at projet manager or at senior levels.  The Functional Spec (Specification) which is a comprehensive document is created after the (SRS) Software Requirements Document. It provides more details on selected items originally described in the Software Requirements Template. Elsewhre organizations combine these two documents into a single document.
    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. 
    The functional specification translates the Software Requirements template into a technical description which
    a) Ensures that the product feature requirements are correctly understood before moving into the next step, that is detchnical developement  process. 
    b) Clearly and unambiguously provides all the information necessary for the technical consultants to develop the objects.
    At the consultant level the functional spects are preapred by functinal consultants on any functionality for the purpose of getting the same functinality designed by the technical pepole as most of the times the functionalities according to the requirements of the clients are not available on ready made basis.
    Let me throw some light on documentation which is prepared before and in a project:
    1) Templates
    2) Heat Analysis -
    3) Fit Gap or Gap Analysis
    4) Business Process Design
    5) Business Process Model
    6) Business Change & Impact
    7) Configuration Design, which is just 5 % of Total SAP- have different names -
    8) Future Impact & Change Assessement
    9) Functional Design (Module Wise)
    10) Risk Assessement
    11) Process Metrics and Many More-- Which has impact on Business and its work flow
    In Details
    Functional specifications (functional specs), in the end, are the blueprint for how you want a particular report and transaction to look and work. It details what the report will do, how a user will interact with it, and what it will look like. By creating a blueprint of the report or transaction first, time and productivity are saved during the development stage because the programmers can program instead of also working out the logic of the user-experience. It will also enable you to manage the expectations of your clients or management, as they will know exactly what to expect.
    A key benefit of writing up a Functional Spec is in streamlining the development process. The developer working from the spec has, ideally, all of their questions answered about the report or transaction and can start building it. And since this is a spec that was approved by the client, they are building nothing less than what the client is expecting. There should be nothing left to guess or interpret when the spec is completed.
    Functional Specification
    A functional specification (or sometimes functional specifications) is a formal document used to describe in detail for software developers a product's intended capabilities, appearance, and interactions with users. The functional specification is a kind of guideline and continuing reference point as the developers write the programming code. (At least one major product development group used a "Write the manual first" approach. Before the product existed, they wrote the user's guide for a word processing system, then declared that the user's guide was the functional specification. The developers were challenged to create a product that matched what the user's guide described.) Typically, the functional specification for an application program with a series of interactive windows and dialogs with a user would show the visual appearance of the user interface and describe each of the possible user input actions and the program response actions. A functional specification may also contain formal descriptions of user tasks, dependencies on other products, and usability criteria. Many companies have a guide for developers that describes what topics any product's functional specification should contain.
    For a sense of where the functional specification fits into the development process, here are a typical series of steps in developing a software product:
    Requirements:
    This is a formal statement of what the product planners informed by their knowledge of the marketplace and specific input from existing or potential customers believe is needed for a new product or a new version of an existing product. Requirements are usually expressed in terms of narrative statements and in a relatively general way.
    Objectives: Objectives are written by product designers in response to the Requirements. They describe in a more specific way what the product will look like. Objectives may describe architectures, protocols, and standards to which the product will conform. Measurable objectives are those that set some criteria by which the end product can be judged. Measurability can be in terms of some index of customer satisfaction or in terms of capabilities and task times. Objectives must recognize time and resource constraints. The development schedule is often part or a corollary of the Objectives.
    Functional specification.: The functional specification (usually functional spec or just spec for short) is the formal response to the objectives. It describes all external user and programming interfaces that the product must support.
    Design change requests: Throughout the development process, as the need for change to the functional specification is recognized, a formal change is described in a design change request.
    Logic Specification:
    The structure of the programming (for example, major groups of code modules that support a similar function), individual code modules and their relationships, and the data parameters that they pass to each other may be described in a formal document called a logic specification. The logic specification describes internal interfaces and is for use only by the developers, testers, and, later, to some extent, the programmers that service the product and provide code fixes to the field.
    User documentation:
    In general, all of the preceding documents (except the logic specification) are used as source material for the technical manuals and online information (such as help pages) that are prepared for the product's users.
    Test plan: Most development groups have a formal test plan that describes test cases that will exercise the programming that is written. Testing is done at the module (or unit) level, at the component level, and at the system level in context with other products. This can be thought of as alpha testing. The plan may also allow for beta test. Some companies provide an early version of the product to a selected group of customers for testing in a "real world" situation.
    The Final Product:
    Ideally, the final product is a complete implementation of the functional specification and design change requests, some of which may result from formal testing and beta testing. The cycle is then repeated for the next version of the product, beginning with a new Requirements statement, which ideally uses feedback from customers about the current product to determine what customers need or want next.
    Most software makers adhere to a formal development process similar to the one described above. The hardware development process is similar but includes some additional considerations for the outsourcing of parts and verification of the manufacturing process itself.

Maybe you are looking for

  • How can I use Automator to extract specific Data from a text file?

    I have several hundred text files that contain a bunch of information. I only need six values from each file and ideally I need them as columns in an excel file. How can I use Automator to extract specific Data from the text files and either create a

  • Define Statements in SQL Developer

    Hi, I'm really new to SQL Developer and I'm having one or two issues. The most annoying is to do with Define statements. Say I have the following script to run - define p_start_date = TO_DATE('01-Jan-2010','DD-Mon-YYYY'); SELECT &&p_start_date FROM d

  • Click on an Image?

    How can I add a click to an image, so that when its clicked, it will do this: myTexta[event.target.repeaterIndices-mapRepeater.startingIndex].visible = true;

  • Removing iMessage from dock

    I can't get the imessage icon off my dock on my mackbook pro.  I've tried several things and I still can't get it off the dock.  I don't want to delete it but I just want it to stay in the appications list.  I don't like it on the dock for privacy re

  • Homemade shortcut keys in OSX

    In the old days, I was able to assign text to keys on my keyboard -- For example, if I found that I was typing my name a lot, I could assign my name to "F5" and then every time I hit "F5", the computer would insert my name. If I recall, it worked wit