A. Loose coupling with core business processes
B. Reduction of complexity through a single IT provider
C. Strict tool-based approach
D. Software lifecycle of extensions coupled to stable systems of records
E. Monolithic Architecture
A. Role Template
B. Scope
C. Role
D. Permission
E. Role Collection
A. Heterogenic
B. Tightly coupled
C. Monolithic
D. Highly distributed
E. Monolithic
A. Unite build and run stages
B. Traceability and reproducibility of all changes
C. Stateless and self-contained application processes
D. Separation of application code and runtime configuration
E. Multiple codebases tracked in revision control, single deploy
A. Analytical Cube
B. CDS Table
C. External API
D. Analytical Sphere
E. Analytical Dimension
F. Standard CDS View
A. As side-by-side extensions always rely on asynchronous patterns such as events there's no dependency to the core system. Thus updates to it don't affect the extension.
B. With side-by-side extensions residing in the SAP application, they are upgraded as well.
C. SAP APIs are guaranteed to be lifecycle-stable. Unless important changes happen in the backend application, the APIs will continue the same when the SAP application is upgraded to the next release
D. When upgrading to the next release the side-by-side extension is automatically checked for changing dependencies and updated accordingly
A. The code of the pipeline, the lifecycle management script, and the required Docker images can be updates easily.
B. A project generated through the provided archetypes already includes a Jenkins file which loads the CI/CD pipeline automatically.
C. Pipelines running everything in parallel, so given enough computing resources, builds run fast.
D. Having a local download cache
E. Isolation of the builds
A. Ruby
B. Python
C. Java
D. Scala
E. JavaScript
F. Go
A. They have the smallest granularity. They can be defined directly at the programming level, for example by calling methods of your Java classes. Dependencies on other modules or systems can be mocked to ensure they run quickly and test only the code under test. These tests are usually inexpensive. You should use them to verify that your software modules, such as classes, behave as expected.
B. They have reduced complexity. They skip the user interface and work directly on the defined backend APIs. They test the integration between software modules or systems. Although they have reduced complexity, they still have medium cost. They still have overhead, such as network communication or spawning a small server to make the backend APIs available. You should use them to verify that your backend services can communicate with your SAP S/4HANA system and to test that the services behave as the user interface expects.
C. The idea is to simulate a typical user workflow. An automated web browser clicks through the application's web interface and verifies that the expected screens appear. Tests at this level show that the application's features work. However, these tests are expensive to create and run because, for example, interacting with the browser consumes many resources. In addition, it is usually difficult to specify the interaction with the browser so that it can handle minor changes in the structure of the application's user interface.
D. They are run when the application is deployed to production, to verify that the deployment was successful.
A. Performance Tests
B. Smoke Test
C. Integration Test
D. Unit Test
