No description available.

In software development, customer trust hinges on a product performing as expectedand ensuring appropriate steps are taken to prevent incidents due to faulty systems. Oneway of achieving this lies within in requirement validation – the process of validatingthe requirements set on the software. However, the complexity of the requirementvalidation domain can be challenging for companies and organizations seeking toimprove their validation processes. This research investigates this area, pinpointingpotential failure factors that may hinder effective requirement validation. The study wasconducted using a multi-case research design, involving individual interviews with fourdistinct divisions at SAAB: hardware, software, systems, and test equipment.This study built upon Niazi’s & Shastry's previous research where findings of failurefactors in requirement engineering are brought forward. What this research has done istaking the failure factors and applying them to requirement validation, which is asubcategory to requirement engineering. The failure factors taken into consideration inthis research are therefore the following: • Vague requirements• Undefined requirements process• Lack of stakeholder involvement• Business needs are not considered• Lack of requirement management• The requirements do not reflect the real needs of the customer• The requirements are inconsistent and/or incomplete• It is expensive to make changes to requirements after they have been agreed• Requirements growth• Stakeholders’ communication problems During the research, focus was placed on noting how often the interviewees mentionedeach failure factor. This helped in understanding which issues were most often seen asproblems in the requirement validation process.Particularly, stakeholder issues and the tendency towards vague requirement definitionsemerged as prevalent problems. The findings of this research do not only concernsafety-critical software companies but can additionally prove beneficial to any industrydealing with stakeholders and product/service requirements. The research providesiiipotential pitfalls in requirement validation, aiding organizations in refining theirapproach for better software product reliability and customer trust.

The secondary use of Dementia Care Mapping (DCM) data, if that data were held in a data warehouse, could contribute to global efforts in monitoring and improving dementia care quality. This qualitative study identifies requirements for the secondary use of DCM data within a data warehouse using a user-driven approach. The thesis critically analyses various technical methodologies and then argues the use and further demonstrates the applicability of a modified grounded theory as a user-driven methodology for a data warehouse. Interviews were conducted with 29 DCM researchers, trainers and practitioners in three phases. 19 interviews were face to face with the others on Skype and telephone with an average length of individual interview 45-60 minutes. The interview data was systematically analysed using open, axial and selective coding techniques and constant comparison methods. The study data highlighted benchmarking, mappers’ support and research as three perceived potential secondary uses of DCM data within a data warehouse. DCM researchers identified concerns regarding the quality and security of DCM data for secondary uses, which led to identifying the requirements for additional provenance, ethical and contextual data to be included in a warehouse alongside DCM data to meet requirements for secondary uses of this data for research. The study data was also used to extrapolate three main factors such as an individual mapper, the organization and an electronic data management that can influence the quality and availability of DCM data for secondary uses. The study makes further recommendations for designing a future DCM data warehouse.

Requirements are features or attributes which we discover at the initial stage of building a product. Requirements describe the system functionality that satisfies customer needs. An incomplete and inconsistent requirement of the project leads to exceeding cost or devastating the project. So there should be a process for obtaining sufficient, accurate and refining requirements such a process is known as requirement elicitation. Software requirement elicitation process is regarded as one of the most important parts of software development. During this stage it is decided precisely what should be built. There are many requirements elicitation techniques however selecting the appropriate technique according to the nature of the project is important for the successful development of the project. Traditional software development and agile approaches to requirements elicitation are suitable in their own context. With agile approaches a high-level, low formal form of requirement specification is produced and the team is fully prepared to respond unavoidable changes in these requirements. On the other hand in traditional approach project could be done more satisfactory with a plan driven well documented specification. Agile processes introduced their most broadly applicable technique with user stories to express the requirements of the project. A user story is a simple and short written description of desired functionality from the perspective of user or owner. User stories play an effective role on all time constrained projects and a good way to introducing a bit of agility to the projects. Personas can be used to fill the gap of user stories.

