<p>Systemutvecklingsmetoder har funnits för att utveckla system och</p><p>programvaror sedan vattenfallsmodellen gjorde sin introduktion på den</p><p>tiden då IT kallades för data processning. Sedan dess har det funnits ett</p><p>antal metoder, vissa av dem används än idag. Gemensamt för de flesta</p><p>metoderna är att de är anpassade till mycket komplexa system som används</p><p>inom stora organisationer. Inom det Svenska samhället så fanns det år 2005</p><p>över 890 000 småföretag (0-49 anställda) enligt statistiska centralbyrån.</p><p>Det är lätt att förstå att småföretagen är viktiga för Sverige. För att Sveriges</p><p>småföretag skall kunna överleva i en allt tuffare konkurrenssituation så är</p><p>det viktigt att de hela tiden effektiviserar sina verksamhetsprocesser med</p><p>exempelvis innovativa IT lösningar. Denna rapport kommer att undersöka</p><p>tänkbara systemutvecklingsmetoder till småföretag och där efter</p><p>specialanpassa en metod.</p> / <p>System development methods have existed to develop systems and</p><p>programs since the waterfall model was introduced when IT was called</p><p>data processing. There have been a number of methods since that day,</p><p>some of them are still used. A common denominator for the most software</p><p>development methods are that they where all developed to support software</p><p>engineering to complex system in large organizations. Within the Swedish</p><p>society there were over 890 000 small businesses (0-49 employed) in year</p><p>2005 according to statistiska centralbyrån. It’s no secret that the small</p><p>businesses are very important to Sweden. To assure survival when the</p><p>competition gets harder the small businesses must the entire time look over</p><p>there business processes. Sometimes this means that they need new custom</p><p>made IT systems. This thesis will examine possible system development</p><p>methods for small Swedish businesses and adopt one method to fit small</p><p>business software development.</p>

Control and flexibility may appear an unlikely pair. However, I propose that effective management of dynamic environments, such as systems development under conditions of uncertainty, must still provide clear control mechanisms to manage the progress and quality of the resulting products. This dissertation presents research to understand the types of control used in the context of flexible software development processes. The dynamic capabilities extension to the resource-based view of the firm is used to understand dynamic environments. Within those environments, control theory is used to understand how activities are guided and controlled to achieve management objectives. Specifically, control theory acts as a lens to contrast the control mechanisms found in plan-driven and flexible processes. I extend current thinking to include emergent outcome controls for team coordination in a taxonomy of control mechanisms. These phenomena are studied through a qualitative field study. The results show that organizations will choose more flexible management approaches as uncertainty increases, and that more controlled-flexible approaches managed with emergent outcome controls will lead to better outcomes than uncontrolled, ad hoc approaches.

All the work was devoted to the education and development of employees in small and medium enterprises. The main aim of the work was to evaluate the present state in this field in a firm chosen, and to find and refer to the drawbacks which can occur in a common life. Making a suggestion of changes was part of the work

A escolha entre o uso de metodologias ágeis ou metodologias tradicionais de desenvolvimento de software continua sendo amplamente discutida em vários aspectos, sendo um deles a presença ou ausência de certos fatores que precisam ser identificados para que as aplicações das metodologias sejam realizadas com sucesso. Neste estudo, tanto metodologias ágeis quanto tradicionais são discutidas através da literatura desde seu surgimento, histórico e evolução, até estudos comparativos entre ambas e outros com evidências empíricas, embora ainda haja a necessidade de estudos deste último tipo para o domínio. Com o intuito de avaliar as adequações dos tipos de metodologia para os diferentes cenários que uma organização ou projeto pode apresentar a partir dos fatores encontrados na literatura, foram realizadas entrevistas e questionários com pessoas envolvidas em desenvolvimento e definição de processos de desenvolvimento de software em um estudo de caso em empresa selecionada para a obtenção de mais evidências empíricas sobre o tema. Com os resultados obtidos, identifica-se então entre os fatores estudados quais são habilitadores e quais são inibidores para cada tipo de metodologia, propondo-se um modelo para a escolha de um ou de outro tipo a partir da presença ou ausência destes fatores nos cenários de aplicação das metodologias. / The choice between agile or traditional software development methodologies continues to be widely discussed in several aspects, being one of these aspects that certain factors presence or absence must be identified for methodologies usage to be successful. In this study, both agile and traditional methodologies are discussed on the domain literature from their emergence, historical facts and evolution, to comparative studies and empirical evidences obtained, despite there is still need for studies on this last subject for the domain. In order to evaluate adequacy for both types of methodologies to the different scenarios in which an organization or project may occur considering the factors appointed by literature, interviews and surveys where done with key people involved in software development or software processes in a case study in a selected company for more empirical evidence achievement. Then it is possible to identify between the factors which are enablers and which are inhibitors for each type of methodology, then purposing a model for the choice between the two types from the presence or absence of these factors in the scenarios for their uses.

