Chapter 1: Creating Custom Code Flashcards

1
Q

SAP systems can be enhanced in 5 ways

A
Customizing 
Personalization
Modification 
Enhancement
Custom Development
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
2
Q

Customizing

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
3
Q

Personalization

A

Setting up global attributes to display certain fields

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
4
Q

Modification

A

Changes SAP repository objects make at the client side.

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
5
Q

Enhancement

A

Creating a repository object inside a standard SAP program

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
6
Q

Custom development

A

Creating objects that are unique to the client repository

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
7
Q

Design thinking

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
8
Q

5 steps of design-thinking

A
Empathy
Define the problem
Ideas
Prototypes
Tests
How well did you know this?
1
Not at all
2
3
4
5
Perfectly
9
Q

Empathy

A

The needs of the group must be known

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
10
Q

Define the problem

A

We need to define the exact problem to be solve

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
11
Q

Ideas

A

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

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
12
Q

Prototypes

A

Make a preliminary visualization of the idea

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
13
Q

Tests

A

Product tested in a real environment

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
14
Q

BDUF/LDUF

A

Big design up front, little design up front

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
15
Q

LDUF

A

The process of modeling a small subsystem before coding

How well did you know this?
1
Not at all
2
3
4
5
Perfectly
16
Q

BDUF

A

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

17
Q

2 categories of BDUF

A
  • 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
18
Q

Aspects of LDUF

A
  • Highly informal
  • Code is crated in small subsystem
  • Not prescriptive
19
Q

Aspects BDUF

A
  • Hard and expensive
  • Needs big team
  • Perspective
20
Q

2 areas of software quality

A
  • 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
21
Q

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

A

Models and methods for measuring objectives

22
Q

Understandability

A

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

23
Q

Conciseness

A

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

24
Q

Consistency

A

The software should follow the notation conventions present in the system

25
Maintainability
Well documented and not complex to allow for future updates
26
Testability
Software written in a way that allows tests to check its correctness and performance
27
Reliability
The code should behave properly in all conditions
28
Security
Should consider preventive measures to avoid unauthorized access to important data
29
Additional factors
* Intuitiveness * Ease of use * Sensibleness of messages, errors * Responsiveness of the interface
30
Ground rules for UI design
* Use written words * Use the user’s language * Use consistent terminology
31
Psychological principles for screens
* The effect of proximity * The effect of similarity * The effect of closure * The effect of continuity
32
Designing services
* 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