A product line organization using an open development method

Opening access to the source code for a product is a business strategy that is increasingly used as the basis for innovative collaborations with stakeholders. The strategy has been successful at producing a large quantity of high-quality software. A tactic in this strategy is to effectively use the efforts of many widely dispersed professionals. The processes, software tools and the communication mechanisms used to facilitate concurrent development by a large number of people are of as much interest as the software being created. In this position paper we present our view of how a software product line organization might operate if it used an open development method (ODM) but is not necessarily producing open source software. We will describe a hypothetical product line (HPL), which is part speculation, part our experience, and partly the experience of others

ERP implementation for an administrative agency as a corporative frontend and an e-commerce smartphone app

This document contains all the descriptions, arguments and demonstrations of the researches, analysis, reasoning, designs and tasks performed to achieve the requirement to technologically evolve an managing agency in a way that, through a solution that requires a reduced investment, makes possible to arrange a business management tool with e-commerce and also a mobile application that allows access and consultation of mentioned tool. The first part of the document describes the scenario in order to contextualize the project and introduces ERP (Enterprise Resources Planning). In the second part, a deep research of ERP market products is carried out, identifying the strengths and weaknesses of each one of the products in order to finish with the choice of the most suitable product for the scenario proposed in the project. A third part of the document describes the installation process of the selected product carried out based on the use of Dockers, as well as the configurations and customizations that they make on the selected ERP. A description of the installation and configuration of additional modules is also made, necessary to achieve the agreed scope of the project. In a fourth part of the thesis, the process of creating an iOS and Android App that connects to the selected ERP database is described. The process begins with the design of the App. Once designed, it is explained the process of study and documentation of technologies to choose the technology stack that allows making an application robust and contemporary without use of licensing. After choosing the technologies to use there are explained the dependencies and needs to install runtime enviornments prior to the start of coding. Later, it describes how the code of the App has been raised and developed. The compilation and verification mechanisms are indicated in continuation. And finally, it is showed the result of the development of the App once distributed. Finally, a chapter for the conclusions analyzes the difficulties encountered during the project and the achievements, analyzing what has been learned during the development of this project

Influential factors of aligning Spotify squads in mission-critical and offshore projects – a longitudinal embedded case study

Changing the development process of an organization is one of the toughest and riskiest decisions. This is particularly true if the known experiences and practices of the new considered ways of working are relative and subject to contextual assumptions. Spotify engineering culture is deemed as a new agile software development method which increasingly attracts large-scale organizations. The method relies on several small cross-functional self-organized teams (i.e., squads). The squad autonomy is a key driver in Spotify method, where a squad decides what to do and how to do it. To enable effective squad autonomy, each squad shall be aligned with a mission, strategy, short-term goals and other squads. Since a little known about Spotify method, there is a need to answer the question of: How can organizations work out and maintain the alignment to enable loosely coupled and tightly aligned squads? In this paper, we identify factors to support the alignment that is actually performed in practice but have never been discussed before in terms of Spotify method. We also present Spotify Tailoring by highlighting the modified and newly introduced processes to the method. Our work is based on a longitudinal embedded case study which was conducted in a real-world large-scale offshore software intensive organization that maintains mission-critical systems. According to the confidentiality agreement by the organization in question, we are not allowed to reveal a detailed description of the features of the explored project

Software Reuse in Agile Development Organizations - A Conceptual Management Tool

The reuse of knowledge is considered a major factor for increasing productivity and quality. In the software industry knowledge is embodied in software assets such as code components, functional designs and test cases. This kind of knowledge reuse is also referred to as software reuse. Although the benefits can be substantial, software reuse has never reached its full potential. Organizations are not aware of the different levels of reuse or do not know how to address reuse issues. This paper proposes a conceptual management tool for supporting software reuse. Furthermore the paper presents the findings of the application of the management tool in an agile development organization

Pembangunan Modul Pengajaran Kendiri (MPK) keusahawanan dalam topik isu keusahawanan bagi pelajar diploma di politeknik

Terdapat pelbagai kaedah pembelajaran yang telah diperkenalkan termasuklah kaedah pembelajaran yang menggunakan pendekatan pembelajaran bermodul secara kendiri. Kajian ini adalah bertujuan untuk mengkaji kesesuaian Modul Pengajaran Kendiri Keusahawanan dalam topik Isu Keusahawanan yang telah dihasilkan bagi pelajar yang mengikuti pengajian Diploma di Jabatan Perdagangan Politeknik. Antara aspek yang dikaji ialah untuk menilai sama ada rekabentuk modul yang dihasilkan dapat memenuhi ciri-ciri modul yang baik, MPK yang dihasilkan dapat membantu mencapai objektif pembelajaran, MPK ini bersifat mesra pengguna dan MPK yang dihasilkan membantu pensyarah menyampaikan pengajarannya dengan lebih berkesan. Kajian ini dilakukan ke atas 110 orang pelajar semester en am yang mengikuti pengajian diploma dan 4 orang pensyarah yang mengajar subjek Keusahawanan di Jabatan Perdagangan Politeknik Sultan Salahuddin Abdul Aziz Shah, Selangor. Kaedah analisa data yang digunakan dalam kajian ini ialah skor min dan peratus. Hasil daripada kajian ini menunjukkan bahawa rekabentuk modul yang dihasilkan memenuhi ciri-ciri modul yang baik, MPK ini membantu untuk mencapai objektif pembelajaran, MPK ini bersifat mesra pengguna dan MPK yang dihasilkan dapat membantu pensyarah menyampaikan pengajarannya dengan lebih berkesan. Ini bermakna secara keseluruhannya, hasil kajian menunjukkan bahawa modul yang dihasilkan oleh pengkaji adalah sesuai digunakan oleh pelajar-pelajar semester enam yang mengikuti pengajian diploma di Jabatan Perdagangan peringkat politeknik. Seterusnya, beberapa pandangan telah dikemukakan bagi meningkatkan rnutu dan kualiti MPK yang dihasilkan. Semoga kajian ini dapat memberi manfaat kepada mereka yang terlibat dalam bidang pendidikan

Software test automation : a design and tool selection approach for a heterogeneous environment

textThis report describes a design approach for implementing a software test automation solution that can accommodate existing test processes in an organization. The process of implementing a software test automation solution is a large undertaking and requires careful planning to avoid unsuccessful implementations. This report outlines a design that can integrate with existing business and development processes in an organization, and recommends automation and development frameworks for achieving the test automation goals. Considerations for a heterogeneous test environment with varying types of supported operating systems, such as Windows and Linux, and multiple test execution environments, such as Java and .NET, have been made in this design and in the tool selections for the system implementation. The report also describes some of the challenges and caveats of automation in a heterogeneous environment along with recommended solutions to these challenges.Electrical and Computer Engineerin