The scope of this project includes a re-engineering of the internal architecture of the Solicitation Management System (SMS), a web-based application that facilitates the running of grant proposal solicitations for the Office of Technology Transfer and Commercialization at California State University San Bernardino (CSUSB). A goal of the project is to increase consistency and efficiency of the code base of the system, making it easier to understand, maintain, and extend. The previous version of SMS was written to rely on the Spring and Hibernate frameworks. The project includes a restructuring of the system to remove reliance on the Spring framework, but maintain reliance on Hibernate. The result is an updated version of the SMS. The system was written using current technologies such as Java, JSP, and CSS.

This study represents an attempt to address and discuss some of the most significant questions in the research on virtual software development work today. The research is held as a collective case study, including three cases with distinctive characteristics in both the software projects investigated and the types of collaborations. The study aims to reveal the success factors in virtual work, especially on the issues of communication, coordination and collaboration, by presenting the unfavorable experiences and major issues encountered in each case, as well as the favorable ones and lessons learned at the end of the development processes. The collective research focuses on both the global and non-global contexts. As a result, it points out the distinctive and opposite findings of the cases, and proposes discussions of those findings according to the properties of the development settings.

In vielen Bereichen des täglichen Lebens, angefangen vom Online-Banking bis hin zur Steuerung im Flugzeug, kommt Software mit laufzeitkritischen nicht-funktionalen Eigenschaften (NFE) zum Einsatz. Die Erfüllung der NFE spielt in diesen Anwendungen eine zentrale Rolle. Um dies zu erreichen, ist eine systematische und zielorientierte Behandlung dieser Anforderungen während der Entwicklung zwingend erforderlich. NFE zeichnen sich im Gegensatz zu funktionalen Eigenschaften durch besondere Merkmale aus, die ein adaptives Vorgehen zur Definition des Entwicklungsprozesses erzwingen. In der Arbeit wird eine Methodik zur kontextbasierten Anpassung von Vorgehensmodellen an laufzeitkritische NFE auf der Basis von Prozessmustern sowie das PROKRIS-Framework als unterstützende Umgebung vorgestellt.

Title from PDF of title page. / Document formatted into pages; contains 83 pages. / Thesis (M.S.I.E.)--University of South Florida, 2003. / Includes bibliographical references. / Text (Electronic thesis) in PDF format. / ABSTRACT: Software industry is getting very competitive in the wake of recession. In most cases, an organization that quotes a lower price and promises to deliver the product at the earliest walks away with the project. But the factor of quality of the product delivered is also very important because that in turn determines the reputation of an organization, which also plays an important role in getting the next project. Interactions in a software development are dynamic in nature and involve human factors. Models are built taking into account all possible factors so as to present a realistic picture of the development process. System dynamics methodology is used to build these models in Vensim. / ABSTRACT: Three models have been proposed to help manager estimate an approximate time and cost of the project, monitor the project once the timeline is set and monitor the project development to change various factors as the development process goes through various phases of development and testing. / System requirements: World Wide Web browser and PDF reader. / Mode of access: World Wide Web.

