Standard Development Methodology

I work as a software development team leader in Oracle platform.
We have been using Developer/2000 and Oracle Workgroup server for
most of our projects. As a team leader I always tried to
implemented a standard software development mothodology in our
team's work. However, as I have not gone through any such
standards that is recommended by Oracle or any other
International bodies, I have always tried to make our software
development suitable for my self and our team which, I wonder,
may not meet any standards recommended by Oracle.
I am thus looking for some resources, books, magazines that
describe, in detail, standard methods of software development in
Oracle platform. Starting from naming an entity, naming a form,
report, a block in a form, naming variables, using color schemes,
etc., I would like to use standard names/methods to all objects
of our application and implement standard software development
methodology in our development.
Please suggest me such methods or resources and let me know where
I can find them.
null

Bal Ram (guest) wrote:
: I work as a software development team leader in Oracle
platform.
: We have been using Developer/2000 and Oracle Workgroup server
for
: most of our projects. As a team leader I always tried to
: implemented a standard software development mothodology in our
: team's work. However, as I have not gone through any such
: standards that is recommended by Oracle or any other
: International bodies, I have always tried to make our software
: development suitable for my self and our team which, I wonder,
: may not meet any standards recommended by Oracle.
: I am thus looking for some resources, books, magazines that
: describe, in detail, standard methods of software development
in
: Oracle platform. Starting from naming an entity, naming a form,
: report, a block in a form, naming variables, using color
schemes,
: etc., I would like to use standard names/methods to all objects
: of our application and implement standard software development
: methodology in our development.
: Please suggest me such methods or resources and let me know
where
: I can find them.
My suggestion on this would be.
1. Check the Developer's manual in which Oracle has given certain
guidelines in application development.
2. Naming convention can be used as per your convenience, but
should follow the same pattern throughout.
3. Most big companies make their Methodology book, but that is
changed or reviewed every two year or later.
4. If you find such book do let me know as well
-bj
null

Similar Messages

Development Methodology

Hi Friends and Experts,
Can any one please let me know what is Development methodology used in ABAP.

***********Please reward points ,if found useful
Hi,
ASAP: Accelerated Systems Application and Products in Data Processing
ASAP methodoligy means nothing but standard process for implementation of SAP, It consists of 5 phases.
1. Project preperation - consists of identifying team members and developing strategy as how to go.
2. Business Blue print - consists of identifying the client current process, reqeirement and how SAP provides solution.
Consists of detailed documentaion
3. Realization -The purpose of this phase is to implement all the business and process requirements based on the
Business Blueprint.
4 Final Preparation - The purpose of this phase is to complete testing, end-user training,
5 Go Live and Support
All the functinal consultatns need good rapo with Abapers. right from uploading of legacy data, devoloping customised reports, BDC's, Forms etc, here functinal consultatns need to give guidence as to get the requried data for reports and all.. like the table name, fields etc
All implementation projects have the the following phases:
Scoping - What is to be implemented i.e. which submodules are to be implemented some clients may not require credit management for example. Look at the project scope document carefully it will tell you what SAP sub-modules in SAP you should be prepared for. Usually the sales people along with project manager do it.
As is - Here you understand the existing business processes of the client . Your BPOcollect all the ISO-documentation (if client is ISO certified), reports and forms at this stage and you analyse how and when the reports/forms are generated, where the data is coming from. You also do a Level -2 training for your BPO so he is made aware of all the required transactions in SAP.
Once this is over BPO can start learning with the consultants help more about SAP. This is crucial because if you miss out any transactions the BPO may forget about some of his Business processes which may come up later. It is a good practice to ask the BPO to make flow charts to explain business processes.
To-Be - Parallely you map these processes to SAP. Processes that you are not sure of as to whether they are present in SAP or not you try to do a configuration of those processes, and along with the BPO(Business process owner he is the clients employee who knows about the clients business processes probably a middle management guy, ther can more than one), BPO involvement is required as he may be able to tell you his requirements better. Once you do the business modelling you
will also be made aware of the gaps between as-is and to-be , here decisons have to be made as to wether a ABAP development/system modification is required or not and so on. Involve the BPO as much as possible and document everything it is good practice do not be lazy about it.
Business blueprint: Here the as-is and to-be and gap analysis is explained. This is the document that you will be using to do your configuration in the realization phase.
Realization phase: Here you do the configuration in the development server (there are three clients -development,quality, production). You also decide on the master data format, so that BPO can go collect the master data. You also gove ABAP specifications for forms, reports etc, system modifications etc. Unit testing: Your BPOs and a few key users sit down and test your configuration in your module only. It is good to test the BDCs that you need for uploading data at this stage so you have more realistic data and your BDCs are tested.
Integration testing:
Once all modules unit testing is over then the configuration is trasported to the Quality server, where testing for all the modules is done by BPOs and end user, this is to check if any problems are there in integration between various modules. Once all is okay from the QA server config is transported to the production server.
Go live preparation
Data uploading: The collected master data is checked and the uploaded into production server(sever and client I have used interchangeably). Now you are ready for go live i.e. users can now use the production server.
With Regards,
BVS

