Automated Web Applications Testing

Unit tests are a vital part of several software development practices and processes such as Test-First Programming, Extreme Programming and Test-Driven Development. This article shortly presents the software quality and testing concepts as well as an introduction to an automated unit testing framework for PHP web based applicationssoftware quality, continuous integration, unit testing

Modeling the object-oriented software process: OPEN and the unified process

A short introduction to software process modeling is presented, particularly object-oriented modeling. Two major industrial process models are discussed: the OPEN model and the Unified Process model. In more detail, the quality assurance in the Unified Process tool (formally called Objectory) is reviewed

Dealing with Fuzzy Information in Software Design Methods

Software design methods incorporate a large set of heuristic rules that should result in stable software architecture of high quality. In general, clearly defined inputs are required to deliver the desired results. Unfortunately, especially in the early phases of software development, it is very difficult or even impossible to provide precisely defined information. Since methods cannot deal with imprecision, the designers need to make approximations which are generally not justifiable. In this paper, we will advocate an approach where the inputs for software design methods are modeled by using fuzzy sets. This approach renders the need for introduction of extra information for removal of inexactness obsolete

The Synonym management process in SAREL

The specification phase is one of the most important and least supported parts of the software development process. The SAREL system has been conceived as a knowledge-based tool to improve the specification phase. The purpose of SAREL (Assistance System for Writing Software Specifications in Natural Language) is to assist engineers in the creation of software specifications written in Natural Language (NL). These documents are divided into several parts. We can distinguish the Introduction and the Overall Description as parts that should be used in the Knowledge Base construction. The information contained in the Specific Requirements Section corresponds to the information represented in the Requirements Base. In order to obtain high-quality software requirements specification the writing norms that define the linguistic restrictions required and the software engineering constraints related to the quality factors have been taken into account. One of the controls performed is the lexical analysis that verifies the words belong to the application domain lexicon which consists of the Required and the Extended lexicon. In this sense a synonym management process is needed in order to get a quality software specification. The aim of this paper is to present the synonym management process performed during the Knowledge Base construction. Such process makes use of the Spanish Wordnet developed inside the Eurowordnet project. This process generates both the Required lexicon and the Extended lexicon that will be used during the Requirements Base construction.Postprint (published version

Can using Fagan Inspections improve the quality of specification in 2011? A Case Study

In this paper, we explore why Fagan Inspections have become obsolete in the software industry, given the body of evidence which supports their use to improve the quality of software artefacts and the software development process. Since the late 1970’s, much has been written about how Fagan Inspections improve the quality of both processes and outputs of the software development process. The literature indicates that the Fagan Inspection technique can improve quality of software (or other software development artefacts) by a reduction in defects of 60 – 90%. However, recent literature suggests that inspection techniques in general and Fagan Inspections in particular, are no longer used. A study in 1998 found that respondents used inspections either irregularly or not at all. Teams often review artefacts informally, but believe that they are performing an inspection or formal review. The lack of rigour in the review process results in reduced benefits and more defects in the artefacts. To explore this situation, we conducted a case study with a local enterprise and we report on the early findings. These suggest that the introduction of Fagan Inspections may have a number of benefits before they have even been introduced fully, including recognition of flaws in the current development process, development of technical knowledge relating to the software process domain, and improved team relations and a ‘quality’ culture. In addition, the personnel using Fagan Inspection gain experience in the production of ‘quality’ artefacts

Relationship Determinants between AI Technology Adoption Behavior and Performance of Software Enterprises

With the continuous progress of science and technology, the arrival of artificial intelligence subverts the traditional industries. Enterprises urgently need to carry out technological innovation to reduce costs. The introduction of artificial intelligence technology can reduce workload and improve development efficiency for software enterprises. Reduce operating costs. This paper takes the software enterprise as the research object, takes the artificial intelligence as the independent variable and the software development cost as the dependent variable. The hypothesis is proposed through the four intermediate variables of development efficiency, management innovation, product quality, labor force and the degree of introduction of artificial intelligence. A total of 332 valid questionnaires were collected by using electronic questionnaires. The sample data are analyzed by Smartpls 3.0 software, and the data are analyzed by Algorithm, Bootstrapping, cross multiplication, structural equation and other methods. The results show that AI has a significant positive impact on software development cost, a significant positive impact on product quality, a significant positive impact on labor force, a significant positive impact on development efficiency, a significant positive impact on management innovation, and a significant positive impact on software development cost. Labor has a significant positive impact on software development costs. Development efficiency has a significant positive impact on software development cost. Management innovation has a significant positive impact on software development cost. Product quality plays an intermediary role between the introduction of artificial intelligence and the cost of software development. Development efficiency also plays an intermediary role between the introduction of artificial intelligence and the cost of software development. From the research, we know that the introduction of AI can enrich the theories of process reengineering, process optimization and management decision-making, and can also find the factors that affect output performance from the perspective of technological innovation to provide reference for future research

The Private Value of Software Patents

We investigate the value creation or destruction associated with the introduction of software patents in the United States in two ways. The first looks at the cumulative abnormal returns to Information and Communication Technology (ICT) firms around the time of important court decisions that impacted software patents, and the second analyzes the relationship between firms’ stock market value, the sector in which they operate, and their holdings of software patents. We conclude that the market evaluated software patents as a negative development ex ante. Ex post, a greater number of firms in all ICT sectors invested in these patents, and these firms had slightly higher market values than those with no software patents. However, while we obtain clear evidence that the technological importance or quality of patented innovation mattered for the market value of hardware firms both before and after the legal changes, it is less clear that the marginal patent right per se was associated with increases in market value, and there are no significant valuation effects associated with patents for pure software firms after the change.