The main aim of this thesis is to explore the industrial practices of requirements negotiation and conflict resolution within distributed software development. The motivation for this study is to get insight of the industrial practices in particular interventions (Communication tools, Models, Communication media) that used by practitioners to resolve requirements negotiation and conflicts resolution between clients and suppliers, since many researchers purposed interventions in the literature for requirements negotiation and conflicts resolution in distributed software development. Context: In Requirements Engineering, requirements negotiation and conflict resolution are crucial activities to achieve a common ground between clients and suppliers, it is considered as one of the crucial factors for delivering successful software. However, the shift from traditional collocated practices to a distributed environment offers both benefits and drawbacks which were studied earlier by researcher, but surprisingly there are few studies with insight of exploring the distributed requirements negotiations and conflict resolution practices. This research investigates the state of requirements negotiation and conflict resolution activities in distributed software development with an insight on their importance and relevance to this research area. Objectives: Overall goal of this thesis is to understand how requirements negotiations and conflict resolution are performed in distributed software development, knowing what are the available tools to perform requirements negotiation and conflict resolution, whether these existing tools are good enough to cope up with the industrial practices, knowing most widely used tools, methods and approaches, most importantly does the present research able to bridge the gap with in distributed software development? Methods: This thesis study comprises of two research methodologies. 1. Systematic mapping study (SMS)- To identify the proposed interventions in the literature to perform requirements negotiation and conflict resolution activities in Industrial Software Development within a distributed environment. 2. Industrial Survey- To identify industrial practices to perform rei quirements negotiation and conflict resolution in Industrial Software Development within a distributed environment. Results: 20 studies were identified through systematic mapping study (SMS). After analyzing the obtained studies, the list of interventions (Preparatory activities/communication tools/ Models) were gathered and analyzed. Thereupon, an industrial survey is conducted from the obtained literature, which has obtained 41 responses. Effective communication media for preparatory activities in requirements negotiations and conflict resolution are identified, validation of communication tools for effective requirements negotiations and conflict resolution is performed. Apart from the validation, this study provided list of factors that affects the requirement negotiations and conflict resolution activities in distributed software development. Conclusions: To conclude, the obtained results from this study will benefit practitioner in capturing more insight towards the requirements negotiations and conflict resolution in distributed software engineering. This study identified the preparatory activities involved for effective communication to perform requirements negotiation activities, effective tools, models and factors affecting of requirements negotiations and conflict resolution. In addition to this, validation of results obtained from the literature is carried through survey. Practitioners can be benefitted from the end results of by knowing the effective requirements negotiation and conflict resolution interventions (Communicational tools/ Models/ Communication media) for early planning in distributed software development. Researchers can extend the study by looking in to the real-time approaches followed by the practitioners to perform the both activities in the direction of future studies.

Orientadores: Marcos Augusto Francisco Borges, Regina Lúcia de Oliveira Moraes / Dissertação (mestrado) - Universidade Estadual de Campinas, Faculdade de Tecnologia / Made available in DSpace on 2018-08-24T22:28:54Z (GMT). No. of bitstreams: 1 Cantanhede_MarcoAndreDias_M.pdf: 5891395 bytes, checksum: 151886bf1ce7211aa3c33cae7ca6698a (MD5) Previous issue date: 2014 / Resumo: A área de tecnologia da informação (TI) atravessou, e continua atravessando, os mesmos desafios de qualquer outra área da indústria. Desafios como: obter bons níveis de produtividades; entender e se aproximar do cliente; reduzir custos; e produzir inovação. Para gerenciar esses desafios a área de TI tem buscado novos mecanismos, por vezes criando práticas e métodos próprios, ou os trazendo de outras áreas de conhecimento. O Lean trouxe para a indústria, primeiramente a automobilística, e depois para várias outras, um novo padrão de produção e qualidade. O Lean questionou os padrões da produção em massa e trouxe novas formas para combater o desperdício, aumentar a qualidade e obter lucratividade no longo prazo. O termo Lean IT é usado para denotar o uso do Lean no combate dos desafios da indústria de TI, e o Lean Software Development é termo usado para uso do lean na área de desenvolvimento de software. O trabalho estuda e aplicada uma ferramenta de avaliação do nível de lean para a área de software, criando um procedimento para aplicação da ferramenta no Brasil. A ferramenta e o procedimento criado foram aplicados em três empresas de Desenvolvimento de Software com diferentes perfis. Os resultados demonstraram a aplicabilidade da ferramenta de avaliação do nível de lean nas empresas selecionadas, foram apontados ajustes e apresentados a necessidade de novos estudos. Também foram revistos os autores do Lean Thinking e do Lean Software Development / Abstract: The technology information (IT) industry has been facing challenges common to any other industry type. Challenges as: achieve good productive level; understand the client need; pressure for cost reductions; and innovation. IT has been searching for solution to address these challenges, sometimes creating own methods and practices, and sometimes, bringing them from other type of industries. The Lean has showed clear benefits and introduced a new standard to the automobile industry and manufacture type of business. Mass production standards were challenged by Lean creating new ways of dealing with quality and productivity. Lean has been positioned as an important alternative to deal with waste, to increate quality and expand long term profitability. The term Lean IT is used on application of Lean to address IT industry challenges, and Lean Software Development the application of lean at software development industry. The research reviews a leanness assessment tool adapted for software industry, developing an adaptation for the application at Brazil software industry. A procedure of application was created and the tool was applied at three different Software companies (enterprises). The results showed that the tool to evaluate leanness at software is applicable at the selected companies, adjustments were need and further studies are required. Lean thinking and Lean Software Development authors were also reviewed by this research work / Mestrado / Tecnologia e Inovação / Mestre em Tecnologia

