scholarly journals JPIAspectZ: A Formal Requirement Specification Language for Joint Point Interface AOP Applications

2019 ◽  
Vol 9 (4) ◽  
pp. 4338-4341
Author(s):  
C. L. Vidal-Silva ◽  
E. Madariaga ◽  
T. Pham ◽  
F. Johnson ◽  
L. A. Urzua ◽  
...  
Keyword(s):  
Software Development ◽  
Software Development Process ◽  
Advantages And Disadvantages ◽  
Joint Point ◽  
Formal Requirement ◽  
Development Approach ◽  
Definition Of ◽  
Join Point ◽  
Formal Requirements ◽  
Requirement Specifications

Aspect-oriented software development (AOSD) solves a few issues of the object-oriented software development (OOSD) approach and adds a few more concerning modules and their relationships. Join point interface (JPI) is an AOSD methodology that by the definition of the interface between advised artifacts and aspects solves associated AOSD issues to get software with a high modularity level. Looking for a JPI software development approach, this article proposes and exemplifies the use of JPIAspectZ, an extension of the formal aspect-oriented language AspectZ for the software JPI requirement specifications. Mainly, JPIAspectZ looks for a concept and model consistency in a JPI software development process. Since the main JPI characteristics are the joining point interfaces definitions, i. e. explicit associations definition between aspects and advised modules, thus, by JPI, classes are no longer oblivious of possible interaction with aspects, and aspects, for their action effectiveness, do not depend anymore on signatures of advisable module components. JPIAspectZ fully supports these JPI principles. As JPI application examples, this article shows the formal requirements specification for classic aspect-oriented and JPI examples, along with describing the advantages and disadvantages of this language.

scholarly journals ScrumOntoBDD: Agile software development based on scrum, ontologies and behaviour-driven development

2021 ◽  
Vol 27 (1) ◽  
Author(s):  
Pedro Lopes de Souza ◽  
Wanderley Lopes de Souza ◽  
Luís Ferreira Pires
Keyword(s):  
Software Development ◽  
Agile Software Development ◽  
Agile Development ◽  
Software Life Cycle ◽  
System Requirements ◽  
Definition Of ◽  
Agile Software ◽  
Requirement Specifications ◽  
Software Development Practices ◽  
Test Suites

AbstractWhen developing a Learning Management System (LMS) using Scrum, we noticed that it was quite often necessary to redefine some system behaviour scenarios, due to ambiguities in the requirement specifications, or due to misinterpretations of stories reported by the Product Owners (POs). The definition of test suites was also cumbersome, resulting in test suites that were incomplete or did not at all comply with the system requirements. Based on this experience and to deal with these problems, in this paper, we propose the ScrumOntoBDD approach to agile software development, which combines Scrum, ontologies and Behaviour-Driven Development (BDD). This approach is centred on the concepts and techniques of Scrum and BDD and focuses on the planning and analysis phases of the software life cycle, since the BDD tools currently provide little support to these phases, while most of the problems during the LMS development were found exactly there. We claim that our approach improves the software development practices in this respect. Furthermore, ScrumOntoBDD employs ontologies in order to reduce ambiguities intrinsic to the use of a natural language as a BDD ubiquitous language. In this paper, we illustrate and systematically evaluate our approach, showing that it is beneficial since it improves the communication between members of an agile development team.

scholarly journals Integración de marcos de trabajo para desarrollo de software: Scrum, PSP e ISO 25000 [Integrating software development frameworks: Scrum, PSP and ISO25000]

2015 ◽  
Author(s):  
Jhon Alexander Holguín Barrera
Keyword(s):  
Software Development ◽  
Development Process ◽  
Software Industry ◽  
Positive Contribution ◽  
Software Development Process ◽  
Single Application ◽  
Small And Medium Enterprise ◽  
Quality Costs ◽  
Medium Enterprise ◽  
Definition Of

