Business to System Requirements Agile Mapping

Malgorzata Pankowska

Department of Informatics, University of Economics in Katowice, 1 Maja, Katowice, Poland

Keywords: Business Requirement, System Requirement, Requirement Diagram, SysML, Archimate.

Abstract: Business and Information Technology (IT) alignment methods and models have been developed for the last

few years. Mainly, they focus on strategic alignment, however, the misunderstanding and lack of alignment

are hidden in requirement mapping methods, tools, and approaches. Therefore, the paper aim is to present a

model of business to system requirements mapping, based on the application of SysML and ArchiMate

diagrams. The proposed approach is assumed to be considered as agile, because of its features. Finally, the

approach is supported by online store case study. Beyond that, systematic literature review was done on

SysML requirements engineering.

1 INTRODUCTION

Business requirements and IT requirements are

accepted as aligned, if the IT functions are

implemented to achieve business objectives.

According to Mekawy et al. (2009), business – IT

alignment is an ongoing process. However, this

process is not only to be considered on strategic level,

because each business change requires alignment

considerations on the operational level. The purpose

of this paper is not to evaluate the strategic alignment

models, but to focus on the operationalization of the

business – IT alignment (BITA). Therefore, the

structure of the paper covers at first the discussion on

System Modeling Language (SysML) requirement

engineering. Next, systematic literature review (SLR)

results are presented to reveal what requirement

modeling languages, challenges, paradigms, and

domain applications are included in literature.

Finally, author presents an approach of mapping of

business to system requirements and justifies the need

to apply the agile principles and techniques in the

proposed approach.

2 BITA OPERATIONALIZATION

IT alignment with business goals is considered as a

critical success factor for private companies as well

https://orcid.org/0000-0001-8660-606X

as for administrative sector units. As organizations

cope with rapid changes in their business and IT

environments, they need models and measures of

BITA, e.g., Strategic Alignment Model (SAM),

Integrated Architecture Framework (IAF),

Luftman’s Alignment Model (LAM), Reich and

Benbasat Model (RBM), Sabherwal and Chan

Alignment Model (SCAM), Hu Huang Alignment

Model (HHAM) (Mekawy et al.,2009). The main

problem is that models present high level discussions

on BITA. Similarly, de Haes and van Grembergen

(2009) have considered the impact of Enterprise

Governance of IT on BITA on a strategic level, but

BITA modeling requires further operationalization

for business success. The operationalization covers

the development and application of specific methods,

languages and tools. According to Delligatti (2014)

there are many useful languages and notations, i.e.,

Service oriented architecture Modeling Language

(SoaML), Business Process Modeling Notation

(BPMN), or visual modeling standards, e.g., Unified

Profile for DoDAF/MODAF (UPDM) to support the

development of system architecture, Semantics of

Business Vocabulary and Business Rules (SBUR)

specification, or Business Motivation Model (BMM).

In this paper, SysML is considered as a profile of

the UML language to integrate many views of

systems engineering, not only hardware and software,

but also requirements, mathematical parametrization,

facilities management, and designing for

Pankowska, M.

Business to System Requirements Agile Mapping.

DOI: 10.5220/0009823600370048

In Proceedings of the 17th International Joint Conference on e-Business and Telecommunications (ICETE 2020) - Volume 3: ICE-B, pages 37-48

ISBN: 978-989-758-447-3

maintenance. The purpose of this paper is to present

that SysML is a graphical modeling language to

communicate the design of socio-technical systems of

different scales and applications. According to the

ISO/IEC 19514:2017 standard, SysML is a general

purpose modeling language for systems engineering,

i.e., for the specification, analysis, design,

verification, and validation of complex systems. For

applying SysML, the Model Based System

Engineering (MBSE) approach was developed as a

formalized application of modeling to support system

requirements elicitation and management.

Alternative to MBSE is the document-based

approach, in which system architects generate

artefacts, e.g., documents of requirements

specifications and their traceability and verification

matrices (RTVMs) manually (Delligatti, 2014).

Concurrently, according to Patton (2014), the

document-based approach offers certain advantages.

Particularly, the usage of user story is to ensure the

whole picture of business requirements. The stories

are expected to ensure sharing the understanding, and

they are supplemented by video and audio materials.

The MBSE system models cover diagrams that

present requirements, test cases, design rationale, and

their interrelationships (Friedenthal et al., 2015).

Modeling methods, tools, and SysML are the three

MBSE pillars. The SysML diagrams include

packages for requirements, behavior, structure, and

parameters. The SysML requirement diagram is used

to display text-based requirements, the relationships

among requirements, and relationships to other

SysML diagrams, i.e., use case, activity, sequence, or

parameter diagrams.

Requirement engineering and mapping

techniques for business information system design

have been developed for years, however, just SysML

is the most suitable language for requirement

analysis, because of the requirement diagram

development opportunity. The Visual Paradigm tool

is proposed to combine system requirements with

business requirements.

In the system development lifecycle, a lack of

understanding may occur during the system

conceptualization, as well as in the development

phase. There is still an open question of “why”. The

business stakeholders focus on business

requirements, which drive the business rather than the

information system. They may drive particular

aspects of IT projects or set up some constraints on

information system functionalities. The business

requirements are to be considered in the business

organization context, covering comparable systems,

user groups, formal studies, or prototypes provided to

stakeholders. They eventually need to be transformed

into system requirements. The system engineering

with SysML application concentrates on the

definition and documentation of system requirements

in the early development phase, the preparation of a

system design, and the verification of the system as to

comply with the business requirements. In this paper,

aligning business and technology is not considered as

an ongoing strategic executive responsibility, but as a

process to learn and adopt business requirements to