Context: Despite continuously increasing importance of Agile and Lean in software development, the number of studies that investigate on use of metrics relevant to Agile or Lean are limited and yet few studies implements was unclear. Unclear is which are the prominent metrics that are useful in industries, and their purpose of usage. Objectives: Main goal of this study is to find the metrics useful in Agile and Lean practicing industries; that are evaluated in industries by systematically identifying all the metrics from empirical evidence found in Literature as well as verifying which of them are prominently being used in industries. In addition, the purpose of using these metrics in industries are reported, and causes for dissatisfaction on use of some of the identified metrics among surveyed companies are investigated and reported. Methods: Two research methodologies are used; Systematic Literature Review (SLR) and Industrial Survey. SLR is performed using snowballing as search approach to select primary studies. SLR is used to identify all the metrics that are useful for Agile and Lean software development. Rigor and relevance analysis is performed to assess the quality of the resulted primary studies. Industrial survey was conducted in order to verify and extend the empirical evidence exists in Literature regarding metrics by finding which of them are more prominently being used. Moreover causes for dissatisfaction over outcome of metrics use for process improvements were observed by performing comparative analysis between unsatisfied respondents results and satisfied respondents results. Results: In total 20 metrics were identified from the studies having high rigor and high relevance. Moreover 11 out of these 20 metrics were identified to be prominently being used in industries using survey and other 9 metrics are found useful for Agile or Lean methods but need more awareness. Evidence from both SLR and survey shows that most of these identified or potential metrics are used for time associated purposes which are predictability, tracking, forecasting or planning, and very little evidence found for metrics that are being used directly for quality purpose. It was observed that some of the surveyed respondents who answered not satisfied with the metrics being used are not aware of the potential benefits these metrics can offer in Agile or Lean settings. Conclusion: Evidence from both SLR and survey shows that the identified 20 metrics are very important and useful for Agile or Lean methods. 11 out of these 20 metrics are prominently being used by industries and evidence shows for other 9 metrics are also useful for Agile but needs more awareness for industries to realize their potential benefits in large scale. Also, more evidence is found for metrics that are used for time related purposes which are being dominant and important in industries than quality focused metrics. Therefore, it is important for industries not only to know which metrics are appropriate for Agile or Lean but also to have a deep understating of metrics behaviors. This will help to realize the level predictability these metric’s offer in order to make right assumptions or planning. / Mobile no: (+46)-723110118

