Chapter 1: Creating Custom Code

Question 1

SAP systems can be enhanced in 5 ways

Answer 1

Customizing 
Personalization
Modification 
Enhancement
Custom Development

Question 2

Customizing

Answer 2

Specific business and functional process configuration according to the implementation guide.

Question 3

Personalization

Answer 3

Setting up global attributes to display certain fields

Question 4

Modification

Answer 4

Changes SAP repository objects make at the client side.

Question 5

Enhancement

Answer 5

Creating a repository object inside a standard SAP program

Question 6

Custom development

Answer 6

Creating objects that are unique to the client repository

Question 7

Design thinking

Answer 7

A method of problem-solving. Multi-staged division of tasks.

Question 8

5 steps of design-thinking

Answer 8

Empathy
Define the problem
Ideas
Prototypes
Tests

Question 9

Empathy

Answer 9

The needs of the group must be known

Question 10

Define the problem

Answer 10

We need to define the exact problem to be solve

Question 11

Ideas

Answer 11

The stage consists of creating as many ideas as possible for solutions relating to the previously defined problem.

Question 12

Prototypes

Answer 12

Make a preliminary visualization of the idea

Question 13

Tests

Answer 13

Product tested in a real environment

Question 14

BDUF/LDUF

Answer 14

Big design up front, little design up front

Question 15

LDUF

Answer 15

The process of modeling a small subsystem before coding

Question 16

BDUF

Answer 16

Modeling system where the whole system needs to be modeled before implementation.

Question 17

2 categories of BDUF

Answer 17

• A document of high-level architecture, which determines the key features of architecture
• General documentation describes everything from high-level architecture to the smallest detail of the system

Question 18

Aspects of LDUF

Answer 18

• Highly informal
• Code is crated in small subsystem
• Not prescriptive

Question 19

Aspects BDUF

Answer 19

• Hard and expensive
• Needs big team
• Perspective

Question 20

2 areas of software quality

Answer 20

• How it complies with functional requirements—whether the product does what it is supposed to
• How it meets the non-functional requirements—whether it reaches the goals in the right way

Question 21

Goal question metric(GQM)
Balanced scoreboard(BS)
Practical software Measurement(PSM)

Answer 21

Models and methods for measuring objectives

Question 22

Understandability

Answer 22

Both the code and all the documentation should be readable by peers

Question 23

Conciseness

Answer 23

Code should be kept small, and also not process unnecessary data

Question 24

Consistency

Answer 24

The software should follow the notation conventions present in the system

Question 25

Maintainability

Answer 25

Well documented and not complex to allow for future updates

Question 26

Testability

Answer 26

Software written in a way that allows tests to check its correctness and performance

Question 27

Reliability

Answer 27

The code should behave properly in all conditions

Question 28

Security

Answer 28

Should consider preventive measures to avoid unauthorized access to important data

Question 29

Additional factors

Answer 29

• Intuitiveness
• Ease of use
• Sensibleness of messages, errors
• Responsiveness of the interface

Question 30

Ground rules for UI design

Answer 30

• Use written words
• Use the user’s language
• Use consistent terminology

Question 31

Psychological principles for screens

Answer 31

• The effect of proximity
• The effect of similarity
• The effect of closure
• The effect of continuity

Question 32

Designing services

Answer 32

• Keep services singular-task oriented
• Avoid direct database manipulation in services
• Expect, but check
• Provide consistent and explanatory responses
• Keep the service well documented
• Keep the service interface unchanged