Search icon CANCEL
Subscription
0
Cart icon
Your Cart (0 item)
Close icon
You have no products in your basket yet
Arrow left icon
Explore Products
Best Sellers
New Releases
Books
Videos
Audiobooks
Learning Hub
Conferences
Free Learning
Arrow right icon
Arrow up icon
GO TO TOP
Mastering SAP ABAP

You're reading from   Mastering SAP ABAP A complete guide to developing fast, durable, and maintainable ABAP programs in SAP

Arrow left icon
Product type Paperback
Published in May 2019
Publisher Packt
ISBN-13 9781787288942
Length 548 pages
Edition 1st Edition
Languages
Arrow right icon
Authors (4):
Arrow left icon
Wojciech Ciesielski Wojciech Ciesielski
Author Profile Icon Wojciech Ciesielski
Wojciech Ciesielski
Philipp Deth Philipp Deth
Author Profile Icon Philipp Deth
Philipp Deth
Paweł Grześkowiak Paweł Grześkowiak
Author Profile Icon Paweł Grześkowiak
Paweł Grześkowiak
Wojciech Ćwik Wojciech Ćwik
Author Profile Icon Wojciech Ćwik
Wojciech Ćwik
Arrow right icon
View More author details
Toc

Table of Contents (19) Chapters Close

Preface 1. Creating Custom Code 2. The Basic Structure of ABAP FREE CHAPTER 3. Database Access in ABAP 4. Import and Export to Document Formats 5. Exposing Data to Print Forms 6. ABAP and XML 7. Building User Interfaces 8. Creating Stunning UI5 Interfaces 9. Business Object Processing Framework 10. Modification and Customization Techniques 11. Handling Exceptions in ABAP 12. Testing ABAP programs 13. Advanced Techniques in ABAP Objects 14. Integrating SAP with Third-Party Systems 15. The Background Processing of ABAP Programs 16. Performance and Optimization of ABAP Code 17. Assessments 18. Another Book You May Enjoy

Designing for quality and use

When designing new software, it is not only a matter of creating functional code. The eventual outcome is going to be a product that serves its purpose, but is also possible to improve, is robust, is easily maintained, and can be used for a long time. From the user's perspective, once the product is paid for, it won't require much more cost in terms of funds, man effort, or any other measurable value.

In order to fulfill these goals and achieve user satisfaction, the philosophy of quality engineering was introduced. In principle, it defines product quality as the ratio of the result of efforts and the total cost; however, in detail, it considers various factors, such as reliability, maintainability, continuous improvement, corrective actions, and risk management.

Particularly in software engineering, there is a need to estimate the quality through an end-to-end view. It requires the collaboration of various actors, whose roles are mostly independent—business architects, security officers, project managers, and more.

One of the basic steps in designing for quality is to determine quality objectives that describe the requirements for software quality. The software quality should be considered in two areas:

  • How it complies with functional requirements—whether the developed product is actually doing what it is supposed to do
  • How it meets the non-functional requirements—whether it reaches its goals in the correct way

Once the objectives are defined, they can be measured with help of appropriate models and various methods, such as Goal Question Metric (GQM), Balanced Scoreboard (BS), or Practical Software Measurement (PSM).

There is no universal way to measure and control the value of quality in all environments. From the vast list of factors, several apply to SAP systems, and should always be considered when developing new code:

  • Understandability: Both the code and all the documentation should be readable by peers.
  • Conciseness: Not only should the code be kept small, but it also should not process unnecessary data.
  • Consistency: The software should follow the notation conventions present in the system.
  • Maintainability: It should be well documented and not complex (modularized as needed) to allow for future updates.
  • Testability: The software should be written in a way that allows tests to check its correctness and performance.
  • Reliability: The code should behave properly (non-erroneously) in all conditions.
  • Security: It should always consider preventive measures to avoid unauthorized access to important data.

Depending on the level of interaction with the user, there are several additional factors that should be considered:

  • The intuitiveness of the UI 
  • Ease of use
  • Sensibleness of messages, for example, errors
  • Responsiveness of the interface

Although these terms tend to be subjective and, in general, hard to determine in the design phase, they have a major impact on the quality of the software as seen by the end user, and therefore, cannot be neglected.

lock icon The rest of the chapter is locked
Register for a free Packt account to unlock a world of extra content!
A free Packt account unlocks extra newsletters, articles, discounted offers, and much more. Start advancing your knowledge today.
Unlock this book and the full library FREE for 7 days
Get unlimited access to 7000+ expert-authored eBooks and videos courses covering every tech area you can think of
Renews at $19.99/month. Cancel anytime