Actualmente la industria del software tiene grandes retos para la construcción y mantenimiento del software en términos de calidad, costos y tiempo. Para esto se han generado diversidad de metodologías, marcos de trabajo, normas y modelos que permiten afrontar estos retos, pero es complejo que la aplicación de solo un referente logre cumplir con todo lo requerido, y por lo general se toman elementos de varios modelos o metodologías. El presente estudio contiene la definición de un proceso de desarrollo de software en una PYME a través de la integración de varios de estos marcos de trabajo (Scrum, PSP e ISO 25000) analizados bajo los lineamientos dados por SWEBOK y apoyados por tecnicas como GQM, que permitan dar un aporte positivo en el cumplimiento de estos objetivos.Palabras Claves: ISO25000, Procesos, PSP, Scrum, SWEBOKCurrently, the software industry has big challenges for the construction and maintenance of software in terms of quality, costs and time. For this the industry generated diversity of methodologies, frameworks, standards and models that meet these challenges, but is complex to accomplish this with the single application of only one reference that meets the goal, usually elements from various models and methodologies are taken. This study contains the definition of a software development process inside of a SME (Small and Medium Enterprise), through the integration of several of this frameworks (Scrum, PSP, and ISO25000) analyzed under the guidelines given by SWEBOK and supported by techniques such as GQM, that allow to make a positive contribution to meet this goals.Keywords: ISO25000, Process, PSP, Scrum, SWEBOK

scholarly journals Wiki support for automated definition of software test cases

Kybernetes ◽  
2019 ◽  
Vol 49 (4) ◽  
pp. 1305-1324
Author(s):  
Leandro Antonelli ◽  
Mariángeles Hozikian ◽  
Guy Camilleri ◽  
Alejandro Fernandez ◽  
Julian Grigera ◽  
...  
Keyword(s):  
Software Development ◽  
Test Generation ◽  
Development Process ◽  
Early Stage ◽  
Software Test ◽  
Test Cases ◽  
Software Development Process ◽  
Content Type ◽  
Definition Of ◽  
Method Model

Purpose The design of tests is a very important step in the software development process because it allows us to match the users’ expectations with the finished product. Considered as a cumbersome activity, efforts have been made to automatize and alleviate the burden of test generation, but it is still a largely neglected step. The study aims to propose taking advantage of existing requirement artifacts, like scenarios that describe the dynamic of the domain in a very early stage of software development, to obtain tests from them. Design/methodology/approach In particular, the approach proposed complement the scenarios that are textually described with a glossary, the language extended lexicon. Thus, a set of rules to derive tests from scenarios is also proposed. The tests are then described using the task/method model. Findings The main findings of this study consist of an extension of a previously presented set of rules. And, a tool based on a media wiki platform that makes possible to record scenarios and the language extended lexicon and implement the rules to obtain the tests. Originality/value The main originality of this study is the glossary which complements scenarios, the semantic support to obtain tests and the tool to automatize the approach.

Lean Development

2013 ◽  
pp. 142-150
Author(s):  
Saqib Saeed ◽  
Izzat Alsmadi ◽  
Farrukh Masood Khawaja
Keyword(s):  
Software Development ◽  
Process Development ◽  
Software Process ◽  
Agile Development ◽  
Software Systems ◽  
Software System ◽  
Software Development Process ◽  
Complex Activity ◽  
Development Approach ◽  
Software Development Practices

Software development is a complex activity, which is human intensive in nature. In order to build quality software systems, organizations need to follow mature software development practices, which are continually improved. As a result, the concept of software development process emerged, which highlighted a systematic set of activities required to develop a software system. Recently, agile development methodologies have provided a rich set of innovative software development approaches, aiming to optimize the software process. In order to be successful in adopting these approaches, a thorough understanding of their implementation procedures is required. In this chapter, we took a look at the lean development approach to understand how its principles pave the way in fostering knowledge management initiatives in software process development.

scholarly journals Comparative Study of Different SDLC Models

2021 ◽  
Vol 9 (11) ◽  
pp. 73-80
Author(s):  
Aparna Gupta
Keyword(s):  
Life Cycle ◽  
Software Development ◽  
Development Process ◽  
Cost Effective ◽  
Software Development Process ◽  
Application Development ◽  
Advantages And Disadvantages ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Life Cycle Models

