An investigation into the learnability of object-oriented case tools for computing education

The use of Computer Aided Software Engineering (CASE) tools for teaching object-oriented systems analysis and design (OOSAD) has many potential benefits, but there are also several problems associated with the usage of these tools. A large portion of these problems relate to the usability and learnability of these tools. Learnability is one of the most important attributes of usability and refers to the capability of the system to enable the user to learn its application. The main research question that this study aims to address is “How can the learnability of OO CASE tools for computing education in South Africa be evaluated?”. In order to answer this question several frameworks for evaluating CASE tool usability and learnability were investigated. One of these frameworks, as proposed by Senapathi, was selected as being the most appropriate for evaluating CASE tool learnability for computing education. This framework maintains that the learnability of a CASE tool is dependent on context of use factors such as the tool used, as well as user characteristics such as gender. The primary aim of this research was thus to validate Senapathi's framework for CASE tool learnability in a South African context. A secondary aim of the research was to extend the implementation of the framework in order to enable the comparison of two CASE tools and to support the inclusion of other user characteristics. An experiment was performed at the Nelson Mandela Metropolitan University (NMMU) in 2006. The participants recruited for this experiment were second year computing students at NMMU. During this experiment, the learnability of two OO CASE tools, namely IBM's Rational Software Modeller and Microsoft's Visio, was evaluated and compared. The quantitative and qualitative results supported Senapathi's results and showed that her framework could be used to evaluate CASE tool learnability and could be adapted to evaluate two CASE tools. The results also showed that the majority of the participants rated the learnability of Microsoft Visio higher for both tasks and that the main reasons participants preferred Visio was due to its simplicity, familiarity and recoverability

Towards useful and usable interaction design tools: CanonSketch

Despite all the effort dedicated to bringing better User-Centered Design (UCD) tools to market, current studies show that the industry is still dominated by tools that do not support the activities and workstyles of designers. Also, there is a growing need for interaction design tools aimed at software engineers, a problem related to bringing usability into the software engineering processes. We propose a new workstyle model that can be effectively used to envision, design and evaluate a new generation of innovative interaction and software design tools, aimed at integrating usability and software engineering. We illustrate the effectiveness of our model by describing a new tool, called CanonSketch, that was built in order to support UCD in terms of the dimensions in our workstyle model. We also describe an evaluation study aimed at contrasting paper prototyping with our tool as well as the level of workstyle support.info:eu-repo/semantics/publishedVersio

Web collaboration for software engineering

Tese de mestrado integrado. Engenharia Informática e Computação. Faculdade de Engenharia. Universidade do Porto. 200

Experimental Object-Oriented Modelling

This thesis examines object-oriented modelling in experimental system development. Object-oriented modelling aims at representing concepts and phenomena of a problem domain in terms of classes and objects. Experimental system development seeks active experimentation in a system development project through, e.g., technical prototyping and active user involvement. We introduce and examine "experimental object-oriented modelling" as the intersection of these practices

Evaluation of UML tools using an end-to-end application

Master of Science in Engineering - EngineeringAny software project goes through the different stages of a Software Development Life Cycle (SDLC). Like any other commercial product, software has a design stage but this stage is unique and critical to software due to its soft nature. A system that is given careful thought at the design phase results in a correct and complete system and adheres to software design principle. The “Unified Modelling Language” (UML) is a standard modelling language for object-oriented systems. Many tools are currently available to support the design and implementation of software. Generating skeletal code from a design brings down the implementation time considerably. This research report presents a list of criteria against which one can compare different UML tools, and puts forward a rating system where decisions can be made on them. It presents a comparison between four UML tools: ArgoUML, Rational Rose, Together Control Centre, and MasterCraft. An end-to-end application was developed on each of these tools as part of the evaluation process. During the design phase a detailed design was done using the ICONIX process. The different features of an ideal UML tool is analysed and used to evaluate the four selected tools. Of the four tools, Rational Rose, Together Control Centre, MasterCraft are offthe-shelf modelling softwares whereas ArgoUML is an open source modelling software. From the evaluation it is observed that Together Control Centre attains a high score with Rational Rose following just behind. MasterCraft comes third. Argo UML has the least score but it has the advantage of being an open source software

Can We Work Together?

