Integration of Behavioural Requirements Specification within Knowledge Engineering

Herlea, Daniela E.; Jonker, Catholijn M.; Treur, Jan; Wijngaards, Niek J. E.

doi:10.1007/3-540-48775-1_11

Cited by 4 publications

(6 citation statements)

References 9 publications

Supporting

Mentioning

Contrasting

Order By: Relevance

“…The DFARS process is a partial response to the need identified by Garfinkel et al 6 to develop statistical and other approximation techniques to ensure that the interpretation of digital evidence is grounded in facts and science and not simply upon opinion. Herlea et al 9 deal with the integration of behavioural requirements specifications within compositional knowledge engineering. They define requirement engineering as a process that addresses the development and validation of methods for eliciting, representing, analysing and confirming system requirements.…”

Section: Related Workmentioning

confidence: 99%

“…This process combines the discussion of requirements and scenarios, which are continually honed over time to arrive at a system description that satisfies all stakeholders. Herlea et al 9 emphasise the involvement of the users, who are considered the "experts" at the critical early stage of software development. However, not only are the users important participants in the consultation, but all stakeholders -who include domain experts, system customers, managers, and developers -are important participants in the consultation process.…”

Section: Related Workmentioning

confidence: 99%

See 1 more Smart Citation

Digital forensic application requirements specification process

Omeleze

Venter

2017

Australian Journal of Forensic Sciences

View full text Add to dashboard Cite

The requirements to identify the cause of an incident, following the trail of events preceding the incident, as well as proving the consistency of the potential evidence recovered from the alleged incident, ultimately demand a proactive approach towards the design of digital forensics (DF) applications. Success in the use of digital evidence for analysis or validation in digital forensic investigations depends on established processes, scientific methods, guidelines and standards that are used in the DF application designs and developments.Adding legal and scientific processes capable of absorbing the constant upgrades and updates in the design of DF applications is a boost to the already existing DF processes and standards. However, there is need for such processes to be clearly defined, so that non-technical audience involved in crime investigations and decisions, can easily comprehend the DF application designs and development processes.To proactively overcome this challenge, this paper proposes the digital forensic application requirements specifications (DFARS) process. The proposed DFARS process outlines an easy-to-apply design process for designing any DF application. It further demonstrates in a case scenario, how to apply the DFARS process using the online neighbourhood watch (ONW) system. The ONW system is a DF application that crowd-source potential digital evidence (PDE). One of the objectives of the ONW system is to increase the volume of available PDE to enhance success in prosecution of neighbourhood crime.Therefore using the DFARS process with the ONW system as a case scenario, the result shows that the DFARS process ensures an easy application of modifiability, pluggability and reliability features at any point in the life-cycle of a DF application. This thereby accommodates the constant upgrades and changes associated with electronic devices, operating systems, hardware and other requirements. It further shows an easy-to-follow process that is understandable to both technical and non-technical audiences in the field of digital forensics.

show abstract

Section: Related Workmentioning

confidence: 99%

Section: Related Workmentioning

confidence: 99%

Digital forensic application requirements specification process

Omeleze

Venter

2017

Australian Journal of Forensic Sciences

View full text Add to dashboard Cite

show abstract

“…The progression suggested as being characteristic of a software-related design requirement evolution is illustrated in reference [5], although it stops short of metamorphosis of the formal representation of the requirement into the solution proper. Here the distinction and necessity for representations that are informal, semiformal and formal are illustrated.…”

Section: The Character Of the Design Requirementmentioning

confidence: 99%

“…As such, scenario use lends itself to EDR evolution. Herlea et al [5 ], discussed a method by which the transition from informal to formal expression of the design requirement can be achieved by the parallelled re®nement of scenarios and requirements, these two entities being accorded the same importance. As noted above, this paper also provided a good example of the transition process between informal, semiformal and formal representations in RE.…”

Section: Conceptual Modellingmentioning

confidence: 99%

Current research in the engineering design requirement

Darlington

Culley

2002

Proceedings of the Institution of Mechanical Engineers, Part B:

View full text Add to dashboard Cite

The design requirement is a description of the desired solution to a problem. In engineering design, as in all other, a clear expression of a well-formulated design goal is vital for successful and efficient completion of the design task. The nature of the design requirement and the processes by which it is achieved have been the subject of a wide variety of research. The purpose of the paper is twofold. Firstly, it sets out to collate and discuss representative research in this area in order to give an overview of the current scope of the work. Secondly, it seeks to draw a comparison with the task of developing the design requirement for software and information systems and to initiate a discussion that considers to what extent the substantial body of research in software requirements engineering might help to give an understanding of the design requirement for the engineering design domain. A tentative characterization of the differences between the tasks in the two domains is presented, and representative papers from requirements engineering are used to suggest areas of overlap as a starting point for further investigation.

show abstract

“…In the approach presented in this paper requirements and scenarios are considered equally important; see also (Herlea, Jonker, Treur and Wijngaards, 1999c) .…”

Section: Introductionmentioning

confidence: 99%

A Compositional Knowledge Level Process Model of Requirements Engineering

Herlea

Jonker

Treur

et al. 2002

Int. J. Soft. Eng. Knowl. Eng.

Self Cite

View full text Add to dashboard Cite

In current literature few detailed process models for Requirements Engineering are presented: usually high-level activities are distinguished, without a more precise specification of each activity. In this paper the process of Requirements Engineering has been analyzed using knowledge-level modelling techniques, resulting in a well-specified compositional process model for the Requirements Engineering task. This process model is considered to be a generic process model: it can be refined (by instantiation or specialisation) into a process model for a specific kind of Requirements Engineering process.

show abstract

Integration of Behavioural Requirements Specification within Knowledge Engineering

Cited by 4 publications

References 9 publications

Digital forensic application requirements specification process

Digital forensic application requirements specification process

Current research in the engineering design requirement

A Compositional Knowledge Level Process Model of Requirements Engineering

Contact Info

Product

Resources

About