Except for tyrosine, the amino acid requirement of parenterally fed (PN) human neonates has not been derived. Methionine and cysteine are indispensable and dispensable sulphur amino acids respectively. Cysteine is synthesized from methionine. Cysteine is unstable in solution, and is left out or added in very small amounts to amino acid solutions. Methionine is added to compensate for the lack of cysteine, assuming that the neonate will convert methionine to cysteine to meet the body’s metabolic demand. Methionine is hepatotoxic and there is evidence that the neonate has limited ability for its conversion to cysteine. To determine the requirement of the neonate for methionine, PN-fed, stable, post-surgical neonates received graded intakes of methionine. The mean methionine requirement was estimated to be 49 mg.kg-1.day-1, which is 48 to 90% of the methionine content of current commercial amino acid solutions. Because cysteine is the rate limiting substrate for glutathione (GSH) synthesis and current methods of determining amino acid requirement measure requirement for protein synthesis, SAA requirements for maintenance of GSH status was deleniated in healthy adult males and in PN-fed human neonates. GSH kinetics was measured in healthy men receiving the mean methionine requirement and graded intakes of cysteine. GSH synthesis did not change with the addition of cysteine. Additionally, PN-fed post-surgical neonates recieved a methionine-adequate cysteine-free PN followed by cysteine supplemented PN for two 3-day periods and GSH kinetics measured on days 3 and 6. There was no change in GSH synthesis in response to cysteine supplementation. It is concluded that the PN-fed human neonate is capable of synthesizing enough cysteine from methionine not only for protein synthesis but for GSH synthesis. For both healthy men and stable post-surgical neonates, the requirement for GSH synthesis is met at the sulphur amino acid requirement derived using the indicator amino acid technique

Except for tyrosine, the amino acid requirement of parenterally fed (PN) human neonates has not been derived. Methionine and cysteine are indispensable and dispensable sulphur amino acids respectively. Cysteine is synthesized from methionine. Cysteine is unstable in solution, and is left out or added in very small amounts to amino acid solutions. Methionine is added to compensate for the lack of cysteine, assuming that the neonate will convert methionine to cysteine to meet the body’s metabolic demand. Methionine is hepatotoxic and there is evidence that the neonate has limited ability for its conversion to cysteine. To determine the requirement of the neonate for methionine, PN-fed, stable, post-surgical neonates received graded intakes of methionine. The mean methionine requirement was estimated to be 49 mg.kg-1.day-1, which is 48 to 90% of the methionine content of current commercial amino acid solutions. Because cysteine is the rate limiting substrate for glutathione (GSH) synthesis and current methods of determining amino acid requirement measure requirement for protein synthesis, SAA requirements for maintenance of GSH status was deleniated in healthy adult males and in PN-fed human neonates. GSH kinetics was measured in healthy men receiving the mean methionine requirement and graded intakes of cysteine. GSH synthesis did not change with the addition of cysteine. Additionally, PN-fed post-surgical neonates recieved a methionine-adequate cysteine-free PN followed by cysteine supplemented PN for two 3-day periods and GSH kinetics measured on days 3 and 6. There was no change in GSH synthesis in response to cysteine supplementation. It is concluded that the PN-fed human neonate is capable of synthesizing enough cysteine from methionine not only for protein synthesis but for GSH synthesis. For both healthy men and stable post-surgical neonates, the requirement for GSH synthesis is met at the sulphur amino acid requirement derived using the indicator amino acid technique

