Although there is greater adoption of crowdsourcing, relatively little is known about internal crowdsourcing (ICS). Since there are key differences between ICS, and external crowdsourcing (ECS) and user-generated content (UGC) endeavors within organizations, a deeper understanding of what motivates employees to contribute is crucial to ICS success. Altruism is often cited as an attribute motivating employees to engage in self-initiated voluntarism. While employees engaged in a firm-initiated ICS exercise are also likely to be driven by their altruistic tendencies, identifying factors beyond altruism holds the key to realizing greater employee contribution. The authors draw from theories in job design to develop a research framework that includes three high-level dimensions of non-altruistic motivations: work-directed, task-directed, and self-directed. Using language translation as ICS task, we conduct an empirical study to appraise a set of hypotheses using data collected from IBM. Results support all hypotheses except one. Managerial and research implications are discussed.

Grounded on principles of manufacturing design, component-based software development (CBSD) has been viewed as the future trend in software development. In this paper, we propose a methodology for component fabrication and argue that, as in classical product development, business strategy of component development companies must guide the design of reusable business components. Accordingly, we link business strategy with component design through managerial goals (identified as cost effectiveness, ease of assembly, customization, reusability, and maintainability). These managerial goals are then mapped to technical features (identified as coupling, cohesion, number of components, component size, and complexity). We develop a formal model, called Business Strategy-based Component Design that uses the object-oriented model of a business to derive the component structure by grouping appropriate object classes to achieve the desired business strategy. We examine the validity of the model by a two-phase application process.

In software inspection, a key principle endorsed by Fagan (1986) is openness. However, scholars have recently questioned the efficacy of openness. For example, some argue that ego-involvement and personality conflicts that become more transparent due to openness might impede inspection. Still others point out that familiarity and (preexisting) relationships among inspection team members negatively affect the comprehensiveness in detection of defects. This brings up concerns if the openness as originally envisioned by Fagan may in fact lead to suboptimal outcomes. As the trend towards computer-based inspection continues, we believe that anonymity could play a positive role in overcoming some of the drawbacks noted in team-based inspection. Drawing upon the literature on software inspection and group support systems, this research proposes possible influences of group member anonymity on the outcome of computer-mediated software inspection and empirically examines the validity of the posited relationships in a set of controlled laboratory experiments. Two different inspection tasks with varying levels of software code complexity are employed. While both the control groups (i.e., teams without anonymity) and treatment groups (i.e., teams with support for anonymity) consume more or less the same time in performing the inspection tasks, the treatment groups are more effective in identifying the seeded errors in the more complex task. Treatment groups also express a more positive attitude toward both code inspection tasks. The findings of the study suggest a number of directions for future research.

Component-based development (CDB) promises to reduce complexity and cost of software development and maintenance through reuse. For CBD to be successful, a vibrant market for commercial business components is essential. One of the key requirements of an active market for business components is an effective scheme for classifying and describing them at various levels of detail, as well as a corresponding repository for storing and retrieving these components. Such a scheme needs to support various constituents such as business users, managers, and application assemblers. The scheme and repository should help users and managers to select components that match their requirements and aid application assemblers in identifying components most compatible with their deployment environment (such as the platform) and system inputs (such as data types). Drawing from the concepts of group technology and software reuse paradigm, this paper proposes a scheme for classifying and describing business components and the design of a knowledge-based repository for their storage and retrieval. The proposed scheme is implemented in a prototype repository. The effectiveness of the prototype and the underlying classification and coding scheme is assessed empirically through controlled experiments. Results support the assertion that the scheme is effective in enhancing the users' and analysts' ability to find the needed business components.