The thesis is concerned with a comparison of two rapid web development frameworks for the Java platform - Tapestry 5 and Grails. The goal is to get acquainted with both of the frameworks, explain their basic principles and usage, compare their solution to common challenges and their contribution to faster development. Furthermore, the goal is to de fine a set of criteria for the comparison and match each one of them with their respective weights representing their importance in certain decision making scenarios. The frameworks are new and under dynamic development, therefore the bene ts of this thesis are an extensive research in foreign resources, summary of the acquired knowledge, practical usage examples and furthermore the assessment of the frameworks' strenghts and weaknesses. The conclusions and comparison quanti cation can then be used to strategically choose the appropriate framework if necessarry.

Agile development is a software development methodology that originated in 2001 (Beck, et al.). It has since gained wide recognition and use in the software industry, and is characterized by iterative development cycles. Organizations outside of the software industry are also finding ways to adapt Agile development to their contexts. BYU Independent Study (BYUIS) is an online education program at Brigham Young University that provides online courses at the high school and university levels. In April 2016, BYUIS implemented the Agile development process to the design and development of online courses. This thesis is a case study that looks specifically at the adoption of Agile at BYUIS, from its implementation in April 2016 to the time of this study in summer of 2017. The question this qualitative study seeks to answer is as follows: how and why did the adoption of the Agile development methodology to instructional design practices at BYUIS reflect or differ from the 12 principles of Agile development? To answer this research question, the researcher used multiple data sources: semi-structured interviews with three administrators, two production team managers, and three instructional designers; surveys for BYUIS student employees (i.e., scrum team members) after each week of observation; and field note observations of three Agile scrum teams for two weeks each. The data from each of these sources was analyzed through a descriptive coding process and then organized into a thematic network analysis. The Results section analyzes evidence from the interviews, surveys, and observations that reflect or differ from each of the 12 principles of Agile. The Discussion addresses three main issues of implementing Agile at BYUIS: how to accommodate for part-time schedules, the complexity of working on different projects, and how to facilitate communication in scrum teams if co-location is not possible. It also looks at how these three issues could be manifest in other organizations and introduces potential solutions. The researcher then presents suggestions for future research on Agile in instructional design or other contexts.

Erfolg macht attraktiv – das gilt auch für die Prinzipien und Methoden der agilen Softwareentwicklung. Diese finden momentan eine weite Verbreitung, denn sie geben offenbar gute oder zumindest bessere Antworten auf die Probleme, mit denen die herkömmlichen Projektmethoden nicht zurande kommen (Royce 1970). Agile, manchmal auch »leichtgewichtig« genannte Methoden vermeiden übermäßige Planung und Spezifikation, sie ersetzen sie durch eine schnelle Abfolge von Zyklen aus Aktion-Reflexion und Neuausrichtung. Sie bevorzugen die Kollaboration unter gleichberechtigten Experten, die Kommunikation statt Weisung. Und sie beziehen den Kunden und späteren Nutzer bereits in die Entwicklungsarbeit mit ein, denn der Kunde ist die wichtigste Informationsquelle, er bestimmt, inwiefern das Produkt für ihn nützlich ist. Durch solche Prinzipien ist es möglich, Zeit- und Budgetüberschreitungen besser zu vermeiden, einen produktiven Umgang mit Ungewissheit und wechselnden Situationen zu entwickeln und schonender mit der menschlichen Arbeitskraft umzugehen (Abrahamsson et al. 2003). So hat sich das Konzept der »Agilität« auch auf andere Bereiche übertragen, z.B. auf die Gründung von Unternehmen (»Lean Start Up«, Ries 2011) oder die Gestaltung von Organisationsstrukturen (»Agile Organisation«, Richardson 2005). [... aus dem Text]

In the rapidly changing market of today, companies need to be responsive and react quickly to changes in both their competitors’ behaviour but also to changes in their own technical environment. In this thesis I have examined the agile characteristics of a number of companies in Stockholm, with focus on three agile concepts; Scrum, eXtreme Programming and Test Driven Development. The work started off by a prestudy, in which I have identified the criteria that a company needs to fulfil in order to be considered agile. This resulted in four main categories of characteristics; Quality, Flexibility, Communication and Competence. After doing the prestudy, these characteristics were investigated through a combination of a quantitative study and a case study. While the results mostly lean towards agile behaviour rather than non agile, it was shown that a lot of work still remains, for instance regarding improvements in the communications area, and also in the way these companies apply the agile methodologies examined. / Inom dagens snabba marknad behöver företag kunna reagera snabbt och effektivt på förändringar i både sina konkurrenters beteende, men också på förändringar i sin egen tekniska miljö. I den här uppsatsen har jag undersökt de agila attributen hos ett antal företag i Stockholm, med fokus på tre agila koncept; Scrum, eXtreme Programming och Test Driven Development. Arbetet inleddes med en förstudie, där jag identifierade de kriterium ett företag behöver uppfylla för att kunna anses vara agilt. Detta resulterade i fyra kategorier av attribut; Kvalitet, Flexibilitet, Kommunikation och Kompetens. Efter förstudien undersöktes dessa attribut genom en kombination av en enkätstudie och en studie av ett enskilt företag. Resultaten lutar mestadels åt ett agilt beteende hos de undersökta företagen, men jag har också kunnat påvisa att mycket arbete återstår, exempelvis inom kommunikationsområdet, och även gällande hur de observerade företagen applicerar de tre undersökta agila koncepten.