Abstract: The Software Development Life Cycle (SDLC) refers to a methodology with clearly defined processes for creating highquality software which are cost effective and reliable. This method of software developing process is quite systematic and structural. SDLC defines the framework that has different activities and tasks to be administered during the software development process. Software development process is quite complex, and to do it without any proper planning would be inefficient. So, we use these SDLC models to make the Software development process simple and systematic. There are various software development life cycle models that are used in the software development process, all having their own advantages and limitations. In this paper, we have included six of these SDLC models - Waterfall Model, Spiral Model, V Model, Agile Model, Iterative Model and Rapid Application Development (RAD) Model. These Software Development processes have their own Advantages and Disadvantages, and the main purpose of this paper is to explain these models and know the difference between them. Keywords: Software Development life cycle, Models, Risk Analysis, Framework, SRS.

scholarly journals Software Development Life Cycle Models-A Comparative Study

2020 ◽  
pp. 30-37
Author(s):  
Gagan Gurung ◽  
Rahul Shah ◽  
Dhiraj Prasad Jaiswal
Keyword(s):  
Software Development ◽  
Small Firms ◽  
Development Process ◽  
Software Development Process ◽  
Advantages And Disadvantages ◽  
Step Procedure ◽  
Development Life Cycle ◽  
Software Development Life Cycle ◽  
Traditional Work

Software Development is one of the most powerful, vital, and the need for an hour in today's generation. Every organization, industries, small firms, institutes, etc. require the software for the functionality of their system and reducing the manual work or the traditional work, which used to be insecure and had more errors. SDLC is all about the minimization of the risk and failure and maximization of the quality of the product. To make the development works in a step by step procedure and precisely SDLC came into existence. The SDLC defines the framework that includes different activities and tasks to be carried out during the software development process. There are many types of SDLC models, which have their advantages and disadvantages and will work as per their needs.

scholarly journals An Automated Testing Model using Test Driven Development Approach

2017 ◽  
Vol 10 (2) ◽  
pp. 385-390
Author(s):  
C.P Patidar ◽  
Arun Dongre
Keyword(s):  
Software Development ◽  
Software Testing ◽  
Automobile Industry ◽  
Development Process ◽  
Web Applications ◽  
Automated Testing ◽  
Software Development Process ◽  
Test Driven Development ◽  
Testing Model ◽  
Development Approach

Today we live in the era of software and web applications. Software is used in every minor and major field. In defense, medical, education, research, government, administration and much other field software became a necessary part. Software also brings transparency in the systems. Software also makes people’s life easy and comfortable. Software testing is a very important part of any software development process. Software testing requires approximately forty percent budget of any software development process. Like in an automobile industry every vehicle is tested before it goes to the customer. Also in software testing it is must to test the software before deployment. Because if software deployed without testing then user will face the bug and user will be unhappy with the software. In this paper we compare manual and automated testing and proposed an automated testing model with test driven development (TDD).

Historical Experience of Criminalization: to the Centenary of the Guiding Principles on Criminal Law of the RSFSR

2019 ◽  
pp. 31-35
Author(s):  
Ivan Kozachenko
Keyword(s):  
Criminal Law ◽  
Criminal Code ◽  
Historical Experience ◽  
Law System ◽  
Political Situation ◽  
Historical Method ◽  
Advantages And Disadvantages ◽  
Concept Planning ◽  
Guiding Principles ◽  
Definition Of

The creation of the Guiding Principles on the Criminal Law of the RSFSR of 1919 is studied taking into account extremely complicated internal and external political situation in the country at the beginning of the twentieth century. Using the methods of analysis, synthesis, as well as comparative and historical method, the author determines the significance of the Guiding Principles in the law system of the young Soviet state. Some key norms of the document are examined. In particular, the definition of criminal law is analyzed and its advantages and disadvantages are identified. It is noted that the definition of a crime was formulated too broadly, and more significant steps in criminalization of different acts were made with the adoption of the RSFSR Criminal Code of 1922. It is indicated which persons were not punished according to the Guidelines. Attention is drawn to the way in which such a method of protection as necessary defense was set forth in this act. The Guiding Principles are not without certain disadvantages: for example, the institution of complicity is not sufficiently disclosed, there is lexical redundancy in the definition of the concept «planning the offence». However, the discrepancies between the main provisions covered in the Guidelines are explainable and excusable, taking into account the historical situation at the time of their adoption. The analyzed document became the basis for Russian criminal law, and some of its provisions are still relevant.

Sign in / Sign up

Export Citation Format

Share Document