M2000 Documentation Improvements

7/28/2019 M2000 Documentation Improvements

1/13

www.huawei.com

Introduction to Wireless Documentation

Improvements-M2000Documentation Dept, WN

2013-03


2/13

Page 2

Customer voice:

Please provide feature description documentation.

Action: The feature description documents circled by red lines have been added.

The documents describe the feature overview and implementation principles.

Value:Users can learn about the feature overview and principles from these feature description documents.

Implemented in: M2000 V200R013C00

New Feature Descriptions in Feature Documentation


3/13

Page 3

Customer voice:

Software management descriptions should be scenario-based. Redundant descriptions need to be removed.

Action: End-to-end upgrade-related descriptions are integrated by upgrade mode based on the upgrade scenario.

Value:Operation guide to the end-to-end upgrade is now scenario-based.


Operation Guide Optimization Software Management (1)


4/13

Page 4

Customer voice:Software management descriptions should be scenario-based. Redundant descriptions need to be

removed.

Action: Redundant descriptions have been removed. A table is now used to illustrate the related operations and differences

between the operations.

Value:Redundant information has been pruned. The information is now provided in a reader-friendly manner.


Operation Guide Optimization Software Management (2)


5/13

Page 5

Customer voice:

The authorization-related descriptions are not scenario-based. The authorization-related descriptions are closely

related to security concepts, and therefore readers may have difficulties in understanding them. It will help readers

better understand if the meanings of each tab page on the GUI can be explained.

Action:

1. The GUI for user management is optimized. The authorization-related descriptions are scenario-based.

2. Examples of the common authorization scenarios are given in the documentation.

3. The security concepts are described in sequence according to the authorization process. The main GUI for

authorization are also described.

Value:The authorization-related descriptions are now scenario-based, which helps readers better understand them.


Operation Guide Optimization User Management

3

2

1


6/13

Page 6

Customer voice:

The descriptions are wordy, which reduces the readability of the documentation.

Action:

Figures, instead of words, are now used to illustrate the related operations.

Value:

The figures improve the readability of the documentation and provide better guidance for users.


Operation Guide Optimization Plug and Play (PNP) (1)


7/13

Page 7

Customer voice:

We hope to learn about the main application scenarios of this function and the related operations.

Action:

The main application scenarios are now described. The related operations are provided based on the scenarios.

The commissioning guides for each radio access technology (RAT) are now normalized by function, and therefore only

one commissioning guide is needed. Redundant information has been removed.

Value:

The optimization improves the readability of the documentation and provides better guidance for users.


Operation Guide Optimization Plug and Play (PNP) (2)


8/13

Page 8

Customer voice:We hope to learn about the main application scenarios of this function and the related operations.

Action:

The main application scenarios are now described. The related operations are provided based on the scenarios.


Value:

The optimization improves the readability of the documentation and provides better guidance for users.


Operation Guide Optimization NodeB License Management


9/13

Page 9

Customer voice:

The FARS-related descriptions should be scenario-based.

Action:

The FARS-related operations are no longer sorted by RAT, but by task type. The task types are trace and monitoring.

The end-to-end operation procedures are provided for each task type.


Value:

The FARS-related descriptions are now scenario-based, which provides better guidance for users.


Operation Guide Optimization FARS


10/13

Page 10

Customer voice:

It would be better to preinstall the M2000 server software on the PC server.

Action:The PC server is preinstalled with the M2000 server software so that users do not need to install the software onsite.

If exceptions occur, users can refer to the FAQs in M2000 Commissioning Guide (x3850&x3650, SUSE10, Sybase).

Value:FAQs are sorted by application scenario so that readers can easily locate the FAQ they need.


Preinstalled M2000 Server Software on the PC Server


11/13

Page 11

Customer voice:License changes and user rights changes were not provided in M2000 V200R012. Please provide them in M2000

V200R013C00.

Please provide a comparison between menus in the traditional and application styles.

Action:

License changes, user rights changes, and the comparison between the menus in the traditional and application

styles are now provided.

Value:Users can now learn about the license changes and user rights changes.

Users can now learn about the changes in menus in traditional and application styles.


Differences in Documents Between R012 and R013


12/13

Page 12

Customer voice:

The M2000 obtains the configuration file of each NE and the M2000 from the mediation and resolves

configuration file. Therefore, users can obtain the M2000 and NE product documentation on the GUI.

Action:

Users can choose Help > Obtain Documentation List to obtain the M2000 and NE product documentation.

Value:

Users can now easily obtain the M2000 and NE product documentation.


Obtaining M2000 and NE Documentation on the GUI


13/13

Thank youwww.huawei.com

One Documentation, One Satisfaction