Requirements change: What's the alternative?

Numerous studies have shown that a software project's cost, schedule and defect density escalate as the rate of requirements change increases. Yet none of these studies have explored the effects of not making requirements changes in response to changes in user needs. This paper explains why a project incurs just as much, if not more, risk when requirements changes are suppressed. © 2008 IEEE

Metrics for Dynamics: How to Improve the Behaviour of an Object Information System

If we ask about which is the main difference between modelling a system using a traditional model like the entity relationship model or an object oriented model, from our point of view the answer is that, in the first one, the processes are not located somewhere, and, in the second one, the processes (operations or methods) are encapsulated in classes. The choice of the right classes to home every operation is essential for the behaviour of the system. It is totally useless to design a well built system, according to a lot of statics metrics, if the system does not run well after. In other words, dynamic metrics allowing to evaluate the behaviour of a system when it runs are much more useful than any static metrics used to tell if the system is correctly built or not. According to this, we propose in this paper, a new approach to evaluate a priori the behaviour of a system, by taking into account the notion of event cost and the notion of time (which is obviously essential). The final goal of this approach is to deliver information on the way operations have to be placed in classes in order to get better performances when the system is running. However, the proposal of metrics is of no value if their practical use is not demonstrated, either by means of case studies taken from real projects or by controlled experiments. For this reason, an optimisation tool is being under construction in order to provide solutions to this proble

Tackling Traceability Challenges through Modeling Principles in Methodologies Underpinned by Metamodels.

Traceability is recognized to be essential for supporting software development. However, a number of traceability issues are still open, such as link semantics formalization or traceability process models. Traceability methodologies underpinned by metamodels are a promising approach. However current metamodels still have serious limitations. Concerning methodologies in general, three hierarchical layered levels have been identified: metamodel, methodology and project. Metamodels do not often properly support this architecture, and that results in semantic problems at the time of specifying the methodology. Another reason is that they provide extensive predefined sets of types for describing project attributes, while these project attributes are domain specific and, sometimes, even project specific. This paper introduces two complementary modeling principles to overcome these limitations, i.e. the metamodeling three layer hierarchy, and power-type patterns modeling principles. Mechanisms to extend and refine traceability models are inherent to them. The paper shows that, when methodologies are developed from metamodels based on these two principles, the result is a methodology well fitted to project features. Links semantics is also improved

Метод анализа динамики изменения требований назначения многофункциональных программно-технических систем

В работе приведена модель системы требований назначения в виде изменяемой иерархии функциональных компонентов, введен показатель динамики изменения требований назначения многофункциональных систе

A Mixed Mode Analysis of the Impact of Requirement Volatility on Software Project Success

Requirement volatility has been identified as a significant risk factor behind software project success. This paper describes our findings of a 2-phase study comprising of interviews and surveys on the preparedness of organizations in managing requirement volatility and the resultant effect on project success and failure. Findings illuminate on the current level of awareness and management response to the problem of requirement volatility affecting software projects. The subjective treatment of project success/failure is brought out, and the association with requirement volatility is explored. Results are expected to lead to better governance mechanisms and improve project success rates under requirement volatility

Towards a framework for improving goal-oriented requirement models quality

Goal-orientation is a widespread and useful approach to Requirements Engineering. However, quality assessment frameworks focused on goal-oriented processes are either limited or remain on the theoretical side. Requirements quality initiatives range from simple metrics applicable to requirements documents, to general-purpose quality frameworks that include syntactic, semantic and pragmatic concerns. In some recent works, we have proposed a metrics framework for goal-oriented models, but the approach did not cover the cycle of quality assessment. In this paper we present a semiotic-based quality assessment proposal built upon the i* framework and the SEQUAL proposal. We propose a simplification of SEQUAL which can be applied to i* models by defining semantic, pragmatic and social metrics. As a result, we obtain suites of metrics that can be applied to i* goal-oriented requirements models. This theoretical work is put into practice by using iStarML, a XML representation of i* models, over which XQuery sentences compute the proposed metrics.Peer ReviewedPostprint (published version

Software Engineering Tools For Secure Application Development

Software security has become a crucial part of an organization’s overall security strategy due to increasingly sophisticated attacks at the application layer. One of the major concerns in software engineering is the inadequate use of secure software development methods and tools. Such deficiency is caused by a lack of knowledge and training on available secure tools among software developers. This project conducts a thorough investigation of the tools that can be used by developers throughout the software development life cycle to assist in the development of secure applications, including tools used by individuals and teams, classified by open-source or commercial, tools based on project size, etc. This paper also includes a summary table that provides a quick overview of all the tools listed for developers and individuals to use

Towards improving information quality requirements for online health information systems: A review on the recent frameworks

The recent demand of accessing online health information has increased sharply due to the mass production of information and their value strongly depends on the quality of information that is inside the content of the system. However, many of the online health information portals provide poor information quality for its users, and the main reason is that the information quality requirements weren’t included at the earliest stages of the system development process. The objective of this research is to provide a literature review on frameworks that improves the implementation of information quality requirements. At least several recent papers were searched from various sources, between 2012 to 2017. The findings show that all frameworks include the information quality requirements during the earliest phases of the system development process through various methods, so mistakes are avoided during the ongoing stages of the process. The research gives a clear understanding for practitioners and administrators about the gaps in their content that should overcome and put into consideration. © 2018 IEEE