Software Interface Modeling Analysis)

Analysis of Software Interface Modeling

 

In qingrun's full-Process Modeling implementation of software engineering, the paper proposes to use interface design as a task in the need analysis stage. I used to perform interface modeling in the demand analysis phase, and communicated with users using the interface model, achieving good results. Interface modeling is an important step in requirement work and also part of the design work. Many people argue about the time at which interface modeling should begin. I agree that the interface modeling should be placed in the requirement analysis stage. On the one hand, the requirement of the software interface is also part of the user requirement, and on the other hand, the functional requirements of the interface model and the user communication system are intuitive and clear, it is easy for users to understand. The interface combines a previously developed project to talk about software interface modeling.

1Interface Design Requirements

• The interface design should fully reflect the expression of user requirements.
• The interface design should be elegant and elegant. Generally, the results of the interface design should conform to the user group's habits, senses, and feelings.
• The interactive operation process in the interface design must conform to the user's habitual work process.

2Main Work of interface Modeling

First, determine the interface elements. Generally, the elements of a software interface include the main color, font color, font size, interface layout, interface interaction mode, interface function distribution, and interface input and output mode. Elements that have a significant impact on user productivity include: input/output mode, interaction mode, and function distribution. The interface elements are designed to give end users an aesthetic, improve work efficiency, and make the system easy to use. The work of this project is completed by the interface designer in collaboration with the artist and determined in the form of interface design specifications.

Thirdly, we need to propose some designs for users based on our understanding of the software background, industry characteristics, user usage level, and preferences. Considering that the users of this system are in the highway industry and the computer application level is relatively low, many parts strive to be concise and clear, and provide user operation and use convenience as much as possible, in many places, try to simulate users' manual operations to meet their usage habits. For example, you can use a workflow to deploy a function in the function layout mode, so that the user can clearly understand what to do next after completing this work. In addition, we specially designed the data input interface to be exactly the same as the table in the user's actual work.

Finally, the user interface model is created and interacted with the user. This work is very important for interface modeling, because the user's requirements for functions are relatively clear, but the requirements for interfaces are vague, however, when a system is presented to them, they have many requirements and ideas. Through this work, users can find out their requirements for the interface, it is also easy to expose design defects. After designing the interface model, we invited the user to participate in our review, and then modified the interface model based on the user's opinions.

3, Modeling tools

I chose Visio as the interface modeling tool. Visio is a Microsoft chart rendering software. The Visio mold provides Windows interface elements and various annotation elements, so that we can easily create a Windows user interface model. In addition, Visio provides a better publishing function that allows us to publish a Visio Document as a webpage. Because UML does not support interface modeling well, it is difficult to use UML modeling tools for interface modeling.

4Interface model example

This system uses Visio to express the layout, function distribution, and interaction of interface elements. For some content that cannot be expressed in this model (such as the font size) use the interface design specifications for presentation. We use this model to communicate with users in the early stage to help testers understand system functions. In the later stage, the interface layer overlays the call to the business layer in the interface model, that is, the interface model specifies under what circumstances the method of the object to be called to implement user requests, this guides developers to build a system. In this way, it is similar to the Dynamic Modeling Mechanism of UML in some aspects, and it is more intuitive and effective.

 

Figure 1 Main Interface

Figure 2 Management User Interface

 

Figure 3 overlay the Management User Interface