Thèses : « Software development companies »

1

Giardino, Carmine, et Nicolò Paternoster. « Software Development in Startup Companies ». Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3652.

Texte intégral

Résumé :

Context: Software startups are newly created companies with no operating history and are extremely fast in producing cutting-edge technologies. These companies develop software un- der highly uncertain conditions, tackling fast growing markets with severe lack of resources. Startups present an unique combination of characteristics which pose several challenges to the software development activities, creating interesting problems for software engineers. However, despite the increasing economical importance and the high failure rate, there are only a few sci- entific studies attempting to address software engineering (SE) issues, especially for early-stages startups. In a context where a wrong decision can easily lead the entire business to failure, the support of SE can contribute to foster performances of startups and making a big impact on a large number of companies. Objective: In view of a lack of primary studies, the first step to attending the software development strategies with scientific and engineering approaches is by an understanding of the startups’ behavior. For this reason this research aims to understand how software development strategies are engineered by practitioners, in the period of time that goes from idea conception to the first open beta release of the software product. Methods: This research combines a systematic review of the state-of-the-art with a cross- sectional case study conducted in 13 web startups recently founded and distributed in di↵erent geographic areas and market sectors. A grounded theory approach guided the execution of a sys- tematic mapping study, integrated with semi-structured interviews and follow-up questionnaires to explore the state-of-practice. Results: We selected, classified and evaluated 37 relevant studies. The systematic review revealed that the studies which constitute the body of knowledge are generally not rigorously designed and executed, make use of inconsistent terminology, and cover only small samples of startups. Moreover, we extrapolated concepts from the case study to form a theoretical model, explaining the underlying phenomenon of software development in early-stage startups. The model is grounded in the empirical data and its explanatory power was further validated through a systematic procedure. Finally we proposed a multi-faceted evolutionary model to describe the dynamics of the software development after the first product release. Conclusions: The research provided a wide set of evidences fostering the understanding of how software development is structured and executed, from idea conception to the first release. The results revealed the urgent priority of startups of releasing the product as quickly as possi- ble to verify the product/market fit and to adjust the business and product trajectory according to the early collected user feedbacks. Nevertheless, the initial gain obtained in speeding-up the development by low-precision and product-centric engineering activities is counterbalanced by the need of restructuring the product and the workflows before setting o↵ for further grow. In fact, when user requests and company’s size start to increase startups face an initial and temporary drop-down in productivity, creating the need of mitigation strategies to find a sweet spot between being fast enough to enter the market early while controlling the amount of accu- mulated technical debt. The conclusions can be generalized with a good degree of confidence to the majority of early-stage software startups involved in the production of innovative products, especially for web and mobile applications.

Styles APA, Harvard, Vancouver, ISO, etc.

2

Lindmark, Fanny, et Hanna Kvist. « Security in software : How software companies work with security during a software development process ». Thesis, Linköpings universitet, Institutionen för datavetenskap, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:liu:diva-130964.

Texte intégral

Résumé :

This study is conducted, due to recent interest in privacy and software security, on how a number of software development companies work during a development process to develop secure software to the possible extent. The study is based on four interviews with four software companies located in Linköping, Sweden. The interviews followed a semi-structured format to ensure the possibility to compare the given answers from the companies to each other. This structure was chosen to give each company the liberty to express what they valued and thought were important during a software development process. The aim was to analyze how and if these companies work with security when developing software, and to see what differences and similarities that could be established. We found differences between the companies' perspective of security and on their methods of working. Some valued secure software more than others and performed more measures to ensure it. We also found some similarities on their view on importance of secure software and ways to work with it. The differences and similarities were related to the size of the companies, their resources, the types of products they develop, and the types of clients they have.

Styles APA, Harvard, Vancouver, ISO, etc.

3

Smith, Stanley A. (Stanley Alan). « Software development in establised and new entrant companies : case studies of leading software producers ». Thesis, Massachusetts Institute of Technology, 1993. http://hdl.handle.net/1721.1/12725.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

4

Rodríguez, P. (Pilar). « Combining lean thinking and agile software development:how do software-intensive companies use them in practice ? » Doctoral thesis, Oulun yliopisto, 2013. http://urn.fi/urn:isbn:9789526203324.

Texte intégral

Résumé :

