Critical success factors for the requirements engineering process, with reference to quality management of information systems development

Preliminary research into the critical factors associated with software development/implementation identified three dimensions for successful implementation based on alignment of the requirements engineering process with business needs, change management process and quality of the implementation process. Research results demonstrate the link between the conceptual model for process quality and the process management attributes determined during the research.

Software reliability growth models based on local polynomial modeling with kernel smoothing

Software reliability growth models (SRGMs) are extensively employed in software engineering to assess the reliability of software before their release for operational use. These models are usually parametric functions obtained by statistically fitting parametric curves, using Maximum Likelihood estimation or Least–squared method, to the plots of the cumulative number of failures observed N(t) against a period of systematic testing time t. Since the 1970s, a very large number of SRGMs have been proposed in the reliability and software engineering literature and these are often very complex, reflecting the involved testing regime that often took place during the software development process. In this paper we extend some of our previous work by adopting a nonparametric approach to SRGM modeling based on local polynomial modeling with kernel smoothing. These models require very few assumptions, thereby facilitating the estimation process and also rendering them more relevant under a wide variety of situations. Finally, we provide numerical examples where these models will be evaluated and compared.

Performance analysis for object-oriented software: a systematic mapping

Performance is a crucial attribute for most software, making performance analysis an important software engineering task. The difficulty is that modern applications are challenging to analyse for performance. Many profiling techniques used in real-world software development struggle to provide useful results when applied to large-scale object-oriented applications. There is a substantial body of research into software performance generally but currently there exists no survey of this research that would help identify approaches useful for object-oriented software. To provide such a review we performed a systematic mapping study of empirical performance analysis approaches that are applicable to object-oriented software. Using keyword searches against leading software engineering research databases and manual searches of relevant venues we identified over 5,000 related articles published since January 2000. From these we systematically selected 253 applicable articles and categorised them according to ten facets that capture the intent, implementation and evaluation of the approaches. Our mapping study results allow us to highlight the main contributions of the existing literature and identify areas where there are interesting opportunities. We also find that, despite the research including approaches specifically aimed at object-oriented software, there are significant challenges in providing actionable feedback on the performance of large-scale object-oriented applications.

Performance appraisal of software testers

Context To determine the effectiveness of software testers a suitable performance appraisal approach is necessary, both for research and practice purposes. However, review of relevant literature reveals little information of how software testers are appraised in practice. Objective (i) To enhance our knowledge of industry practice of performance appraisal of software testers and (ii) to collect feedback from project managers on a proposed performance appraisal form for software testers. Method A web-based survey with questionnaire was used to collect responses. Participants were recruited using cluster and snowball sampling. 18 software development project managers participated. Results We found two broad trends in performance appraisal of software testers - same employee appraisal process for all employees and a specialized performance appraisal method for software testers. Detailed opinions were collected and analyzed on how performance of software testers should be appraised. Our proposed appraisal approach was generally well-received. Conclusion Factors such as number of bugs found after delivery and efficiency of executing test cases were considered important in appraising software testers' performance. Our proposed approach was refined based on the feedback received.

An empirical investigation of personality traits of software testers

Software testing is the process of an execution based investigation of some aspects of the software's quality. The efficiency of the process depends on the methods and technologies used, but crucially also on the human testers. Software testers typically attempt to anticipate and expose ways software may be defective, a fundamentally different task set to those of other software development practitioners. This raises the question of whether the personality of software testers may be different to other people involved in software development. To test this hypothesis, we collected personality profiles using the big five factor model of around 200 software development practitioners. Analysis of this data indicates that software testers are significantly higher on the conscientiousness factor than other software development practitioners, while other factors remain broadly consistent.

The effect of software engineers' personality traits on team climate and performance: a systematic literature review

Context Over the past 50 years numerous studies have investigated the possible effect that software engineers' personalities may have upon their individual tasks and teamwork. These have led to an improved understanding of that relationship; however, the analysis of personality traits and their impact on the software development process is still an area under investigation and debate. Further, other than personality traits, "team climate" is also another factor that has also been investigated given its relationship with software teams' performance. Objective The aim of this paper is to investigate how software professionals' personality is associated with team climate and team performance. Method In this paper we detail a Systematic Literature Review (SLR) of the effect of software engineers' personality traits and team climate on software team performance. Results Our main findings include 35 primary studies that have addressed the relationship between personality and team performance without considering team climate. The findings showed that team climate comprises a wide range of factors that fall within the fields of management and behavioral sciences. Most of the studies used undergraduate students as subjects and as surrogates of software professionals. Conclusions The findings from this SLR would be beneficial for understanding the personality assessment of software development team members by revealing the traits of personality taxonomy, along with the measurement of the software development team working environment. These measurements would be useful in examining the success and failure possibilities of software projects in development processes. General terms Human factors, performance.

Negotiating meaning: Effects of group dynamics on information system development.

The research explored the impacts that the psychological processes within and between work groups had on software development and IS project failure. It has identified and demonstrated ways to moderate such group dynamics and their causes; in turn providing an approach to reduce IS project failure.

