Abstract
The article considers a classification for validation and quality assessment of the user interface (UI) from the point of view of the main aspects of design and its application in the development of web-applications. The problem with inaccurately crafted user interface requirements is relevant and as a result, developers often have to redesign the interface and architecture of the application. The article analyzes the role and place of UI in the architecture of client-server applications, analyzes aspects of UI design, on the basis of which the classification is formed. The classification is used to analyze UI design oversights of the developed web-applications for BPMS “Fireproof Corporation” company. Based on the results of UI validation, a set of typical UI design oversights has been added.
Highlights
There is a problem with inaccurately crafted user interface requirements according to business analytics data
Developers often have to redesign the interface and architecture of the application. To make this process manageable, it is logical to propose a classification of common UI design oversights, on the basis of which the user interface is validated, assessed the quality of the UI and to anticipate design oversights at an early stage
The classification is based on the main aspects [1, 6] of the user interface design, it determines the frequency of occurrence of this oversight, the impact of the oversight on the work with the system and the design phase at which this oversight occurred
Summary
There is a problem with inaccurately crafted user interface requirements according to business analytics data. There is the greatest uncertainty regarding the behavior component, caused by the diversity of points of view on this component and its implementations in different models and patterns Associated with it are terms such as use case, controller, scenario, view model, which are related to both architectural solutions and systems analytics. The business scenario is implemented as a trajectory (dotted lines on Figure 1) in the user interface of the application (the sequence of opening forms and actions with controls);. The components of the user interface in the form of architectural classes do not contain elements of behavior (scenario), are separated from the components that determine the behavior, and interact with them through the interfaces of events and actions - the MVP pattern;. The view scenario is implemented by a separate component (controller, representative), has its own state (behavior model) and uses business entities (business objects) of the model in accordance with their states.
Sign-in/Register to view highlights & summary Talk to us
Join us for a 30 min session where you can share your feedback and ask us any queries you have
Schedule a callDisclaimer: All third-party content on this website/platform is and will remain the property of their respective owners and is provided on "as is" basis without any warranties, express or implied. Use of third-party content does not indicate any affiliation, sponsorship with or endorsement by them. Any references to third-party content is to identify the corresponding services and shall be considered fair use under The CopyrightLaw.