Denna rapport behandlar tekniska beskrivningar. Främst med fokus på problematiken för att skapa dessa på national men även global nivå samt utvecklingspotentialen med att standardisera dessa. Rapporten inriktar sig på stora industriella aktörer med en repetitiv hantering av byggprojekt för att på minsta möjliga sätt hindra sin kärnverksamhet men även underlätta utveckling och utökning av sin produktion. Rapporten tar upp fördelar men även potentiella nackdelar med ett standardiserat förfarande, därigenom vad företag måste tänka på och säkerställa för att få en fungerande och utvecklande process. I syfte att motivera företagens arbete med standardiserade beskrivningar visar rapporten vilka riktvärden som kan påverkas. Riktvärden som baseras på kompetenta personers erfarenhet inom branschen. Med detta förklaras även vikten i att sätta upp mål för utvecklingen och samtidigt processer för att följa upp så att uppsatta mål uppnås men även återkopplas genom erfarenhetsåterföring och revidering. Tre större industriella aktörer har medverkat i arbetet med rapporten, alla tre med ett stort fokus på vad en standardisering kan innebära för deras verksamhet. Där av har rapportens kärndelar anpassats efter att stämma överens med företagens frågeställningar. Då tekniska beskrivningar inom branschen inte är något nytt fenomen men att standardisera dessa ännu ej är i bruk, konstateras att ämnet måste undersökas mer samt testas i praktiken för att helt kunna följa upp att företagen mål uppnås. Dock kan av rapportens slutsatser dras att det finns stora besparingar och effektiviseringar som potentiellt kan påverkas. Detta med utgångspunkt av digniteten för de projekt företagen kommer i kontakt med.

Este trabalho apresenta os métodos consensuais como uma proposta para reduzir as insatisfações das pessoas envolvidas no processo de levantamento de requisitos e respeitar as dimensões humanas e sociais já no inicio do ciclo de vida de um sistema sociotécnico, considerando a aderência desses métodos às demais fases do ciclo de vida. / This text proposes the use of consensual methods to reduce people dissatisfaction in take part of requirement elicitation process and indentify, and respect, the human and social dimensions since the beginning of a sociotechnical system life cycle, evaluating the adhesion of these methods to the other phases of the lifecycle.

Este trabalho apresenta os métodos consensuais como uma proposta para reduzir as insatisfações das pessoas envolvidas no processo de levantamento de requisitos e respeitar as dimensões humanas e sociais já no inicio do ciclo de vida de um sistema sociotécnico, considerando a aderência desses métodos às demais fases do ciclo de vida. / This text proposes the use of consensual methods to reduce people dissatisfaction in take part of requirement elicitation process and indentify, and respect, the human and social dimensions since the beginning of a sociotechnical system life cycle, evaluating the adhesion of these methods to the other phases of the lifecycle.

