The Experts below are selected from a list of 18216 Experts worldwide ranked by ideXlab platform
Peter Bielkowicz - One of the best experts on this subject based on the ideXlab platform.
-
CAiSE - A Comparison and Evaluation of Data Requirement Specification Techniques in SSADM and the Unified Process
Notes on Numerical Fluid Mechanics and Multidisciplinary Design, 2020Co-Authors: Peter BielkowiczAbstract:During the analysis stage of a typical information system development process, user Requirements concerning system functionality and data are captured and specified using Requirement Specification techniques. Most of these Specification techniques are graphical (semi-formal), i.e. they involve modelling. This paper presents a comparison of data Requirement Specification techniques in SSADM, which is a strong data-centred method, and the Unified Process, an object-oriented method. In particular, we investigated how data groups (entities and classes), their attributes and relationships are identified, specified and validated in both methods. Data Requirement Specification techniques used in both methods are then evaluated against a set of detailed criteria based on five Requirement Specification quality attributes. Both methods seem to have a similar informal approach to producing initial data Requirement Specifications, but they differ when these initial models are refined. The refinement in SSADM is more rigorous. Therefore, this paper makes a few recommendations for the Unified Process.
-
a comparison and evaluation of data Requirement Specification techniques in ssadm and the unified process
Conference on Advanced Information Systems Engineering, 2001Co-Authors: Peter BielkowiczAbstract:During the analysis stage of a typical information system development process, user Requirements concerning system functionality and data are captured and specified using Requirement Specification techniques. Most of these Specification techniques are graphical (semi-formal), i.e. they involve modelling. This paper presents a comparison of data Requirement Specification techniques in SSADM, which is a strong data-centred method, and the Unified Process, an object-oriented method. In particular, we investigated how data groups (entities and classes), their attributes and relationships are identified, specified and validated in both methods. Data Requirement Specification techniques used in both methods are then evaluated against a set of detailed criteria based on five Requirement Specification quality attributes. Both methods seem to have a similar informal approach to producing initial data Requirement Specifications, but they differ when these initial models are refined. The refinement in SSADM is more rigorous. Therefore, this paper makes a few recommendations for the Unified Process.
Matias Urbieta - One of the best experts on this subject based on the ideXlab platform.
-
improving mockup based Requirement Specification with end user annotations
International Conference on Agile Software Development, 2018Co-Authors: Matias Urbieta, Nahime Torres, Jose Matias Rivero, Gustavo Rossi, F J DominguezmayoAbstract:Agile approaches, one of the key methodologies used in today’s software projects, often rely on user interface mockups for capturing the goals that the system must satisfy. Mockups, as any other Requirement artifact, may suffer from ambiguity and contradiction issues when several points of view are surveyed/elicited by different analysts. This article introduces a novel approach that enhances mockups with friendly end-user annotations that helps formalizing the Requirements and reducing or identifying conflicts. We present an evaluation of the approach in order to measure how the use of annotations improves Requirements quality.
Yosuke Hatakeyama - One of the best experts on this subject based on the ideXlab platform.
-
conversion method for user experience design information and software Requirement Specification
International Conference of Design User Experience and Usability, 2016Co-Authors: Ayumi Takeda, Yosuke HatakeyamaAbstract:In the era of the Internet of Things, system development is becoming increasingly complex and diverse due to the need for advanced user experience design (UXD) and cross-platform systems. However, current software Requirement Specification methods have no way to describe UXD. We propose a description method to reflect UXD information, such as user behavior, as UXD Requirements.
-
HCI (16) - Conversion Method for User Experience Design Information and Software Requirement Specification
Design User Experience and Usability: Design Thinking and Methods, 2016Co-Authors: Ayumi Takeda, Yosuke HatakeyamaAbstract:In the era of the Internet of Things, system development is becoming increasingly complex and diverse due to the need for advanced user experience design (UXD) and cross-platform systems. However, current software Requirement Specification methods have no way to describe UXD. We propose a description method to reflect UXD information, such as user behavior, as UXD Requirements.
-
Conversion method for user experience design information and software Requirement Specification
Lecture Notes in Computer Science (including subseries Lecture Notes in Artificial Intelligence and Lecture Notes in Bioinformatics), 2016Co-Authors: Ayumi Takeda, Yosuke HatakeyamaAbstract:In the era of the Internet of Things, system development is becoming increasingly complex and diverse due to the need for advanced user experience design (UXD) and cross-platform systems. However, current software Requirement Specification methods have no way to describe UXD. We propose a description method to reflect UXD information, such as user behavior, as UXD Requirements. © Springer International Publishing Switzerland 2016.
Sangsoo Choi - One of the best experts on this subject based on the ideXlab platform.
-
enhanced misuse case model a security Requirement analysis and Specification model
Lecture Notes in Computer Science, 2006Co-Authors: Sangsoo ChoiAbstract:An information security system of public or private organization should be developed securely and cost-effectively by using security engineering and software engineering technologies, as well as a security Requirement Specification (SRS). We present the E-MUC model that is analysis and Specification model of security Requirement based on UML, and a development process by using E-MUC model. Our approach is based on the paradigm of Common Criteria (ISO/IEC 15408), that is an international evaluation criteria for information security products, and PP which is a common security functional Requirement Specification for specific types of information security product.
-
srs tool a security functional Requirement Specification development tool for application information system of organization
International Conference on Computational Science and Its Applications, 2005Co-Authors: Sangsoo Choi, Sooyoung ChaeAbstract:An application information system (IS) of public or private organization should be developed securely and cost-effectively by using security engineering and software engineering technologies, as well as a security Requirement Specification (SRS). We present a SRS-Process that is a development process for SRS of IS, and a SRS-Tool that is a development tool for SRS in accordance with the SRS-Process. Our approach is based on the paradigm of Common Criteria (ISO/IEC 15408), that is an international evaluation criteria for information security products, and PP which is a common security functional Requirement Specification for specific types of information security product.
F J Dominguezmayo - One of the best experts on this subject based on the ideXlab platform.
-
improving mockup based Requirement Specification with end user annotations
International Conference on Agile Software Development, 2018Co-Authors: Matias Urbieta, Nahime Torres, Jose Matias Rivero, Gustavo Rossi, F J DominguezmayoAbstract:Agile approaches, one of the key methodologies used in today’s software projects, often rely on user interface mockups for capturing the goals that the system must satisfy. Mockups, as any other Requirement artifact, may suffer from ambiguity and contradiction issues when several points of view are surveyed/elicited by different analysts. This article introduces a novel approach that enhances mockups with friendly end-user annotations that helps formalizing the Requirements and reducing or identifying conflicts. We present an evaluation of the approach in order to measure how the use of annotations improves Requirements quality.