the SysML requirements. Therefore, the fundamental

questions, which system analysts are requested to

formulate are as follows:

 Why do people need the information system and

software functionalities?

 Which information do you owe to the people

with whom you work and on whom you depend?

In what form? In what time period? What

information is needed and from whom?

 Why is information important to compete in the

business?

 What priorities for information use and

management are important?

 When and why can information user be

satisfied?

Table 1: Findings on Agile Requirement Engineering.

No Representative

Research

Findings

1 Abdullah et al.,

2011

Using a combination of qualitative

data collection and cognitive analysis

techniques, authors termed “shared

conceptualization” for engineering

activities

2 Asghar et al.,

2017

Prioritizing requirements helps

software team to understand the

importance of a particular

requirement

3 Meligy et al.,

2018

The ethnographic analyst remains in

the organization and observes the

actual ways in which people work,

rather than only the formal

requirements documented by the

organization

4 Lorca et al.,

2018

Motivational modeling is an efficient

technique to support discussions

between developers and non-technical

clients.

5 Villamizar et

al., 2018

Agile approaches typically involve

modifying agile methods, introducing

guidelines to handle security issues.

More efforts are needed for empirical

evaluations

The answers trigger business activities and explain

the motivations and constraints that determine how the

information system is designed. Managers usually

need information for achieving the following goals:

risk management, cost reduction, value adding, better

ICE-B 2020 - 17th International Conference on e-Business

market position, eliminating the competitors, or

creating new reality (Marchand, 2000).

The above questions are also valid in agile

approach to the mobile business application

development. Agile methods are expected to focus on

the justification of business application development,

not only on providing the functionalities in a short

product design cycle. Therefore, the agile

requirement engineering is a process of analysis of

stakeholders, recognition of the system context,

requirement elicitation, documenting, evaluation, and

management, and business to system requirements

mapping in an incremental and iterative manner

(Cuesta, 2019). Table 1 includes illustrious papers on

agile requirement engineering, wherein authors

emphasize the benefits of agile method application.

However, they focus on requirements conceptuali-

zation, traceability analysis, transformation into

software components, and implementation. So, they do

not accentuate any particular tools nor languages for

that requirement engineering process.

Agile methods are nowadays developed and

applied in different business management domains.

Among others, they are very popular in information

technology (IT) project management domain, in

which they are oriented towards successful fulfilment

of users’ requirements in short time. The issue of

combining of requirement engineering and project

management methods is considered by Lampa et al.

(2017). They focus strictly on linking project scope

engineering and requirements engineering.

In this paper, the system context, stakeholders,

principles, constraints, and regulation politics are

assumed to be modelled in ArchiMate language and

further the business requirements are mapped into

SysML requirement diagram. The document-based

approach and MBSE are proposed as the most

suitable for e-business system analysis and design.

3 LITERATURE REVIEW

Systematic literature review (SLR) is accepted as a

research method and a means for evaluating and

interpreting all the available studies that are relevant

to a particular research questions and topic areas. The

SLR, which was conducted this year revealed the

constraining and enabling factors of requirement

mapping. The SLR research was realized in 2 phases,

depending on the questions, formulated as follows:

RQ1: Requirement Mapping

RQ2: SysML Requirement

In the repositories, i.e., Association for

Information Systems electronic Library (AISeLib),

IEEE Xplore, SAGE Journals, Science Direct, and

Scopus, overall 246 945 publications were found on

Requirement AND Mapping (Table 2).

Table 2: Requirement Mapping Publications in 2009-2020

(absolute values).

AISeLib IEEE

Xplore

SAGE

journals

Science

Direct

Scopus

2009 654 461 5517 7450 906

2010 589 516 5829 7355 980

2011 545 549 6200 8387 1073

2012 535 512 6425 9222 1138

2013 557 517 6983 10422 1138

2014 543 560 7041 11305 1148

2015 647 475 7250 12482 1159

2016 645 600 7485 13028 1201

2017 868 593 7933 14411 1252

2018 848 677 8603 16068 1378

2019 666 684 13335 18783 1333

2020 26 2 2257 7086 113

Unfortunately, they are not strictly on business to

system requirements mapping (BSRM), because in

literature, mapping is understood as reviewing.

However, some of the found publications are

important for BSRM activities. Kalbach (2016)

argues that experiences mapping for BITA should

respect the principles of holistic approach,

multiplicity aspects, visualization, validity, and

relevance. These principles, although proposed for

experience mapping, are applicable for business

requirement understanding and mapping into system

requirements. Kop and Mayer (2012) proposed an

approach that provided mechanisms for an automatic

transformation of natural language requirements’

specifications into UML or other conceptual

languages specifications. Motta and Pignatelli (2010)

discussed a proposed method that mapped strategic

enterprise information into system conceptual

information. Paper written by Wolny et al. (2020)

seems to be important to answer question on SysML

requirements (RQ2). Authors analyzed SysML

publications in 2005-2017. They have noticed that

language was used for design and validation, but not

for implementation. They found requirement

diagram, parametric and block diagrams, and activity

and state machine diagrams as frequently used. Their

research question was similar to the research question

formulated in this paper, i.e., on SysML requirement.

In the second SLR, the focus was on solutions that are

either novel or a significant extension of existing

techniques.

Table 3 includes the numbers of searching results

in repositories, i.e., AIS eLib, IEEE Xplore, SAGE

journals, Science Direct, Scopus, and Web of Science

(WoS). In general, 2133 publications were found.

Business to System Requirements Agile Mapping

Table 3: SysML Requirement Publications in 2009-2020

(absolute values).

AIS

eLib

IEEE

Xplore

SAGE

journals

Science

Direct

