23,831 Hits in 3.2 sec

Investigating factor interactions in formalising the process of developing new products
Istraživanje interakcija faktora u formalizaciji procesa razvoja novih proizvoda

Bozhana Stoycheva, Diana Antonova
2018 Serbian Journal of Management  
The aim is to establish independent factor variables and their value impacts on the effective management of the process of developing new products related to the dependent variable "formalisation or use  ...  of officially documented procedures describing the new product development (NPD) process".  ...  Formalising the process of NPD .686 .470 .423 42.30 0.002 Table 3 . 3 Indexes for evaluation of the independent variables in the regression mode of the dependent variable "Formalising the NPD process  ... 
doi:10.5937/sjm13-16409 fatcat:ub3acldy6zeqdgw6s2msqn6sk4

An Axiom Based Metamodel for Software Process Formalisation: An Ontology Approach [chapter]

Edward Kabaale, Lian Wen, Zhe Wang, Terry Rout
2017 Communications in Computer and Information Science  
Software development usually follows well known process models and standards for development processes.  ...  However, to systematically and faithfully formalise heterogeneous processes from different standards and process models, there is a need to utilise uniform concepts to underpin the formalisation process  ...  Software development processes are typically too complex to be modeled and maintained without the help of tools [11] . As this work is ongoing, we are yet to evaluate it in a practical setting.  ... 
doi:10.1007/978-3-319-67383-7_17 fatcat:ay3i3we3fzhh7l4ce5lbx5d7iu

Evaluating a formal modelling language [chapter]

Fidel Ruiz, Frank Harmelen, Manfred Aben, Joke Plassche
1994 Lecture Notes in Computer Science  
In order to analyse the properties of (ML) ¤ that influence its usability, we designed a set of evaluation criteria.  ...  Finally, extensive software-support is required when constructing formal specifications.  ...  Errors in the Formalisation Process Not many errors were made during the formalisation process: in the beginning approximately three errors per page specification text were made, in the last formalisation  ... 
doi:10.1007/3-540-58487-0_2 fatcat:wyjoniqcfzhejilciirgaextt4

Special issue: software verification and testing

Mohammad Reza Mousavi, Jun Pang
2013 Innovations in Systems and Software Engineering  
He uses this formalisation to verify the implementation of several primitive arithmetic functions using Separation Logic.  ...  Welcome to the special issue dedicated to the selected extended papers of the Software Verification and Testing (SVT 2012) track held at the 27th ACM Symposium on Applied Computing (ACM SAC 2012).  ...  intensive process.  ... 
doi:10.1007/s11334-013-0211-1 fatcat:win6zy5fwffjnlh5mtzu4uvc64

A New Approach to Visualise Accessibility Problems of Mobile Apps in Source Code

Johannes Feiner, Elmar Krainz, Keith Andrews
2018 Proceedings of the 20th International Conference on Enterprise Information Systems  
We propose a novel workflow to bring usability issues into the development process: A quick accessibility evaluation (QAC) with 15 predefined metrics allow to collect issues.  ...  These issues are further condensed into formalised (UsabML) and the issues are tagged with the location in the source code.  ...  UsabML The QAC results are formalised into Usability Markup Language (UsabML) for further processing.  ... 
doi:10.5220/0006704405190526 dblp:conf/iceis/FeinerKA18 fatcat:72hf7ybyr5catouyv6sy7t6flu

SUMLOW: early design‐stage sketching of UML diagrams on an E‐whiteboard

Qi Chen, John Grundy, John Hosking
2008 Software, Practice & Experience  
SILK attempts to recognize the sketched user interface elements as soon as they are drawn and to formalise them.  ...  We describe the motivation for SUMLOW, illustrate use of the tool to sketch various UML diagram types, describe its key architecture abstractions and implementation approaches, and report on two evaluations  ...  The sketch formalisation process proceeds as follows: 6.  ... 
doi:10.1002/spe.856 fatcat:onla3ilmavcrfbboohrnkgl2ra

A formal experiment to assess the efficacy of certification standards [article]

Virginie Wiels
2014 arXiv   pre-print
Proving the efficacy of certification standards  ...  We will focus on the fact that the certification standard proposes to evaluate the embedded software by looking at some properties of some elements of the process used to produce this software. IV.  ...  And this formalisation would require in particular to formalise the notion of "correctness" of software (compliance to system requirements only?)  ... 
arXiv:1404.7542v1 fatcat:3356uot2brewzgw76v6v4iqtrm

Towards Enhanced Automated Support for Collaborative Software Requirements Management [chapter]

Michael Lang, Jim Duggan
2002 New Perspectives on Information Systems Development  
In particular, the communication of software requirements is extremely problematic.  ...  At one level, these may be considered to be process issues, but at a more basic level, they are issues of communication and collaboration,both between the development team and the client, and within the  ...  INTRODUCTION The objectives of the software requirements management process are to develop a shared, documented understanding of the requirements (in the form of the SRS), and to enforce a mechanism to  ... 
doi:10.1007/978-1-4615-0595-2_31 fatcat:2y4lj43kwvch5lnyoqlpmfab24

