Change search
Refine search result
1 - 5 of 5
CiteExportLink to result list
Permanent link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf
Rows per page
  • 5
  • 10
  • 20
  • 50
  • 100
  • 250
Sort
  • Standard (Relevance)
  • Author A-Ö
  • Author Ö-A
  • Title A-Ö
  • Title Ö-A
  • Publication type A-Ö
  • Publication type Ö-A
  • Issued (Oldest first)
  • Issued (Newest first)
  • Created (Oldest first)
  • Created (Newest first)
  • Last updated (Oldest first)
  • Last updated (Newest first)
  • Disputation date (earliest first)
  • Disputation date (latest first)
  • Standard (Relevance)
  • Author A-Ö
  • Author Ö-A
  • Title A-Ö
  • Title Ö-A
  • Publication type A-Ö
  • Publication type Ö-A
  • Issued (Oldest first)
  • Issued (Newest first)
  • Created (Oldest first)
  • Created (Newest first)
  • Last updated (Oldest first)
  • Last updated (Newest first)
  • Disputation date (earliest first)
  • Disputation date (latest first)
Select
The maximal number of hits you can export is 250. When you want to export more records please use the Create feeds function.
  • 1.
    Ismail, Muhammad
    Jönköping University, School of Engineering, JTH, Computer Science and Informatics.
    Ontology Learning from Software Requirements Specification2017In: / [ed] Paolo Ciancarini, Francesco Poggi, Matthew Horridge, Jun Zhao, Tudor Groza, Mari Carmen Suarez-Figueroa, Mathieu d'Aquin, Valentina Presutti, Springer, 2017, p. 251-255Conference paper (Refereed)
    Abstract [en]

    Learning ontologies from software requirements specifications with individuals and relations between individuals to represent detailed information, such as input, condition and expected result of a requirement, is a difficult task. System specification ontologies (SSOs) can be developed from software requirement specifications to represent requirements and can be used to automate some time-consuming activities in software development processes. However, manually developing SSOs to represent requirements and domain knowledge of a software system is a time-consuming and a challenging task. The focus of this PhD is how to create ontologies semi-automatically from SRS. We will develop a framework that can be a possible solution to create semi-automatically ontologies from SRS. The developed framework will mainly be evaluated by using the constructed ontologies in the software testing process and automating a part of it. i.e. test case generation.

  • 2.
    Ismail, Muhammad
    University of Skövde, Sweden.
    Ontology learning from software requirements specifications: Research Proposal2017Report (Other academic)
    Abstract [en]

    Using ontologies is a promising way to automate some time-consuming activitiesin software development processes, such as requirements analysis and validation,and software verification. Ontologies can also be used to support software developmentprocesses by sharing domain knowledge between development phases. Systemspecification ontologies (SSOs) can be developed from software requirementsspecifications (SRS) to represent requirements and knowledge about the softwaresystem that is being developed. SSOs can be interpreted by a tool to infer the knowledgethat can be used to automate some time-consuming activities in software developmentprocesses, in order to reduce the cost and time of the software development.However, manually developing SSOs to represent the software requirementsknowledge is a time-consuming and a challenging task.

    The focus of this PhD project is to understand how to generate system specificationontologies semi-automatically from software requirements specifications. This thesiswill guide how software requirements specifications can be processed to capturedomain knowledge and knowledge about the software system, and represent softwarerequirements in an ontology semi-automatically. We will develop a frameworkand a set of methods within this framework which can be a possible solution tocreate semi-automatically ontologies from SRS. The constructed ontologies can beused in software processes to automate time-consuming activities, such as requirementsvalidation and software test case generations. The developed framework andmethods will be evaluated by comparing with existing ontology learning methodsand by using constructed ontologies to automate test case generation which is partof software testing process. The proposed solution will be evaluated by in differentcase studies that can have similar software requirements specifications.

  • 3.
    Tan, He
    et al.
    Jönköping University, School of Engineering, JTH. Research area Computer Science and Informatics. Jönköping University, School of Engineering, JTH, Computer Science and Informatics, JTH, Jönköping AI Lab (JAIL).
    Ismail, Muhammad
    Jönköping University, School of Engineering, JTH, Computer Science and Informatics. Jönköping University, School of Engineering, JTH. Research area Computer Science and Informatics.
    Tarasov, Vladimir
    Jönköping University, School of Engineering, JTH. Research area Computer Science and Informatics. Jönköping University, School of Engineering, JTH, Computer Science and Informatics, JTH, Jönköping AI Lab (JAIL).
    Adlemo, Anders
    Jönköping University, School of Engineering, JTH, Computer Science and Informatics. Jönköping University, School of Engineering, JTH. Research area Computer Science and Informatics.
    Johansson, Mats
    Saab Avionics Systems, Jönköping.
    Development and evaluation of a software requirements ontology2016In: SKY 2016 - 7th International Workshop on Software Knowledge, Proceedings - In conjuction with IC3K 2016 / [ed] Iaakov Exman, Juan Llorens and Anabel Fraga, SciTePress, 2016, p. 11-18Conference paper (Refereed)
    Abstract [en]

    This paper presents an ontology which has been developed to represent the requirements of a software component pertaining to an embedded system in the avionics industry. The ontology was built based on the software requirements documents and was used to support advanced methods in the subsequent stages of the software development process. In this paper it is described theprocess that was used to build the ontology. Two pertinent quality measures that were applied to the ontology, i.e. usability and applicability, are also described, as well as the methods used to evaluate the quality measures and the result of these evaluations.

    Download full text (pdf)
    Fulltext
  • 4.
    Tarasov, Vladimir
    et al.
    Jönköping University, School of Engineering, JTH, Computer Science and Informatics, JTH, Jönköping AI Lab (JAIL).
    Tan, He
    Jönköping University, School of Engineering, JTH, Computer Science and Informatics, JTH, Jönköping AI Lab (JAIL).
    Adlemo, Anders
    Jönköping University, School of Engineering, JTH, Computer Science and Informatics.
    Ismail, Muhammad
    Jönköping University, School of Engineering, JTH, Computer Science and Informatics.
    Mats, Johansson
    Saab AB, Avisonics.
    Olsson, Daniel
    AddQ AB.
    Ontology-based Software Test Case Generation (OSTAG)2015In: European Projects in Knowledge Applications and Intelligent Systems - Volume 1: EPS Lisbon 2016 / [ed] R. J. Machado, J. Sequeira,H. Plácido da Silva, & J. Filipe, SciTePress, 2015, p. 135-159Conference paper (Refereed)
    Abstract [en]

    Testing is a paramount quality assurance activity in every software developmentproject, especially for embedded, safety critical systems. During thetest process, a lot of effort is put into the generation of test cases. The presentedOSTAG project aimed at developing methods and techniques to automate thesoftware test case generation for black-box testing. The proposed approach wasbased on the creation of a software requirements ontology and the applicationof inference rules on the ontology to derive test cases. The ontology representsknowledge of the requirements, the software system and the corresponding applicationdomain while the inference rules formalize knowledge from documentsand experienced testers in the domain of test planning and test case generation.A software prototype of the approach was implemented and one of the industrialproject partners evaluated the results. An alternative method for generating testcases, based on genetic algorithms, was also explored.

    Download full text (pdf)
    Fulltext
  • 5.
    Tarasov, Vladimir
    et al.
    Jönköping University, School of Engineering, JTH, Computer Science and Informatics, JTH, Jönköping AI Lab (JAIL).
    Tan, He
    Jönköping University, School of Engineering, JTH, Computer Science and Informatics, JTH, Jönköping AI Lab (JAIL).
    Ismail, Muhammad
    Jönköping University, School of Engineering, JTH, Computer Science and Informatics.
    Adlemo, Anders
    Jönköping University, School of Engineering, JTH, Computer Science and Informatics.
    Johansson, Mats
    Saab AB.
    Application of inference rules to a software requirements ontology to generate software test cases2017In: OWL: Experiences and Directions – Reasoner Evaluation: 13th International Workshop, OWLED 2016, and 5th International Workshop, ORE 2016, Bologna, Italy, November 20, 2016, Revised Selected Papers / [ed] Dragoni, Mauro; Poveda-Villalón, María; Jimenez-Ruiz, Ernesto, Cham: Springer, 2017, p. 82-94Chapter in book (Refereed)
    Abstract [en]

    Testing of a software system is resource-consuming activity. One of the promising ways to improve the efficiency of the software testing process is to use ontologies for testing. This paper presents an approach to test case generation based on the use of an ontology and inference rules. The ontology represents requirements from a software requirements specification, and additional knowledge about components of the software system under development. The inference rules describe strategies for deriving test cases from the ontology. The inference rules are constructed based on the examination of the existing test documentation and acquisition of knowledge from experienced software testers. The inference rules are implemented in Prolog and applied to the ontology that is translated from OWL functional-style syntax to Prolog syntax. The first experiments with the implementation showed that it was possible to generate test cases with the same level of detail as the existing, manually produced, test cases.

    Download full text (pdf)
    Fulltext
1 - 5 of 5
CiteExportLink to result list
Permanent link
Cite
Citation style
  • apa
  • ieee
  • modern-language-association-8th-edition
  • vancouver
  • Other style
More styles
Language
  • de-DE
  • en-GB
  • en-US
  • fi-FI
  • nn-NO
  • nn-NB
  • sv-SE
  • Other locale
More languages
Output format
  • html
  • text
  • asciidoc
  • rtf