Abstract Software engineering is advancing according to market needs. Consequently, software development methods that initially caused controversies such as Agile, and more recently Lean, are increasingly being adopted by the software industry. Particularly, Lean Software Development, which was initially regarded as one of the Agile methods, is acquiring an identity of its own as a means to scale Agile. However, Lean thinking is still open to interpretation in the domain of software development, which differs fundamentally from the manufacturing domain where Lean originally emerged. Specific issues such as the essence of Lean Software Development, the compatibility of Lean and Agile and the best combination of them are not properly understood. This dissertation addresses Lean thinking and its combination with Agile in the field of software development, by providing empirical evidence on how software-intensive organisations use them in practice. The research was performed in four phases. First, the relevant literature was analysed to identify research opportunities. Second, a survey strategy was used to investigate status and trends in the adoption of Agile and Lean. The third phase explored in detail how Agile and Lean are combined in practice, by conducting case studies on two large-scale, industry-leading companies that were transforming their processes from Agile Software Development into Lean Software Development. Finally, in the fourth phase, the results of the previous research phases were synthetized to draw conclusions and outline implications. The results of the study confirmed the interest of practitioners in using a combination of Agile and Lean. Unlike in manufacturing, the borders of Agile and Lean are not clearly defined in the software domain. The results provided evidence of numerous compatibilities between Agile and Lean in software development. Generally, the use of Agile methods at a prescriptive level is guided by Lean principles. However, Lean thinking also brings new practical elements to software development processes, such as Kanban, work-in-progress limits, a ‘pull’ and ‘less waste’-oriented culture and an extended emphasis on transparency and collaborative development. The results showed the fundamental importance of practices that enable quick feedback, fast learning and adaptation
Tiivistelmä Ohjelmistotuotanto kehittyy markkinoiden tarpeiden mukaisesti. Aiemmin kiisteltyjä ketteriä menetelmiä, ja nykyään myös Lean-menetelmiä sovelletaan yhä useammin ohjelmistoteollisuudessa. Lean-menetelmiin perustuva Lean-ohjelmistokehitys erottuu selkeämmin välineenä laajentaa ketterien menetelmien käyttöä. Lean on yhä monitulkintainen ohjelmistotuotannossa, joka poikkeaa teollisuustuotannosta, josta Lean on peräisin. Lean-ohjelmistokehitystä, Lean- ja ketterien menetelmien yhteensopivuutta ja niiden parasta yhdistelmää ei vielä ymmärretä riittävän hyvin. Tämä väitöskirja käsittelee Lean-menetelmien yhdistämistä ketteriin menetelmiin ohjelmistotuotannossa. Tutkimus esittää kokemusperäistä tietoa, kuinka näitä menetelmiä käytetään ohjelmisto-alan organisaatioissa. Tutkimus oli nelivaiheinen. Aluksi tutkimusmahdollisuudet kartoitettiin tutkimalla aiheeseen liittyvää kirjallisuutta. Seuraavaksi tutkittiin kyselytutkimuksen avulla Lean- ja ketterien menetelmien käyttämisen nykytilaa ja kehitystä. Kolmannessa vaiheessa tapaustutkimuksilla selvitettiin Lean- ja ketterien menetelmien yhdistämistä käytännössä. Tapaustutkimuksia tehtiin kahdessa suuressa yrityksessä, jotka olivat muuttamassa prosessejaan ketteristä menetelmistä kohti Lean-ohjelmistokehitystä. Lopuksi aiemmat tutkimusvaiheet yhdistettiin johtopäätöksiä ja vaikutusten hahmottamista varten. Tutkimuksen tulokset vahvistavat Lean- ja ketterien menetelmien yhdistämisen kiinnostavan ohjelmistotuotannonharjoittajia. Lean- ja ketterien menetelmien rajat eivät ole selkeästi määriteltyjä ohjelmistotuotannossa. Tulokset tukevat käsitystä Lean- ja ketterien menetelmien yhteensopivuudesta. Lean ohjaa yleisellä tasolla ketterien menetelmien käyttöä. Lean tuo kuitenkin myös uusia elementtejä ohjelmistotuotantoon, kuten Kanban-menetelmän, keskeneräisen työn rajoittamisen, kysyntään perustuvan ’pull’-menetelmän ja turhan työn vähentämistä tavoittelevan ’less-waste’-työkulttuurin. Lean-ajattelu myös lisää painotusta läpinäkyvyyteen ja yhteistyöhön

Styles APA, Harvard, Vancouver, ISO, etc.

5

Saarnak, Stefan, et Björn Gustafsson. « A comparison of lifecycles : Agile software processes vs. projects in non-Agile software companies ». Thesis, Blekinge Tekniska Högskola, Institutionen för programvaruteknik och datavetenskap, 2003. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3251.

Texte intégral

Résumé :

In the software industry a number of different software processes has been used throughout the years to address known problems with software development, despite their intention complains has been raised that some of these are too bureaucratic. The Agile Alliance was formed in 2001 and aimed to solve this problem, they developed a manifesto and twelve principles which are supported by all Agile software processes. The purpose with the manifesto and its principles is to uncover better ways of developing software and these are by many intercessors of Agile seen as common sense and not completely new ideas. The aim with this master thesis is to answer the question if companies that explicitly claim that they do not use any Agile software process are already applying some of these ideas since they are thought of as obvious and common sense. The comparison in this thesis is performed between the project lifecycles used in specific projects by five non-Agile software companies and four identified lifecycle characteristics and two more general characteristics of the Agile software processes Extreme Programming (XP) and Dynamic Systems Development Method (DSDM). The result from the analysis of these interviews has shown that it is very difficult to decide if a software company really is working as described by XP or DSDM, this is due to that many different factors affect the final outcome. For example type of project and is the software company using different software processes for different kinds of projects. Since we just covered specific projects we were only able to conclude with absolute certainty actions that really were performed in just these projects. The project lifecycles of these software companies had some similarities with the above mentioned Agile software processes, but as a whole the analysis showed that they are quite different due to that two very important characteristics according to us, namely iterative development and frequent releases, were not applied by any of the software companies and that their project phases differed tremendously compared to XP and DSDM. Our common sense hypothesis for Agile software development was shown in this investigation to be incorrect since important activities were not performed by any of the software companies. Instead of using an iterative approach with frequent releases they all followed sequential waterfall like software processes.

Styles APA, Harvard, Vancouver, ISO, etc.

6

Soliński, Adam. « Analysis of the application and integration of methodologies by software development companies ». Thesis, Blekinge Tekniska Högskola, Sektionen för datavetenskap och kommunikation, 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-2924.

Texte intégral

Résumé :

Context. In recent years there has been observed a significant shift from plan-driven development towards agile, which is considered as a vast improvement to processes. However, it has also been spotted that agile methodologies are hardly ever applied in their pure form. Moreover, hybrid processes as combinations of plan-driven and agile practices emerge. In addition, agile adoption has been reported to result in both: benefits and limitations. Objectives. In this study the following matters are investigated: 1) the commonness of plan driven and agile practices usage, 2) common practices combinations, 3) patterns for agile adoption over time, 4) hybrid development models and 5) the actual effects of agile adoption in terms of benefits and limitations as perceived by practitioners. Methods. The thesis presents an empirical investigation of software development organizations. The objectives are achieved through a targeted survey based on existing evidence and a multidimensional data analysis. The mean for obtaining data is a web-based questionnaire with an interactive board with practices and time indication sliders (to capture applied development models and practices adoption strategies) and hierarchical cumulative voting (to measure the relative significance of benefits and limitations). The data analysis is supported by hierarchical cluster analysis and an extended hierarchical voting analysis framework (EHV-F). Results. In total, 45 practitioners have been successfully surveyed. The commonness of 7 plan-driven and 14 agile practices usage was investigated. The relative significance of agile adoption benefits (32 factors in 10 categories) and limitations (23 factors in 7 categories) was measured with respect to global view (all respondents and perspectives), different agile adoption strategies as well as distinguished development models. Conclusions. It is concluded that agile practices dominate over plan-driven, however, hybrid approaches, being combinations of plan-driven and agile practices, are frequently applied. It is also concluded that some practices are commonly used together since they facilitate each other (e.g. continuous integration with testing which facilitate short iterations and releases). Some agile practices are still unsuccessfully applied and eventually abandoned (e.g. pair programming), what should be further investigated by researchers. Incremental agile adoption strategy was found to be the most beneficial approach. It is also concluded that agile adoption leads first of all to improved quality of working life, increased knowledge transfer and improved verification and validation processes. On the other hand, agile adoption is very demanding since it requires high professional skills from development teams as well as managers. Hence, more resources should be devoted to training on agile for all the parties involved in development. Agile is still commonly considered to be poorly scalable. Moreover, the quality of design with agile methods is not considered as a benefit at all. These areas should be further investigated by researchers.

