Balanced Objective-Quantifiers Method (BOQM) For Software Intensive Organizations Strategies

Spanish university facilitates a method to link the strategic management with Software and Process improvement based on measurement. The method uses the process philosophy to build measurable information in Indicators templates (Based on ISO/IEC 15939) and a Balanced Scorecard (BSC) template, the process is followed by the participation of SIO’s roles such as the CEO, TI director, CPO, and others measurement roles such as measurement analyst, measurement librarian, and the measurement user

Método Objetivo-Cuantificadores Balanceado (MOCB) para estrategias en organizaciones intensivas de software

Universidad española facilita un método para unir la gestión estratégica con la mejora del proceso software basado en la medición. El método usa la filosofía de procesos para construir información medible en plantillas indicadores (ISO 15939) y una plantilla del CMI, el proceso es seguido por la participación de roles de la SIO tales como el CEO, Director TI, Dirección de proyectos, y otros roles de medición como el analista de medición, el bibliotecario de medición, y el usuario de medición

Developments in Aerospace Software Engineering practices for VSEs: An overview of the process requirements and practicesof integrated Maturity models and Standards

As part of the evolution of the Space market in the last years – globally referred to as Space 2.0 - small companies are playing an increasingly relevant role in different aerospace projects. Business incubators established by European Space Agency (ESA) and similar entities are evidence of the need of moving initiatives to small companies characterized by greater flexibility to develop specific activities. Software is a key component in most aerospace projects, and the success of the initiatives and projects usually depends on the capability of developing reliable software following well-defined standards. But small entities face some difficulties when adopting software development standards that have been conceived thinking on larger organizations and big programs. The need of defining software development standards tailored to small companies and groups is a permanent subject of discussion not only in the aerospace field, and has led in recent years to the publication of the ISO/IEC 29110 series of systems and software engineering standards and guides, aimed to solve the issues that Very Small Entities (VSEs) () – settings having up to twenty-five people -, found with other standards like CMMI or SPICE. This paper discusses the tailoring defined by different aerospace organizations for VSEs in the aerospace industry, and presents a conceptual arrangement of the standard based on meta-modeling languages that allow the extension and full customization with the incorporation of specific software engineering requirements and practices from ECSS (European Cooperation for Space Standardization)

Estudio geométrico de la cadena cinemática de un motor diésel mono-cilíndrico

A modo de sinopsis, este proyecto ha consistido en la medición de la geometría característica de la cadena cinemática de un motor diésel SD60 series modelo 178F, plasmándola en un conjunto de croquis y planos más elaborados que luego servirán para modelizar cada una de las partes del motor en el programa de diseño SOLIDWORKS. Este trabajo asume una serie de hipótesis simplificativas por facilitar la medición dado que los recursos, tiempo y capacidades son limitados. Sin embargo, la calidad y fiabilidad en las medidas de la cadena cinemática no ha sufrido deterioro como se verá en este trabajo y en el posterior. A lo largo de esta memoria se explicará en más detalle las fases del trabajo desarrollado durante este semestre: desmontaje, medición de piezas, diseño de planos y selección de materiales.As a synopsis, this Project has consisted in the measurement of the characteristic geometry of the kinematics chain of a modified single cylinder diesel motor SD60, shaping it in a set of sketchs and more developed plans that later will serve to modeling each one of the motor pieces in SOLIDWORKS. This Project assumes some simplifying hypothesis about the measurement because of the lack of means and time. However, the quality and reliability of the measurement of the kinematics chain have not suffered deterioration as will be seen in this Project and the next one. Along this memoir will be explained the phases of the Project developed during the semester: disassembly, parts’ measurement, plans and materials selection.Graduado o Graduada en Ingeniería en Tecnologías Industriales por la Universidad Pública de NavarraIndustria Teknologietako Ingeniaritzan Graduatua Nafarroako Unibertsitate Publikoa

Vers une pédagogie de l'organisation sociale dans le mouvement d'éducation populaire en Amérique latine : valeurs, stratégies, tactiques

Thèse, Université de Montréal, 199

Diseño de una metodología CASE de desarrollo de software