In this thesis we investigate the usage of several agile software development methods as well as the usage of certain agile core practices. By conducting a web survey, we examine what makes these practices beneficial and what tends to make them rather less suitable for certain situations. Based on the results, we finally set up some recommendations for practitioners to reflect upon and improve their own software development process. Concerning these recommendations as well as the list of the investigated practices, we hope (and are almost sure) that there are some practices or ideas contained which are worth at least thinking about. The main findings of this thesis are: - Agile software development methods have already entered the professional market but they are still no cure-all. In many cases they also produce only middle-quality software. Nevertheless, there is – even if only little – evidence that at least XP projects meet the requirements of the customer better than traditional, non-agile methods. - For a successful software development project it is important that it has a suitable requirements engineering process, that the produced software is tested sufficiently (using automated regression testing among other types of testing), that there is a good communication between the customer and the developer side, that the risks of the project are considered, that the pros and cons of practices are considered and that processes are improved continuously. - Besides, it is important to consider the whole context when implementing a certain practice. For some contexts, certain practices do not fit for their purpose and this has to be realized. However, certain shortcomings of a specific practice might be reduced or even eliminated if implemented in combination with other practices.

In this thesis, we tried to solve those problems by adapting agile development methods with Non-functional requirements-framework (NFR-Framework). In this thesis, we have inspected many research papers, and we have met industrial experts for feedback regarding our theoretical results. As a result of the inspection, we have been able to adapt agile development methods (extreme programming (XP)) with NFR-framework. We use XP since it is more practically oriented process than other agile development methods. In the first try for this process model, we got three alternatives for applying it. The first one is based on collecting all NFRs from the beginning of the development process. The second one is based on updating the SIG (software interdependency graph) every time we have new functional requirements (FR) and the third one is based on the incremental nature of agile development methods. Each one of these alternatives has it is own advantages and disadvantages. We tried to extract those advantages and disadvantages by brainstorming and reading research papers. The most important issue in all of the three alternatives is the applicability. Finally we got industrial feedback regarding all of them. As a result of the industrial feedback, we were able to find another alternative of how to apply the process model which is presented in 7.2.

Systemutvecklingsmetoder har funnits för att utveckla system och programvaror sedan vattenfallsmodellen gjorde sin introduktion på den tiden då IT kallades för data processning. Sedan dess har det funnits ett antal metoder, vissa av dem används än idag. Gemensamt för de flesta metoderna är att de är anpassade till mycket komplexa system som används inom stora organisationer. Inom det Svenska samhället så fanns det år 2005 över 890 000 småföretag (0-49 anställda) enligt statistiska centralbyrån. Det är lätt att förstå att småföretagen är viktiga för Sverige. För att Sveriges småföretag skall kunna överleva i en allt tuffare konkurrenssituation så är det viktigt att de hela tiden effektiviserar sina verksamhetsprocesser med exempelvis innovativa IT lösningar. Denna rapport kommer att undersöka tänkbara systemutvecklingsmetoder till småföretag och där efter specialanpassa en metod. / System development methods have existed to develop systems and programs since the waterfall model was introduced when IT was called data processing. There have been a number of methods since that day, some of them are still used. A common denominator for the most software development methods are that they where all developed to support software engineering to complex system in large organizations. Within the Swedish society there were over 890 000 small businesses (0-49 employed) in year 2005 according to statistiska centralbyrån. It’s no secret that the small businesses are very important to Sweden. To assure survival when the competition gets harder the small businesses must the entire time look over there business processes. Sometimes this means that they need new custom made IT systems. This thesis will examine possible system development methods for small Swedish businesses and adopt one method to fit small business software development.