Development Methodology: urgent

what is development methodology in sap development.

ASAP methodology
AcceleratedSAP (i.e. ASAP) methodology/roadmap is a proven, repeatable and successful approach to implement SAP solutions across industries and customer environments. ASAP is widely used for SAP Business Suite (SAP ERP, SAP CRM, SAP SCM, SAP PLM, SAP SRM), SAP xApps, SAP NetWeaver and SAP Solutions for Mobile Business among many other solutions. The methodology covers the necessary project management, the configuration of business processes, testing and training aspects as well as technical implementation activities.
In order to ensure central data access, the ASAP roadmap and tools have become a standard component in SAP Solution Manager (service.sap.com/solutionmanager) - the implementation and operations platform. In addition, ASAP is available for browsing and offline use on Service Market Place. From tool perspective, the SAP Solution Manager implementation function is the successor to the ASAP tools, hence some tools such as the Implementation Assistant, Q&Adb, and the Master Lists are replaced by Solution Manager Implementation Function.
ASAP Roadmap
Use
The ASAP Roadmap provides the methodology for implementing and continuously optimizing
your SAP software. It divides the implementation process into five phases and offers detailed
Project Plans to assist you (in Microsoft Project format). The documentation stored at each level
of the Roadmap tree structure contains recommendations on implementing your SAP software
and links to helpful tools and accelerators.
Purpose
When you install the Implementation Assistant you can choose from several Roadmap types and
flavors. You can select one of the following flavors:
R/3 - Implementation and Continuous Improvement
APO - Advanced Planner & Optimizer
BW - Business Information Warehouse
B2B - Business to Business
CRM - Customer Relationship Management
Features
Implementation of SAP software covers the following phases:
1. Project Preparation
In this phase you plan your project and lay the foundations for successful implementation. It
is at this stage that you make the strategic decisions crucial to your project:
− Define your project goals and objectives
− Clarify the scope of your implementation
− Define your project schedule, budget plan, and implementation sequence
− Establish the project organization and relevant committees and assign resources
2. Business Blueprint
In this phase you create a blueprint, which documents your enterprises requirements and
establishes how your business processes and organizational structure are to be represented
in SAP software. You also refine the original project goals and objectives and revise the
overall project schedule in this phase.
3. Realization
In this phase, you configure the requirements contained in the Business Blueprint. Baseline
configuration (major scope) is followed by final configuration (remaining scope), which can
consist of up to four cycles. Other key focal areas of this phase are conducting integration
tests and drawing up end user documentation.
4. Final Preparation
In this phase you complete your preparations, including testing, end user training, system
management, and cutover activities. You also need to resolve all open issues in this phase.
At this stage you need to ensure that all the prerequisites for your system to go live have
been fulfilled.
5. Go Live & Support
In this phase you move from a pre-production environment to the live system. The most
important elements include setting up production support, monitoring system transactions,
and optimizing overall system performance.
After your system has gone live, you can use a separate Roadmap with six work
packages, in order to optimize your R/3 System continuously.
These phases are the main milestones for implementing SAP software. Each phase has:
Work packages, which consist of activities, for which project teams are responsible.
Activities, which consist of tasks, which are processed by one or more team members.
Tasks, which are carried out by a project team member. You can also access the How-to
sections and accelerators at this level.
Also check this AcceleratedSAP document.
http://help.sap.com/printdocu/core/print46b/en/data/en/pdf/SVASAP.pdf
Regards,
Maha