People have a versatility to adapt to various situations in order to communicate with each other regardless of a person's disability. We research separate computer interfaces to support remote synchronous collaboration in two situations. First, a deaf person collaborating with a hearing person uses a shared workspace with video conferencing, such as the Facetop system. Second, a blind person collaborating with a sighted person uses our loosely coupled custom shared workspace called Deep View. The design features of the respective interfaces accommodate the disability of a deaf person or a blind person and enable communication with a person without a disability. The interfaces expand the ways in which people with disabilities participate in a collaborative task to a level of detail not possible without our interfaces. The design features of our user interfaces provide alternative channels for the collaborators with disabilities to communicate ideas or coordinate actions that collaborators without disabilities would otherwise do verbally or visually. We evaluate the interfaces through three user studies where collaborators complete full fledged tasks that require managing all aspects of communication to complete the task. Throughout the research we collaborated with members of the Deaf community and members of the blind community. We incorporated the feedback from members of these communities into the implementation of our interfaces. The members participated in our user studies to evaluate the interfaces

WARP : speeding up the software development process

Estágio realizado na Qimonda Portugal, S. ATese de mestrado integrado. Engenharia Informátca e Computação. Faculdade de Engenharia. Universidade do Porto. 200

A business analysis methodology

Synopsis Business analysis is defined as the process in which business needs are identified and solutions proposed. This process is regarded as one of the most important parts of systems development because no other part is more difficult to rectify later. However, current business analysis methodologies are inadequate because they are at a too high level and only address portions of the complete business analysis process. In particular, the lack of clear objectives, relevance and outcomes of the phases make business analysis methodologies inadequate. Moreover, activities, techniques and tools not mapped to those phases are also problematic. The aim of this research was to develop a business analysis methodology for business analysts in the South African financial services environment. The intentions were to identify the phases, as well as objectives, relevance and outcomes for each of these phases. Furthermore, this research intended to identify appropriate activities, techniques and tools to address the objectives of each phase of a methodology. This was done by presenting a literature review of previous research relating to business analysis methodologies. For information gathering, 45 participants (comprising of business analysts, project managers, IS managers and CIOs) contributed to this research, 22 of whom were interviewed individually while 23 participated in focus group interviews. The data from each of these methods was analysed independently and did not influence or feed into any of the other methods. Once the individual interviews and focus group interviews had been transcribed, content analysis and analysis within and between interviews (Merriam, 1998; Strauss, 1987) was used to analyse the information gathered independently. The phases of a business analysis methodology identified by the research are the: • feasibility phase; • business case phase; • analysis and design phase; and • post-implementation evaluation phase. Objectives, relevance and outcomes of these phases were also identified. In addition, activities, techniques and tools were mapped to each of these phases

An integrated product and process information modelling system for on-site construction

The inadequate infrastructure that exists for seamless project team communications has its roots in the problems arising from fragmentation, and the lack of effective co-ordination between stages of the construction process. The use of disparate computer-aided engineering (CAE) systems by most disciplines is one of the enduring legacies of this problem and makes information exchange between construction team members difficult and, in some cases, impossible. The importance of integrating modelling techniques with a view to creating an integrated product and process model that is applicable to all stages of a construction project's life cycle, is being recognised by the Construction Industry. However, improved methods are still needed to assist the developer in the definition of information model structures, and current modelling methods and standards are only able to provide limited assistance at various stages of the information modelling process. This research investigates the role of system integration by reviewing product and process information models, current modelling practices and modelling standards in the construction industry, and draws conclusions with similar practices from other industries, both in terms of product and process representation, and model content. It further reviews various application development tools and information system requirements to support a suitable integrated information structure, for developing an integrated product and process model for design and construction, based on concurrent engineering principles. The functional and information perspectives of the integrated model, which were represented using IDEFO and the unified modelling language (UML), provided the basis for developing a prototype hyper-integrated product and process information modelling system (HIPPY). Details of the integrated conceptual model's implementation, practical application of the prototype system, using house-building as an example, and evaluation by industry practitioners are also presented. It is concluded that the effective integration of product and process information models is a key component of the implementation of concurrent engineering in construction, and is a vital step towards providing richer information representation, better efficiency, and the flexibility to support life cycle information management during the construction stage of small to medium sized-building projects