This is an open source education management system developed on React with Agile management method. Suitable for learning various languages, it is currently developed for the purpose of learning Chinese. Teachers can post assignments and announcements, and students can do lots of practice and quiz on this.

For the past few decades researchers, development agencies and government have focussed on the use of Information and Communication Technologies to improve the socio-economic status of people in underdeveloped rural communities. In recent years there has been remarkable recognition of the importance of developing systems that address the specific needs of rural communities. Education, health, commerce, government and agriculture are amongst the needs of rural communities that could well be addressed by these systems. System development is a complex process and studies have shown that if poorly conducted, the process could lead to the failure of the system being developed. Due to differences in context and application, the processes followed in the development of the rural community systems need to differ from those of commercial applications. One such difference is the choice of the Information System Development Methodology (SDM) used. Following a methodical approach to Information Systems development is important as it improves discipline, standardization and monitoring of a quality system. There are hundreds of SDM available for use during development and choosing the wrong SDM has been linked to problems such as systems being delivered late, being over budget or not meeting the needs of the users. Developing systems for disadvantaged communities is different from developing system for organisations or even affluent communities. Some of the challenges that developers encounter include lack of structure, poor computer literacy, and poor infrastructure. Lack of user involvement during system development has been linked to system failures. A Living Labs approach to socio-economic development is aimed at involving multiple stakeholders towards improving the living standards. Developing Community Information Systems aimed at solving varying community problems is one of the objectives of the Living Labs. There are only few CISs that are fully operational from South African Living Labs, and a number of systems developed are not in use. Poor user involvement and lack of use of system development are some of the reasons for system failures. The purpose of this study is to evaluate the use and effectiveness of System Development Methodologies when developing community information systems aimed at socio-economic development of disadvantaged communities. To achieve the objectives of this study, an interpretive, multiple case study research was conducted in three Living Labs around South Africa. To improve the chances for success during the development of Community Information Systems for use by disadvantage communities, this study proposes a framework for evaluating use and effectiveness of SDMs. The second output of the Study is an SDM framework that could be adopted specifically for Living Labs which adopts an agile approach and prototyping. These frameworks takes into account the social attributes of people in disadvantaged communities, the nature of the living lab, the nature of the systems being developed and the role of the users in the systems being developed. / PhD (Computer Science), North-West University, Potchefstroom Campus, 2014

For the past few decades researchers, development agencies and government have focussed on the use of Information and Communication Technologies to improve the socio-economic status of people in underdeveloped rural communities. In recent years there has been remarkable recognition of the importance of developing systems that address the specific needs of rural communities. Education, health, commerce, government and agriculture are amongst the needs of rural communities that could well be addressed by these systems. System development is a complex process and studies have shown that if poorly conducted, the process could lead to the failure of the system being developed. Due to differences in context and application, the processes followed in the development of the rural community systems need to differ from those of commercial applications. One such difference is the choice of the Information System Development Methodology (SDM) used. Following a methodical approach to Information Systems development is important as it improves discipline, standardization and monitoring of a quality system. There are hundreds of SDM available for use during development and choosing the wrong SDM has been linked to problems such as systems being delivered late, being over budget or not meeting the needs of the users. Developing systems for disadvantaged communities is different from developing system for organisations or even affluent communities. Some of the challenges that developers encounter include lack of structure, poor computer literacy, and poor infrastructure. Lack of user involvement during system development has been linked to system failures. A Living Labs approach to socio-economic development is aimed at involving multiple stakeholders towards improving the living standards. Developing Community Information Systems aimed at solving varying community problems is one of the objectives of the Living Labs. There are only few CISs that are fully operational from South African Living Labs, and a number of systems developed are not in use. Poor user involvement and lack of use of system development are some of the reasons for system failures. The purpose of this study is to evaluate the use and effectiveness of System Development Methodologies when developing community information systems aimed at socio-economic development of disadvantaged communities. To achieve the objectives of this study, an interpretive, multiple case study research was conducted in three Living Labs around South Africa. To improve the chances for success during the development of Community Information Systems for use by disadvantage communities, this study proposes a framework for evaluating use and effectiveness of SDMs. The second output of the Study is an SDM framework that could be adopted specifically for Living Labs which adopts an agile approach and prototyping. These frameworks takes into account the social attributes of people in disadvantaged communities, the nature of the living lab, the nature of the systems being developed and the role of the users in the systems being developed. / PhD (Computer Science), North-West University, Potchefstroom Campus, 2014