Best practice when modifying SAP Standard Development Component

Hello Experts,
What is best practice when modifying SAP Standard Development Component (Java Web Dynpro)? Iu2019m looking for the best method to do modifications to SAP Standard DC so that my changes will be kept (or need low maintenance) after a new service package (or EHP) is applied.
Thanks,
Kevin

Hi,
'How to use Busiess Packages in Enterprise Portal 6.0' is available in this link.
http://help.sap.com/bp_epv260/EP_EN/documentation/How-to_Guides/misc/Using_Business_Packages.pdf
Check out for the best practices.
Regards,
Harini S

Jdeveloper (ADF) development methodology

Hi,
I am new to Jdeveloper and trying to learn as much as possible from it.
The target is to be able to develop soon web applications based on ADF Faces and ADF BC.
There are lots of useful tutorials in the OTN (also have been testing and analyzing the SRDemoSample). However, I haven't found any formal development methodology I can use as a basis when using ADF Faces together with ADF BC (maybe something like RUP but applied to ADF).
I know Oracle has something called JCDM, but I think it is for internal use and also I don't know if they have a version instantiated for ADF.
Anyone out there with any recommendation / practice in this regard?
Thanks,
Claudio.

Shay,
Thanks for your answer.
Maybe I expressed myself in the wrong way, but I am not looking for implementation details such as i18n and securing an application. Those details are pretty clear in the SRDemo.
What I am really looking for is how Oracle recommends on doing a detailed design of an ADF application. Let's say you have the requirements and use cases of the application, and you are asked to do the detail design of an application that will use JSF and ADF BC (notice I am saying BC: Toplink in our case is not an option).
First thing that comes into my mind is to do UML class diagrams, sequence diagrams, etc and then show that to the developers to give them the starting point for implementation. But will these diagrams be of use for the developers, given the fact that ADF is mostly wizard based?
I mean in a large project you can't just leave the developers only with the use cases and requirements because when the project starts to grow, it will become unmanageable. So I think there should be a detailed design (that is updated as the project evolves) - but how do you match this design with ADF wizards, I know Jdeveloper has UML support, but is there a tutorial (or documentation) that starts with the detail design and then builds the application from there ?
Thanks again,
Claudio.

Do you know rule for standard development ?

Hi exeprt,
do you know some document about creation of standard development ? I mean that a document where is explained all object to name on system to start a development in a new system.
tks.

Well for starters, here is a list of (all) possible objects to be created for which naming convention must be established:
Global booleans
Global constants
Global internal tables
Workarea global internal table
Global ranges
Global statics
Global structures (records)
Global types
Global variable (character)
Global variable (date)
Global variable (integer)
Global variable (packed)
Global workarea database table
Parameters
Check boxes
Radio buttons
Select options
Class
Interface
Local booleans
Local constants
Local internal tables
Workarea local internal table
Local ranges
Local statics
Local structures (records)
Local types
Local variable (character)
Local variable (date)
Local variable (integer)
Local variable (packed)
Local workarea database table
Forms using parameters
Forms using parameters (table)
Forms changing parameters
Forms changing parameters (table)
Forms tables parameters
Tables parameters must not be used anymore
Function Module/Method importing parameters
Function Module/Method importing parameters (table)
Function Module/Method exporting parameters
Function Module/Method exporting parameters (table)
Function Module/Method changing parameters
Function Module/Method changing parameters (table)
Function Module tables parameters
Tables parameters must not be used anymore
Function Module/Method exceptions
Method returning parameters
I'm not saying this list is complete, for example objects specific for module pool programming are not included, neither are BAdI's (or enhancements in general for that matter), Web Dynpro development (etc.) , but it will help you on your way. If somewhere along the line, some new objects are created at this customer, you should enhance this document.