Scopus WoS

2009 1 7 4 11 25 19

2010 2 17 1 14 51 25

2011 2 13 1 29 55 22

2012 1 15 5 66 64 23

2013 1 18 5 76 62 33

2014 1 21 6 111 70 46

2015 1 26 6 117 56 44

2016 1 20 5 93 61 51

2017 5 24 5 85 64 41

2018 4 27 10 89 73 42

2019 5 25 11 94 62 35

2020 1 1 1 19 5 1

Table 2 data is before deduplication and

standardization. In Figures 1 and 3, linear graphs

present the standardized number of publications.

The standardization was done in the following

way (1): assuming that i=1…6, i=repository number,

t=1…12, t=year

/AVG (x

) (1)

The SLR was done at the beginning of 2020, so

publications of 2020 are not included in Figure 1 nor

in Figure 2. The searching results are usually poor at

beginning of a year, because of their infinitesimal

quantities.

Figure 1: Requirement Mapping publications in 2009-2019

(standardized values).

Taking to account values in Figure 1, the

exponential increase of publication numbers has been

noticed, particularly for publications of Science

Direct, SAGE journals, and IEEE Xplore repositories.

The AIS eLibrary (AIS eLib) has registered less

publications in 2019 than in 2017-2018.

Figure 2: Requirement Mapping publications in 2009-2019

–legend.

Figure 3: SysML Requirement publications in 2009-2019.

Figure 4: SysML Requirement publications in 2009-2019 -

legend.

Considering values in Figure 3, in 2009-2013 an

increase of publication numbers has been noticed,

later however, no exponential increase of data was

observed. Numbers of papers from AIS eLib and from

SAGE journals repositories increase in 2016-2017.

After deduplication, papers have been grouped in

six sets and the most representative papers are

discussed below.

3.1 SysML vs. Other Languages

The first group of papers concerns the transformation

of SysML requirements and SysML diagrams

elements into elements of diagrams in other data

modeling languages.

1.5

2.0

2.5

3.0

3.5

4.0

4.5

5.0

0.0

0.5

1.0

1.5

2.0

2.5

3.0

3.5

4.0

ICE-B 2020 - 17th International Conference on e-Business

Table 4: Publications on SysML and other languages.

No Representative

Research

Findings

1 Ahmad et al.,

2012

Applying of RELAX for adaptive

systems

2 Ali et al., 2015 Internal block diagram of SysML is

translated to PRISM language

3 Amyot et al.,

2016

Combining SysML with the User

Requirements Notation (URN)

4 Anda, 2018 Proposal of goal modeling with the Goal

oriented Requirement Language and

SysML

5 Berbedienne et

al., 2015

SysML extension named TheReSe is

proposed

6 Carrillo et al.,

2014

Association of SysML requirement

diagram with atomic requirements,

represented as Linear Temporal Logic

properties

7 Chabibi et al.

2019

Integration of SysML with Simulation

Modeling Language (SimuML)

8 Chang et al.,

2014

Transformation of requirement diagrams

into other diagrams according to rules

defined by ATLAS Transformation

Language

9 Chourey &

Sharma, 2019

Development of Enhanced Functional

Flow Block Diagram (EFFBD)

10 Clegg et al,

2019

SysML Safety Profile development to

model fault trees

11 Dori, 2016 Combining Object-Process Methodology

(OPM) with SysML

12 Gaydamaka,

2019

Applicability of the ArchiMate to

support requirement engineering

13 Helming et al.,

2010

Proposal of the Unified Requirements

Modeling Language (URML) to ensure

integrity and interdisciplinary

traceability

14 Hernandez et

al., 2016

Combining SysML with process

simulation language ASPEN

15 Kanthabhabhaj

eya, 2012

Comparison of SysML and Sequence

Planner Language

16 Kapos et al.,

2014

DEVS and SysML application in system

structure description

17 Rahim et al.,

2015

Transformation of SysML activity

diagrams into modular Petri nets

18 Rebeiro et al.,

2017

UML and SysML are used together for

modeling non-functional requirements,

as well as software functionalities.

19 Roudier &

Apvrille, 2015

SysML-Sec for safety-related and

security-related functions exploration

with regard to attacks

20 Sena Marques

et al., 2014

Integration of UML, MARTE and

SysML standard notations

21 Sneps-Sneppe

et al., 2017

Proposal of Lifecycle Modeling

Language for digital economy

information modeling

22 Vidal &

Villota, 2018

SysML is coupled with Matlab and

Modelica, enabling requirements

verification

23 Zhe et al., 2018 Joint use of SysML, Architecture

Analysis and Design Language (AADL)

and Future Airborne Capability

Environment (FACE) Technical

Standard

24 Yamagishi et

al., 2014

Applying the Design Structure Matrix

clustering analysis and use of SysML

diagrams

Although SysML is applied for modeling artefacts

for designing software and hardware, researchers

combine views in SysML with other languages views.

Figure 5 presents the SysML linkages with other

languages. Explanations of the links are in Table 4.

Figure 5: SysML and other modeling languages.

3.2 SysML Research and Development

SysML application encourages many practitioners

towards research, development, and implementation

of paradigms which control and impact the use of

SysML (Table 5, Figure 6).

Table 5: Publications on SysML development paradigms.

No Representative

Research

Findings

1 Abid et al.,

2015

Combining SysML and holonic

control paradigm for system design

2 Al-Fedaghi,

2014

Offering the Flowthing Model to

capture the requirement dynamics

3 Brace &

Ekman, 2014

Checklist-oriented requirement

analysis approach presentation

CORAMOD methodology

4 Cui & Page,

2012

Combining SysML with Business

Motivation Model (BMM)

