Thesis (MTech (Business Information Systems))--Cape Peninsula University of Technology, 2017. / Ensuring that predetermined quality standards are met is an issue which software development companies, and the software development industry at large, is having issues in attaining. The software testing process is an important process within the larger software development process, and is done to ensure that software functionality meets user requirements and software defects are detected and fixed prior to users receiving the developed software. Software testing processes have progressed to the point where there are formal processes, dedicated software testing resources and defect management software in use at software development organisations. The research determined implications that the case study software development organisation could face when deviating from software testing processes, with a focus on function performed by the software tester role. The analytical dimensions of duality of structure framework, based on Structuration Theory, was used as a lens to understand and interpret the socio-technical processes associated with software development processes at the case study organisation. Results include the identification of software testing processes, resources and tools, together with the formal software development processes and methodologies being used. Critical e-commerce website functionality and software development resource costs were identified. Tangible and intangible costs which arise due to software defects were also identified. Recommendations include the prioritisation of critical functionality for test execution for the organisation’s e-commerce website platform. The necessary risk management should also be undertaken in scenarios with time constraints on software testing, which balances risk with quality, features, budget and schedule. Numerous process improvements were recommended for the organisation, to assist in preventing deviations from prescribed testing processes. A guideline was developed as a research contribution to illustrate the relationships of the specific research areas and the impact on software project delivery.

Thesis (M. Tech. (Information Technology)) -- Central University of technology, Free State, 2013 / This study compared the usability of three Information and Communication Technology (ICT) network programs in a learning environment. The researcher wanted to establish which program was most adequate from a usability perspective among second-year Information Technology (IT) students at the Central University of Technology (CUT), Free State. The Software Usability Measurement Inventory (SUMI) testing technique can measure software quality from a user perspective. The technique is supported by an extensive reference database to measure a software product’s quality in use and is embedded in an effective analysis and reporting tool called SUMI scorer (SUMISCO). SUMI was applied in a controlled laboratory environment where second-year IT students of the CUT, utilized SUMI as part of their networking subject, System Software 1 (SPG1), to evaluate each of the three ICT network programs. The results, strengths and weaknesses, as well as usability improvements, as identified by SUMISCO, are discussed to determine the best ICT network program from a usability perspective according to SPG1 students.

Appealing features of cloud services such as elasticity, scalability, universal access, low entry cost, and flexible billing motivate consumers to migrate their core businesses into the cloud. However, there are challenges about security, privacy, and compliance. Building compliant systems is difficult because of the complex nature of regulations and cloud systems. In addition, the lack of complete, precise, vendor neutral, and platform independent software architectures makes compliance even harder. We have attempted to make regulations clearer and more precise with patterns and reference architectures (RAs). We have analyzed regulation policies, identified overlaps, and abstracted them as patterns to build compliant RAs. RAs should be complete, precise, abstract, vendor neutral, platform independent, and with no implementation details; however, their levels of detail and abstraction are still debatable and there is no commonly accepted definition about what an RA should contain. Existing approaches to build RAs lack structured templates and systematic procedures. In addition, most approaches do not take full advantage of patterns and best practices that promote architectural quality. We have developed a five-step approach by analyzing features from available approaches but refined and combined them in a new way. We consider an RA as a big compound pattern that can improve the quality of the concrete architectures derived from it and from which we can derive more specialized RAs for cloud systems. We have built an RA for HIPAA, a compliance RA (CRA), and a specialized compliance and security RA (CSRA) for cloud systems. These RAs take advantage of patterns and best practices that promote software quality. We evaluated the architecture by creating profiles. The proposed approach can be used to build RAs from scratch or to build new RAs by abstracting real RAs for a given context. We have also described an RA itself as a compound pattern by using a modified POSA template. Finally, we have built a concrete deployment and availability architecture derived from CSRA that can be used as a foundation to build compliance systems in the cloud. / Includes bibliography. / Dissertation (Ph.D.)--Florida Atlantic University, 2015. / FAU Electronic Theses and Dissertations Collection

by Ng Mei Po Mabel. / Thesis (M.B.A.)--Chinese University of Hong Kong, 1994. / Includes bibliographical references (leave 51-52). / ABSTRACT --- p.ii / TABLE OF CONTENTS --- p.iii / Chapter / Chapter I. --- INTRODUCTION --- p.1 / Chapter II. --- PROBLEM IN FOCUS --- p.3 / Chapter III. --- SCOPE OF STUDY --- p.7 / Chapter IV. --- RESEARCH METHODOLOGY --- p.8 / Chapter V. --- ORGANISATION OF INFORMATION TECHNOLOGY SERVICES DEPARTMENT --- p.8 / Function --- p.8 / Mission --- p.8 / Organisation Structure --- p.8 / Personnel Schedule --- p.8 / Requests for Computerisation --- p.10 / Departmental IS Strategic Planning --- p.10 / Microcomputer Systems and Items --- p.10 / Mainframe Systems and Mid Range Systems --- p.10 / Chapter VI. --- SYSTEMS DEVELOPMENT LIFE CYCLE --- p.12 / Introduction --- p.12 / Detailed Description --- p.15 / What is SSADM+ in ITSD ？ --- p.22 / Implementation of SSADM+ in ITSD --- p.26 / Chapter VII. --- THE ROAD TO ACHIEVE IS09001 --- p.28 / The Principal Concepts and Significance of IS09000 --- p.28 / Why is IS09000 Recommended to be Necessary for ITSD? --- p.29 / Overview of the Feasibility of Applying IS09000 in ITSD --- p.30 / Recommendations --- p.35 / Problems of Study --- p.38 / APPENDIX --- p.39 / BILIOGRAPHY --- p.51

