![](bg9.png)
intensive physical workshop. This forms the backlog
forms on which an agile tool development approach
is then carried out based on teams both in Europe and
China. Important milestones are typically set every
month and the common sprint duration is one week.
Open and Evolutive Solutions. Chinese compa-
nies are fast paced with constant tooling evolution.
In any long term project, the software environment
will change for sure and it is thus important to build
on solutions that have a big adaptation capability. At
some point, it may also be necessary to consider start-
ing on new grounds and let a past solution aside. In
our case, at some point we moved from a desktop-
centric tooling to a web-based tooling because desk-
top centric tooling could not cope with key needs
of scalability, flexible multi-user and ease of deploy-
ment/integration/maintenance. A major improvement
in the process was the definition of powerful integra-
tion interfaces for third party tools.
Paying Attention to Usability was a major con-
cern. Software engineering tools should pay great at-
tention about an efficient way to communicate all rel-
evant information to the user. They should also pro-
vide efficient ways to conduct frequent operations by
minimising the number of steps to trigger them and
enable some form of batch processing.
7 CONCLUSION
In this paper, we reported on the ongoing process at
Huawei to deploy Goal-Oriented Requirements En-
gineering in cooperation with other methods with
an important focus on building a globally efficient
and effective toolchain. This joint work is a cross-
fertilisation at different levels. It was a meeting
point between industrial needs and researchers views,
as well as a transcontinental cooperation between
Westerners and Easterners who could gather differ-
ent views on requirements engineering and the whole
software development process. This rich collabora-
tion was the source of many innovative work, often
triggered by the need to provide simple yet powerful
tools based on sound methodological grounds. So, we
believe the reported work can be valuable both for the
industrial point of view and for triggering more ap-
plied research as we tried to abstract away from the
specific case and identify different areas of concern
both at the method and tool levels.
Based on the work achieved, strong foundations
are available, most of work ahead related to complet-
ing integration with specific tools, support specific in-
teroperability standard but also less technical yet very
important tasks such as the preparation of model tem-
plates, tutorials, guidelines that will ease the transi-
tion to the new platform and foster its adoption by
users. So far, the approach has been applied on a few
pilots. Hence, it is not yet possible to quantify the
gain in quality and productivity of introducing GORE
at a large scale. The deployment phase is expected to
progressively roll out across this year and will offer
the opportunity to gather valuable material about the
benefits and limits of the approach.
ACKNOWLEDGEMENT
Warm thanks to Zhang Wei, Liu Zhipeng, Yang Yang
(Davin), Lin Zhi Qiang (James), Wang Jianan (John)
for their great support for the method and tool de-
ployment at Huawei Limited in Shenzhen and across
China.
REFERENCES
Adzic, G. (2011). Specification by Example: How Success-
ful Teams Deliver the Right Software. Manning Pub-
lications Co., Greenwich, CT, USA, 1st edition.
Amyot, D. and Mussbacher, G. (2011). User requirements
notation: The first ten years, the next ten years. JSW,
6(5):747–768.
Atlantic Guild (2014). Volere Requirements Specifica-
tion Template - Edition 17. http://www.volere.co.
uk/template.htm.
Cockburn, A. (2000). Writing Effective Use Cases.
Addison-Wesley Longman Publishing Co., Inc.,
Boston, MA, USA, 1st edition.
Cohn, M. (2004). User Stories Applied: For Agile Software
Development. Addison Wesley Longman Publishing
Co., Inc., Redwood City, CA, USA.
Cresswell, J. (2011). Gherkins. https://github.com/ cucum-
ber/cucumber/wiki/Gherkin.
Dardenne, A., van Lamsweerde, A., and Fickas, S. (1993).
Goal-directed requirements acquisition. Sci. Comput.
Program., 20(1-2):3–50.
Fast Company (2016). Huawei Ranked Among
the World’s 50 Most Innovative Companies.
http://www.fastcompany.com/company/huawei.
Group, S. (2015). 2015 CHAOS Report. http://www. stan-
dishgroup.com.
Hughes, D. L. et al. (2015). Success and Failure of IS/IT
Projects: A State of the Art Analysis and Future Di-
rections. Springer Int. Publishing.
International Telecommunication Union (2012). Recom-
mendation Z.151 (10/12), User Requirements Nota-
tion (URN) Language Def.
Majchrowski, A., Ponsard, C., Saadaoui, S., Flamand, J.,
and Deprez, J.-C. (2015). Software Development
Practices in Small Entities : an ISO29110-based Sur-
vey. In Proc. EuroAsiaSPI 2015.
ICSOFT 2017 - 12th International Conference on Software Technologies
380