Shulou(Shulou.com)06/02 Report--

Because the enterprise portal technology is unfamiliar to most enterprises or users, the working method of the enterprise portal project is different from the traditional project. Two methods are usually used in the actual implementation.

First, the prototype modeling method. Namely: build a HTML version of the interface and operation prototype, guide users to try the operation, find problems in the operation, and then continue to improve. Note: in the process of implementing this method, many project teams have been lazy, so it is not advisable to use JPG static images instead of operation prototypes. Portal technology is unfamiliar to users, and simply using a few static pictures can not guide users' real thoughts at all. When the project development is almost done, the user will not find the problem until the trial, so many project teams complain that the portal project is difficult to do because of the changeable needs of users. In fact, it is not that the user needs are changeable, but that the user needs are not guided from the very beginning. This article will introduce the prototype modeling method of portal system in detail.

Second, the requirements use case. In general, people think that writing requirements use cases is a complex task, so this method of requirements research should only be used for large projects. Wrong! The function points in the portal are inherently complicated, and if you don't have a clear definition of the use case specification, the user will not be able to understand your requirements description at all. There is no doubt that without the use case specification, you will not get the real needs of the user at all. This article describes in detail how to use the requirements use case specification approach to write a user requirements description of a portal project.

In addition, the portal project involves an unprecedented number of departments, leaders and users, and no project can involve almost everyone in the enterprise like the portal. so the organization of the enterprise portal project requirements survey phase tests the ability of a project team very much. This paper will focus on how to organize the demand research of the portal project in an orderly manner, so that the project team can complete the demand research phase quickly, orderly, quality and quantity, get the user's needs accurately, avoid later demand changes, and reduce project risks. improve the implementation quality of the portal project.

As we all know, many software projects, especially large-scale integrated projects, involve many departments, many application systems, many databases, and various requirements, so demand research and confirmation are very important, and even directly determine the success or failure of the whole project.

In order to thoroughly understand the needs and confirm the needs of users, after years of accumulation, we have summed up one, two, three, as shown in figure 1-1.

Figure 1-1 the core ideas and ideas adhered to in the project demand research phase

A core.

A core idea means that when we consider the needs, we should not only use the system as a user, but also put aside other conflicts of interest, for example, no one should worry about guiding and expanding the needs of users. are you increasing your workload? In my opinion, the interests of users come first, and the technical changes brought about by the expansion of requirements are always not a problem. If we pay a little more now, we can add a lot of fun to users in the future.

Two basic principles

The first basic principle is to focus on the concerns of the most critical users. If it is not the problem that users care about and need us to solve, no matter how much energy is invested, the result will be twice the result with half the effort, and our efficiency is closely related to the cost of users. We focus on the problems that users are most concerned about, the things that users have the most headache, and the problems that users need us to solve most, which is to save our costs, but also to save users' costs. A project team that emphasizes efficiency and cost is believed to be needed by all users.

The second basic principle is to change the user's "I want" to "what I need". In some projects with complex requirements, especially in large-scale portal integration projects, users often do not express their software requirements clearly, and they can only talk about what they want from their own business point of view. but what they want is still a long way from the real software requirements and design. We need to use a lot of project experience to express what the user wants clearly, and then convert it into software requirements, and make a system prototype to confirm to the user. After users use the system prototype and make comments, we modify the requirement understanding and system model, and iterate the requirement description. After many rounds and multi-level requirements iteration, after making each user satisfied, we can basically understand and grasp the real needs of users to the greatest extent, and ensure that the design work of the next stage of the software is close to the actual needs of users. so as to ensure the success of the whole project.

Three basic methods

The first basic method is the prototype modeling iteration technique.

The second basic method is the requirements research method based on the use case specification.

The third method is to have enough users to participate and train.

The above three methods are described in detail below.

Prototype Modeling method of Portal

System requirements modeling means that various scenarios generated according to the use case specification are integrated into an integrated requirement description, and the user interaction interface designer (artist) makes a full and accurate HTML version of the system simulation, and then asks the user to try to use it. This kind of prototype modeling is higher than the traditional interface design, and even higher than the effect drawing. It is close to the system that the user finally uses to the greatest extent, and helps the user to understand and understand the system function in the future, and puts forward the operation points that do not meet the requirements in time.

This section describes how to develop a requirements guidance and functional validation model using the Portal modeling tool. The purpose of this model is to inspire users' thinking and guide users' requirements, and then to confirm functional requirements after many rounds of correction and optimization.

This requires a plug-in to be installed in Eclipse, and after the installation is complete, start Eclipse and perform the following steps.

① creates a project, as shown in figure 1-2.

Figure 1-2 create the project

② selects the project type as: Portal model project, as shown in figure 1-3.

Figure 1-3 Select the project type

③ is named for the Portal prototype modeling project, as shown in figure 1-4.

Figure 1-4 names the Portal prototype modeling project.

④ defines the first role: the anonymous user group, as shown in figure 1-5.

Figure 1-5 defines the first role

⑤ creates additional roles, each representing a user group with independent permissions, such as finance department user group, human resources department user group, group leader user group, and so on, as shown in figure 1-6.

Figure 1-6 create additional roles

⑥ enters the attributes for the role and creates more roles, as shown in figure 1-7.

Figure 1-7 enter role attributes

⑦ creates level 1, level 2, and level 3 navigation menus for each character. Place is the first-level menu, Page is the second-level menu, and Subpage is the third-level menu, as shown in figure 1-8.

⑧ finds and copies each Portlet from the navigation bar on the left, as shown in figure 1-9.

Figure 1-8 create navigation menus for each role

Figure 1-9 copy Portlet

⑨ uses HTML syntax and XML syntax (xlst) to write content for each Portlet, as shown in figures 1-10. Support for text, tables, pictures, JavaScript events, etc., pages or pages can have complex logic.

Figure 1-10 Writing content for each Portlet

⑩ lays out the pages for each role, emitting Portlet, as shown in figure 1-11. Panel is the column, and several Panel are arranged on each page. Specify a name and Portlet source code package for each Portlet.

Figure 1-11 arranges the layout and discharges Portlet

⑪ compiles the project under the focus of the wem file, as shown in figure 1-12.

Figure 1-12 Editing the project

⑫ opens or copies the output folder and clicks index.htm to open the prototype. The default interface is for all roles, as shown in figure 1-13.

⑬ selects the role to use and goes to the choreography page for that role, as shown in figure 1-14.

Figure 1-13 prototype interface

Figure 1-14 goes to the choreography page

To enhance the demo, ⑭ can add a batch file named start Demo. Bat, as shown in figure 1-15.

Figure 1-15 contents of batch files

Let the users try the model, put forward their opinions, iterate and optimize the model many times according to the users' opinions, until it is thoroughly approved by the users.

At this point, the prototype modeling is complete. Combined with the use case specification writing described in the next section, let the user know very clearly what you want to design the portal system to look like, in order to reach a consensus.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.