Complex modern software is often built using existing application frameworks and middleware frameworks. These frameworks provide useful common services, while simultaneously imposing architectural rules and constraints. Existing software architecture evaluation methods do not explicitly consider the implications of these frameworks for software architecture. This research extends scenario-based architecture evaluation methods by incorporating framework-related information into different evaluation activities. I propose four techniques which target four different activities within a scenario-based architecture evaluation method. 1) Scenario development: A new technique was designed aiming to extract general scenarios and tactics from framework-related architectural patterns. The technique is intended to complement the current scenario development process. The feasibility of the technique was validated through a case study. Significant improvements of scenario quality were observed in a controlled experiment conducted by another colleague. 2) Architecture representation: A new metrics-driven technique was created to reconstruct software architecture in a just-in-time fashion. This technique was validated in a case study. This approach has significantly improved the efficiency of architecture representation in a complex environment. 3) Attribute specific analysis (performance only): A model-driven approach to performance measurement was applied by decoupling framework-specific information from performance testing requirements. This technique was validated on two platforms (J2EE and Web Services) through a number of case studies. This technique leads to the benchmark producing more representative measures of the eventual application. It reduces the complexity behind the load testing suite and framework-specific performance data collecting utilities. 4) Trade-off and sensitivity analysis: A new technique was designed seeking to improve the Analytical Hierarchical Process (AHP) for trade-off and sensitivity analysis during a framework selection process. This approach was validated in a case study using data from a commercial project. The approach can identify 1) trade-offs implied by an architecture alternative, along with the magnitude of these trade-offs. 2) the most critical decisions in the overall decision process 3) the sensitivity of the final decision and its capability for handling quality attribute priority changes.

CAPES / O Paradigma Orientado a Notificações (PON) é uma alternativa para o desenvolvimento de aplicações em software e propõe resolver certos problemas existentes nos paradigmas usuais de programação, nomeadamente o Paradigma Declarativo (PD) e o Paradigma Imperativo (PI). Na verdade, o PON unifica as principais vantagens do PD e do PI, ao mesmo tempo que resolve (em termos de modelo) várias de suas deficiências e inconvenientes relativas ao cálculo lógico- causal em aplicações monoprocessados a de software, completamente supostamente multiprocessados. desde O PON ambientes tem sido materializado em termos de programação e modelagem, mas ainda não possuía um método formalizado para orientar os desenvolvedores na elaboração de teste de software. Esta dissertação propõe um método de teste para projetos de software que empregam o PON no seu desenvolvimento. O método de teste de software proposto foi desenvolvido para ser aplicado nas fases de teste unitário e teste de integração. O teste unitário considera as menores entidades testáveis do PON e requer critérios de teste específicos. O teste de integração considera o funcionamento das entidades PON em conjunto para realização de casos de uso e pode ser realizado em duas etapas: (1) teste sobre as funcionalidades descritas nos requisitos e no caso de uso e (2) teste que exercitem diretamente as entidades PON que compõem o caso de uso (como Premisses, Conditions e Rules). Esse método de teste foi aplicado em um caso de estudo que envolve a modelagem e desenvolvimento de um software de combate aéreo e os resultados desta pesquisa mostram que o método proposto possui grande importância no teste de programas PON. / The Notification Oriented Paradigm (NOP) is an alternative to the development of software applications and proposes to solve certain problems in the usual programming paradigms, including the Declarative Paradigm (DP) and Imperative Paradigm (IP). Indeed, the NOP unifies the main advantages of DP and IP while solving (in terms of model) several of its deficiencies and inconveniences related to logical-causal calculation, apparently from both mono and multiprocessor environments. The NOP has been materialized in terms of programming and modeling, but still did not have a formalized method to guide developers in designing and software testing activity. This dissertation proposes a test method for software projects that use the NOP in its development. The proposed software testing method was developed for use in the phases of unit testing and integration testing. The unit testing considers the smallest testable entities of the NOP and requires specific techniques for generating test cases. The integration testing considers the operation of the PON entities together to carry out use cases and can be accomplished in two steps: (1) test on the features described in the requirements and use case and (2) test that directly exercise the NOP entities that make up the use case (as Premisses, Conditions and Rules). The test method was applied in a case study involving the modeling and development of a simple air combat and the results of this research show that the proposed method has great importance in testing NOP programs in both unit and integration testing.