Fatores ambientais adversos, dos quais o déficit hídrico constitui a restrição mais severa à agricultura, representam cerca de 70% das perdas de produtividade em todo o mundo. A irrigação da cana-de-açúcar é hoje, uma das principais alternativas tecnológicas para o aumento da produtividade do setor sucroenergético, melhorando não só a eficiência no campo como, também, reduzindo a ociosidade industrial das usinas. Contudo, havendo-se disponibilidade hídrica para irrigação, implica-se na necessidade de outorga de direito de uso para captação. A outorga é um dos seis instrumentos da Política Nacional de Recursos Hídricos (Lei Federal nº 9.433, de 08 de janeiro de 1997). Esse instrumento tem como objetivo assegurar o controle quantitativo e qualitativo dos usos da água e o efetivo exercício dos direitos de acesso aos recursos hídricos. O cálculo das vazões mensais de outorga para captação em corpos hídricos de domínio federal é atualmente obtido através de dados estimados de precipitação pluvial efetiva provável e evapotranspiração de referência do local, fornecidos pela Agência Nacional de Águas (ANA), de parâmetros da cultura (época de plantio e coeficientes de cultura - kc), área irrigada e eficiência da irrigação, fornecidos pelo requerente da outorga. Assim, como hipótese primária deste estudo de que a metodologia de cálculo das vazões mensais de outorga proposta pela ANA não fornece segurança operacional para grandes empreendimentos, uma vez que esta não possui um caráter probabilístico adequado, que leve em consideração as variações anuais de precipitação pluvial e evapotranspiração e, ainda, como hipótese secundária de que na determinação das vazões através da metodologia recomendada pela FAO (CROPWAT 8.0) ocorram vulnerabilidades diante dos critérios de escolha dos anos representativos (anos secos, médios e úmidos), ambas podendo restringir as vazões de captação. Este trabalho teve como objetivo comparar tais metodologias com um estudo de caso mais detalhado, levando-se em consideração a variabilidade temporal destas estimativas (séries históricas), bem como, buscando-se determinar a influência do critério de irrigação e dos níveis de probabilidade de ocorrência da evapotranspiração de referência (ETo) e precipitação (PPT) na determinação das vazões mensais de outorga para irrigação de cana-de-açúcar. Evidenciou-se que, durante o período compreendido entre os meses de abril a setembro (período \"seco\"), a metodologia de cálculo proposta pela ANA atendeu as necessidades de projeto. Contudo, no período onde se concentram as precipitações pluviais (outubro a março), esta tendeu a subestimar os valores mensais das vazões outorgáveis, uma vez que não dispõe de um critério adequado que considere as variações anuais deste elemento meteorológico, limitando a outorga a uma condição média provável. Entretanto, diante da morosidade da análise de séries históricas, ano-a-ano, é compreensível que se busque facilitar estas estimativas. Assim, a metodologia proposta pela FAO (simulações de anos com diferentes probabilidades teóricas de valores \"atingíveis\" de PPT acumulada anual), bem como, a metodologia alternativa proposta neste estudo (PPT acumulada no período seco) aproximaram-se ou, até mesmo, superam a condição \"ideal\", porém, devido à determinação destes anos não levar em consideração a distribuição dos acumulados (dentro do período considerado), a metodologia apresentou limitações. / The adverse environmental factors, of which drought is the most severe agriculture limitation, account for about 70% of yield losses worldwide. The irrigation of sugarcane is today one of the main technological alternatives to increase the productivity, improving not only the field efficiency but also reducing the idleness of industrial plants. However, having up water availability for irrigation implies on the need of water rights for its catchment. The water right is one of six instruments of the Brazilian National Water Resources Policy (Federal Law nº 9.433, January 08, 1997). This instrument aims to ensure the quantitative and qualitative control of water use and the effective exercise of the access rights to water resources. The calculation of the monthly flows to water rights for catchment in rivers of federal domain is currently obtained through estimated local data of probable effective rainfall and reference evapotranspiration, provided by the National Water Agency (ANA), crop parameters (time planting and crop coefficients - kc), irrigated area and irrigation efficiency, in turn provided by the claimant of water right. Thus, as the primary hypothesis of this study that the calculation methodology of monthly flows of water right proposed by the ANA does not provide operational safety for large enterprises, since it does not have a suitable probabilistic character that takes into account the annual variation of rainfall and evapotranspiration, and also, as a secondary hypothesis that in determining the water rights flows through the methodology proposed by FAO (CROPWAT 8.0) is subject to vulnerabilities on the selecting criteria for the representative years (dry, average and wet year), both methodologies may be restricted the flow of catchment. This study aimed to compare these methodologies with a more detailed study of case, that takes into account the temporal variability of these estimates (time series), seeking to determine the influence of irrigation criterion and probability levels of occurrence of the reference evapotranspiration (ETo) and precipitation (PPT) in the determination of monthly flows rate of water right applied to sugarcane irrigation practices. It was evident that during the period between the months from April to September (\"dry\" period), the calculation methodology proposed by ANA supplied the project requirements. However, the period which are concentrated rainfall (October to March), this tended to underestimate the monthly values of water rights flows rate, as it does not provide an appropriate criterion to consider the annual weather variations of this element, limiting the water rights to an average probable condition. Though, given the difficulty of working with data time series analysis, year-on-year, it is understandable the use of simplified methodologies that facilitate these estimatives. Thus, the methodology proposed by FAO (years simulations with different theoretical probability \"attainable\" values of PPT annual accumulated), as well as the alternative method proposed in this study (PPT accumulated in dry period) approached or even exceeded the \"ideal\" condition, however, the determination of these years did not take into account the distribution of rainfall accumulated (within the period considered) an thus, the methodology presented limitations.