Search results for "software process"

showing 10 items of 29 documents

Using organizational influence processes to overcome IS implementation barriers: lessons from a longitudinal case study of SPI implementation

2014

A fundamental tenet of the information systems (IS) discipline holds that: (a) a lack of formal power and influence over the organization targeted for change, (b) weak support from top management, and (c) organizational memories of prior failures are barriers to implementation success. Our research, informed by organization influence, compellingly illustrates that such conditions do not necessarily doom a project to failure. In this paper, we present an analysis of how an IS implementation team designed and enacted a coordinated strategy of organizational influence to achieve implementation success despite these barriers. Our empirical analysis also found that technology implementation and …

Information managementKnowledge managementlongitudinal case studyComputer sciencebusiness.industrybarriersIS implementation; longitudinal case study; organizational influence processes; software process improvement; barriersInformation technologyLibrary and Information SciencesBusiness modelManagement information systemsIS implementationAccounting information systemInformation systemSoft systems methodologyStrategic information systemorganizational influence processessoftware process improvementbusinessInformation SystemsEuropean Journal of Information Systems
researchProduct

Java Integrated Development Environments' Support for Reuse-Oriented Software Development

2002

Component reuse is a promising direction to develop software more efficiently and cost effectively. One part of software development is the actual programming with an integrated development environment (IDE). We studied three Java IDEs and how they support reuse-oriented software development. We derived evaluation criteria from a known reuse model. As a conclusion we suggest that current Java IDEs need to improve their support for the reuse process.

Javabusiness.industryComputer scienceSoftware developmentSoftware development processPersonal software processGoal-Driven Software Development ProcessComponent-based software engineeringSoftware constructionSystems engineeringPackage development processbusinessSoftware engineeringcomputercomputer.programming_language
researchProduct

Use and Identification of Components in Component-Based Software Development Methods

2000

New software systems are needed ever more but to keep up with this trend software developers must learn to create quality software more efficiently. One approach is to (re-)use components as building blocks of the new software. Recently there has been more interest to create component-based software development methods to support this. In this article we first set out requirements for reuse-based software development and then evaluate three component-based methods, namely Catalysis, OMT++, and Unified Process. As a conclusion we argue that evaluated methods produce prefabricated components and that component-based means that software developers can change better components to existing syste…

Resource-oriented architectureComputer scienceKnowledge engineeringReuseSoftware walkthroughcomputer.software_genreSoftware development processSoftware analyticsSoftwareSoftware verification and validationSoftware systemSoftware requirementsUnified ProcessReusabilitySocial software engineeringbusiness.industrySoftware developmentSoftware frameworkSoftware deploymentComponent-based software engineeringSoftware constructionPersonal software processPackage development processBackportingSoftware architecturebusinessSoftware engineeringcomputer
researchProduct

A root cause analysis method for preventing erratic behavior in software development: PEBA

2019

Measures taken to prevent faults from being introduced or going undetected can secure development of highly reliable software systems. One such measure is analyzing root causes of recurring faults and preventing them from appearing again. Previous methods developed for this purpose have been reactive in nature and relied heavily on fault reporting mechanisms of ogranizations. Additionally, previous efforts lack a defined mechanism for innovating corrective actions. In this study, we strive to complement the existing methods by introducing a proactive and qualitative method that does not rely on fault data. During the course of the research, in addition to an extensive literature search, an …

Root (linguistics)Computer sciencefault removalohjelmistotekniikka0211 other engineering and technologiesfault preventionContext (language use)quality assurance02 engineering and technologyFault (power engineering)Industrial and Manufacturing EngineeringField (computer science)Software systemsoftware process improvementSafety Risk Reliability and Quality021110 strategic defence & security studies021103 operations researchbusiness.industrytietokoneohjelmatSoftware developmentProactivitysoftware reliabilityRisk analysis (engineering)root cause analysisohjelmistokehitysRoot cause analysisbusinessReliability Engineering & System Safety
researchProduct

Which Test Artifacts Testing Service Providers should Reuse and How? Experiences from a Case Study in the Chinese ICT Sourcing Market

2011

Software testing service providers are facing new requirements to shorten service times, lower costs, and increase service customization and quality. Reuse of test artifacts is a possible solution that can help providers to meet the requirements because reuse can improve software quality and productivity. However, the extant literature does not explain in depth which test artifacts should be reused and how. This paper focuses on ICT-enabled sourcing of software testing services in the Chinese market to identify the most important reusable test artifacts. There are two reasons for this research. First, most Chinese service providers are small or medium-sized and have to overcome obstacles su…