J2EE development methodology

Hi,
I am preparing a proposal to push J2EE as our enterprise application standard. I don't know what methodology we should use to develop J2EE application, it seems that water-fall is not a good idea here.
Could anybody help? Thanks in advance.

Here is the methodology I used on my latest project (it turned out that by focussing on the first development as waterfall we could produce a set of reusable beans that allow us to now select the most appropriate methodology for future developments).
We focussed on one particular application, used UML to capture the design and then built individual components using a waterfall method.
The design divided the components into a reusable layer, and an application specific layer (effectively a layer that provided various services, and a layer that co-ordinated those services together)
We have effectively built other applications now by using a strong design to identify functionality that can be reused (from the service layer) and functionality required in the application specific layer. Any new service layer components can be built using the most appropriate methodology.
Building a client and the application specific layer we have done using both classical waterfall and RAD approaches, depending upon which is most appropriate. Development times are obviously reduced since we have a pool of service layer bean functionality.
Adam

Development Methodology for MI

Hi,
Can anyone have Implementation Methodology document for Mobile Infrastructure or any informaion where I will get the document?
Thanks & Regards
Nileshwar.

hello nileshwar,
there are steps and recommendations regarding MI application
development on <a href="http://media.sdn.sap.com/public/html/submitted_docs/MI/MDK_2.5/index.htm">Mobile Development Kit</a>.
for MI implemenation you can refer to <a href="http://help.sap.com/saphelp_nw04/helpdata/en/bb/b670bbaa991845924982155b7c3726/content.htm">Configuration of SAP Mobile Infrastructure</a>
in the NW04 help document.
regards
jo

Jdeveloper's own development methodology.

as developers we wonder the methods (not secret ones).
are used to develop J developer IDE.
For example microsoft publish their some of the methods MOF, MS Team system etc.
Maybe Oracle will do it in the future?
if there is no company restriction to mention
Can you explain these methodology briefly? J dev own lifecyle.
Thanks.

Thanks.
We are waiting series next articles.

[Solved] Development "methodology"

This is not strictly speaking, a programming question, but this section of the forum seemed the more appropriate. So, say you want to start developing pacman, or vim, or (to stretch the question), KDE. How do you set up your environment? For pacman I would modify the source and do something like makepkg --noextract (but do speak up if there are better ways!). I guess this could also work for vim but, and for KDE? Chroot? Virtual machine?
And even for "simpler" things like vim, I don't think it's possible to install say, vim alongside a vim-devel version... is it? Again, are there better alternatives?
Thanks in advance for the help, and my apologies for such a "broad" question...
Last edited by gauthma (2014-03-25 23:28:22)

Remember, all pacman (and PKGBUILD) files do is automate the installation of software. You can run the same commands yourself just by typing what you see in the PKGBUILD file into Bash. Also, you can alter where you install it in order to test it out.
Let's use Vim as an example: Vim uses the standard "./configure && make && make install" build instructions. So, first get a copy of the Vim source code. (Now, since you have a developer's version of the source instead of a packager's version, you may need to run "autoconf" now.) Next, build and install it into a personal location like this:
./configure --prefix=~/tmp/vim-dev && make && make install
Now, edit the source code, re-run "make && make install", and run it with "~/tmp/vim-dev/bin/vim". That personal copy of Vim will ONLY use the files that are under "~/tmp/vim-dev".
I don't know how to configure, build, and install KDE, but (in theory) it will be a similar process. Just read the PKGBUILD file for it.
Does that help?

Office 3013 32bit Pro Plus vs. Standard (Developer tab, add-in issues)

In a domain environment with Windows 7 64bit systems and Office 2013 Standard 32bit installed, we have had some issues with using Outlook templates. When the outlook templates are opened/created and then edited and sent, the resulting email is missing
all edited content and looks as the original opened/created template. Also, the developer tab is not enabled by default.
When Office Pro Plus 32bit is installed on the same system, the templates that are opened/created are able to be edited and sent without issue. Also, the developer tab is enabled by default.
Has anyone else ran inot this before or have any suggestions?
Thank you for your time.

