326 reputation
29
bio website hupperts.de
location Germany
age 46
visits member for 1 year, 9 months
seen Sep 17 at 20:25

Addicted to computers and programming since I got my ZX81 at age of 11. Working in software development since 1991. Now at SAP as software architect.


Jan
30
awarded  Yearling
Dec
2
comment Is securing the credit card data is considered a requirement from the customer
PCI does not depend on US law. It is a legal contract between the credit card companies and whoever wants to accept credit cards. Thus, it works world wide. The contract gives PCI certain rights to examine your IT systems and procedures in case of an incident. They can even shut down the IT systems for investigation (remember Sony hack? 3 weeks downtime).
Nov
25
comment Is SOA as a concept intended to function within code or between machines over a network?
In my company, we even have internal standards which forbid that business logic is included in a interface layer. So transport logic is in the API layer, no matter if SOA or whatever. THe common businness logic shall not care about the transport form. However, there is still some dependency mainly because of performance reasons: if you have an API which only returns one field from a complex business object, then the business logic layer might need to support that instead of reading the whole fat object.
Nov
24
answered Is SOA as a concept intended to function within code or between machines over a network?
Nov
20
comment Multiple APIs, or one API with a “chooser” parameter?
Concerning "You wind up with a proliferation of interfaces and adapters.": OP said that the APIs transport data from views. That indicates to me that there is a common data model below the views, database tables probably. As long as all views and the corresponding APIs are derived from such a common data model, the APIs will at least be less likely to contradict each other. A certain degree of overlap and proliferation is the necessary flipside of having specialized APIs.
Oct
13
comment Should there be a formal role (internal or external) assigned to dev environments to control wasteful complexity?
Because it is possible to sell investment into a platform/framework as investment with a good ROI to management. Refactoring has much less glamour and is hard to sell.
Oct
13
comment Should there be a formal role (internal or external) assigned to dev environments to control wasteful complexity?
Good answer. I'd like to add bullet point 4.: you will need a management which allows the other roles (1-3) to pay back technical debt. This will speed up development in the current releases because 1-3 know they can refactor later as needed. If management always uses up all available ressources for new features, architects and developers are pushed towards inventing flexible frameworks which try to solve all potential future problems. That is nearly impossible and creates the problems described by the original author.
Sep
26
revised How do you decide how much business requirements documentation you need and how to structure it?
Typo
Sep
25
revised How do you decide how much business requirements documentation you need and how to structure it?
formatting edit
Sep
25
answered How do you decide how much business requirements documentation you need and how to structure it?
Jun
9
awarded  Custodian
Jun
9
reviewed Approve suggested edit on Software Architecture Modelling
Jun
4
awarded  Enthusiast
Jun
2
answered Suggested Web Application Framework and Database for Enterprise, “Big-Data” App?
May
28
awarded  Critic
May
25
comment How to design a good receipt number
Could you please add the following information: does the number need to be human readable? Is there only one server generating the numbers, or could it happen that you need to scale out to multiple servers? Do you have any legal requirements on the number, e.g. does the number need to be sequential or even gapless?
May
24
answered Software Architecture Modelling
May
24
awarded  Commentator
May
24
comment Software Architecture Modelling
"it can sometimes be challenging to diagram architecture-level concepts using notations designed for object-oriented design." Works nicely, we do that in nearly every of our software products using a slimmed down version of UML.
May
20
awarded  Analytical