Context. Global Software Development (GSD) is the plan of action in which software development is performed under temporal, political, organizational and cultural boundaries. Offshore outsourced software development is the part of GSD, which refers to the transfer of certain software development activities to an external organization in another country. The primary factors driving offshore outsourced software development are low cost, access to a large pool of skilled laborers, increased productivity, high quality, market access and short development cycle. Requirements engineering (RE) and especially requirements elicitation is highly affected by the geographical distribution and multitude of stakeholders. Objectives. The goal of conducting this study is to explore the challenges and solutions associated with requirements elicitation phase during offshore software projects, both in research literature and in industrial practice. Moreover, this study examines that which of the challenges and practices reported in literature can be seen in industrial practice. This helped in finding out the similarities and differences between the state of art and state of practice. Methods. Data collection process has been done through systematic literature review (SLR) and web survey. SLR has been conducted using guidelines of Kitchenham and Charters. During SLR, The studies have been identified from the most reliable and authentic databases such as Compendex, Inspec (Engineering village) and Scopus. In the 2nd phase, survey has been conducted with 391 practitioners from various organizations involved in GSD projects. In the 3rd phase, qualitative comparative analysis has been applied as an analysis method. Results. In total 10 challenges and 45 solutions have been identified from SLR and survey. Through SLR, 8 challenges and 22 solutions have been identified. While through industrial survey, 2 additional challenges and 23 additional solutions have been identified. By analyzing the frequency of challenges, the most compelling challenges are communication, control and socio-cultural issues. Conclusions. The comparison between theory and practice explored the most compelling challenges and their associated solutions. It is concluded that socio-cultural awareness and proper communication between client and supplier organization’s personnel is paramount for successful requirements elicitation. The scarcity of research literature in this area suggests that more work needs to be done to explore some strategies to mitigate the impact of additional 2 challenges revealed through survey. / 0046 707123094

Context: In Web applications, the Software vulnerability can be reduced by applying security testing in all phases of the software development life cycle (SDLC). Lot of vulnerabilities might occur if the security testing is applied in the last phase of SDLC. In order to mitigate these vulnerabilities, a lot of rework is required that involves reverse engineering in the development and design phases. To overcome this situation, organizations are shifting from security testing (performed in last phase) towards security testing in the early phases of SDLC. Objectives: The main objectives of this thesis are to gather the benefits and challenges of security testing in the last phase versus security testing in every phase of the SDLC. After gathering, authors want to compare both implementations because these days most organizations are shifting from last phase to every phase of SDLC. Justification to the reason can be achieved by this comparison. Methods: In order to satisfy the objectives of this thesis, a literature review and interviews were conducted. The literature review was conducted by gathering benefits and challenges of last phase and every phase of SDLC. Authors have applied coding technique to the data gathered from literature review. By using the results from literature review, a set of questions were framed. Based on these questions, interviews in various organizations were performed. To analyze the practitioner’s data we used Sorting and Coding technique. Then, we conducted a comparative analysis to compare both results. Results: Application of security testing in the last phase of the SDLC results in a lot of rework which in turn leads to instability in managing the cost, time and resources in an organisation. In order to overcome this, more and more organisations are introducing security testing at each and every phase of SDLC. Conclusions: It can be concluded that every phase of security testing in SDLC has more benefits than applying in last phase of SDLC. To evaluate this process more research is needed to acquire more knowledge of security testing in all phases of SDLC. Through literature review and interviews conducted, it is evident that security testing at early phases causes a reduction in rework which in turn leads to more efficient management of cost, time and resources of a project. / +91 8977404640

The development of enterprise software is a complex activity that requires a diverse set of stakeholders to communicate and coordinate in order to achieve a successful outcome. In this dissertation I introduce a high-level physical architecture for a platform titled FeatureIT that has the goal of supporting the collaboration between stakeholders throughout the entire Software Development Life Cycle (SDLC). FeatureIT is the result of unifying the theoretical foundations of the multi-disciplinary field of Computer Supported Cooperative Work (CSCW) with the paradigm and associated technologies of Web 2.0. The architecture was borne out a study of literature in the fields of CSCW, Web 2.0 and software engineering, which facilitated the identification of functional and non-functional requirements necessary for the platform. The design science research methodology was employed to construct this architecture iteratively to satisfy the requirements while validating its efficacy against a comprehensive set of scenarios that typically occur in the SDLC. / Computing / M. Sc. (Information Systems)