GUI – graphic user interface
There are several tools with which designers can create the entire graphic interface with one mouse click. Some tools can be built into the software environment (IDE).
GUI implementation tools provide a powerful array of GUI controls. To configure software, designers can change the code accordingly.
There are different segments of tools with a graphic interface depending on their use and platform.
example
Mobile graphic interface, computer graphic interface, sensory graphic interface, etc. Here is a list of several tools that will come in handy to create a graphic interface:
Liquids
Appinventor (Android)
Lucidchart
Wavemaker
Visual Studio
User interface Golden Rules
The following rules are mentioned as gold rules for the design of the GUI described by SHNEIDERMAN and PLAISANT in their book (user interface design).
Strive for sequence – in such situations there should be consistent sequences of actions. The same terminology should be used in hints, menu and reference screens. Consistent commands should be used everywhere.
Allow frequent users to use shortcuts. The user’s desire to reduce the amount of interactions increases with the frequency of use. Contractions, functional keys, hidden commands and macro means are very useful for an experienced user.
Provide informative feedback – for each operator’s action there must be some system feedback. For frequent and minor actions, the answer should be modest, while for infrequent and large actions the answer should be more significant.
The design dialog box in order to ensure closing – the sequence of actions must be organized into groups with the beginning, middle and end. Informative feedback at the end of the group of actions gives the operators to satisfy the execution, a sense of relief, a signal of the rejection of plans in case of unforeseen circumstances and options for their thoughts, and this indicates that the path to the future is clear to prepare for the next group of actions.
Offer a simple error processing – if possible, design the system so that the user does not make a serious mistake. If the error is made, the system should be able to detect it and offer simple, understandable mechanisms for processing error.
Allow an easy cancellation of actions – this function relieves anxiety, because the user knows that errors can be canceled. A slight change in actions stimulates the study of unfamiliar options. Units of reversibility can be one action, data entry or a complete group of actions.
Support for the internal locus of control. Experienced operators really want to feel that they are responsible for the system and that the system is responding to their actions. Develop the system so that users become initiators of action, not respondents.
Reduce the short -term load for memory. The restriction of the processing of human information in short -term memory requires that the displays are simple, multi -page displays are consolidated, the speed of the window is reduced and sufficient training time for codes, mnemonics, and sequence of actions are distinguished.
GUI implementation tools
There are several tools with which designers can create the entire graphic interface with one mouse click. Some tools can be built into the software environment (IDE).
GUI implementation tools provide a powerful array of GUI controls. To configure software, designers can change the code accordingly.
There are different segments of tools with a graphic interface depending on their use and platform.
example
Mobile graphic interface, computer graphic interface, sensory graphic interface, etc. Here is a list of several tools that will come in handy to create a graphic interface:
Holstead complexity measures
In 1977, Mr. Maurice Howard Holsted presented metric to measure the complexity of software. Holsteda metrics depend on the actual implementation of the program and its measures, which are calculated directly from operators and operands from the source code in a static way. This allows you to evaluate the test time, vocabulary, size, complexity, errors and efforts for the source code C / C ++ / Java.
According to Holstead, “a computer program is the implementation of an algorithm that is considered a set of tokens, which can be classified as operators or operand.” Holstead metric considers the program as a sequence of operators and the associated operands.
It defines various indicators to check the complexity of the module.
Parameter referring in mind
N1 The number of unique operators
N2 Number of unique operands
N1 The number of the general appearance of operators
N2 the number of the general appearance of operands
When we select the source file to view the details of its complexity in Metric Viewer, the following result appears in Metric Report:
Identification and tracking – includes actions related to the identification of the requirements of modification or maintenance. It is generated by the user or the system itself can report through magazines or error messages. The type of service is also classified here.
Analysis – modification is analyzed for its impact on the system, including consequences for security. If the probable impact is serious, an alternative solution is looking for. The set of necessary modifications is then materialized in the specification of requirements. The cost of modification / maintenance is analyzed and the assessment is completed.
Design. New modules that need to be replaced or modified are developed taking into account the requirements established at the previous stage. Control examples are created for verification and confirmation.
Implementation. New modules are encoded using a structured project created at the design stage. It is assumed that each programmer will perform modular testing in parallel.
System testing – integration testing is carried out among newly created modules. Integration testing is also carried out between new modules and the system. Finally, the system is tested in general, following the regressive testing procedures.
Accepting testing. After internal testing, the system is checked for reception using users. If the user is in this state, he complains about some problems that he solves or notes to solve in the next iteration.
Delivery – after acceptance testing, the system unfolds throughout the organization using a small package of updates or a new installation of the system. The final testing is carried out on the side of the client after the delivery of software.
The training center is provided, if necessary, in addition to the printed user manual.
Maintenance management. Configuration management is an integral part of the system maintenance. This helps to control versions control versions, semi-versions or corrections.