Styles APA, Harvard, Vancouver, ISO, etc.

7

Wiener, Martin Amberg Michael. « Critical success factors of offshore software development projects the perspective of German-speaking companies / ». Wiesbaden : Deutscher Universitäts-Verlag, 2006. http://site.ebrary.com/id/10231882.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

8

Loughnane, David, et Henrik Oskarsson. « The Contract Winning Process A guide for small development companies ». Thesis, Blekinge Tekniska Högskola, Avdelningen för programvarusystem, 2004. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-3717.

Texte intégral

Résumé :

In order to survive in today’s business world it is necessary to win contracts. If companies fail to do this then their existence is threatened. Therefore, the manner in which companies conduct their contract winning activities become of paramount importance. Much focus in software engineering research and academic literature centres around the post-contract winning activities, such as project planning, costing and scheduling. The emphasis on the contract winning process, though not neglected, is quite small in comparison. There exists a need for more research in this interesting area and this thesis aims to partly address this need. Consequently, the main focus of this research is the contract winning process. The approach used to investigate this area consisted of a theoretical study followed by an empirical study, where eight small development companies were interviewed. The findings show that a uniform formal process does not exist for winning and negotiating contracts. As a result of these findings, from both the theoretical and empirical studies, a contract winning process model for small development companies was formulated. The proposed model consists of five sequential stages with recommended activities for each stage. The model is intended for small software engineering development companies but because the model is generic it could also be used by non-software companies.

Styles APA, Harvard, Vancouver, ISO, etc.

9

Wang, Anjia. « Apparel Companies' Management System (APLAN) ». CSUSB ScholarWorks, 2004. https://scholarworks.lib.csusb.edu/etd-project/2524.

Texte intégral

Résumé :

APLAN is a computer software system developed to aid in an apparel company's management system. APLAN is designed to improve the efficiency of production management by combining the companies' main production activities in one system. This project was designed to use MYSQL as the database system. JSP (Java Server Pages) is an interface between MySQL and the web browser and the database access scheme is JDBC (JAVA Database Connectivity).

Styles APA, Harvard, Vancouver, ISO, etc.

10

Wiener, Martin. « Critical success factors of offshore software development projects : the perspective of german-speaking companies / ». Wiesbaden : Dt. Univ.-Verl, 2006. http://bvbr.bib-bvb.de:8991/F?func=service&doc_library=BVB01&doc_number=014952985&line_number=0001&func_code=DB_RECORDS&service_type=MEDIA.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

11

Westerlind, Anna. « To be or not to be a software product manager ? : What is the product manager's responsibility and accountability in software companies ? » Thesis, Karlstads universitet, Handelshögskolan, 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:kau:diva-43775.

Texte intégral

Résumé :

Business success in software industry is about deploying a product to the right market, with the right features, in the right time with a good quality. Many development projects exceed the budget, is not completed within schedule or do not reach business objectives. One key role managing the business of the product is the software product manager. The software product manager role is though seldom clearly described, competence needed is not always clear and education to become a product manager is today only offered by separate courses provided by some few private initiatives. This thesis uses a qualitative descriptive approach, the purpose with this thesis is to produce further knowledge around the software product manager role. The clarification and structure of the software product manager role is limited in academia; therefore, this research will be combined with an exploratory approach to be able to verify the empirical findings. The thesis also includes observations and data collection from actual job applications to further define the requested competences of a software product manager. This thesis has found that domain competence is the top most important competence for a software product manager. To be able to make success in the role communication skills and analytic skills are most important. The right soft skills are as important as the educated competences. The thesis conclude that the product manager role is wide and it is important to be surrounded with colleagues that support the role were there are lacking of competence in technology, business or market expertise. A successful product manager build network among people, cross-functional teams, around the product and establish an effective way to communicate with those groups. Findings suggest that software companies define the responsibilities and expectations of the product manager role. As important is to support the product manager with the input data needed to be able to perform the product manager activities. By defining the responsibilities and securing the input data needed, the product manager will have a higher probability to produce a result with an impact.

Styles APA, Harvard, Vancouver, ISO, etc.

12

Korhonen, P. (Pyry). « Business models and motivation of companies that take part in open source software development projects ». Master's thesis, University of Oulu, 2014. http://urn.fi/URN:NBN:fi:oulu-201310121790.

Texte intégral

Résumé :

The subject matters in this study were open source software development, companies, business models and motivation. The intention of the study was to study profit oriented companies in order to identify and understand their business models and motivation for taking part in open source software development methods. As background research material I used articles available through the Oulu university library. I also interviewed and assessed several actual companies. In one of these companies I had worked in an open source software development project, two of the companies I interviewed face to face in Oulu, two other Finnish companies I e-mail interviewed. I also assessed a very successful foreign company in order to bring contrast to the Finnish companies. In order to assess the case companies I refined the software business model framework developed by Rajala, Rossi and Tuunainen (2003). I constructed themes under the components of the framework as advised by Hirsjärvi and Hurme in their book “Teemahaastattelu” from 1985. These themes contained some guiding questions that I posed to the interviewees in the case companies and then noted what they had to say about the subject themes and matters. The results of the study are that there are many kinds of business models that profit oriented firms can utilize in order to gather revenues from open source software development projects. Utilizing these models is also viable for firms of all sizes. Based on the study it is also clear that the easiest business model to pull off is the subscription based open source business model. In order to succeed with open source business models companies need to understand what actors there are on the open source field and how they affect development projects. It is vital for companies to understand what motivations drive these actors in open source development projects and how the companies can generate and benefit from those motivations. Future work should concentrate on integrating the motivation component to the framework.

Styles APA, Harvard, Vancouver, ISO, etc.

13

Lagergren, Viktor, et Anna Norelius. « Managing the Transition Towards Open Source Software Adoption : : Considerations for Large IT Companies ». Thesis, KTH, Skolan för industriell teknik och management (ITM), 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-264204.