Evaluating how agent methodologies support the specification of the normative environment through the development process

Emilia Garcia, Simon Miles, Michael Luck, Adriana Giret
2014 Autonomous Agents and Multi-Agent Systems  
Evaluating how agent methodologies support the specification of the normative environment through the development process. Autonomous Agents and Multi-Agent Systems. 1-20.  ...  of a system in the development process.  ...  ) evaluation of the final design.  ... 
doi:10.1007/s10458-014-9275-z fatcat:muv6vtotire2lkfxccd43eldke

A Risk-Based Approach to Formalise Information Security Requirements for Software Development [chapter]

Lynn Futcher, Rossouw von Solms
2013 IFIP Advances in Information and Communication Technology  
This paper presents a risk-based approach to formalise information security requirements for software development.  ...  In this way it hopes to provide some educational guidelines on how risk assessment can be incorporated in the education of software developers.  ...  The Risk Evaluation According to [3] , the purpose of the risk evaluation process is two-fold.  ... 
doi:10.1007/978-3-642-39377-8_30 fatcat:caylublaqfbbjhg77w43q4rlsa

Evaluating a formal KBS specification language

F. van Harmelen, M. Aben, F. Ruiz, J. van de Plassche
1996 IEEE Expert  
(ML) 2 is strongly based on the structure of the knowledge-models used in the KADS KBS development method. We first designed a set of evaluation criteria.  ...  We then applied (ML) 2 in two case-studies and scored the language on our evaluation criteria. (ML) 2 scored well on most of our criteria.  ...  Errors in the Formalisation Process Not many errors were made during the formalisation process: in the beginning approximately three errors per page of specification text were made, in the last formalisation  ... 
doi:10.1109/64.482959 fatcat:muyeelvmebeyxdvqdrohakrcr4

Formalized systems development methodologies: a critical perspective

Brian Fitzgerald
1996 Information Systems Journal  
Many researchers see the solution to the software crisis in terms of increased control and the more widespread adoption of rigorous and formalised system development methodologies.  ...  Many researchers see the solution to the software crisis in terms of increased control and the more widespread adoption of rigorous and formalised system development methodologies.  ...  Acknowledgements The author would like to acknowledge the insightful suggestions and support of Frédéric Adam, Guy Fitzgerald, Nimal Jayaratna, Trevor Wood-Harper in the evolution of this work, and also  ... 
doi:10.1046/j.1365-2575.1996.00100.x fatcat:xircxmlahnelrhzqdjxy7zzjyq

Formal reasoning over class models using TOMM

Juan Jose Mendoza Santana, Juliana Küster Filipe Bowles
2019 Journal of Object Technology  
However, constant changes to requirements and manual modelling may result in invalid software models, and potentially invalid software solutions.  ...  They capture the relation between the requirements specification (problem domain) and system components (solution domain).  ...  In the next Section (5) we discuss the notation and the process to formalise class diagrams using first-order predicates.  ... 
doi:10.5381/jot.2019.18.2.a12 fatcat:7klisogvkfhnphoqvazklrecoq

Protocure: supporting the development of medical protocols through formal methods

Michael Balser, Oscar Coltell, Joyce van Croonenborg, Christoph Duelli, Frank van Harmelen, Albert Jovell, Peter Lucas, Mar Marcos, Silvia Miksch, Wolfgang Reif, Kitty Rosenbrand, Andreas Seyfang (+1 others)
2004 Studies in Health Technology and Informatics  
The Protocure II project will aim at integrating formal methods in the life cycle of guidelines.  ...  However, the work done on developing and disseminating them far outweighs the efforts on guaranteeing their quality.  ...  The main subjects we are working on are structured around this simple life-cycle model, including a study and enhance the life-cycle model itself: Process model As in the design of software, the process  ... 
pmid:15537209 fatcat:inwy25vl2fg2nc2dsny2al6ddq

Development of an Expert Knowledge-Based Genomic Variant Prioritisation Platform [chapter]

Aurora Sucre, Gregory Maclair, Iride Martinez, Concha Vidales, Gorka Epelde, Alba Garin-Muga
2022 Studies in Health Technology and Informatics  
This tool allows the users to set-up the pre-processing pipeline, filter the obtained data, annotate it using external and local databases (DBs) and help on deciding which variants are more relevant for  ...  This tool was developed using a user-centred methodology, where an iterative process was followed until a useful product was developed.  ...  This process will be performed by a larger group of experts that will evaluate: 1) software usability, 2) results accuracy and 3) software efficiency. Figure 1 . 1 Figure 1.  ... 
doi:10.3233/shti210855 pmid:35062088 fatcat:ugrfiyqn4ncpvlyw4hl6of3efa
« Previous Showing results 1 — 15 out of 23,831 results