This thesis provides a tour of main software development methods and their assimilation with usability. Various software development methods have been developed since the origin of software products, and with integration of usability they have achieved great heights. Software developers and researchers are also keen to integrate usability with their methods to develop a successful software product, as their product might not lose its grip over their competitors. This thesis is a preliminary literature review that provides solutions to key questions such as: Which development methods are used in projects with high demands on usability?Do agile methods positively contribute to the usability of the product? Do projects with high demands on usability use usability specialists?Which types of usability are addressed in articles relating development methods and usability? The research aim is to identify how software development methods deal with usability. This thesis clearly discusses about previous empirical studies on software development methods and usability. In this thesis, Kitchenham’s systematic literature review was followed to extract the knowledge from the databases (Inspec and ACM). Validation on the literature is performed using Cohen’s kappa value with a researcher. Four research questions mentioned above are discussed in detail to analyse the results. Agile software development methods have been widely deployed due to its iterative, incremental approach and positive contribution towards usability rather than traditional approach. The role of an usability expert has been analyzed in this thesis and their need in the development process. Futhermore, various usability types like satisfaction, efficiency and effectiveness have also been discussed in detail. Finally, this thesis suggess a solution of incorporating usability with software development methods.

The diploma thesis is focused on defining the peripheral regions in the Czech Republic. This topic is still very actual, both nationally, and internationally. Study of definition of unexposed regions is a part of comprehensive research of the territory polarization. Concern about this question was intensifying during the nineties. This time was characterized by growing differentiation between regions. This evoked interest about rise and progress of periphery. The theoretical part consists of important concepts, major theoretical approaches, policies and principles, which define the periphery of concern. Also development of interest in the Czech Republic is described as well as situation in foreign countries and time comparison. Practical knowledge of methods in the Czech Republic are summarized in conclusion of the thesis.

Agile software development methods, characterized by delivering customer value via incremental and iterative time-boxed development processes, have moved into the mainstream of the Information Technology (IT) industry. However, despite a growing body of research which suggests that a predictive manufacturing approach, with big up-front specifications, detailed estimates, and speculative plans applicable to manufacturing domains, is the wrong paradigm for software development, many IT organizations are still hesitant to adopt agile approaches (Larman, 2004). This study extends research based on the Unified Theory of Acceptance and Use of Technology (Venkatesh, Morris, Davis, & Davis, 2003) into the domain of business processes. Specifically, processes related to the `behavioral intent' to adopt agile software development methods. Further, it investigated relationships between adoption and the impact on project performance attributes. A sample was obtained from a population of IT practitioners from within the IT industry. The sampling frame consisted of members from the global Software Process Improvement Network (SPIN) chapters, Agile User Groups, and I.T. industry conference promoters and presenters. Independent variables included performance expectancy, effort expectancy, social influence, and facilitating conditions, with the dependant variable being behavioral intent to adopt agile software development methods. The independent variable of agile software development adoption and dependent variables of project performance were also included as well as predictive models relating adoption to on-time delivery of project functionality and stakeholder satisfaction. The variables in the study were measured via a 65-item questionnaire based on previous scales, and tested to ensure validity and reliability. The research questions were developed to identify correlations between performance expectancy, effort expectancy, social influence, facilitating conditions, and the behavioral intent to adopt agile software development methods. Additional questions measured the correlation between adoption and key project performance attributes. The research found positive correlations between performance expectancy, effort expectancy, social influence, facilitating conditions, and behavioral intent to adopt agile software development methods, positive correlations between adoption and on-time delivery of project functionality and stakeholder satisfaction, and weak positive correlations with post delivery defects and project success rates.