Texte intégral

Résumé :

The promise of reduced costs, increased flexibility, and independence from vendors of proprietary products has convinced organizations worldwide to deploy Open Source Software (OSS) in their production environments and commercial offerings. Therefore, the ability to scale software, seamlessly integrate open source software in products and increase benefits from OSS participation are crucial capabilities. However, the nature of OSS is not entirely compatible with the rigid structures and processes of many large companies and thus successfully managing OSS has proven to be highly difficult. Previous research has shown that many companies have built previous success on ‘closed innovation’ logic and must now move in a highly counterintuitive direction towards an ‘open innovation’ mindset. This creates various strategic and operational challenges which they need to identify and overcome to avoid disruption. Based on the aforementioned, the purpose has been to investigate key patterns in how development and increased use of open source software could affect large IT companies. This is to illustrate the transition between closed innovation to open innovation strategy for software, but also to describe the strategic and operational challenges that come appear thereafter. To create a deeper understanding of this process of change, a single (qualitative) case study by a large Swedish IT company has been carried out. The hope is to be able to contribute to research by presenting general conclusions from the case study where empirical data is linked to contemporary research in the field. In order to be able to generalize based on the empirical data, interviews have been conducted with both doctoral students and professors in the field, but also experts in the business world. Our findings have generated insights concerning the OSS adoption process of Company A. The findings of the study include a 6-step model that describes the adoption process as well as strategic and operational considerations for successful transition towards efficient OSS governance.
Med förhoppningar om reducerade kostnader, ökad flexibilitet och ett minskat beroende av tredjepartsleverantörer har användandet av open source-mjukvara (OSS) eskalerat under det senaste årtiondet och kommit att dominera stora delar av mjukvaruindustrin. Förmågan att skala och integrera open source-mjukvara har således blivit en viktig kompetens för att skapa konkurrensfördelar. Dock är nuvarande processer för integrering av open source-mjukvara emellertid inte helt förenligt med många etablerade företags strukturer och processer. Hantering och integrering har istället visat sig vara en stor utmaning då många företag historiskt byggt sina framgångar genom en logik som präglas av sluten innovationsstrategi och immateriella rättigheter (IPR). Företag tvingas idag att röra sig i en kontraintuitiv riktning som präglas av öppen innovation, och i kölvattnet av teknisk och industriell förändring uppenbarar sig strategiska och operativa utmaningar. Dessa utmaningar måste företag identifiera, förstå och övervinna för att undvika att bli utkonkurrerade. Med detta som bakgrund är syftet med denna studie att Identifiera viktiga mönster som beskriver hur utvecklingen och en ökad användning av open source-mjukvara kan påverka stora IT-företag. Detta för att belysa övergången mellan sluten innovationsstrategi och öppen för open source-mjukvara, men även för att skildra vilka strategiska och operativa utmaningar som uppenbarar sig därefter. För att skapa en djupare förståelse för denna förändringsprocess har en enskild (kvalitativ) fallstudie av ett stort svenskt IT-företag genomförts. Förhoppningen är att kunna bidra till forskning genom att presentera generella slutsatser från fallstudien där empirisk data kopplas an till nutida forskning inom området. För att kunna generalisera utifrån empirin har intervjuer genomförts med dels doktorander och professorer inom området, men också experter inom affärsvärlden. Empirin har genererat en 6-stegs modell som beskriver adoptionsprocessen för OSS. Modellen har sedermera jämförts med samtida forskning inom samma område där likheter och skillnader diskuterats och presenterats. Vidare har strategiska och operativa överväganden belysts och diskuterats för att kunna bidra till en ökad förståelse för de utmaningar som många företag står inför.

Styles APA, Harvard, Vancouver, ISO, etc.

14

Stanberry, Lorena. « Critical Success Factors for Large and Distributed Agile Software Development Projects Using Scrum in U.S.-Based Global Companies ». Thesis, Capella University, 2018. http://pqdtopen.proquest.com/#viewpdf?dispub=10748199.

Texte intégral

Résumé :

This study expands upon research previously conducted on critical success factors for the implementation of agile software development methodologies. The purpose was to examine the relationships between 12 independent variables, representing possible critical success factors for agile software development projects (Management Commitment, Organization Environment, Team Environment, Team Capability, Customer Involvement, Project Management Process, Project Definition Process, Agile Software Engineering Techniques, Delivery Strategy, Project Nature, Project Type, and Project Schedule); and the dependent variable of project success, consisting of four dimensions (Quality, Scope, Time, and Cost). Participants in the study included 132 practitioners in U.S.-based global companies that have served as product owner, Scrum master, software developer, business analyst, and/or tester, for a completed large and distributed agile software development project using Scrum methodology. Graphical and quantitative data analysis techniques served to examine the study research model and test the hypotheses. Findings from data analysis support that all 12 critical success factors have an impact on the successful resolution of agile software development projects using Scrum methodology in U.S.-based global companies; however, with differing levels of significance. The results reflect all 12 factors are not significant for one or more of four dimensions of project success. Also, results support that five of the 12 critical success factors are significant; however, of these, three ranked higher than the others, and showed a significant effect on more than one of the dimensions of project success. These three factors are Delivery Strategy, Team Capability, and Project Definition Process.

Styles APA, Harvard, Vancouver, ISO, etc.

15

Steczko, Jan. « Analysis of companies’ experience with cross-platform development compared to native development for mobile devices ». Thesis, Linnéuniversitetet, Institutionen för datavetenskap (DV), 2016. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-54424.

Texte intégral

Résumé :

Today, there are a handful of different platforms for mobile phones. Writing an application natively for each mobile operating system is time consuming and expensive. This situation has created a need for using cross-platform frameworks, that allow programmers to create an application once and run it on all platforms. The problem is that it is not certain whether cross-platform apps can fully replace native ones, or if by using cross-platform tools some desired qualities are lost. Investigating this issue would allow to find out which one of these two application development methods is better, or in which situation it is better to choose one over the other. Such knowledge would allow to decrease development time and costs. Companies that create mobile applications on a daily basis have expertise in this area. Thus, thirteen interviews were done with thirteen distinct businesses in order to research this problem. The results showed that native development produces higher quality applications, but there are some situations where it might be better to use cross-platform frameworks.

Styles APA, Harvard, Vancouver, ISO, etc.

16