Agile practices have become norm, also in large scale organizations. Applying agile methods includes introducing continuous practices, including continuous architecture. For web scale applications microservices is a rising star. This thesis investigates if microservices could be an answer also for embedded systems to tackle the synchronizing problem of many parallel teams.

Este trabalho analisa os principais métodos ágeis utilizados em empresas startup, como scrum, extreme programming, kanban e lean, isolando suas práticas e mapeando-as no Kernel do SEMAT para escolher os elementos essenciais da engenharia de software que estão relacionados a cada prática de forma independente. Foram identificadas 34 práticas que foram reduzidas a um conjunto de 26 pelas similaridades. Um questionário foi desenvolvido e aplicado no ambiente de startups de software para a avaliação do grau de utilização de cada determinada prática. Através das respostas obtidas foi possível a identificação de um subconjunto de práticas com utilização acima de 60% onde todos os elementos essenciais da engenharia de software são atendidos, formando um conjunto mínimo de práticas capazes de sustentar este tipo específico de ambiente. / This work analyses the main agile methods used in startup companies such as scrum, extreme programming, kanban and lean, isolating their practices and mapping them on SEMAT Kernel to choose the essential elements of software engineering that are related to each practice independently. 34 practices were identified and reduced to a set of 26 by similarities. A questionnaire was developed and implemented in software startups environment to evaluate the usage degree of each particular practce. Through the responses obtained it was possible to identify a subset adopted by more than 60% of respondents where all the essential elements of software engineering are met, forming a minimum set of practices capable of sustaining this specific type of environment.

É possível notar no trabalho diário das empresas que a pressão por diminuir o prazo de entrega dos softwares ainda é uma realidade. Neste contexto, empresas adotam técnicas de desenvolvimento ágil de software, implementando entregas constantes e estabelecendo ciclos iterativos e curtos no processo de desenvolvimento de software. Mas, se por um lado estas técnicas visam inovar e reduzir tempo de desenvolvimento, por outro, as empresas sentem-se pressionadas a adotar a forma tradicional de manter a qualidade de software. Neste ponto, o CMMI se apresenta como um modelo de maturidade de reconhecimento mundial e é classificado na abordagem tradicional por pregar grande formalismo e foco no processo. A abordagem ágil coloca que os indivíduos e suas interações têm maior importância que os processos e as ferramentas e que ser adaptável às mudanças é mais importante do que seguir a rigor o planejado. Ao integrar estes dois modelos de abordagens distintas espera-se que as práticas ágeis possam ajudar organizações maduras a se tornarem mais flexíveis. Com o intuito de averiguar esta integração, utilizou-se o método de pesquisa de estudo de caso, de modo a se aprofundar nas empresas que possuem certificação CMMI e decidiram adotar o modelo de desenvolvimento ágil. O objetivo é levantar como estas empresas resolveram os pontos de conflito da abordagem tradicional e ágil, de modo a se tornarem mais eficazes. O estudo ainda contém um quadro de integração CMMI versus desenvolvimento ágil de modo a elencar os pontos que merecem maior atenção e esforço de adaptação, visando a concretização da integração. / It\'s possible to notice in the daily work of companies that pressure by decreasing the delivery of software is still a reality. It is in this context that companies adopt the techniques of agile software development, implementing and establishing constant deliveries and short iterative cycles in the process of software development. But if on the one hand these techniques aim to innovate and reduce development time, on the other, companies feel pressured to adopt the traditional way of maintaining the quality of software. At this point, the CMMI is presented as maturity model worldwide recognition, classified in the traditional approach for preaching extensive formalism and focus on the process, as the agile approach puts individuals and their interactions is more important than processes and tools, where being adaptable changes is more important than following the strict what was planned. By integrating these two models of different approaches, it is expected that agile practices can help organizations mature to become more flexible. In order to investigate this integration is that this study uses the research method of case study so as to deepen the companies that have decided to adopt CMMI and agile development model. The goal is to raise as these companies solved the trouble spots of the traditional approach and agile in order to become more effective. The study also contain a framework for integrating CMMI vs. Agile development in order to list the points that deserve more attention and effort to adapt in order to achieve integration.