5 Hinckel et al.

2016

Applying SysML for Product

Development Process in

multidisciplinary aspect. Adoption of

the DSR principles.

6 Soares & Do

Nascimento,

2014

Application of Technology

Acceptance Model (TAM) for SysML

diagrams evaluations

7 Zingel at al.,

2012

Use of Contact & Channel Approach

(C&C2-A), MBSE and SysML for

system architecture planning

Figure 6: SysML development paradigms.

Business to System Requirements Agile Mapping

3.3 SysML Challenges

The IT involves practitioners of SysML application to

formulate new challenges. They are presented as

prototypes or as a proofs of concept in scientific

publications (Table 6, Figure 7).

Table 6: Publications on SysML challenges.

No Representative

Research

Findings

1 Alenazi et al.,

2018

Authors leverage goal-oriented

obstacle analysis to identify the

impediments to the fulfilment of

SysML requirements

2 Gardan &

Matta, 2017

Inclusion of Knowledge Management

and SysML diagrams in MBSE

3 Jakjoud et al.,

2012

Proposal of a meta-model to combine

Software Process Engineering Meta-

model (SPEM) and SysML concepts

4 Kinoshita et

al., 2014

Translation of SysML diagrams to the

abstract machine notations of the B

method

5 Kotronis et al.,

2020

A proof of concept of Level of

Service (LoS) supported by SysML

6 Lopata et al.,

2015

Enterprise Model generation process

from SysML models and Knowledge

Based Model Driven Architecture

7 Mir et al., 2011 Introduction of the Ontology for

Requirements Engineering (ORE)

compatible with SysML

8 Mori et al.,

2016

Proposal of SysML profile for

System-of-Systems (SoS) design and

its applicability in a Smart Grid

scenario

9 Nikolaidou &

Michalakelis,

2017

Focus on the financial assessment of

SysML models, estimating Total Cost

of Ownership (TCO) and Return on

Investment (ROI)

10 Tueno Fotso et

al. 2018

Authors focused on mapping

SysML/KAOS models into B System

specifications

11 Zahoor et al.,

2019

Use of Analytic Hierarchy Process

(AHP) to rank the software

requirements and to extend SysML

Requirement diagram

12 Zhang et al.,

2018

Method to combine SysML

requirement diagrams and Event-B to

model distributed system is proposed.

Figure 7: SysML Challenges.

3.4 SysML Application Domains

SysML is applied for modeling and designing

hardware as well as software. The domains of

applications are different, as it was presented in Table

7 and in Figure 8.

Table 7: Selected Papers on SysML Applications.

No Representative

Research

Findings

1 Artery &

Spain, 2011

Development of SysML model of an

integrated Product Lifecycle

Management environment

2 Durugbo, 2013 SysML requirement diagram for

product service system analysis and

verification in the automotive

industry

3 Hammad et al.,

2013

By taking into account static,

dynamic and requirement diagrams in

SysML, realization of virtual

verification of Wireless Sensor

Network energy consumption

4 Hetherinton,

2014

Implementation of the SysML

requirements model and the Blender

industrial game sample

5 Jamro, 2015 SysML is applied for modeling

communication between devices in

Distributed Control Systems and

Human Machine Interfaces

6 Lahboube et

al., 2014

SysML for complex system

modeling, e.g. Hospital Information

Systems (HIS)

7 Leserf et al.,

2015

Methodology for Embedded

Cognitive Safety System design,

using extension of SysML

8 Mahboob et

al., 2017

SysML applied for virtual product

modelling. Presentation of proof of

concept

9 Maschotta et

al., 2019

SysML graphical edition of model of

automotive and E/E systems

10 Mhenni et al.,

2014

SysML-based methodology is

proposed, including black box and

white box analysis

11 Qiao et al.,

2013

SysML for analysing the complexity

of the production management system

for complex product

12 Tsadimas,

2015

For Enterprise Information System

architecture design, SysML is applied

as a modeling language

13 Wrycza &

Marcinkowski

2011

Presentation of the authors’

experiences in system specification

relating to the SysML requirement

diagrams

Figure 8: SysML application domains.

ICE-B 2020 - 17th International Conference on e-Business

3.5 SysML Tools

Considering the SLR results on SysML Requirement

it should be noted that authors do not emphasize value

of particular modeling tools. The searching results are

included in Table 8 and in Figure 9.

Table 8: Findings on SysML Software Tools.

No Representative

Research

Applied Software Tools

1 Casse, 2017 No Magic Cameo Systems

Modeler

2 Chabibi et al. 2016 MATLAB/Simulink

3 Berrani et al., 2013 Topcased-toolkit in open source

for critical applications &

systems development

4 Cuesta, 2019 Papyrus graphical editing tool

5 Gross &

Mukherjee, 2016

MagicDraw

Figure 9: Tools for SysML use support.

3.6 SysML Specific Goals

The final group of papers includes publications,

which illustrate the most characteristic goal of SysML

application, i.e., requirement specification,

traceability, verification, validation, and modeling

contingency (Table 9, Figure 10). The system

modeling language (SysML) is preferred more for

analysis and modeling technical system than for

business information systems.

Figure 10: SysML application goals.

Table 9: SysML Application Goals.

No Representative

Research

Findings

1 Haidrar et al.,

2018

Requirement traceability throughout

system development process

2 Ribeiro et al.,

2018

Real-time systems specification,

analysis and design

3 Gauthier et al.

2015

Model Driven Engineering with

requirements validation and

verification using SysML

4 Nottage et al.,

2015

Using SysML to enhance the

collaboration with experts in the

design domain

3.7 Case Study

The SLR research results encourage to focus on the