Hi,
How did you create the templates? Through an add-in?
Does this issue happen to all custom Outlook templates?
If you installed any security programs, please temporarily turn off them to check the result.
Please let me know the result.
Best Regards,
Steve Fan
TechNet Community Support

BW authorizations for standard development

For a training workshop, I need to define some authorizations for the trainees. They shouldn't be allowed to do whatever they want on the BW and R/3 systems. So I can't give them the SAP_ALL profile!
On the source system, the users would be allowed to do something like the following:
- Activate DataSources as local objects (in the package $TMP or in test packages T*);
- Edit the DataSource's active version;
- Edit the function EXIT for the LO DataSources (can the EXIT be a local object?)
On the BW side:
- Replicate the DataSources;
- Create DataSources for the FILE source system;
- Create export DataSources for the myself source system;
- Develop data models and flows;
- Start InfoPackages;
- Develop and run BEx queries.
All these BW objects would be local (yes, this is the default behaviour in BW -- but how can I be absolutely sure a user is prevented altogether from putting an object in a productive package by mistake?)
I'm not a security expert.. Can you give me some good advice and send me some links to useful docs on this topic?
Thanks, <a href="https://wiki.sdn.sap.com/wiki/display/profile/Davide+Cavallari">Davide</a>

Hello David,
using BI Authorizations in BW and then adding data level security in the Universe on top of that will only lead to situations like you have now.
Data Level security goes into BW alone or into the Universe alone, mixing both will lead to issues and remember that the Universe has far less capabilities in this area.
0BI_ALL is only related to data level security, so the fact that you see the request for 0BI_ALL in the trace clearly shows that your defined data level security entries contradict each other somehow and that BW then requires 0BI_ALL for the user to give the data that was requested.
like I said above, not a good idea to mix those data level security concepts. all data level security should be in BW already.
Also - why even use the Universe inbetween ?
regards
Ingo Hilgefort, SAP

BPEL develop methodology

Anybody who can provide the methodology or experience on How to build a new system by using bpel technology? Note that the new system no need to integrate other applications. So, it is a question about building a new system in SOA(Service Oriented Architecture).
Best Regards,
Sean

Hi Sean,
Please have a look at "http://www.oracle.com/technology/products/ias/bpel/index.html". This will give you a good start. After going through this URL, if you have any question feel free to ask.

XI Development methodologies

All - Is there a good doc or an URL that I can review to start looking at this ?
Thanks much !
Madhu

Here's a link.
http://media.sdn.sap.com/html/submitted_docs/Implementation_Roadmap_XI/index.htm
If the answer is satisfied, please assign points and close the thread.
regards
Shravan

The development methodology of scenarios in Discovery system

Dear Experts,
I am new to the Discovery System(DS) and I have done all the scenarios of DS in my environment.
I would like to know following things regarding the scenarios:
1. How are the designing of the scenarios done?
When I have to design the scenario, what are the basic things I should bear in mind to make a business application for a client?
( Making simple WebDynpros and Visual composers are not that difficult, but I would like to know how the designing is done at first?
2. What are the basics to decide whether we will use the guided procedure or Visual composer to make a business workflow?
I am really looking forward to hearing from you.
Thanks in advance
sudeep

Hi Sudeep,
1) typically you'd start with a definition of the scenario (business process) you'd like to cover. This could be done using any tool. Here https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/5d84c39c-0d01-0010-da89-f91b698cdfcd is an example how to do it for the Procurement Process that is on the Discovery System. After having the scenario 'on paper' you can have a look at the different steps and activities and map these to technology.
2) the main differentiator: GP would be used to tie different steps of a scenario together. VC would be used to design the user facing part. VC screens can be then integrated into the larger context of a GP.
Hope that helps,
rAimund

Standard Development Methodology

Similar Messages

Maybe you are looking for