Boden, Alexander [Verfasser]. « Coordination and learning in global software development : articulation work in distributed cooperation of small companies [[Elektronische Ressource]] / Alexander Boden ». Siegen : Universitätsbibliothek der Universität Siegen, 2011. http://d-nb.info/1019027851/34.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

17

Yokomizo, Cesar Akira. « Avaliação de desempenho organizacional : um estudo exploratório em empresas brasileiras de desenvolvimento de software ». Universidade de São Paulo, 2009. http://www.teses.usp.br/teses/disponiveis/12/12139/tde-16122009-153626/.

Texte intégral

Résumé :

Este trabalho procurou unir dois temas que, embora sejam muito relevantes, parecem trilhar caminhos independentes na administração: a avaliação de desempenho organizacional e as empresas brasileiras de desenvolvimento de software. Se, por um lado, a avaliação de desempenho organizacional pretende fornecer ferramentas e processos que auxiliem os gestores na condução de seus negócios, por outro lado, o desenvolvimento de software é tido como um setor que gera empregos de alta qualificação e que exporta um produto ou serviço com margens reais bem mais altas que aquelas registradas pela pauta tradicional de exportação. Nesse cenário, uma pesquisa de interesse é entender como é que as empresas brasileiras de desenvolvimento de software fazem avaliação de desempenho organizacional. Para cumprir com os objetivos deste trabalho exploratório, foi utilizada uma abordagem tanto qualitativa (dois estudos de caso) quanto quantitativa (16 respondentes de survey). Como resultados preliminares, há indicação de que existe um processo de amadurecimento da avaliação de desempenho das empresas de desenvolvimento de software e esse amadurecimento inclui a diminuição da importância atribuída ao curtíssimo prazo e o aumento da importância do médio e longo prazos. Estágios mais avançados desse amadurecimento devem incluir níveis cada vez maiores de sistematização das práticas de avaliação de desempenho e também devem privilegiar determinadas dimensões de avaliação. Em relação à percepção e à prática, também como resultados preliminares, percebe-se que as empresas não consideram importante preocuparem-se com as dimensões sociais e de meio-ambiente e não acreditam que eles gerem impactos positivos nos indicadores financeiros e, talvez, por esse motivo, as práticas são pouco maduras. Por fim, e talvez o resultado preliminar mais importante (até surpreendente), as empresas consideram que ter inovação e pessoas motivadas e desenvolvidas tecnicamente são as dimensões mais importantes e as que geram mais impactos positivos nos indicadores financeiros, mas elas não sabem ou não conseguem implementar indicadores para mensurá-las adequadamente.
This study has tried to bind two subjects of utmost importance but that seems to have independent pathways in Management: organizational performance measurement and Brazilian software development companies. On the one hand, organizational performance measurement intends to offer tools and processes so that managers can improve the way they run their businesses; on the other hand, the software development industry generates highly qualified jobs and exports goods and services with higher margins when compared to the Brazilian traditional export basket. As a result, a research of interest should ask how Brazilian software development companies are conducting organizational performance measurement. In order to comply with the goals of this exploratory study, both qualitative (two study cases) and quantitative (16 respondents of a survey) approaches were applied. Preliminary findings show that evidences lead to the existence of a performance measurement maturation process that software development companies undergo. According to this maturation process, companies shift their focus from the short term to the medium and long terms. More matured companies may experience a growing performance measurement systematization, even if it is non-declared at the beginning, and they should also privilege certain measurement perspectives. Regarding perception and practice, preliminary results show that companies do not perceive social and environmental perspectives as important, and they believe these perspectives do not have positive impacts on financial indicators. Consequently, practices related to these perspectives are not matured. Finally, the most important-even surprising-preliminary findings show companies believe that producing innovation and having motivated and well-trained employees are the most important perspectives to their businesses and they have positive impacts on financial indicators. Nevertheless, they do not know or they are unable to adequately implement performance measurement indicators of these perspectives.

Styles APA, Harvard, Vancouver, ISO, etc.

18

Paykina, Ekaterina, et Li Zhou. « What characteristics are suited to help choosing traditional or agile project management methods for software development projects ? » Thesis, Umeå universitet, Handelshögskolan vid Umeå universitet (USBE), 2012. http://urn.kb.se/resolve?urn=urn:nbn:se:umu:diva-54062.

Texte intégral

Résumé :

Nowadays, the nature of the projects has changed to be unique, uncertain, ambiguous,complex and innovative. It becomes hard to plan in advance the project progress, asdeviations from plans and unpredictable changes occur more frequently. This can bespecifically observed in the software development industry which needs to constantlymeet customers’ rapidly changed requirements. Traditionally, software projects aredeveloped through a plan-driven approach which emphasizes an overall project plan andcontrol process in terms of project management. Recently, this has been challenged byagile approach that focuses on flexibility to quickly meet changing requirements, andthese new agile methods provoked huge interest and got more and more popular andwidely applied especially in IT industry. However, the popularity does not mean theagile methods have advantage over traditional plan-based project management methods.In fact, both methods have own advantages and disadvantages and cannot be fullyreplaced by each other. Therefore, it becomes important and necessary for companymanagement to know how to select a suitable method for the new software developmentproject to get the maximum benefits.The purpose of this study is to describe different project management methods(traditional plan-driven and agile methods) and their various consequences for themanagement of software-development projects. Additionally, a more practical purposeis to suggest on what grounds a choice between methods may be made. Morespecifically, this research aims to provide the possible solution on how to selecttraditional plan-driven or agile project management method for managing a newsoftware development project. The research conducted a qualitative study in a casecompany of IT industry through several semi-structured interviews and questionnaireswith experienced and knowledgeable employees. It started with the analysis andcomparison of traditional and agile project management methods’ characteristics andapplication domains based on two specific examples (PROPS and Scrum) selected fromtraditional and agile project management methods respectively, in order to identify a setof preliminary outstanding characteristics which could be used to help IT company tochoose project management methods for new software development projects. Theempirical data obtained from interviews of case company was investigated to verifythese characteristics based on the literature review, and further adjusted thecharacteristics identification. After going through the whole research process, finallyresearchers identified the most suitable characteristics that were important both intheory and practice to examine on what ground a software development company needsto base the selection of project management methods. These suitable characteristics are:Project Complexity, Communication, Competencies and Requirements, in order to helpselect the best management way for the specific project.