Accessing database information using mobile agents

Many real-world applications on the Internet require accessing database information and typical technology employed is client/server plus Web (C/S + Web). Although past few years saw many success applications by using this technique, there are still some drawbacks that need to be overcome. One of the drawbacks is that the transaction often fails if the network connection is unstable. Another disadvantage is high bandwidth requirement and latency. This paper argues that mobile agent technology provide an easy way to overcome the shortcomings in CIS + Web in database access on the Internet. A success case study using mobile agents to admit new students to China's institutions is then presented. The mobile agent was created by using IBM's Aglets Software Development Kit (SDK). Based on the experimental results, it is evident that mobile agent technology is well suited for such applications.

Managing the requirements engineering process

Process management is a crucial issue in developing information or computer systems. Theories of software development process management suggest that the process should be supported and managed based on what the process really is. However, our learning from an action research study reveals that the requirements engineering (RE) process differs significantly from that which the current literature tends to describe. The process is not a systematic, smooth and incremental evolution of the requirements model, but involves occasional simplification and restructuring of the requirements model. This revised understanding of the RE process suggests a new challenge to both the academic and industrial communities, demanding new process management approaches. In this paper, we present our understanding of the RE process and its implications for process management.

Managing the requirements engineering process

Process management is a crucial issue in developing information or computer systems. Theories of software development process management suggest that the process should be supported and managed based on what the process really is. However, our learning from an action research study reveals that the requirements engineering (RE) process differs significantly from what the current literature tends to describe. The process is not a systematic, smooth and incremental evolution of the requirements model, but involves occasional simplification and restructuring of the requirements model. This revised understanding of the RE process suggests a new challenge to both the academic and industrial communities, demanding new process management approaches. In this paper, we present our understanding of the RE process and its implications for process management.

Providing process for projects in capstone courses

Our capstone course has undergone a number of evolutionary changes over the past few years. It was restructured to provide more realistic experiential learning with the introduction of larger software development projects involving 'real clients (sponsors)' and larger student teams with a mix of students across disciplines. We have introduced a project management focus into the course that allows for a more structured process of product development. This restructure was possible because the curriculum prior to the project course emphasized teamwork and project management.

This paper provides some background about our capstone course and the significance of the contribution made by two other courses taken earlier in the programme.

A reactive system architecture for building fault-tolerant distributed applications

Most fault-tolerant application programs cannot cope with constant changes in their environments and user requirements because they embed policies and mechanisms together so that if the policies or mechanisms are  changed the whole programs have to be changed as well. This paper presents a reactive system approach to overcoming this limitation. The reactive system concepts are an attractive paradigm for system design, development and maintenance because they separate policies from mechanisms. In the paper we propose a generic reactive system architecture and use group communication primitives to model it. We then implement it as a generic package which can be applied in any distributed applications. The system performance shows that it can be used in a distributed environment effectively.

Project quality management in virtual environments : a primer

The rise of geographically dispersed project teams enabled by technology has made project quality management a significant challenge for organizations. This paper uses findings from a project on geographically dispersed, cooperating SMEs in the building trade, to explore whether concepts and artefacts from the Rational Unified Process® (RUP®) software development approach could be adapted and used to better manage quality in virtual projects. Our future research aims to explore the use of RUP artefacts in a virtual environment and their impact on
project management and quality.

Technologies and considerations for developing internet and multiplayer computer games: a tutorial (extended abstract)

Games are universal and probably as old as humankind. Today the development of computer technology, especially the development of fast networks and the Internet, brings games a faster growth than ever before. Game design and development is now a fast-growing entertainment field, with a lot to offer professionally and creatively. In fact, from IT professional’s point of view, creating computer games provides us with all the usual technical challenges associated with software development, such as requirement analysis, architectural design, rapid prototyping, HCI, parallel and distributed processing, code reuse, programming, performance evaluation, testing and maintenance. It also provides challenges on other exciting aspects, such as storyboarding, screenplays, illustration, animation, sound effects, music, and social impact. By developing a computer game from start to finish, one would be able to acquire multi-disciplinary knowledge to become an IT professional for the modern era.

Exploring the cultural and social impacts on the requirements engineering processes-highlighting some problems challenging virtual team relationships with clients

Abstract:

Requirements engineering is a crucial phase in software development. Software development in a virtual domain adds another dimension to the process of requirements engineering. There has been growing interest in virtual teams, and more specifically in virtual software development. While structured software development methods are the obvious first choice for project managers to ensure a virtual software development team remains on track, the social and cultural aspects of requirements engineering cannot be ignored. These social aspects are especially important across different cultures, and have been shown to affect the success of an information system. The discussion in this paper is centred around the requirements engineering processes of a virtual team in a Thai Software House. This paper explains the issues and challenges of requirements engineering in a virtual domain from a social and cultural perspective. Project managers need to encourage a balance between structured methods and social aspects in requirements engineering for virtual team members. Cultural and social aspects influence the relationship between the virtual team and the client.