Service (systems architecture)Process managementComputer scienceSoftware walkthroughReuseSoftware peer reviewGlobalizationSoftware quality analystSoftware verification and validationMarketingta113Social software engineeringbusiness.industrySoftware as a serviceSoftware developmentService providerSoftware qualityInformation and Communications TechnologySoftware deploymentPersonal software processSoftware quality managementPackage development processbusinessSystem integration testingSoftware project managementSoftware quality control
researchProduct

Towards Understanding of Software Engineer Motivation in Globally Distributed Projects

2011

Motivation in software engineering is reported to be a source for performance improvement, which leads to project overall success. Since it is a soft factor and difficult to quantify it is usually neglected. Research in this field is rather scarce and outdated. On the basis of a recent systematic review of software engineers' motivation we set an agenda for further investigation of the role of motivation in contemporary projects. As software organizations nowadays seek opportunities inherited in both - global software development (GSD) and agile projects, it is important to understand how different project environments influence motivation.

Social software engineeringEngineeringKnowledge managementbusiness.industryTeam software processPersonal software processSoftware developmentSoftware prototypingProject managementbusinessSoftware project managementAgile software development2011 IEEE Sixth International Conference on Global Software Engineering Workshop
researchProduct

Apathy Towards the Integration of Usability Work: A Case of System Justification

2016

In this article we report from a case study of a software development organization and we study in particular the developers’ and product managers’ attitudes towards integrating usability work into software development. We offer explanations based on system justification theory illuminating what would-be integrators might be up against. The analysis shows how the developers only pay lip service to usability work and how they treat users superficially. It further shows how that leads to stereotyping of usability designers and users in order to preserve status quo, and how internalization of inequality between the developers and usability designers rationalizes the preservation of status quo.…

Social software engineeringKnowledge managementHCI design and evaluation methodsComputer sciencebusiness.industry05 social sciencesSoftware development050109 social psychologyUsabilitySoftware creation and managementSoftware peer reviewCollaboration in software developmentHuman-Computer InteractionSoftware development processPersonal software processSoftware constructionSoftware process managementPackage development process0501 psychology and cognitive sciencesbusiness050107 human factorsSoftwareInteracting with Computers
researchProduct

Experiences from Software Maintenance Seminars: Organizing Three Seminars with 127 Groups

2009

Software maintenance and evolution (SME) is an important but problematic topic-area for university-level computer science education. Seminars can be used to provide versatile and up-to-date knowledge for students regarding scientifically relevant issues. We have organized three systematic university-level seminars on SME with a total of 127 seminar groups. Each group has been assigned a task of analyzing one scientific SME-article. The main results include the general confirmed feasibility of the selected seminar-based approach. The paper describes the background of the seminars, their contents, and experiences concerning organization and feasibility of the seminars. The results support org…

Social software engineeringSoftware Engineering Process GroupComputingMilieux_THECOMPUTINGPROFESSIONbusiness.industryComputer scienceSoftware maintenanceSoftware peer reviewTask (project management)Engineering managementPersonal software processComputingMilieux_COMPUTERSANDEDUCATIONSoftware engineeringbusinessSoftware project management
researchProduct

A modest but practical software process modeling technique for software process improvement

2002

One of the main problems with software engineering is due to the difficulties in evaluating and improving our software processes, especially in the light of the fact that reuse depends on a process which supports it. Generally used approaches to the evaluation and improvement of software processes are based on the CMM, for example. In this paper we present a technique to improve software processes through modeling and evaluation. The presented technique is fairly easy to use, provides reasonably good results and requires only a fraction of resources required by CMM appraisals. Copyright © 2002 John Wiley & Sons, Ltd.

Software Engineering Process GroupComputer sciencebusiness.industrySoftware developmentReliability engineeringSoftware sizingSoftware constructionPersonal software processGoal-Driven Software Development ProcessPackage development processSoftware verification and validationbusinessSoftware engineeringSoftwareSoftware Process: Improvement and Practice
researchProduct

Group Decision-Making Processes in Industrial Software Evolution

2007

Software evolution decision-making is important. Decisions can be made by an individual or a group. Currently it is not known how decision-making is organized in software industry. However, that knowledge is needed to improve the decision-making processes. Therefore, we have studied 29 decision making experts, who were involved in software evolution decision-making. The study was performed with qualitative methods, which enabled the gathering of versatile information concerning the views of the decision-makers. The study revealed group decisions are widely used both in private and public organizations and attitudes towards them are generally positive or neutral. The study provided informati…

Software Engineering Process GroupEngineeringSoftware analyticsSocial software engineeringKnowledge managementTeam software processbusiness.industryPersonal software processbusinessR-CASTSoftware evolutionGroup decision-makingInternational Conference on Software Engineering Advances (ICSEA 2007)
researchProduct