Styles APA, Harvard, Vancouver, ISO, etc.

19

Vávra, Pavel. « Podpora řízení softwarové kvality v malé firmě ». Master's thesis, Vysoká škola ekonomická v Praze, 2009. http://www.nusl.cz/ntk/nusl-15631.

Texte intégral

Résumé :

The goal of this thesis is to create a proposal of framework which can be used to support software quality management in a small development company. Framework is composed of processes, methodologies and tools which together should improve the quality of software products of a company. Concrete implementation of the framework is shown as a case study. Data for the case study were collected in the company Cleverbee, where the author worked during the case study's creation. Personal contribution of the author of the thesis is firstly the creation of the framework concept based on author's experiences and commented list of concrete results of framework's implementation. The detailed goal setting for this thesis and the definition of the target reader can be found in the chapter 1. Introduction. The definition of main terms, which will appear in the rest of the thesis, is contained in the chapter 2. Terms. Chapter 3. Software quality and its definition is explains the term "software quality" and the nature of the small companies. Chapter 4. Software quality management forms the theoretical foundation of the thesis. In this chapter you find how the methodologies RUP and CMMI view the software quality. Chapter 5. Framework concept contains the concept of the software quality management framework. Framework is based upon relevant sources and also author's personal experience. The chapter 6. Case study describes the concrete example of the implementation of the proposed framework. The case study also contains descriptions of the used software tools. The chapter 7. Conclusion contains the brief resume of the findings of the thesis.

Styles APA, Harvard, Vancouver, ISO, etc.

20

Hsieh, Ying-Che. « The development of human resource management in entrepreneurial firms : based on the experiences of venture capital supported companies in Beijing's information transmission, computer services and software industry ». Thesis, University of Cambridge, 2013. http://ethos.bl.uk/OrderDetails.do?uin=uk.bl.ethos.607794.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

21

Minakhmetova, Dinara, et Anastasia Savchenko. « Mobile marketing strategy development in China, Japan and South Korea : An Apple App Store example ». Thesis, Linnéuniversitetet, Institutionen för marknadsföring (MF), 2015. http://urn.kb.se/resolve?urn=urn:nbn:se:lnu:diva-44667.

Texte intégral

Résumé :

The purpose of this master thesis is to test an individual influence of separate factors on a mobile software development company’s position in a rating of Top Grossing applications in Asian countries, explain how these factors could be interpreted from a modified 4P framework perspective and understand how a mobile developer can adjust its strategy based on the identified factors. The research is based on a ranking data of 90 finance management applications for iPhone on the App Store of China, South Korea and Japan. The hypotheses about an existence of causal relationships between the identified factors and software’s position in the rating of Top Grossing finance mobile applications were tested. The research is based on a multiple regression analysis, conducted separately on the Chinese, South Korean and Japanese markets. In the findings of the research the authors state that a position of financial mobile software in the Apple App Store rating of Top Grossing applications is determined by a unique set of factors, which vary across the studied Asian markets, while a number of factors converge. The models designed for the markets of China, South Korea and Japan allow to identify which factors can potentially elevate the position of an application in the rating of the most profit generating financial programs (Top Grossing rating) and based on that gain an understanding of the way a mobile software company’s marketing strategy could be adjusted to better meet customers’ needs on the studied markets. The originality of this master thesis is in the development of a new approach to the analysis of a mobile software development company’s performance regarding its position in Top Grossing ranking. Since the market of mobile applications emerged only in 2008 the factors influencing the performance of mobile developing companies have not been theoretically discussed before.

Styles APA, Harvard, Vancouver, ISO, etc.

22

Hagsten, Per. « Evaluation of a qualitative model for a company's technical maturity within Continuous Integration, Continuous Delivery and DevOps ». Thesis, KTH, Skolan för elektroteknik och datavetenskap (EECS), 2018. http://urn.kb.se/resolve?urn=urn:nbn:se:kth:diva-233554.

Texte intégral

Résumé :

The purpose of this study is to continue development of a benchmarking model to help companies assess their technical maturity when it comes to adopting Continuous Integration, Continuous Delivery and DevOps in their organization. The goal of the research is to assess how to improve the quality of qualitative models. Which conclusions can be drawn from comparing companies using benchmark and to assess which actions are the most effective to take to reach higher Continuous Integration, Continuous Delivery and DevOps maturity. The benchmark consisted of a questioner of two hundred statements that were answered for level of agreement with a current situation analysis and an ought-to-be analysis to be able to draw conclusions from the possible discrepancy between these categories. The questioner was answered during an interview study with chosen clients. Conclusions drawn from this study were that a lot can be done to improve the quality of qualitative models for examining Continuous Integration, Continuous Delivery and DevOps maturity. Different actions are necessary but the most important seems to be to ask open ended questions as well ass questions about different aspects of the same problem to promote discussion. It was also showed to be important to peer review the questions in the interview material beforehand to increase quality. The study also showed that it is possible to see trends in Continuous Integration, Continuous Delivery and DevOps maturity when comparing qualitative results for research subjects. The study showed that the most effective method for increasing Continuous Integration, Continuous Delivery and DevOps maturity is to use extensive automated testing suites that covers all testing disciplines.
Syftet med studien är att vidareutveckla ett benchmarkingverktyg för att hjälpa företag att bedöma sin tekniska mognad när det gäller att anta Continuous Integration, Continuous Delivery och DevOps i sin organisation. Målet med forskningen är att bedöma hur man kan förbättra kvaliteten på kvalitativa modeller för att mäta detta, samt vilka slutsatser som kan dras av att jämföra företags resultat som nyttjat studien. Samt att undersöka vilka åtgärder som är effektivast att ta för att nå en högre mognadsgrad inom Continuous Integration, Continuous Delivery och DevOps. Benchmarken bestod av ett frågebatteri av tvåhundra påståenden som besvarades av kunden i hur mycket de instämde till ett påstående. Resultatet samanställdes till en aktuell nulägesanalys och en börlägesanalys, med målet att dra slutsatser i vilka skillnaden som fanns mellan dessa två kategorier. Kunden besvarade frågebatteriet under en intervjustudie med utvalda anställda. Slutsatser som härrör från denna studie var att mycket kan göras för att förbättra kvaliteten på kvalitativa modeller för att undersöka Continuous Integration, Continuous Delivery och DevOps mognadsgrad. Olika åtgärder är möjliga, men det viktigaste förefaller vara att fråga öppna frågor för att främja diskussion samt att ställa frågor om olika aspekter av samma problem. Samt att opponera frågorna internt i intervjuundersökningen innan det utförs hos en kund, för att öka kvaliteten. Studien visade också att det även är möjligt att se trender i Continuous Integration, Continuous Delivery och DevOps mognad hos deltagarna när man jämför de kvalitativa resultaten. Studien visade att de mest effektiva metoderna för att öka Continuous Integration, Continuous Delivery och DevOps mognadsgrad är att använda omfattande automatiserade testsviter för samtliga testmetoder.

