ore than half the cost of the development of complex computer-based information systems (IS) is attributable to decisions made in the upstream portion of the software development process; namely, requirements specification and design [20]. There is growing recognition that research on how teams actucilly go about making requirement determinations and design decisions can provide valuable insights lor improving the quality and productivity of large-scale computer-based IS development efforts [9,12,23]. Traditional models of group dynamics, group decision making, and group development are not rich enough to thoroughly explain the real-world complexities faced by software design teams. Most of this research was performed on tasks that were shorter, less complex and did not require the extensive integration of knowledge domains that characterizes soltware systems design [9,12].Knowledge is the raw material of software design teams. For complex projects, knowledge from multiple technical and functional domains is a necessity [12]. Ideally, a software design team is staffed so that both the levels and the distribution of knowledge within the team match those required for the successful completion of the project. Because of knowledge shortfalls such as the thin spread of application domain knowledge in most organizations, however, this is seldom the case [12]. In general, individual team members do not have all of the knowledge required for the project and must acquire additional information before accomplishing productive work. The sources of this information can be relevant documentation, formal training sessions, the results of trial-and-error behavior, and other team members. Group meetings are an important environment for learning, since they allow team members to share information and learn about other domains relevant to their work.Productive design activities need to revolve around the integration of the various knowledge domains. This integration leads to shared models of the problem under consideration and potential solutions. A software design team seldom starts its life with shared models of the system to be built. Instead, these models develop over time as team members learn from one another about the expected behavior of the application and the computational stiuctures required to produce this behavior. This means that team members need to be speaking the same language (or, at least, dialects whose semantics are similar enough to facilitate communication and understanding) in order to share knowledge about the system.Knowledge acquisition, knowledge sharing, and knowledge integration are significant, time-consuming activities that precede the development of a design document. The purpose of this article is to examine how these activities unfolded over time inside an actual software design team. Two related questions with respect to this team will be resolved: 1) How do the group members acquire, share, and integrate project-relevant knowledge? 2) Do the levels of participation in these activities differ ac...

The recruitment, development, and retention of top performing information technology (IT) professionals is a key concern within IT organizations today. It is therefore important for IT management to understand the characteristics and behaviors of high performing IT personnel in order to identify them and to create an environment conducive to their development and retention. However, the personality traits and behaviors of top‐performing developers have not received a lot of attention in the literature on IT personnel. Describes a research method for identifying and measuring the characteristics of exceptional software developers and presents the results of a pilot study using MBA students. The results of the pilot are intended to be used to refine the methodology and serve as input to future research involving IT managers. These results indicate that the research design holds the promise of providing a profile of top performing IT personnel.

User authentication in computer systems has been a cornerstone of computer security for decades. The concept of a user id and password is a cost effective and efficient method of maintaining a shared secret between a user and a computer system. One of the key elements in the password solution for security is a reliance on human cognitive ability to remember the shared secret. In early computing days with only a few computer systems and a small select group of users, this model proved effective.With the advent of the Internet, e-commerce, and the proliferation of PCs in offices and schools, the user base has grown both in number and in demographic base.Individual users no longer have single passwords for single systems, but are presented with the challenge of remembering numerous passwords for numerous systems, from email, to web accounts, to banking and financial services. This paper presents a conceptual model depicting how users and systems work together in this function and examines the consequences of the expanding user base and the use of password memory aids.A system model of the risks associated with password-based authentication is presented from a user centric point of view including the construct of user password memory aids. When confronted with too much data to remember, users will develop memory aids to assist them in the task of remembering important pieces of information. These user password memory aids form a bridge between otherwise unconnected systems and have an effect on system level security across multiple systems interconnected by the user. A preliminary analysis of the implications of this user centric interconnection of security models is presented.

Exceptional application software developers are a scarce resource. It is therefore important for employers to identify, retain, and cultivate individuals who exhibit this capacity. This study compared the personality characteristics of exceptional, experienced application software developers with the personality characteristics of junior and senior level IS and CS students (who can be seen as entry-level, or pre-entry level, IT developers). We used the Adjective Checklist to measure personality characteristics for all subjects, then mapped the resultant scales to the Five Factor Model of Personality. The results of this study suggest that exceptional application software developers exhibit significantly higher levels of Extraversion and Conscientiousness. Exceptional students (as determined by GPA), however, were actually found to be introverted. Thus, when GPA is used to pre-screen or filter for entry-level positions, recruiters may actually be excluding some of those candidates who are most likely to become exceptional application software developers. These results have implications for understanding and managing the recruiting of IT personnel and their progression from entry level (novice) to more experienced positions.

Three types of information systems personnel (programmers, systems analysts, and project managers) were compared to the general population based on responses to a standardized personality test. The IS professionals, in aggregate, exceeded population norms for nearly all of the relevant scales, confirming much prior research.However, the personality profiles of analysts and managers differed widely from that of programmers, but not from one another. Managers and analysts were found to be conservative, logical, analytical, diligent, and ambitious, with strong leadership tendencies and high self-confidence and self-esteem. They were also found to be more sociable and creative than in past research.The differences identified between traditional programmers and systems analysts and managers indicate the importance of studying, managing, and recruiting these groups differently. The findings offer insight into how to retain, promote, and manage IS personnel effectively.

No abstract

No abstract

This study is an update of a previous scientometric study that examined the leading Information Systems (IS) researchers, their university affiliations, and the universities that supply them. We provide geographical comparisons of researcher affiliations for the AIS regions and for North American versus global institutions, along with a comparison of prior and current results. Our analysis shows that coauthorship is increasing in the top three IS journals and that most of the leading researchers continue to affiliate with institutions in North America. However, the proportion of publications from North American researchers in the top three journals has decreased slightly over time This research contributes to the scientometric literature by identifying a more broad and inclusive set of leading IS publications and by providing benchmarks for the productivity of IS scholars. These results can be valuable for deans and department chairs making tenure and promotion decisions. Prospective students and faculty can use these results to identify universities which match their personal research goals. This study also helps to define and expand the boundaries of the IS discipline due to its use of a broader set of leading journals.