agile requirement engineering. As it was presented in

this SLR, there are still many opportunities to use

SysML for business information system modeling.

The requirement engineering with agile methods

gives importance to the requirements as well as to

stakeholders to ensure a correct and traceable process.

By making users immerse into design process, system

analysts can acquire business needs directly from

their knowledge, behaviours, and reflections to

software products. The paper focuses on the research

gap to detect business-IT operational misalignment.

Therefore, Requirement Map is proposed to

transform ArchiMate business requirements into

SysML system requirements (Table 10).

Table 10: Requirement Map.

No ArchiMate

Business

Requirement

System

Requirements

Functional Non

Functional

Interface

1 Sales

Maximization

Sales

Registration

Access

Constraints

Order

Registration

Customer

Interface

Product

Registration

Product

Interface

Product Data

Registration

Statistics of

Orders

Data

Mining

2 Cash Flow

Sustaining

Order

Realization

Order Interface

Customer

Invoice

Creation

Freight Bill

Posting

Transport

Company

Connection

Mapping user requirements into product system

requirements is a crucial step for product design. The

agile requirements engineering is particularly

comfortable for Internet business or mobile business

application design and development, because of the

opportunity to work in a small team of stakeholders.

Face-to-face communication with end user is

absolutely necessary to collect answers on what, why

Business to System Requirements Agile Mapping

and for whom information is needed, what decisions

are made in the business process. This answers are

fundamental for business requirements specification

by analysts. They should be responsible for the

transformation of business requirements into the

system requirements. ArchiMate is a language and

tool strictly for business analyses and business

requirements specification. SysML requirement

diagram is to present the structure of system

requirements. Successfully, Visual Paradigm

modeling platform enables the usage of ArchiMate as

well as SysML.

Figure 11: ArchiMate Business Requirement.

Figure 12: SysML Requirements for Online Store.

Therefore, the business requirements specified in

ArchiMate diagram (Figure 11) are mapped into

system requirements in the SysML requirement

diagram (Figure 12). The Requirement Map in Table

10 is a static solution. Therefore, for agile approach

to requirement engineering and management agile

modeling tool is needed. The Visual Paradigm

analysis and modeling software enables detailed

specification and description of each requirements

(Figure 13).

Figure 13: SysML Requirement Specification – General

view in Visual Paradigm https://www.visual-

paradigm.com/.

In Visual Paradigm, SysML requirement diagram,

each requirement has an extendable list of

characteristics, i.e., General, Attributes, Stereotypes

(Figure 13). Beyond that, developers can add

additional artefacts, i.e., Diagrams, References,

Project Management, and Relations.

Figure 14: Class Diagram for Online Store.

Business information systems are mostly

database system, therefore additional diagrams are

developed. As it was mentioned in the SLR, the

SysML language system model can be combined with

the UML diagrams, i.e., class diagram (Figure 14) or

use case diagram (Figure 15). In SysML requirement

diagram, the use case diagram can be linked directly

to a specific requirement.

ICE-B 2020 - 17th International Conference on e-Business

Figure 15: UML Use Case Diagram included in Product

Registration requirement.

As it was presented in the SLR, researchers

combine different modeling techniques and transfer

models written in one language into another. The

example of combination of modeling techniques in

included in work done by Aparecido Nogueira and

Carvalho de Oliveira (2017). In general, the

combination of modeling techniques improves agility

of requirement engineering and management.

However, there is still a question about software tools

enabling such flexible integration.

4 CONCLUSIONS

In this study, conducting a systematic literature

review was done to investigate the practices, tools,

patterns, and goals of SysML usage and requirement

elicitation in agile context. Based on the SLR

guidelines, eventually 64 papers have been selected

for a detailed analysis. As BITA models are valid for

strategic decisions, agile requirement engineering can

be supported by languages and tools enabling the

operationalization of the business – IT alignment. In

this paper an online store ArchiMate and SysML

diagrams were discussed as useful for that

operationalization

For future work, the Decision Model Notation

(DMN) and Case Management Model and Notation

(CMMN) notations should be considered in business

requirement modeling.

REFERENCES

Abdullah, N.N.B., Honiden, S., Sharp, H., Nuseibeh, B.,

Notkin, D. 2011. Communication patterns of agile

requirements engineering. In Proceedings of the 1

Agile Requirements Engineering Workshop, AREW’11

– In Conjunction with ECOOP’11

Abid, A., Barkallah, M., Hammadi, M., Riviere, A.,

Haddar, M. 2015. Conceptual design of an intelligent

welding cell using SysML and holonic paradigms. In

Lecture Notes in Control and Information Sciences,

789, 3-10.

Ahmad, M., Bruel, J.-M., Laleau, R., Gnaho, C. 2012.

Using RELAX, SysML and KAOS for ambient systems

requirements modeling. In Procedia Computer Science,

10, 474-481.

Al-Fedaghi, S. 2014. System Design: SysML vs. Flowthing

Modeling. In International Journal of Software

Engineering and its Applications, 8(1), 355-370.

Alenazi, M., Niu, N., Wang, W., Savolainen, J. 2018. Using

obstacle analysis to support SysML-based model

testing for cyber physical systems. In Proceedings -

2018 8

International Model-Driven Requirements

Engineering Workshop, 46-55.

Ali, S., Basit-Ur-Rahim, M.A., Arif, F. 2015. Formal

Verification of Time Constraints SysML Internal Block

Diagram Using PRISM. In Proceedings 15

International Conference on Computational Science

and Its Applications, 62-66.

Amyot, D., Anda, A.A., Baslyman, M., Lessard, L., Bruel,

J.-M. 2016. Towards Improved Requirements

Engineering with SysML and the User Requirements

