101 of Commodity Markets

The purpose of the Risk Log is to:

- allocate a unique number to each risk
- record the type of risk
- be a summary of the risks, their analysis and status

You can find more information at : Project Management Institute

Here is Program Risk Log Template: Risk Log Template

The V-model is an internationally recognized development standard for IT systems which uniformly and bindingly lays down what has to be done[Procedure], how the tasks are to be performed[Methods] and what is to be used to carry this out[Tools].
3 Levels of V-Model:
The standardization concept of the German Federal Authorities pursues this objective by regulations on three levels:
Software Lifecycle Process Model.
Methods to be used.
Tool Requirements.

Submodels of V-Model:
The V-Model is structured into functional parts, called submodels. These four submodels are closely integrated and mutually influence one another by exchange of products/results. These submodels are as below:
Project management (PM): plans, controls and informs the SD, QA and CM submodels.
Software/System development (SD): develops the system or the software.
Quality Assurance (QA): specifies quality requirements, test cases and criteria, and examines the products and the compliance with the standards.
Configuration Management (CM): administrates the products generated.
Software Development Submodel - [ Also known as the traditional V-Model ]

Conventional V-Model represents the development process in the form of a V shape. The right side of the V represents the testing where the systems is validated against the specifications defined on the left side. The meeting point of the V represents the actual development.
Use of V-Model in ABAP Development Lifecycle:
Generally in implementation Projects, ABAP development cycle will be somewhat :
Requirement Analysis

Application Design - High Level design - quite functional - contains functional test cases or guidelines for test cases - Review of AD - Review comments implemented till sign off by the stake holders ( client side / consultant side )

Detail Design Detail Level design - quite technical as well - Man-hours required is estimated and mentioned - contains functional & technical unit test cases - Review of DD - Review comments implemented till sign off by the stake holders ( client side / consultant side )

Development - Coding by the developers as per the detail design -

Unit Testing - is done in Development Server by the developer to ensure that program works as per the detail design - add / implement test case results - transport request details & documentation in detail design - Evidence is attached. Code Review to ensure that coding is as per the coding standards ( performance related as well ) - Also check the test cases and verify - Review comments implemented till sign-off by the stake holders. Before Application testing the realted chunk of work is transported to QA Server.

Application Testing / Integration Testing - This is to ensure that programs work along with other components, that might get affected. e.g. Even the Invoice process should be tested if a change is made in the interface related with a PO creation / change. The test cases or created separately ( more functional in nature and considers dependency of components ). Before implementation of the release, the complete product needs to be tested to ensure that it can bear the maximum load of a production environment.

Product Testing / Load Testing - is performed with huge datasets to check if system / product can handle production scenario in terms of memory and performance.

Final Implementation in Production.

Support - Any further problems will be solved as Bug-fix or and enhancments will be carried out as a part of change request.

AcceleratedSAP methodology is proven, repeatable and successful approach to implement SAP solutions across industries and customer environments.
It provides content, tools and expertise from thousands of successful implementations.

Phase 1: Project Preparation :

During this phase the team goes through initial planning and preparation for SAP project.

Define project goals and objectives
Clarify the scope of implementation
Define project schedule, budget plan, and implementation sequence
Establish the project organization and relevant committees and assign resources

Phase 2: Business Blueprint

The purpose of this phase is to achieve a common understanding of how the company intends to run SAP to support their business. Also, to refine the original project goals and objectives and revise the overall project schedule in this phase. The result is the Business Blueprint, a detailed documentation of the results gathered during requirements workshops.

Phase 3: Realization:

The purpose of this phase is to implement all the business process requirements based on the Business Blueprint. The system configuration methodology is provided in two work packages: Baseline (major scope); and Final configuration (remaining scope). Other key focal areas of this phase are conducting integration tests and drawing up end user documentation.

Phase 4: Final Preparation:

The purpose of this phase is to complete the final preparation (including testing, end user training, system management and cutover activities) to finalize your readiness to go live. The Final Preparation phase also serves to resolve all critical open issues. On successful completion of this phase, you are ready to run your business in your live SAP System.

Phase 5: Go Live & Support:

The purpose of this phase is to move from a project-oriented, pre-production environment to live production operation. The most important elements include setting up production support, monitoring system transactions, and optimizing overall system performance.