Styles APA, Harvard, Vancouver, ISO, etc.

23

Molina, Rafael Antonangelo. « Inovação em empresa de tecnologia de informação para mobilidade urbana sustentável ». Universidade de São Paulo, 2017. http://www.teses.usp.br/teses/disponiveis/12/12142/tde-08012018-114012/.

Texte intégral

Résumé :

A experiência profissional em uma empresa de tecnologia centrada na mobilidade urbana permitiu a identificação de três ganhos principais da aplicação de sistemas de informação na operação de ônibus urbanos: econômicos, sociais e ambientais. Porém, no desenvolvimento de novos modelos de negócios foram identificadas dificuldades em posicionar o ganho ambiental como uma proposta de valor para os principais clientes da empresa: empresas operadoras de ônibus urbanos. Baseado nessa problemática, desenvolveu-se esta pesquisa, norteada pela busca por uma proposta de valor que possa ser apresentada por empresas de tecnologia focadas na mobilidade urbana para tornar tangível ganhos ambientais aos seus clientes. Para tanto, foi levantado o histórico de atuação que delineia o modelo de negócio das empresas de ônibus, seu contexto de atuação frente ao movimento de cidades inteligentes, com aumento de atenção às questões ambientais e a aderência da tecnologia a seus processos operacionais. Esse panorama sustentou a identificação de proposta de valor inicial de um sistema de informação para apoio a processos de gestão ambiental em empresas de ônibus. Esse produto foi então exposto aos profissionais de tecnologia e de transporte, para verificação de sua proposta de valor e construção. Os retornos desses profissionais permitiram definir uma proposta de valor alinhada ao interesse de empresários de ônibus em computar indicadores de sustentabilidade de suas operações, especialmente no que tange a gestão ambiental. O produto que entrega essa proposta de valor teve então sua viabilidade de implantação verificada, mediante a valoração junto aos clientes, precificação e custos de desenvolvimento e manutenção
The professional experience in a technology company focused on urban mobility allowed the identification of three main advantages to information systems application in the urban buses operation: economic, social and environmental. However, in the development of new business models, difficulties were identified in positioning the environmental gain as a value proposition for the company\'s main customers: urban bus operators. Based on this problem, this research was developed, guided by the search for a value proposition that can be presented by technology companies focused on urban mobility to achieve environmental gains to their clients. In order to do so, the company\'s history of action was drawn up, outlining the business model of bus companies, their context of action in relation to the movement of smart cities, increasing attention to environmental issues and the adherence of technology to their operational processes. This set supported the identification of initial value proposition of an information system to support environmental management processes in bus companies. This product was then exposed to technology and transportation professionals to verify their value and construction proposal. The feedbacks of these professionals allowed us to define a value proposition according with the interest of bus operators in computing sustainability indicators of their operations, especially regarding environmental management. The product that pack this value proposition had its viability of implementation verified, through customers\' valuation, pricing and development and maintenance costs.

Styles APA, Harvard, Vancouver, ISO, etc.

24

Guedes, Nuno Tiago de Carvalho. « Collaborative Networks : Perspectives from Software Development Companies ». Dissertação, 2014. https://repositorio-aberto.up.pt/handle/10216/77527.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

25

Guedes, Nuno Tiago de Carvalho. « Collaborative Networks : Perspectives from Software Development Companies ». Master's thesis, 2014. https://repositorio-aberto.up.pt/handle/10216/77527.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

26

Wilson, Magnus. « Towards Effective and Efficient Business Model change : Opportunities and challenges for software-intensive product development companies ». Licentiate thesis, 2019. http://urn.kb.se/resolve?urn=urn:nbn:se:bth-17759.

Texte intégral

Résumé :

Digitalization initiates and drives significant changes to the process level, organization level, and business level of software-intensive product development (SIPD) companies and their customers. Digitalization creates new opportunities through digital transformation strategies of the business environment. Digitalization also significantly reduces the turnaround-time on a transaction, driving new challenges for the alignment of business and technology changes. For a successful business model realization, a company must understand what capabilities the organization has (in staff and products), what is required, and more importantly, how to turn these capabilities into good-enough abilities without disturbing the effectiveness and efficiency of the daily operations. Integrating the product and service development and the value delivery with a learning organization is critical for efficient business model change (BMCh). This thesis seeks to develop conceptual models for how BMCh is linked to value, learning organization design, and the transformation of capabilities into abilities derived from business model activities and actor interactions. Such conceptual models facilitate to investigate and identify critical mechanisms and capabilities needed to effectively and efficiently manage BMCh at full scale for SIPD companies, allowing them to exploit the on-going digitalization, may it be through (disruptive) business model innovation, technology innovation, or by continuously adapting and evolving the business operations. I use the SIPD company as the unit of analysis, with the dual-lens of value and knowledge, set in the context of a business model and how the value creation and capture are influenced by the interaction between two actors performing a business model activity. I build on the business model literature and infuse theories for knowledge creation, learning organizations, and contractual promises to create value. Conducting a cross-disciplinary literature review, followed by a synthesis of related literature, industry best-practices, and an associated design science study, my propositions were validated in a longitudinal case study exploring a service industrialization program in the telecommunication industry. I have produced five conceptual models and seven propositions as a start to be able to support the design of a governance mechanism, as the critical engine for both the learning organization and effective and efficient BMCh. The industry now explores the models found during the case study. My synthesis shows a need for further research into BMCh regarding early detection and measurements of gaps in value, gaps in knowledge, ambiguity, equivocality, and abilities. Flexible role-based governance views present the measurements, as part of the governance mechanisms for full-scale, effective, and efficient BMCh. Further, I also aim to implement such governance mechanisms in software, by using the associated research in intent-driven systems. In the meantime, I propose industry to build knowledge and experience related to the seven propositions.