Notation. In Proceedings - 2016 IEEE 24

International Requirements Engineering Conference,

329-334.

Anda, A.A., 2018. Modeling Adaptive Socio-Cyber-

Physical Systems with Goals and SysML. In IEEE 26

International Requirements Engineering Conference.

Aparecido Nogueira, F., Carvalho de Oliveira, H. 2017.

Application of Heuristics in Business Process Models

to Support Software Requirements Specification. In

Proceedings of the 19th International Conference on

Enterprise Information Systems (ICEIS 2017) , Volume

2, 40-51

Artery G., Spain, M.D. 2011. Integrating the life-cycle

process utilizing SysML. In 21

Annual International

Symposium of the International Council on Systems

Engineering, 592-604.

Asghar, A.R., Tabassum, A., Bhatti, S.N., Jadi, A.M. 2017.

Impact and challenges of requirements elicitation &

prioritization in quality to agile process: Scrum as a

case scenario. In International Conference on

Communication Technologies, ComTech, 50-55.

Barbedienne, R., Penas O., Choley, J.-Y., Gasser, L. 2015.

TheReSe: SysML extension for thermal modeling. In

Annual IEEE International Systems Conference,

301-308.

Berrani, S., Hammad, A., Mountassir, H. 2013. Mapping

SysML to Modelica to validate wireless sensor

networks non-functional requirements. In Proceedings

of the 11

International Symposium on Programming

and Systems, ISPS2013, 177-186.

Brace, W., Ekman, K. 2014. CORAMOD: A checklist-

oriented model-based requirements analysis approach.

In Requirements Engineering, 19 (1), 1-26.

Carrillo, O., Chouali, S., Mountassir, H. 2014. Incremental

modeling of system architecture satisfying SysML

Business to System Requirements Agile Mapping

functional requirements. In Lecture Notes in Computer

Science, 8348 LNCS, 79-99.

Casse, O. 2017. SysML in Action with Cameo Systems

Modeler, ISTE Press, London.

Chabibi, B., Douche, A., Anwar, A., Nassar, M. 2016.

Integrating SysML with simulation environments

(Simulink) by model transformation approach. In

Proceedings – 25

IEEE International Conference on

Enabling Technologies: Infrastructure for

Collaborative Enterprises, WETICE2016, 148-150.

Chabibi, B., Nassar, M., Anwar, A. 2019. SimulML: A

DSML for simulating SysML models. In Journal of

Computing Science and Engineering, 13(1), 17-31.

Chang, C.-H., Lu, C.-W., Yang, W.P., Tsai C.-T., Hsiung,

P.-A. 2014. A SysML based requirement modeling

automatic transformation approach. In Proceedings

IEEE 38

Annual International Computers, Software

and Applications Conference Workshops, 474-479.

Chourey, V., Sharma, M. 2019. SR-UML: Quality

visualization in software design. In International

Journal of Innovative Technology and Exploring

Engineering, 8(11), 4140-4148.

Clegg, K., Li, M., Stamp, D., Grigg, A., McDermid, J.

2019. Integrating existing safety analysis into SysML.

In Lecture Notes in Computer Science, 11842 LNCS,

63-77.

Cuesta, B. 2019. Model-based approach for agile

requirements engineering using SysML and Papyrus. In

International Meeting of Technological Innovation,

Journal of Physics, Series 1257(2019) 1-8.

Cui, X., Paige, R. 2012. An integrated framework for

system/software requirements development aligning

with business motivations. In Proceedings -2012 IEEE

ACIS 11

International Conference on Computer and

Information Science, 547-552.

De Haes, S., Van Grembergen W. 2009. An Exploratory

Study into IT Governance Implementations and its

Impact on Business/IT Alignment. In Information

Systems Management, 26: 123-137.

Delligatti, L. 2014. SysML distilled, A Brief Guide to the

System Modeling Language. Addison Wesley. Upper

Saddle River.

Dori, D. 2019. Model-Based Systems Engineering with

OPM and SysML, Springer, New York.

Durugbo, C. 2013. Integrated product-service analysis

using SysML requirement diagrams. In Systems

Engineering 16(1), 111-123.

Friedenthal, S., Moore, A, Steiner, R. 2015. A Practical

Guide to SysML, The Systems Modeling Language.

Elsevier. Amsterdam.

Gardan, J., Matta, N. 2017. Enhancing knowledge

management into systems engineering through new

models in SysML. In Procedia CIRP, 60, 169-174.

Gauthier, J.-M., Bouquet, F., Hammad, A., Peureux, F.

2015. Tooled process for early validation of SysML

models using Modelica simulation. In Lecture Notes in

Computer Science, International Federation for

Information Processing, LNCS 9392, 230-237

Gaydamaka, K. 2019. ArchiMate-based approach to

requirements engineering. In International Journal of

Mathematical, Engineering and Management Sciences,

4(4), 841-850.

Gross, J., Mukherjee, R. 2016. Integrating multibody

simulations with SysML. In International Design

Engineering Technical Conferences and Computers

and Information in Engineering Conference, Vol 6,

number: V006T10A038.

Haidrar, S., Anwar, A., Roudies, O. 2018. A SysML-based

approach to manage stakeholder requirements

traceability. In Proceedings of IEEE/ACS International

Conference on Computer Systems and Applications,

202-207.

Hammad, A., Mountassir H., Chouali, S. 2013. Combining

SysML and Modelica to verify the wireless sensor

networks energy consumption. In MODELSWARD

2013 – Proceedings of the 1

International Conference

on Model-Driven Engineering and Software

Development, 198-201.

Helming J., Koegel, M., Schneider, F., Haeger, M.,