The advent of agile methodologies has brought about an illuminating debate in Software Engineering, particularly with regard to software quality. Some studies have reported that agile methodologies do improve software quality when compared to traditional methodologies; other studies have been inconclusive or contradictory, while others have argued that empirical evidence is limited. This study sought to investigate the correlation between agile methodologies when compared to traditional methodologies for selected software quality parameters. The research design was causal comparative, as well as correlational. The approach was quantitative, using a survey as the data collection method. SPSS was used to conduct descriptive and correlational analysis for 106 responses received. The main findings were that there was a statistically significant relation between traditional methodology use and ease of system testing (p=0.014); a statistically significant relation between traditional methodology use and timeliness (p=0.02); a statistically significant relation between software quality standards used and ease of system testing (p=0.017); a statistically significant relation between active stakeholder participation on projects and ease of system interactivity (p=0.047); and a statistically significant relation between mandatory workshop interactivity (p=0.047); and a statistically significant relation between mandatory workshop attendance or training and ease of system navigation (p=0.031).Claims that agile methodology use leads to improved software quality for selected quality parameters could not be empirically validated. The association between most of the selected software quality criteria in relation to methodology use in general was not apparent. Agile methodologies are suitable in small environments. Scrum was the most widely used agile methodology by far. The popularity and adoption state of XP showed a significantly decreasing trend. Traditional and agile methodologies combined are being used (47%) more than any other methodology. Agile methodology use (28%) surpassed traditional methodology use (19%). A suitable consensus definition for agile methodologies did not emerge from the data collected. The most suitable project life cycle model was evolutionary, incremental and iterative. ‘Other’ methodologies, meaning customised agile or SDLC, are suitable, as the environment becomes increasingly large and complex. Only 13% of organisations surveyed have an agile experience of six years and beyond. Based on these findings and gaps in the literature, implications and recommendations for further research areas are proposed, where the findings and contributions of this study are found to be relevant to practice for application and to academia for further research / College of Engineering, Science and Technology / M. Sc. (Computing)

The focus of the dissertation is on software quality assurance for object-oriented information systems development. A Quality Assurance Reference Model is proposed with aspects dealing with technical and managerial issues. A revised Spiral life cycle model is adopted as well as the Object Modelling Technique. The Quality Assurance Reference Model associates quality factors at various levels, quality criteria and metrics into a matrix framework that may be used to achieve quality assurance for all cycles of the Spiral Model. / Computing / M. Sc. (Information Systems)

The focus of the dissertation is on software quality assurance for object-oriented information systems development. A Quality Assurance Reference Model is proposed with aspects dealing with technical and managerial issues. A revised Spiral life cycle model is adopted as well as the Object Modelling Technique. The Quality Assurance Reference Model associates quality factors at various levels, quality criteria and metrics into a matrix framework that may be used to achieve quality assurance for all cycles of the Spiral Model. / Computing / M. Sc. (Information Systems)

O caráter intensivo em conhecimento da produção de software e sua crescente demanda sugerem a necessidade de definir mecanismos para gerenciar adequadamente os conhecimentos envolvidos com o objetivo de alcançar os requisitos de prazo, custos e qualidade. A capitalização do conhecimento é um processo que envolve desde a identificação até a avaliação dos conhecimentos produzidos e utilizados. Especificamente, para o desenvolvimento de software, a capitalização possibilita facilitar o acesso, minimizar a perda de conhecimento, reduzir a curva de aprendizagem, evitar a repetição de erros e retrabalho. Assim, esta tese apresenta o Know-Cap, um método desenvolvido para sistematizar e orientar a capitalização do conhecimento no desenvolvimento de software. O Know-Cap visa facilitar a localização, preservação, agregação de valor e atualização do conhecimento, com o intuito de utilizá-lo na execução de novas tarefas. O método foi proposto a partir de um conjunto de procedimentos metodológicos: pesquisa bibliográfica, revisão sistemática e análise de trabalhos correlatos. A viabilidade e adequação do Know-Cap foram analisadas a partir de um estudo de aplicação, conduzido em um caso real, e um estudo de análise realizado em empresas de desenvolvimento de software. Os resultados obtidos apontam que o Know-Cap apoia a capitalização do conhecimento no desenvolvimento de software. / The intensive character in knowledge of software production and its rising demand suggest the need to establish mechanisms to properly manage the knowledge involved in order to meet the requirements of deadline, costs and quality. The knowledge capitalization is a process that involves from identification to evaluation of the knowledge produced and used. Specifically, for software development, capitalization enables easier access, minimize the loss of knowledge, reducing the learning curve, avoid repeating errors and rework. Thus, this thesis presents the know-Cap, a method developed to organize and guide the capitalization of knowledge in software development. The Know-Cap facilitates the location, preservation, value addition and updating of knowledge, in order to use it in the execution of new tasks. The method was proposed from a set of methodological procedures: literature review, systematic review and analysis of related work. The feasibility and appropriateness of Know-Cap were analyzed from an application study, conducted in a real case, and an analytical study of software development companies. The results obtained indicate the Know- Cap supports the capitalization of knowledge in software development.