Styles APA, Harvard, Vancouver, ISO, etc.

27

Van, der Linde Judith. « An investigation into the impact of enterprise architecture decisions on the responsibilities of software developers in companies that develop software ». Diss., 2013. http://hdl.handle.net/10500/10147.

Texte intégral

Résumé :

Enterprise Architecture endeavours to resolve the complexity of increasingly distributed systems by aligning business vision with IT strategy, which in turn should reduce the overall costs of IT in the business and provide simpler, better and faster solutions to business problems. There are many Enterprise Architecture frameworks. The main purpose of most of these frameworks is to assist with the challenges of managing the increased complexity of distributed systems, aligning business vision with IT strategy and reducing IT costs. Many of the studies which produced the results stating Enterprise Architecture aligns business vision and reduces IT costs, were based on Zachman’s work, and most of the published Enterprise Architecture success stories focus on the benefits provided to the company with regards to IT. In contrast very little documentation could be found that addresses the impact of Enterprise Architecture implementations on the individuals and systems within a company. If the individuals as the main implementers of any strategy are impacted negatively by Enterprise Architecture management decisions, there would be a negative impact on the return on investment of the company. Enterprise Architecture allows the use of overlapping departments’ processes and data, which translates into less development time as system components would already exist. Changes that are made to the Enterprise Architecture result in several additional changes that had to be implemented by the software developers. These changes influenced the workload, roles and responsibilities of the developers in such a way that the development team became negative about the additional work. The purpose of this study was to investigate the impact of Enterprise Architecture management decisions on the responsibilities, work experience and attitude towards Enterprise Architecture of the software developers in a company that develops software by exploring and describing the nature of software development. Based on the findings of this study, a list of impact of Enterprise Architecture decisions on the responsibilities of software developers in companies that develop software were identified. In this respect, the study identified impacts of Enterprise Architecture management decisions as well as possible solutions to these impacts.
Computing
M. Sc. (Information Systems)

Styles APA, Harvard, Vancouver, ISO, etc.

28

Panday, Annelee. « Recommendations for improvement to the South African information technology curriculum : a case study of new higher certificate graduates' first year of employment ». Diss., 2019. http://hdl.handle.net/10500/26211.

Texte intégral

Résumé :

Employment issues in South Africa (SA) are a significant problem. There are ongoing discussions revolving around the employability challenges facing South African graduates, particularly in the Information Technology (IT) sector. The preparedness of these IT graduates has been questioned with many looking towards skill sets and employability status while others have scrutinised the validity of the IT curriculum meeting industry needs. The research focuses on a case study of graduates from an accredited, private higher education institution in SA. The study followed a qualitative approach using questionnaires and interviews to understand the experiences of employers, employed graduates and recruitment personnel upon employment of the graduates. This study investigated, determined and confirmed recommendations to adapt the South African higher education IT curriculum to improve the productivity of IT graduates upon employment.
School of Computing
M. Sc. (Computing)

Styles APA, Harvard, Vancouver, ISO, etc.

29

Moreira, Sara Rafaela da Silva. « The Importance of Leadership in a Company's Innovativeness : A Contrasting Study of Two Software Development Enterprises ». Master's thesis, 2019. https://hdl.handle.net/10216/122076.

Texte intégral

Styles APA, Harvard, Vancouver, ISO, etc.

30

Pien, Pei Fen, et 卞珮芬. « Enterprise Software Development Resource Planning And Requirements Scheduling-A case study on a high-tech company's IT department ». Thesis, 2010. http://ndltd.ncl.edu.tw/handle/54211055854087685643.

Texte intégral

Résumé :

碩士
長庚大學
資訊管理學系
98
To promote company’s competitive ability, the requirements for the systematization of internal operation are increased continuously, but the evaluation of cost and rationality are often ignored. In additional to, managers cannot budget the man-power cost accurately because development requirements came up roughly, it causes development resource or schedule conflict always. Due to these reasons, it’s necessary to create some fair, rational and transparent criterions for evaluation, also to prioritize bases on company’s maximum profits. Furthermore, a managerial and planning model can quick response the variation will benefit to an enterprise’s productivity and capability. The methodology is focus on the entire requirement management of in-house design systems. Firstly, to utilize the theories of “Multiple criteria decision making”　and “Eigenvector method” on requirement evaluation; “Exponential smoothing with trend forecasting method” to forecast the required workload of coming year; “Mix integer linear programming” to come out man-power strategy; Lastly, “What-if analysis” will be proposed to managers for the reference of decision making.

Styles APA, Harvard, Vancouver, ISO, etc.

31

Chu, Shang-chun, et 祝尚駿. « Exploring the development path of Package Software Vendor based on Dynamic Capabilities Perspective- A case study of Strategy Companion Corporation ». Thesis, 2013. http://ndltd.ncl.edu.tw/handle/13354835783060344081.

Texte intégral

Résumé :

碩士
國立臺灣科技大學
管理學院MBA
101
In today’s society, as time evolves, the development of technology is moving towards a rapidly changing and highly unstable nature. This kind of Industrial structure and environment creates not only opportunities but also competition and threats. When facing the environment mentioned above, firms in technology industry need to accumulate as many core competencies as possible and adjust themselves according to the changing trends in the environment. Therefore, how to increase and update one’s strength and advantages to cope with the rapidly changing market environment and demands becomes an important topic. Since the development of Strategy Management theories, the topic on how to maintain a firm's competitive advantage has been one of the most discussed topics. In year 1997, Teece proposed the Dynamic Capabilities perspective, he advocates that in order to respond to the rapid changing environment, firms should establish, integrate and reconfigure its resource base and capabilities. This paper adopts the case study method by using the three different dynamic capabilities; sensing, seizing and transforming as the framework to explore how a package software firm creates competencies and continue to grow in a rapidly changing environment. In conclusion, this paper highlights the role of dynamic capabilities during the development progress of a new venture and to provide a point of view on the relationship between the three different dynamic capabilities. This paper also aims to contribute an example for future new ventures in Taiwan’s software industry to assist them in setting up their initial business development strategy.

Styles APA, Harvard, Vancouver, ISO, etc.

Thèses sur le sujet « Software development companies »

Créez une référence correcte selon les styles APA, MLA, Chicago, Harvard et plusieurs autres