{"title":"Towards a schema representation through design matrices","authors":"Santiago Gómez, Hoang Duong","doi":"10.1109/ASWEC.2005.48","DOIUrl":"https://doi.org/10.1109/ASWEC.2005.48","url":null,"abstract":"Entity-relationship diagrams and their extensions play a fundamental role for relational databases, and they are widely accepted by the database design community as standard tools for the first stages of development. However, there are a number of issues closely connected with design, including the need for more complete semantics for data domains and sophisticated constraints; the demand for easier ways to expand and evolve an existing database; and the usability of database models for both management and query planning. Being a listing of relation names and attribute names, a database schema suggests the adoption of a two-dimensional structure as a basis for modelling a new or existing database. This work introduces a representation of this type called the design matrix, with at least the same expressive power as that of an enhanced entity-relationship (EER) diagram, and capable of addressing some of the shortcomings pointed out by recent literature.","PeriodicalId":238299,"journal":{"name":"2005 Australian Software Engineering Conference","volume":"46 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-03-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"114851604","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Defining autonomic computing: a software engineering perspective","authors":"Paul Lin, Alexander MacArthur, J. Leaney","doi":"10.1109/ASWEC.2005.19","DOIUrl":"https://doi.org/10.1109/ASWEC.2005.19","url":null,"abstract":"As a rapidly growing field, autonomic computing is a promising new approach for developing large scale distributed systems. However, while the vision of achieving self-management in computing systems is well established, the field still lacks a commonly accepted definition of 'what' an autonomic computing system is. Without a common definition to dictate the direction of development, it is not possible to know whether a system or technology is a part of autonomic computing, or if in fact an autonomic computing system has already been built. The purpose of this paper is to establish a standardised and quantitative definition of autonomic computing through the application of the quality metrics framework described in IEEE Std 1061-1998. Through the application of this methodology, stakeholders were systematically analysed and evaluated to obtain a balanced and structured definition of autonomic computing. This definition allows for further development and implementation of quality metrics, which are project-specific, quantitative measurements that can be used to validate the success of future autonomic computing projects.","PeriodicalId":238299,"journal":{"name":"2005 Australian Software Engineering Conference","volume":"133 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-03-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"132434983","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"Australian software development: what software project management practices lead to success?","authors":"J. Verner, Narciso Cerpa","doi":"10.1109/ASWEC.2005.14","DOIUrl":"https://doi.org/10.1109/ASWEC.2005.14","url":null,"abstract":"We surveyed a number of Australian software practitioners in order to understand what software development practices were used in their recent software projects. We were particularly interested to discover what project management practices are common in Australian software projects. The relationship between practices and software project outcomes enables us to investigate why some projects succeed and others fail. We found that nearly 20% of projects had no lifecycle methodology and 10% of our respondents did not understand what was meant by a software development lifecycle methodology. Many recognized software practices are not being applied consistently in the projects investigated. Fifty percent of projects began with unclear requirements. Risk assessment is not normally a part of the development process and the organizations are not learning from their mistakes as post mortem reviews are much more likely to be held for successful projects than they are for unsuccessful projects.","PeriodicalId":238299,"journal":{"name":"2005 Australian Software Engineering Conference","volume":"36 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-03-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121128461","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}
{"title":"A formal description of design patterns using OWL","authors":"Jens Dietrich, Chris Elgar","doi":"10.1109/ASWEC.2005.6","DOIUrl":"https://doi.org/10.1109/ASWEC.2005.6","url":null,"abstract":"Design patterns have been used successfully in the last decade to reuse and communicate object-oriented design. However, the documentation of pattern usage is often very poor. This motivates the use of tools which can detect and document design patterns found in software. A couple of approaches have been proposed in recent years. The approach introduced is based on a formal description of design patterns using the Web ontology language OWL. Software artefacts used to define design patterns in a formal and machine processable fashion are represented by uniform resource identifiers (URIs). This yields a description that is open and extensible, and facilitates the sharing of design among software engineers. We discuss the developed software design ontology, and how this approach relates to the meta-modelling architecture of the OMG. In the second part, an effective pattern scanner for the Java language is presented. This scanner is based on the ontology developed in part one and uses reflection and AST analysis to verify constraints. Various applications of this scanner are discussed.","PeriodicalId":238299,"journal":{"name":"2005 Australian Software Engineering Conference","volume":"59 1","pages":"0"},"PeriodicalIF":0.0,"publicationDate":"2005-03-29","publicationTypes":"Journal Article","fieldsOfStudy":null,"isOpenAccess":false,"openAccessPdf":"","citationCount":null,"resultStr":null,"platform":"Semanticscholar","paperid":"121656152","PeriodicalName":null,"FirstCategoryId":null,"ListUrlMain":null,"RegionNum":0,"RegionCategory":"","ArticlePicture":[],"TitleCN":null,"AbstractTextCN":null,"PMCID":"","EPubDate":null,"PubModel":null,"JCR":null,"JCRName":null,"Score":null,"Total":0}