Kaminski, Ch., Bruegge, B., Berenbach, B. 2010.

Towards a Unified Requirements Modeling Language.

In Fifth International Workshop on Requirements

Engineering Visualization.

Hernandez, C., Rodriguez, M., Diaz, I., Sanz, R. 2016.

Model Based Engineering of Process Plants using

SysML. In Computer Aided Chemical Engineering, 38,

1281-1286.

Hetherinton, D. 2014. SysML requirements for training

game design. In 17

IEEE International Conference on

Intelligent Transportation Systems, 162-167.

Hinckel, E., Borsato, M., Schmidt, J., Storrer, P., Onofre,

E. 2016. Driving product design and requirement

management with SysML. In Advances in

Transdisciplinary Engineering, 4, 1071-1080.

ISO/IEC 19514:2017. Information Technology – Object

management group systems modeling language, OMG

SysML. http://www.iso.org accessed January 2020.

Jakjoud, A., Zrikem, M., Baron, C., Ayadi, A. 2012.

SysPEM: A SysML and SPEM based process

modelling language for systems engineering. In

International Journal of Services Operations and

Informatics, 7(4), 330-348.

Jamro, M. 2015. SysML modeling of functional and non-

functional requirements for IEC 61131-3 control

systems. In Advances in Intelligent Systems and

Computing, 350, 91-100.

Kalbach, J. 2016. Mapping Experiences, A Complete Guide

to Creating Value Through Journeys, blueprints and

diagrams, O’Reilly, Sebastopol,

Kanthabhabhajeya, S., Falkman, P., Lennartson, B. 2012.

System Modeling Specification in SysML and

Sequence Planner Language - Comparison Study. In

Proceedings of the 14th IFAC Symposium on

Information Control Problems in Manufacturing

Bucharest, Romania.

Kapos, G.-D., Dalakas, V., Nikolaidou, M.,

Anagnostopoulos D. 2014. An integrated framework

for automated simulation of SysML models using

DEVS. In Simulation, vol.90, 6, 717-744.

ICE-B 2020 - 17th International Conference on e-Business

Kinoshita, S., Nishimura, H., Takamura, H., Mizuguchi, D.

2014. Describing software specification by combining

SysML with the B method. In Proceedings – IEEE 25

International Symposium on Software Reliability

Engineering Workshops, 146-151.

Kop, C., Mayer, H.C. 2012. Mapping functional

requirements: From natural language to conceptual

schemata. In Proceedings of the 6

IASTED

International Conference on Software Engineering and

Applications, SEA, 82-87

Kotronis, Ch., Nikolaidou, M., Kapos, G.-D. 2020.

Employing SysML to model and explore levels-of-

service: The case of passenger comfort in railway

transportation systems. In System Engineering, Volume

23, issue 1, 82-99.

Lahboube, F., Haidrar, S., Roudies, O., Souissi, N., Adil, A.

2014. Systems of systems paradigm in a hospital

environment: Benefits for requirements elicitation

process. In International Review on Computers and

Software, 9(10), 1798-1805.

Lampa, I.L., de Godoi Contessoto, A., Amorim, A.R.,

Donega Zafalon, G.F., Valencio, C.R., Gratao de

Souza, R.C. 2017. Project Scope Management: A

Strategy Oriented to the Requirements Engineering. In

Proceedings of the 19th International Conference on

Enterprise Information Systems (ICEIS 2017), Volume

2, 370-378

Leserf, P., De Saqui-Sannes, P., Hugues, J., Chaaban, K.

2015. SysML modeling for embedded systems design

optimization: A case study. In MODELSWARD 2015 –

International Conference on Model Driven

Engineering and Software Development, 449-457.

Lopata, A., Ambraziunas, M., Veitaite, I., Masteika, S.,

Butleris, R. 2015. SysML and UML models usage in

knowledge based MDA process. In Elektronika i

Elektrotechnika, 21(2), 50-57.

Lorca, A.L., Burrows, R., Sterling, L. 2018. Teaching

motivational models in agile requirements engineering.

In Proceedings - 2018 8

International Workshop on

Requirements Engineering Education and Training,

REET, 30-39.

Mahboob, A., Weber, A., Husung, S., Liebal, A., Kromker,

H. 2017. Model based systems engineering (MBSE)

approach for configurable product use-case scenarios in

virtual environments. In Proceedings of the

International Conference on Engineering Design, 281-

290.

Marchand, D. 2000. Creating Business Value with

Information. In Competing with Information,

Marchand, D.A (ed.) John Wiley & Sons. Chichester.

17-34.

Maschotta, R., Wichmann, A., Zimmermann, A., Gruber,

K. 2019. Integrated Automotive Requirements

Engineering with a SysML-Based Domain-Specific

Language. In IEEE International Conference on

Mechatronics (ICM), volume 1. 402- 409.

Mekawy, M.E., Rusu, L., Ahmed, N. 2009. Business and IT

Alignment: An Evaluation of Strategic Alignment

Models. In Best Practices for the Knowledge Society,

Knowledge, Learning, Development and Technology

for All, Lytras M.D., Ordonez de Pablos P., Damiani E.,

Avison D., Naeve A., Horner D.G (eds.). Springer.

Berlin, Heidelberg. 447-455.

Meligy, A., Dabour, W., Farhat, A. 2018. The role of

ethnography in agile requirements analysis. In ACM

International Conference Proceedings Series, 27-31.

Mhenni, F., Choley, J.-Y., Penas, O., Plateaux, R.,

Hammadi, M. 2014. A SysML-based methodology for

mechatronic systems architectural design. In Advanced

Engineering Informatics, 28(3), 218-231.