En la actualidad existe una gran expectación ante la introducción de nuevas herramientas y métodos para el desarrollo de productos software, que permitirán en un futuro próximo un planteamiento de ingeniería del proceso de producción software. Las nuevas metodologías que empiezan a esbozarse suponen un enfoque integral del problema abarcando todas las fases del esquema productivo. Sin embargo el grado de automatización conseguido en el proceso de construcción de sistemas es muy bajo y éste está centrado en las últimas fases del ciclo de vida del software, consiguiéndose así una reducción poco significativa de sus costes y, lo que es aún más importante, sin garantizar la calidad de los productos software obtenidos. Esta tesis define una metodología de desarrollo software estructurada que se puede automatizar, es decir una metodología CASE. La metodología que se presenta se ajusta al modelo de ciclo de desarrollo CASE, que consta de las fases de análisis, diseño y pruebas; siendo su ámbito de aplicación los sistemas de información. Se establecen inicialmente los principios básicos sobre los que la metodología CASE se asienta. Posteriormente, y puesto que la metodología se inicia con la fijación de los objetivos de la empresa que demanda un sistema informático, se emplean técnicas que sirvan de recogida y validación de la información, que proporcionan a la vez un lenguaje de comunicación fácil entre usuarios finales e informáticos. Además, estas mismas técnicas detallarán de una manera completa, consistente y sin ambigüedad todos los requisitos del sistema. Asimismo, se presentan un conjunto de técnicas y algoritmos para conseguir que desde la especificación de requisitos del sistema se logre una automatización tanto del diseño lógico del Modelo de Procesos como del Modelo de Datos, validados ambos conforme a la especificación de requisitos previa. Por último se definen unos procedimientos formales que indican el conjunto de actividades a realizar en el proceso de construcción y cómo llevarlas a cabo, consiguiendo de esta manera una integridad en las distintas etapas del proceso de desarrollo.---ABSTRACT---Nowdays there is a great expectation with regard to the introduction of new tools and methods for the software products development that, in the very near future will allow, an engineering approach in the software development process. New methodologies, just emerging, imply an integral approach to the problem, including all the productive scheme stages. However, the automatization degree obtained in the systems construction process is very low and focused on the last phases of the software lifecycle, which means that the costs reduction obtained is irrelevant and, which is more important, the quality of the software products is not guaranteed. This thesis defines an structured software development methodology that can be automated, that is a CASE methodology. Such a methodology is adapted to the CASE development cycle-model, which consists in analysis, design and testing phases, being the information systems its field of application. Firstly, we present the basic principies on which CASE methodology is based. Secondly, since the methodology starts from fixing the objectives of the company demanding the automatization system, we use some techniques that are useful for gathering and validating the information, being at the same time an easy communication language between end-users and developers. Indeed, these same techniques will detail completely, consistently and non ambiguously all the system requirements. Likewise, a set of techniques and algorithms are shown in order to obtain, from the system requirements specification, an automatization of the Process Model logical design, and of the Data Model logical design. Those two models are validated according to the previous requirement specification. Finally, we define several formal procedures that suggest which set of activities to be accomplished in the construction process, and how to carry them out, getting in this way integrity and completness for the different stages of the development process

High-Risk Corneal Graft Rejection in the Setting of Previous Corneal Herpes Simplex Virus (HSV)-1 Infection

Acknowledgments The authors thank M. Robertson and R. Fordyce for technical support during the duration of the study. The work performed in Aberdeen was supported by grant from Action Medical Research UK (SP4328; London, England, UK), NHS Grampian Endowment grant (12/49; Aberdeen, Scotland, UK), and Saving Sight in Grampian (Charity No.SC002938; Aberdeen, Scotland, UK). The work performed in Pittsburgh was supported by a Fight for Sight Post-Doctoral Award (JEK; New York, NY, USA); unrestricted grants from the Western Pennsylvania Medical Eye Bank Foundation (Pittsburgh, PA, USA), Research to Prevent Blindness (New York, NY, USA), and the Eye and Ear Foundation of Pittsburgh (RLH; Pittsburgh, PA, USA); and National Institutes of Health Grants P30EY08098 (RLH; Bethesda, MD, USA) and EY10359 (RLH).Peer reviewedPublisher PD

A standard-based framework to integrate software work in small settings

Small software companies have to work hard in order to survive. They usually find it challenging to spend time and effort on improving there operations and processes. Therefore, it is important to address such needs by the introduction of a proposed framework that specifies ways of getting things done while consciously encourage them to enhance their ability to improve. Although there are many software process improvement approaches, none of them address the human factors of small companies in a comprehensive and holistic way. Samay is a proposed framework to integrate human factors in the daily work as a way to deal with that challenge. This study suggests managing human factors but pointing out the software process life cycle. The purpose is to converge toward a continuous improvement by means of alternative mechanisms that impact on people. This framework was developed based upon reviews of relevant standards (such as ISO/IEC 29110, ISO 10018, OMG Essence and ISO/IEC 33014) and previously published studies in this field. Moreover, an expert review and validation findings supported the view that Samay could support practitioners when small software companies want to start improving their ways of work