UI5 apps should be designed such that they are intuitive. Nevertheless, users still occasionally need some guidance. This post provides one way of including contextual help in SAPUI5 and OpenUI5 apps.
BPSE Consulting, an SAP Services Partner specialising in Supply Chain Management (SCM), User Experience (UX) and Application Lifecycle Management (ALM), today announced a merger with QualIT, a consultancy specialising in SAP Product Lifecycle Management (PLM) solutions.
One of the major challenges of software development is managing complexity. A common way of reducing some of the complexity of a codebase is to separate the code into different files based on what the code does. In this way, you could have a file that contains your utility functions, a file for each of your classes etc.
SAP UI5 has a very convenient and robust mechanism for doing two-way binding of your data from you data layer (the model) to your presentation layer (the view). By using data binding you are effectively separating the concerns of your application. In an ideal world you want your model code to only be responsible for your data and your presentation code to only be responsible for the way the data is displayed.
Building web applications using the MVC architecture helps with separating concerns and keeping the application modular. In an ideal application every module has only a single responsibility. Model View Controller architecture advocates breaking an application up into three groups that are logically separated.