Mir, M.S., Agarwal, N., Iqbal, K. 2011. Applied ontology

for Requirements Engineering: An approach to

semantic integration of requirements model with

system model. In Proceedings of the IASTED

International Conference on Software Engineering and

Applications, 214-221.

Mori, M., Ceccarelli, A., Lillini, P. 2016. A Holistic

Viewpoint-Based SysML Profile to Design Systems-of-

Systems. In 17

IEEE International Symposium on

High Assurance Systems Engineering, 276-283.

Motta, G., Pignatelli, G. 2010. From strategic to conceptual

enterprise information requirements: A mapping tool.

In ICEIS 2010 – Proceedings in the 12

International

Conference on Enterprise Information Systems, 440-

446.

Nikolaidou, M., Michalakelis, Ch. 2017. Techno-economic

Analysis of SysML Models. In IEEE International

Symposium on Systems Engineering, ISSE, Vienna,

Austria, 165-170.

Nottage, D., Corns, S., Soylemezoglu, A. 2015. A SysML

Framework for Modeling Contingency Basing. In

System Engineering, Volume 18, issue 2, 162-177.

Patton, J. 2014. User Story Mapping. O’Reilly Media Inc.

Sebastopol.

Qiao, D.P., Liu, X.J., Li, H. 2013.Research on SysML

based modeling for production management system. In

Advanced Materials Research, 753, 1868-1874.

Rahim, M., Hammad, A., Boukala-Ioualalen, M. 2015.

Towards the formal verification of SysML

specifications: Translation of activity diagrams into

modular Petri nets. In Proceedings- 3

International

Conference on Applied Computing and Information

Technology and 2

International Conference on

Computational Science and Intelligence, 509-516

Rebeiro, Q.A.D.S., Ribeiro, F.G.C., Soares, M.S. 2017. A

Technique to Architect Real-time Embedded Systems

with SysML and UML through Multiple Views. In

Proceedings of the 19th International Conference on

Enterprise Information Systems (ICEIS 2017), Volume

2, 287-294

Ribeiro, F.G.C., Pereira, C.E., Rettberg, A., Soares, M.S.

2018. Model-based requirements specification of real-

time systems with UML, SysML and MARTE. In

Software and Systems Modeling, 17(1), 343-361.

Roudier, Y., Apvrille, L., 2015. SysML-Sec: A model

driven approach for designing safe and secure systems.

In Proceedings 3

International Conference on Model-

Driven Engineering and Software Development, 655-

664.

Business to System Requirements Agile Mapping

Sena Marques, M.R., Siegert E., Brisolara, L. 2014.

Integrating UML, MARTE and SysML to improve

requirements specification and traceability in the

embedded domain. In Proceedings 12

IEEE

International Conference on Industrial Informatics,

176-181.

Sneps-Sneppe, M.A., Sukhomlin, V.A., Namiot, D.E. 2017.

On information models of the digital economy. In

CEUR Workshop Proceedings 2064, 367-379.

Soares, M.S., Do Nascimento, R.P.C. 2014. Evaluation of

SysML diagrams to document requirements using

TAM. In ACM International Conference Proceedings.

Tsadimas, A. 2015. Model-based enterprise information

system architectural design with SysML. In

Proceedings – International Conference on Research

Challenges in Information Science, 492-497.

Tueno Fotso, S.J., Frappier, M., Laleau, R., Mammar, A.,

Leuschel, M. 2018. Formalisaton of SysML/KAOS

goal assignments with B system component

decompositions. In Lecture Notes in Computer Science,

11023 LNCS, Springer Nature Switzerland, 377-397

Wolny, S., Mazak, A., Carpella, Ch., Geist,V., Wimmer, M.

2020. Thirteen years of SysML: a systematic mapping

study. In Software and Systems Modeling, 19, 111-169.

Wrycza, S., Marcinkowski, B. 2011. SysML Requirement

Diagrams: Banking Transactional Platform Case Study.

In SIGSAND/PLAIS2011: Research in Systems

Analysis and Design: Models and Methods, 15-22.

Vidal, E.J., Vallota, E.R. 2018. SysML as a tool for

requirements traceability in mechatronic design. In

ACM International Conference Proceeding Series,

146-152.

Villamizar, H., Kalinowski, M., Viana, M., Fernandez,

D.M. 2018. A systematic mapping study on security in

agile requirement engineering. In Proceedings - 44

Euromicro Conference on Software Engineering and

Advanced Applications, SEAA, 454-461

Yamagishi, K., Nishimura, H., Ohtomi, K., Seki, K. 2014.

Design information management for product sound

quality. In IFIP Advances in Information and

Communication Technology, 225-235.

Zahoor, T., Azam, F., Anwar, M.W., Maqbool B., Javaid,

H.A. 2019. A UML Profile for Software Requirements

Prioritization. In IEEE 10

Annual Information

Technology, Electronics and Mobile Communication

Conference, IEMCON 2019, 885-891.

Zhang, Q., Huang, Z., Xie, J. 2018. Distributed system

model using SysML and event-B. In Lecture Notes of

the Institute for Computer Sciences, Social-Informatics

and Telecommunications Engineering, LNICST, 326-

336.

Zhe, W., Hugues, J., Chaudemar, J.-C., Lesergent, T. 2018.

An Integrated Approach to Model Based Engineering

with SysML, AADL and FACE. In SAE Technical

Papers. November.

Zingel, C., Albers, A., Matthiesen, S., Maletz, M. 2012.

Experiences and advancements from one year of

explorative application of an integrated model based

development technique using C&C

–A in SysML. In

IAENG International Journal of Computer Science,

39(2), 165-181.

ICE-B 2020 - 17th International Conference on e-Business