“…Our SLR 6 did not uncover any work on methodical support for applying a created domain specification. However, the SLR started the literature search with a search string that included the term "domain".…”
Section: Related Workmentioning
confidence: 99%
“…Deckers and Lago report in a systematic literature review (SLR) 6 that methods for domain-oriented specifications are mostly limited to creating a domain specification (DS), like a domain-specific language (DSL) or domain model (DM). These methods do not incorporate steps and guidance for applying a created DS.…”
Section: Problem Statementmentioning
confidence: 99%
“…The SLR 6 also concluded that none of the found methods on domain-oriented modeling has a complete method definition (i.e., covering underlying model, notation, steps, and guidance). Some approaches provide a metamodel and a notation, and others provide high level steps, sometimes guidance, and sometimes the use of an existing language like UML.…”
Section: Problem Statementmentioning
confidence: 99%
“…We observed that those books did clearly not address all the MuDForM objectives. So, we performed a systematic literature review 6 , which had the same objectives as starting point. We identified some clear gaps in the existing literature, which should be bridged to achieve the objectives.…”
Section: Featurementioning
confidence: 99%
“…MuDForM provides analysis and modeling concepts, analysis and modeling steps, and guidelines to guide the modeling process, which starts with a knowledge source, like a (domain) text or (domain) expert. Deckers and Lago 6 observed that the existing literature on domain modeling approaches does not offer methodical support for using a domain model as the terminology for defining other types of specifications. This paper explains the part of MuDForM for domain-based feature modeling, and its application in a case study.…”
To enable the people involved in a software development process
to communicate and reason close to their area of knowledge, we are
investigating a method to formalize and integrate knowledge of multiple
domains into domain models and into specifications in terms of those
domain models. For this purpose, we have previously defined a set of
method objectives, and an initial version of the method –called
MuDForM. This paper reports on the methodical support for using a domain
model as terminology to define other specifications, and feature
specifications in particular. We performed a case study to validate how
well the method helps in the specification of processes and to realize
the case-specific objectives of the customer. The case study pertains to
the formalization of the ISO26262 standard for functional safety in the
automotive domain. We found that our method is suitable to
systematically formalize a process that is described in natural
language, such that there is a clear separation of domain-specific
concepts, unambiguous process specifications, and concepts from outside
the domain and process of interest. We have extended our method with
concepts, steps, and guidelines for grammatical analysis, for the
formalization of constraints, and for the specification of processes.
The case-specific results are the unambiguous specification of a part of
the ISO26262 processes.
“…Our SLR 6 did not uncover any work on methodical support for applying a created domain specification. However, the SLR started the literature search with a search string that included the term "domain".…”
Section: Related Workmentioning
confidence: 99%
“…Deckers and Lago report in a systematic literature review (SLR) 6 that methods for domain-oriented specifications are mostly limited to creating a domain specification (DS), like a domain-specific language (DSL) or domain model (DM). These methods do not incorporate steps and guidance for applying a created DS.…”
Section: Problem Statementmentioning
confidence: 99%
“…The SLR 6 also concluded that none of the found methods on domain-oriented modeling has a complete method definition (i.e., covering underlying model, notation, steps, and guidance). Some approaches provide a metamodel and a notation, and others provide high level steps, sometimes guidance, and sometimes the use of an existing language like UML.…”
Section: Problem Statementmentioning
confidence: 99%
“…We observed that those books did clearly not address all the MuDForM objectives. So, we performed a systematic literature review 6 , which had the same objectives as starting point. We identified some clear gaps in the existing literature, which should be bridged to achieve the objectives.…”
Section: Featurementioning
confidence: 99%
“…MuDForM provides analysis and modeling concepts, analysis and modeling steps, and guidelines to guide the modeling process, which starts with a knowledge source, like a (domain) text or (domain) expert. Deckers and Lago 6 observed that the existing literature on domain modeling approaches does not offer methodical support for using a domain model as the terminology for defining other types of specifications. This paper explains the part of MuDForM for domain-based feature modeling, and its application in a case study.…”
To enable the people involved in a software development process
to communicate and reason close to their area of knowledge, we are
investigating a method to formalize and integrate knowledge of multiple
domains into domain models and into specifications in terms of those
domain models. For this purpose, we have previously defined a set of
method objectives, and an initial version of the method –called
MuDForM. This paper reports on the methodical support for using a domain
model as terminology to define other specifications, and feature
specifications in particular. We performed a case study to validate how
well the method helps in the specification of processes and to realize
the case-specific objectives of the customer. The case study pertains to
the formalization of the ISO26262 standard for functional safety in the
automotive domain. We found that our method is suitable to
systematically formalize a process that is described in natural
language, such that there is a clear separation of domain-specific
concepts, unambiguous process specifications, and concepts from outside
the domain and process of interest. We have extended our method with
concepts, steps, and guidelines for grammatical analysis, for the
formalization of constraints, and for the specification of processes.
The case-specific results are the unambiguous specification of a part of
the ISO26262 processes.
To enable the people involved in a software development process to communicate and reason close to their area of knowledge, we are investigating and engineering a method that formalizes and integrates knowledge of multiple domains into domain models and into specifications in terms of those domain models. We follow an action research approach, starting with a diagnosis phase, in which we have previously defined a set of method objectives, and performed a systematic literature review. During action planning, we defined how we are going to develop the method—called Multi‐Domain Formalization Method (MuDForM). This paper reports on the methodical support for using a domain model as the terminology for feature specifications. During action taking, we defined an initial version of the method and set up case studies. During the evaluation phase, we performed a case study to validate how well the method helps in the specification of processes and to realize the case‐specific objectives of the customer. The case study pertains to the formalization of the ISO26262 standard for functional safety in the automotive domain. The created models are explained to the involved experts to ensure their consistency with the original text. We found that MuDForM is suitable to systematically formalize processes described in natural language, such that the resulting process models are fully expressed in terms of domain concepts and concepts from outside the domains and processes of interest. Further, during the specifying learning phase, we have extended our method with concepts, steps, and guidelines for grammatical analysis, for formalization of constraints, and for the specification of processes.
This study determined factors affecting the security of Information Systems in Africa. Also, it established the quality of publications in the area of Information Security. The study is based on peer-reviewed publications conducted in Africa. The study adopted the mixed research approach. The study used a systematic literature review, with part of the analysis using descriptive analysis. In total, 70 papers formed the population of publications extracted in the area of Information Security. In addition, 37 papers had the quality to be included in the analysis of factors affecting Information Security. The study found that information Security factors are in four key categories: human factors, policy-related issues, work environment, and demographic factors. Overall, the work environment is the most reported category affecting the security of Information Systems in Africa. In addition, gender is the highest reported individual factor associated with the insecurity of Information Systems; female is the highly affected gender. Other factors include the lack of Information Security training, the unchecked level of trust, carelessness and poor security policies. The study recommends training programs, policy improvement and promoting behaviours that minimise exposure to attacks.
scite is a Brooklyn-based organization that helps researchers better discover and understand research articles through Smart Citations–citations that display the context of the citation and describe whether the article provides supporting or contrasting evidence. scite is used by students and researchers from around the world and is funded in part by the National Science Foundation and the National Institute on Drug Abuse of the National Institutes of Health.