<?xml version="1.0" encoding="UTF-8"?>
<rss xmlns:dc="http://purl.org/dc/elements/1.1/" version="2.0">
<channel>
<title>Argentine Symposium on Software Engineering (ASSE 2002)</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/182989</link>
<description/>
<pubDate>Tue, 10 Nov 2026 22:15:24 GMT</pubDate>
<dc:date>2026-11-10T22:15:24Z</dc:date>
<item>
<title>CMMI, is it a new Model or is the CMM evolution?</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183107</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
This abstract discusses the evolution of the Capability Maturity Model (CMM) into the Capability Maturity Model Integration (CMMI), highlighting its advantages and challenges. ​ The CMM, widely used since the early 1990s, has proven effective in improving productivity, quality, and cycle time in software projects, particularly addressing issues in levels 2 and 3. ​ However, it has limitations, such as ambiguous metrics and lack of coverage in certain areas.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183107</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>This abstract discusses the evolution of the Capability Maturity Model (CMM) into the Capability Maturity Model Integration (CMMI), highlighting its advantages and challenges. ​ The CMM, widely used since the early 1990s, has proven effective in improving productivity, quality, and cycle time in software projects, particularly addressing issues in levels 2 and 3. ​ However, it has limitations, such as ambiguous metrics and lack of coverage in certain areas.</dc:description>
</item>
<item>
<title>Just-in-Time process documentation</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183106</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
High-quality process documentation is challenging to create and maintain due to its complexity, error-prone nature, and the effort required for updates and alternative views. ​ Traditional methods often result in outdated documentation by the time it is deployed. ​ This abstract introduces TeraQuest Metrics Inc.'s Process Management Capability (PMC), a suite of tools and techniques designed to produce accurate, up-to-date process documentation rapidly.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183106</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>High-quality process documentation is challenging to create and maintain due to its complexity, error-prone nature, and the effort required for updates and alternative views. ​ Traditional methods often result in outdated documentation by the time it is deployed. ​ This abstract introduces TeraQuest Metrics Inc.'s Process Management Capability (PMC), a suite of tools and techniques designed to produce accurate, up-to-date process documentation rapidly.</dc:description>
</item>
<item>
<title>AgEnD: Agility Enhanced Development</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183105</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
This paper describes an agile methodology with a strong emphasis towards peopleware and knowledge management. The methodology, called AgEnD, enables frequent deliveries, customer satisfaction, and quality products. The process achieves agility by creating strong team dynamics, allowing people to fully develop their skills. The principles embedded in AgEnD are but the faithful reflection of those best practices comprising the body of knowledge of software engineering.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183105</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>This paper describes an agile methodology with a strong emphasis towards peopleware and knowledge management. The methodology, called AgEnD, enables frequent deliveries, customer satisfaction, and quality products. The process achieves agility by creating strong team dynamics, allowing people to fully develop their skills. The principles embedded in AgEnD are but the faithful reflection of those best practices comprising the body of knowledge of software engineering.</dc:description>
</item>
<item>
<title>Knowledge management: an opportunity for the industrial production of software</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183102</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
This abstract explores the critical role of Knowledge Management (KM) in enhancing the industrial production of software. It emphasizes that learning capability is the key sustainable competitive advantage in today's dynamic global market. ​KM involves identifying, organizing, and disseminating both explicit and tacit knowledge within organizations to improve decision-making, efficiency, and quality. The ultimate goal is to achieve higher value-added products and services through efficient knowledge reuse and process maturity.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183102</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>This abstract explores the critical role of Knowledge Management (KM) in enhancing the industrial production of software. It emphasizes that learning capability is the key sustainable competitive advantage in today's dynamic global market. ​KM involves identifying, organizing, and disseminating both explicit and tacit knowledge within organizations to improve decision-making, efficiency, and quality. The ultimate goal is to achieve higher value-added products and services through efficient knowledge reuse and process maturity.</dc:description>
</item>
<item>
<title>Applying use cases in the real world: a case study</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183101</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
This experience report describes how a credit card processor company is applying use cases in real software projects.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183101</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>This experience report describes how a credit card processor company is applying use cases in real software projects.</dc:description>
</item>
<item>
<title>Software maintenance in Argentina: 2001 status</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183098</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
In the following communication the result of a survey exploring the software maintenance status in Argentina is presented. Responses describing major problems and preferred changes in MIS organizations were classified into general categories and compared with previous similar studies. Important questions regarding effort allocation and other decisions regarding maintenance activities are analyzed, generating possible explanations for the current status of maintenance practices in Argentina.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183098</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>In the following communication the result of a survey exploring the software maintenance status in Argentina is presented. Responses describing major problems and preferred changes in MIS organizations were classified into general categories and compared with previous similar studies. Important questions regarding effort allocation and other decisions regarding maintenance activities are analyzed, generating possible explanations for the current status of maintenance practices in Argentina.</dc:description>
</item>
<item>
<title>An extension of UML activity graph meta-model based on the workflow meta-model</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183097</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
The WfMC (Workflow Management Coalition) proposed an standard to unify the format of the definitions of workflow processes. Such standard is defined by a basic meta-model and a language for workflow process definition (WPDL) based on the same meta-model. On the other hand, the UML activity graph notation is used to model a business process, but it has a certain level of abstraction. Some details can not be modeled, others can represent ambiguities and/or inconsistencies. Therefore, a process specification based on activity graphs can not satisfy the standard of the WfMC. We propose an extension of the activity graph to overcome this deficiency without modifying the UML standart. The models based on this extension will be easily translated to the standard of Workflow. In this paper we show the extension of the UML activity graph meta-model for workflow activities and in particular for Implementation and Subflow activities. We chose this entity because it extension is a good examples of how the Workflow meta-model extends the expressive power of UML activity graph and reduce it ambiguity.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183097</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>The WfMC (Workflow Management Coalition) proposed an standard to unify the format of the definitions of workflow processes. Such standard is defined by a basic meta-model and a language for workflow process definition (WPDL) based on the same meta-model. On the other hand, the UML activity graph notation is used to model a business process, but it has a certain level of abstraction. Some details can not be modeled, others can represent ambiguities and/or inconsistencies. Therefore, a process specification based on activity graphs can not satisfy the standard of the WfMC. We propose an extension of the activity graph to overcome this deficiency without modifying the UML standart. The models based on this extension will be easily translated to the standard of Workflow. In this paper we show the extension of the UML activity graph meta-model for workflow activities and in particular for Implementation and Subflow activities. We chose this entity because it extension is a good examples of how the Workflow meta-model extends the expressive power of UML activity graph and reduce it ambiguity.</dc:description>
</item>
<item>
<title>Conceptual design of a temporal data warehouse</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183096</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
In a data warehouse, time is one of the dimensions for the analysis, but it refers to the moment in which the transaction was made, it does not explain in detail how the attributes or relationship involved in the transactions change. We are proposing a multidimensional schema that includes not only the main fact of analysis but also the temporal schemas, which did not belong to a hierarchy within the dimensions, but will register the variation of certain attributes and relationships. To build this schema, we are proposing an expansion of the algorithm that will allow to build the conceptual design of a data warehouse semi-automatically from a temporal entity-relationship model. We will unite in one model the multidimensional schema and the temporal schema to allow the registration and analysis of temporal variations and queries about the multidimensional structure.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183096</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>In a data warehouse, time is one of the dimensions for the analysis, but it refers to the moment in which the transaction was made, it does not explain in detail how the attributes or relationship involved in the transactions change. We are proposing a multidimensional schema that includes not only the main fact of analysis but also the temporal schemas, which did not belong to a hierarchy within the dimensions, but will register the variation of certain attributes and relationships. To build this schema, we are proposing an expansion of the algorithm that will allow to build the conceptual design of a data warehouse semi-automatically from a temporal entity-relationship model. We will unite in one model the multidimensional schema and the temporal schema to allow the registration and analysis of temporal variations and queries about the multidimensional structure.</dc:description>
</item>
<item>
<title>A prototype for data integration between case tools</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183095</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
his paper presents a solution for data integration between CASE (Computer Aided Software Engineering) tools by using XML (eXtensible Markup Language) documents. The propose makes possible the conversion of an XML document, generated by one CASE tool, in another XML document, that can be read by another CASE tool. To make this conversion possible it is necessary to read sample XML documents from each CASE tool, associate their equivalent structures, generate a transformation script, and finally execute the conversion. In this work we present the specifications, the architecture and the implementation of a prototype (named InterCASE) that supports the XML conversion between CASE tools.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183095</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>his paper presents a solution for data integration between CASE (Computer Aided Software Engineering) tools by using XML (eXtensible Markup Language) documents. The propose makes possible the conversion of an XML document, generated by one CASE tool, in another XML document, that can be read by another CASE tool. To make this conversion possible it is necessary to read sample XML documents from each CASE tool, associate their equivalent structures, generate a transformation script, and finally execute the conversion. In this work we present the specifications, the architecture and the implementation of a prototype (named InterCASE) that supports the XML conversion between CASE tools.</dc:description>
</item>
<item>
<title>A web-based reflective architecture for process support environment</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183093</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
In this paper we present the WRAPPER: a Web-based Reflective Architecture for Process suPport EnviRonment. The base level of the reflective architecture is compound by objects representing the various components involved in a process specification, as well as, the elements of the software development environment. The meta-level is compound of meta-objects that are activated by message flows between the base level objects during the process enactment. The meta-objects can collect data about the process, and they can even change the behavior of the base level objects and consequently change the own process. Additionally, to achieve an integrated environment, the architecture provides facilities to aggregate remote CASE tools from different platforms. The WRAPPER uses the Web as its platform and it provides mechanisms to define and to control distributed objects (and meta-objects) over the Web, based on a CORBA middleware. As benefits, the architecture provides: flexibility for controlling and adapting the process, distribution of the environment in the Web; and heterogeneity for aggregating different components to the environment. We present the structure of the reflective architecture, as well as, the implemented prototype of the process support environment.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183093</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>In this paper we present the WRAPPER: a Web-based Reflective Architecture for Process suPport EnviRonment. The base level of the reflective architecture is compound by objects representing the various components involved in a process specification, as well as, the elements of the software development environment. The meta-level is compound of meta-objects that are activated by message flows between the base level objects during the process enactment. The meta-objects can collect data about the process, and they can even change the behavior of the base level objects and consequently change the own process. Additionally, to achieve an integrated environment, the architecture provides facilities to aggregate remote CASE tools from different platforms. The WRAPPER uses the Web as its platform and it provides mechanisms to define and to control distributed objects (and meta-objects) over the Web, based on a CORBA middleware. As benefits, the architecture provides: flexibility for controlling and adapting the process, distribution of the environment in the Web; and heterogeneity for aggregating different components to the environment. We present the structure of the reflective architecture, as well as, the implemented prototype of the process support environment.</dc:description>
</item>
<item>
<title>The Ubiquitous Broker Environment (TUBE): an architecture for protocol-level systems integration</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183091</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
The fundamental goal of systems integration is to allow diverse, often independently developed software to be integrated for a common purpose. This need for integration stemms from the dynamics of business and technology, as businesses expand, take over other businesses, or join in partnerships and alliances. The new business opportunities afforded by the new technologies are realised with the deployment of new software systems, and with the opporunity for existing systems to use data and functions of other systems. In this environment, the central focus of the integration should be to provide a framework to allow heterogeneous systems to seamlessly inter-operate. A number of solutions, ranging from infrastructure to systems architecture, have been developed over the years, but they generally lack wide applicability and ease of use. This paper describes the architecture of a system prototype being implemented to more simply effect protocol-level integration of computer systems using heterogeneous middleware technologies. The approach taken is declarative, that is, simple declarative procedures should be required to adapt the system to a new or altered middleware platform, with the main objective of avoiding avoid changes to applications if the middleware platform changes.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183091</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>The fundamental goal of systems integration is to allow diverse, often independently developed software to be integrated for a common purpose. This need for integration stemms from the dynamics of business and technology, as businesses expand, take over other businesses, or join in partnerships and alliances. The new business opportunities afforded by the new technologies are realised with the deployment of new software systems, and with the opporunity for existing systems to use data and functions of other systems. In this environment, the central focus of the integration should be to provide a framework to allow heterogeneous systems to seamlessly inter-operate. A number of solutions, ranging from infrastructure to systems architecture, have been developed over the years, but they generally lack wide applicability and ease of use. This paper describes the architecture of a system prototype being implemented to more simply effect protocol-level integration of computer systems using heterogeneous middleware technologies. The approach taken is declarative, that is, simple declarative procedures should be required to adapt the system to a new or altered middleware platform, with the main objective of avoiding avoid changes to applications if the middleware platform changes.</dc:description>
</item>
<item>
<title>AXIS – a data exchange architecture among heterogeneous data sources using XML documents</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183089</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
XML is quickly becoming the industry standard data exchange format for business applications. Since most of the data is stored in relational tables, there must be a way to transform relational data into XML. A problem that arises is the heterogeneity of the business partner’s databases that are involved in the process. For a XML document to be readable for every business associate relational database, a mapping must be provided to specify how a XML document fits a specific database model. This paper proposes an architecture (AXIS – Automatic XML Interchange System) that allows the creation of such mapping and, afterwards, the conversion of relational data to XML and back to relational data.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183089</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>XML is quickly becoming the industry standard data exchange format for business applications. Since most of the data is stored in relational tables, there must be a way to transform relational data into XML. A problem that arises is the heterogeneity of the business partner’s databases that are involved in the process. For a XML document to be readable for every business associate relational database, a mapping must be provided to specify how a XML document fits a specific database model. This paper proposes an architecture (AXIS – Automatic XML Interchange System) that allows the creation of such mapping and, afterwards, the conversion of relational data to XML and back to relational data.</dc:description>
</item>
<item>
<title>Guidelines for applying XP in a CMM Level 5 organization</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183087</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
The Capability Maturity Model for Software (CMM or SW-CMM) is a framework that describes all the key elements that a process must have in order to be effective, it is organized based on five levels of maturity and covers planning, engineering and management practices for software development and maintenance. It is an incremental path for improvement based on the maturity levels of the model. This model has become an industry standard for Software Development. However, some practitioners look at CMM as a very complex model to be applied to small projects, so applying lightweight methodologies is seen as a way of overcoming this problem. Extreme Programming (XP) constitutes one of the most widely used lightweight methodologies, enabling the development of small projects in record time, fostering total customer satisfaction and being a strong alternative when short cycle time and high quality are sought in a Software project. Nevertheless, at first sight it seems controversial to apply XP in a CMM Level 5 organization, mainly because using XP for software development in a process improvement environment barely touches the management and organizational issues that the Software CMM emphasizes. On the other hand, XP supporters claim that there is a potential possibility of XP losing its characteristics when working on a rigid structure such as CMM. The aim of the paper is to show the possible integration of XP method under the CMM framework. This paper briefly introduces the CMM model and the XP methodology, and gives some guidelines for CMM Level 5 organizations to apply XP to small projects, specifying how CMM KPAs’ goals can be fulfilled even when a lightweight methodology such as XP is being used.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183087</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>The Capability Maturity Model for Software (CMM or SW-CMM) is a framework that describes all the key elements that a process must have in order to be effective, it is organized based on five levels of maturity and covers planning, engineering and management practices for software development and maintenance. It is an incremental path for improvement based on the maturity levels of the model. This model has become an industry standard for Software Development. However, some practitioners look at CMM as a very complex model to be applied to small projects, so applying lightweight methodologies is seen as a way of overcoming this problem. Extreme Programming (XP) constitutes one of the most widely used lightweight methodologies, enabling the development of small projects in record time, fostering total customer satisfaction and being a strong alternative when short cycle time and high quality are sought in a Software project. Nevertheless, at first sight it seems controversial to apply XP in a CMM Level 5 organization, mainly because using XP for software development in a process improvement environment barely touches the management and organizational issues that the Software CMM emphasizes. On the other hand, XP supporters claim that there is a potential possibility of XP losing its characteristics when working on a rigid structure such as CMM. The aim of the paper is to show the possible integration of XP method under the CMM framework. This paper briefly introduces the CMM model and the XP methodology, and gives some guidelines for CMM Level 5 organizations to apply XP to small projects, specifying how CMM KPAs’ goals can be fulfilled even when a lightweight methodology such as XP is being used.</dc:description>
</item>
<item>
<title>Tools for the Implementation of LEL and Scenarios (TILS)</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183084</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
In most experiments carried out in Requirement Engineering based on the methodology suggested by Leite [Leite95], the developer invested too much time in activities that had nothing to do with the construction itself, since administration of the data obtained had to be done. In this paper a tool to support the LEL production is presented. This tool incorporates an integrated environment between the Discourse Universe, LEL and Scenarios with hypertext technology to facilitate the surfing between the different elements [Leite90]. This allows a much more flexible interaction in the surfing and administration of the data obtained which enables us to know all the vocabulary of the application domain. In addition, this tool allows the automatic generation of a list of preliminary scenarios.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183084</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>In most experiments carried out in Requirement Engineering based on the methodology suggested by Leite [Leite95], the developer invested too much time in activities that had nothing to do with the construction itself, since administration of the data obtained had to be done. In this paper a tool to support the LEL production is presented. This tool incorporates an integrated environment between the Discourse Universe, LEL and Scenarios with hypertext technology to facilitate the surfing between the different elements [Leite90]. This allows a much more flexible interaction in the surfing and administration of the data obtained which enables us to know all the vocabulary of the application domain. In addition, this tool allows the automatic generation of a list of preliminary scenarios.</dc:description>
</item>
<item>
<title>Empirical studies for validating class diagram metrics</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183082</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
The quality of class diagrams is crucial for all later design work and could be a major determinant for the quality of the software product that is finally delivered. In order to assess class diagram quality in an objective way it is necessary to have quantitative measurement instruments. This paper presents a set of metrics which measure UML class diagram structural complexity based on the use of UML relationships. Also it summarizes two controlled experiments carried out in order to corroborate if those metrics are related with UML class diagram maintainability. The findings obtained trough the experimentation reveal that most of the metrics we proposed (NAssoc, NAgg, NaggH, MaxHAgg, NGen, NgenH and MaxDIT) might be good indicators of class diagram maintainability. We cannot, however, draw such firm conclusions regarding the NDep metric.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183082</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>The quality of class diagrams is crucial for all later design work and could be a major determinant for the quality of the software product that is finally delivered. In order to assess class diagram quality in an objective way it is necessary to have quantitative measurement instruments. This paper presents a set of metrics which measure UML class diagram structural complexity based on the use of UML relationships. Also it summarizes two controlled experiments carried out in order to corroborate if those metrics are related with UML class diagram maintainability. The findings obtained trough the experimentation reveal that most of the metrics we proposed (NAssoc, NAgg, NaggH, MaxHAgg, NGen, NgenH and MaxDIT) might be good indicators of class diagram maintainability. We cannot, however, draw such firm conclusions regarding the NDep metric.</dc:description>
</item>
<item>
<title>Estimating dynamic aspects of distributed software quality</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183081</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
To date, research and practice on software quality has been mainly focused on static aspects of centralised software development, that is, aspects that are resolved at compilation time for an application running on a single computer. However, advances in distributed computing technology have made it now possible to develop applications that, using appropriate communication infrastructure, are built from architectural-level components and execute on heterogeneous platforms. This introduces new possible communication types between remote components of a running application and, consequently, new design possibilities for developers of distributed systems. In this paper, we first identify standard software quality attributes that show dynamic aspects from the distributed point of view, and we focus on three efficiency, reliability and maintainability - that we argue are affected by the choice of communication type between cooperative distributed components. Then, we attempt to quantify the effect of the choice of three communication types and establish estimators in terms of the response time, or the probability of non-failure, or the mean time between changes of software components.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183081</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>To date, research and practice on software quality has been mainly focused on static aspects of centralised software development, that is, aspects that are resolved at compilation time for an application running on a single computer. However, advances in distributed computing technology have made it now possible to develop applications that, using appropriate communication infrastructure, are built from architectural-level components and execute on heterogeneous platforms. This introduces new possible communication types between remote components of a running application and, consequently, new design possibilities for developers of distributed systems. In this paper, we first identify standard software quality attributes that show dynamic aspects from the distributed point of view, and we focus on three efficiency, reliability and maintainability - that we argue are affected by the choice of communication type between cooperative distributed components. Then, we attempt to quantify the effect of the choice of three communication types and establish estimators in terms of the response time, or the probability of non-failure, or the mean time between changes of software components.</dc:description>
</item>
<item>
<title>A taxonomy of the quality attributes for distributed applications</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183079</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
The software engineering community has paid little attention to nonfunctional requirements, or quality attributes, compared with studies performed on capture, analysis and validation of functional requirements. This circumstance becomes more intense in the case of distributed applications. In these applications we have to take into account, besides the quality attributes such as correctness, robustness, extendibility, reusability, compatibility, efficiency, portability and ease of use, others like reliability, scalability, transparency, security, interoperability, concurrency, etc. In this work we will show how these last attributes are related to different abstractions that coexist in the problem domain. To achieve this goal, we have established a taxonomy of quality attributes of distributed applications and have determined the set of necessary services to support such attributes.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183079</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>The software engineering community has paid little attention to nonfunctional requirements, or quality attributes, compared with studies performed on capture, analysis and validation of functional requirements. This circumstance becomes more intense in the case of distributed applications. In these applications we have to take into account, besides the quality attributes such as correctness, robustness, extendibility, reusability, compatibility, efficiency, portability and ease of use, others like reliability, scalability, transparency, security, interoperability, concurrency, etc. In this work we will show how these last attributes are related to different abstractions that coexist in the problem domain. To achieve this goal, we have established a taxonomy of quality attributes of distributed applications and have determined the set of necessary services to support such attributes.</dc:description>
</item>
<item>
<title>Using design patterns for a compiler modeling for posing disjunctive optimization programs</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183070</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
In this article, we describe the compiler model of a language to express disjunctions and logic propositions into mathematical optimization programs. It is linked to a mathematical modeling system, because the introduction of logic into those programs completes their capabilities. It works as a post-compilation step of the mathematical language compiler. The language for disjunctions and logic propositions is based on the proposal of Vecchietti and Grossmann (2000). In order to accomplish the objectives: independence of the mathematical system, flexibility for introducing changes into the language and easy to maintain; several software design patterns are used such as: Visitor, Composite, State and Adapter have been used for modeling the compiler. This paper describes the adaptations made to the patterns and how they help to get the goals pursued for the compiler. LogMIP is now linked to the mathematical program system GAMS. Several test are performed to check its behavior.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183070</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>In this article, we describe the compiler model of a language to express disjunctions and logic propositions into mathematical optimization programs. It is linked to a mathematical modeling system, because the introduction of logic into those programs completes their capabilities. It works as a post-compilation step of the mathematical language compiler. The language for disjunctions and logic propositions is based on the proposal of Vecchietti and Grossmann (2000). In order to accomplish the objectives: independence of the mathematical system, flexibility for introducing changes into the language and easy to maintain; several software design patterns are used such as: Visitor, Composite, State and Adapter have been used for modeling the compiler. This paper describes the adaptations made to the patterns and how they help to get the goals pursued for the compiler. LogMIP is now linked to the mathematical program system GAMS. Several test are performed to check its behavior.</dc:description>
</item>
<item>
<title>Model Refinements in the Object Oriented Software Development Process</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183068</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
In the UML specification document, several concepts are still described in an ambiguous, informal way. Such is the case of a dependency relationship between models known as: “Model Refinement”. Model Refinement is a dependency relationship that relates two elements that represent the same concept at different levels of abstraction. In order to avoid inconsistencies and wrong model interpretations, in this article we propose a formalization of the refinement relation between model elements of the same kind, such as refinement relation between Use Cases. Then on top of this formalization, we discuss refinement relation between models of different kind. The rules defined in this work form an enhancement of the UML metamodel specification. These rules should be used as a formal foundation for the construction of case tools performing consistency checking of models. Support offered by tools will improve the quality of software development process.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183068</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>In the UML specification document, several concepts are still described in an ambiguous, informal way. Such is the case of a dependency relationship between models known as: “Model Refinement”. Model Refinement is a dependency relationship that relates two elements that represent the same concept at different levels of abstraction. In order to avoid inconsistencies and wrong model interpretations, in this article we propose a formalization of the refinement relation between model elements of the same kind, such as refinement relation between Use Cases. Then on top of this formalization, we discuss refinement relation between models of different kind. The rules defined in this work form an enhancement of the UML metamodel specification. These rules should be used as a formal foundation for the construction of case tools performing consistency checking of models. Support offered by tools will improve the quality of software development process.</dc:description>
</item>
<item>
<title>Smartweaver: Aspect-Oriented Development using the Smartbooks Approach</title>
<link>http://sedici.unlp.edu.ar:80/handle/10915/183067</link>
<description>Objeto de conferencia
Simposio Argentino de Ingeniería de Software (ASSE 2002) - JAIIO 31 (Santa Fe, 9 al 13 de septiembre de 2002)
The aspect paradigm is now recognized as an important level of software development, however, the diversity of AOP approaches often requires from developers an important grasp of experience and programming skills in order to implement aspect-based functionality. AOP approaches are usually materialized in terms of specific languages or frameworks. In this work, we aim at providing smart guidance to developers to better take advantage of aspect facilities. We present an agent-based tool called Smartweaver, which allows developers to describe aspect designs using a special documentation method, and then provides assistance to translate these specifications into particular AOP implementation technologies.
</description>
<pubDate>Tue, 01 Jan 2002 00:00:00 GMT</pubDate>
<guid isPermaLink="false">http://sedici.unlp.edu.ar:80/handle/10915/183067</guid>
<dc:date>2002-01-01T00:00:00Z</dc:date>
<dc:description>The aspect paradigm is now recognized as an important level of software development, however, the diversity of AOP approaches often requires from developers an important grasp of experience and programming skills in order to implement aspect-based functionality. AOP approaches are usually materialized in terms of specific languages or frameworks. In this work, we aim at providing smart guidance to developers to better take advantage of aspect facilities. We present an agent-based tool called Smartweaver, which allows developers to describe aspect designs using a special documentation method, and then provides assistance to translate these specifications into particular AOP implementation technologies.</dc:description>
</item>
</channel>
</rss>
