Automatic generation of a Software Requirements Specification (SRS) document

Abstract

High body mass index (BMI) has been shown to be associated with asthma, but the pattern of this association is still unclear and may differ by gender or stage of puberty. BMI is only a proxy of adiposity, whereas estimation of body fat percent (BF%) by the bioimpedance technique is considered an accurate measure of adiposity. We investigated whether BMI and BF% behave differently in their association with asthma between genders, before and during adolescence. Design and Methods: In this cross-sectional study of 10,981 schoolchildren, we used logistic regression models to examine the pattern of association of BMI and BF% with asthma. Results: In the case of BF%, both the highest (odds ratio [OR]: 1.68, 95% confidence interval [95% CI]: 1.21-2.30) and lowest (OR: 1.59, 95% CI: 1.13-2.23) z-score categories conferred an increased adjusted risk for active asthma. The likelihood ratio test (LRT) of nonlinearity yielded significant results (P < 0.01) for BF%. In contrast, the LRT for BMI yielded a nonsignificant result (P ¼ 0.45) indicating a linear association of asthma with BMI. A unit increase in BMI z-score conferred an increase in the adjusted odds of active asthma (OR: 1.14, 95% CI: 1.02-1.27). In the case of BF%, the adjusted ORs for active asthma at the highest and lowest z-score categories in both genders, before and during adolescence, were similarly elevated, exhibiting a U-shape pattern. Conclusions: In contrast to the linear association observed with BMI, BF% displayed a U-shaped association with asthma and may be the preferred measure of adiposity in epidemiological studies of asthma in children.

An Automatic Generation and Verification Method of Software Requirements Specification

“…There has been a lot of work on formal methods for writing and verifying requirements. Georgiades et al [17] provided a novel software tool that attempted to formalize and automate the RE process and extended the use of the tool's SRS document component, which automatically generated well-structured natural language SRS documents. SOFL [18] was proposed to precisely define functional behavior and incorporate security rules as constraints, which created a solid foundation for implementation and testing.…”

Formalizing and Automating Use Case Model Development

“…This is illustrated with the example of the Prescription module of the subsystem Hospital Practice 15 and the Drug module of the Pharmacy subsystem, in which the Pharmacist plays the role of IR in the Prescription module (in UC Create Prescription) and alterer in the Drug module (in UC Alter Drug). Another example related to the Hospital Reception subsystem is the relationship of its Appointment module with the Examination module of the Hospital Practice subsystem, where Doctor is an IR in UC Create Appointment of the former module, and doctor is a crea- 15 Hospital Practice is composed of the modules Prescription, Examination, and Diagnosis, since doctor, as a primary actor, is the creator of all three of them tor in UC Create Examination of the latter module. Therefore the Hospital Practice Subsystem is linked with the Hospital Reception subsystem, as shown in Fig.…”

“…Objective (i) is achieved with the use of predefined types of use cases and actors, as well as guidelines to derive their associations, relationships and business rules. The development of this formalization is guided and derived from corresponding ideas and formalization provided by the NLSSRE (Natural Language Syntax and Semantics Requirements Engineering) methodology [11][12][13][14][15] described later. The elicitation process is also facilitated by the use of formalized sentential patterns-provided by NLSSRE-which provide a structured and expressive way to write the UC elements.…”

Especificación de requerimientos con Áncora y el estándar 830

“…Estándar IEEE 830 para la especificación de requerimientos La falta de herramientas automatizadas y poca habilidad de los ingenieros de software, en la creación de una buena especificación de requerimientos en lenguaje natural, han sido un obstáculo en el proceso eficiente de la ingeniería de requerimientos, por lo que se han desarrollado algunas propuestas, entre las que se encuentra un software Tailandés [5], NALASS [6] y herramientas que permiten la creación y verificación de especificación de requerimientos desde puntos de vista diferentes [7]. El estándar IEEE 830-1998 [8], "Recomendaciones prácticas para la especificación de requerimientos", fue desarrollado por la IEEE y la IEEE-SA (Standards Association), indica la estructura y organización de toda la información que debe incluirse en un buen documento de especificación de requerimientos de software.…”