Business processes form the backbone of all business operations, and workflow technology has enabled companies to gain significant productivity benefits through the automatic enactment of routine, repetitive processes. Process automation can be achieved by encoding the business rules and procedures into the applications, but capturing the process logic in a graphical workflow model allows the process to be specified, validated and ultimately maintained by business analysts with limited technical knowledge. The process models can also be automatically verified at design-time to detect structural issues such as deadlock and ensure correct data flow during process execution. These benefits have resulted in the success of workflow technology in a variety of industries, although workflows are often criticised for being too rigid, particularly in light of their recent deployment in collaborative applications such as e-business. Generally, many events can impact on the execution of a workflow process. Initially, the workflow is triggered by an external event (for example, receipt of an order). Participants then interact with the workflow system through the worklist as they perform constituent tasks of the workflow, driving the progression of each process instance through the model until its completion. For traditional workflow processes, this functionality was sufficient. However, new generation 'responsive' workflow technology must facilitate interaction with the external environment during workflow execution. For example, during the execution of an 'order to cash' process, the customer may attempt to cancel the order or update the shipping address. We call these events 'interruptions'. The potential occurrence of interruptions can be anticipated but, unlike the other workflow events, they are never required to occur in order to successfully execute any process instance. Interruptions can also occur at any stage during process execution, and may therefore be considered as 'expected, asynchronous exceptions' during the execution of workflow processes. Every interruption must be handled, and the desired reaction often depends on the situation. For example, an address update may not be permitted after a certain point, where this point depends on the customer type, and a shipping charge or refund may be applicable, depending on the original and new delivery region. Therefore, a set of rules is associated with each interruption, such that if a condition is satisfied when the event occurs, a particular action is to be performed. This set of rules forms a policy to handle each interruption. Several workflow systems do facilitate the automatic enforcement of 'exception handling' rules and support the reuse of code fragments to enable the limited specification and maintenance of rules by non-technical users. However, this functionality is not represented in a formal, intuitive model. Moreover, we argue that inadequate consideration is given to the verification of the rules, with insufficient support provided for the detection of issues at design-time that could hinder effective maintenance of the process logic or interfere with the interruption handling functionality at run-time. This thesis presents a framework to capture, analyse and enforce interruption process logic for highly responsive processes without compromising the benefits of workflow technology. We address these issues in two stages. In the first stage, we consider that the reaction to an interruption event is dependent on three factors: the progress of the process instance with respect to the workflow model, the values of the associated case data variables at the time at which the event occurs, and the data embedded in the event. In the second stage, we consider that the reaction to each interruption event may also depend on the other events that have also been detected, that is, we allow interruptions to be defined through event patterns or complex events. We thus consider the issues of definition, analysis and enactment for both 'basic' and 'extended' interruption policy models. First, we introduce a method to model interruption policies in an intuitive but executable manner such that they may be maintained without technical support. We then address the issue of execution, detailing the required system functionality and proposing a reference architecture for the automatic enforcement of the policies. Finally, we introduce a set of formal, generic correctness criteria and a verification procedure for the models. For extended policy models, we introduce and compare two alternative execution models for the evaluation of logical expressions that represent interruption patterns. Finally, we present a thorough analysis of related verification issues, considering both the system and user perspectives, in order to ensure correct process execution and also provide support for the user in semantic validation of the interruption policies.

Business processes form the backbone of all business operations, and workflow technology has enabled companies to gain significant productivity benefits through the automatic enactment of routine, repetitive processes. Process automation can be achieved by encoding the business rules and procedures into the applications, but capturing the process logic in a graphical workflow model allows the process to be specified, validated and ultimately maintained by business analysts with limited technical knowledge. The process models can also be automatically verified at design-time to detect structural issues such as deadlock and ensure correct data flow during process execution. These benefits have resulted in the success of workflow technology in a variety of industries, although workflows are often criticised for being too rigid, particularly in light of their recent deployment in collaborative applications such as e-business. Generally, many events can impact on the execution of a workflow process. Initially, the workflow is triggered by an external event (for example, receipt of an order). Participants then interact with the workflow system through the worklist as they perform constituent tasks of the workflow, driving the progression of each process instance through the model until its completion. For traditional workflow processes, this functionality was sufficient. However, new generation 'responsive' workflow technology must facilitate interaction with the external environment during workflow execution. For example, during the execution of an 'order to cash' process, the customer may attempt to cancel the order or update the shipping address. We call these events 'interruptions'. The potential occurrence of interruptions can be anticipated but, unlike the other workflow events, they are never required to occur in order to successfully execute any process instance. Interruptions can also occur at any stage during process execution, and may therefore be considered as 'expected, asynchronous exceptions' during the execution of workflow processes. Every interruption must be handled, and the desired reaction often depends on the situation. For example, an address update may not be permitted after a certain point, where this point depends on the customer type, and a shipping charge or refund may be applicable, depending on the original and new delivery region. Therefore, a set of rules is associated with each interruption, such that if a condition is satisfied when the event occurs, a particular action is to be performed. This set of rules forms a policy to handle each interruption. Several workflow systems do facilitate the automatic enforcement of 'exception handling' rules and support the reuse of code fragments to enable the limited specification and maintenance of rules by non-technical users. However, this functionality is not represented in a formal, intuitive model. Moreover, we argue that inadequate consideration is given to the verification of the rules, with insufficient support provided for the detection of issues at design-time that could hinder effective maintenance of the process logic or interfere with the interruption handling functionality at run-time. This thesis presents a framework to capture, analyse and enforce interruption process logic for highly responsive processes without compromising the benefits of workflow technology. We address these issues in two stages. In the first stage, we consider that the reaction to an interruption event is dependent on three factors: the progress of the process instance with respect to the workflow model, the values of the associated case data variables at the time at which the event occurs, and the data embedded in the event. In the second stage, we consider that the reaction to each interruption event may also depend on the other events that have also been detected, that is, we allow interruptions to be defined through event patterns or complex events. We thus consider the issues of definition, analysis and enactment for both 'basic' and 'extended' interruption policy models. First, we introduce a method to model interruption policies in an intuitive but executable manner such that they may be maintained without technical support. We then address the issue of execution, detailing the required system functionality and proposing a reference architecture for the automatic enforcement of the policies. Finally, we introduce a set of formal, generic correctness criteria and a verification procedure for the models. For extended policy models, we introduce and compare two alternative execution models for the evaluation of logical expressions that represent interruption patterns. Finally, we present a thorough analysis of related verification issues, considering both the system and user perspectives, in order to ensure correct process execution and also provide support for the user in semantic validation of the interruption policies.

Business processes form the backbone of all business operations, and workflow technology has enabled companies to gain significant productivity benefits through the automatic enactment of routine, repetitive processes. Process automation can be achieved by encoding the business rules and procedures into the applications, but capturing the process logic in a graphical workflow model allows the process to be specified, validated and ultimately maintained by business analysts with limited technical knowledge. The process models can also be automatically verified at design-time to detect structural issues such as deadlock and ensure correct data flow during process execution. These benefits have resulted in the success of workflow technology in a variety of industries, although workflows are often criticised for being too rigid, particularly in light of their recent deployment in collaborative applications such as e-business. Generally, many events can impact on the execution of a workflow process. Initially, the workflow is triggered by an external event (for example, receipt of an order). Participants then interact with the workflow system through the worklist as they perform constituent tasks of the workflow, driving the progression of each process instance through the model until its completion. For traditional workflow processes, this functionality was sufficient. However, new generation 'responsive' workflow technology must facilitate interaction with the external environment during workflow execution. For example, during the execution of an 'order to cash' process, the customer may attempt to cancel the order or update the shipping address. We call these events 'interruptions'. The potential occurrence of interruptions can be anticipated but, unlike the other workflow events, they are never required to occur in order to successfully execute any process instance. Interruptions can also occur at any stage during process execution, and may therefore be considered as 'expected, asynchronous exceptions' during the execution of workflow processes. Every interruption must be handled, and the desired reaction often depends on the situation. For example, an address update may not be permitted after a certain point, where this point depends on the customer type, and a shipping charge or refund may be applicable, depending on the original and new delivery region. Therefore, a set of rules is associated with each interruption, such that if a condition is satisfied when the event occurs, a particular action is to be performed. This set of rules forms a policy to handle each interruption. Several workflow systems do facilitate the automatic enforcement of 'exception handling' rules and support the reuse of code fragments to enable the limited specification and maintenance of rules by non-technical users. However, this functionality is not represented in a formal, intuitive model. Moreover, we argue that inadequate consideration is given to the verification of the rules, with insufficient support provided for the detection of issues at design-time that could hinder effective maintenance of the process logic or interfere with the interruption handling functionality at run-time. This thesis presents a framework to capture, analyse and enforce interruption process logic for highly responsive processes without compromising the benefits of workflow technology. We address these issues in two stages. In the first stage, we consider that the reaction to an interruption event is dependent on three factors: the progress of the process instance with respect to the workflow model, the values of the associated case data variables at the time at which the event occurs, and the data embedded in the event. In the second stage, we consider that the reaction to each interruption event may also depend on the other events that have also been detected, that is, we allow interruptions to be defined through event patterns or complex events. We thus consider the issues of definition, analysis and enactment for both 'basic' and 'extended' interruption policy models. First, we introduce a method to model interruption policies in an intuitive but executable manner such that they may be maintained without technical support. We then address the issue of execution, detailing the required system functionality and proposing a reference architecture for the automatic enforcement of the policies. Finally, we introduce a set of formal, generic correctness criteria and a verification procedure for the models. For extended policy models, we introduce and compare two alternative execution models for the evaluation of logical expressions that represent interruption patterns. Finally, we present a thorough analysis of related verification issues, considering both the system and user perspectives, in order to ensure correct process execution and also provide support for the user in semantic validation of the interruption policies.

Business processes form the backbone of all business operations, and workflow technology has enabled companies to gain significant productivity benefits through the automatic enactment of routine, repetitive processes. Process automation can be achieved by encoding the business rules and procedures into the applications, but capturing the process logic in a graphical workflow model allows the process to be specified, validated and ultimately maintained by business analysts with limited technical knowledge. The process models can also be automatically verified at design-time to detect structural issues such as deadlock and ensure correct data flow during process execution. These benefits have resulted in the success of workflow technology in a variety of industries, although workflows are often criticised for being too rigid, particularly in light of their recent deployment in collaborative applications such as e-business. Generally, many events can impact on the execution of a workflow process. Initially, the workflow is triggered by an external event (for example, receipt of an order). Participants then interact with the workflow system through the worklist as they perform constituent tasks of the workflow, driving the progression of each process instance through the model until its completion. For traditional workflow processes, this functionality was sufficient. However, new generation 'responsive' workflow technology must facilitate interaction with the external environment during workflow execution. For example, during the execution of an 'order to cash' process, the customer may attempt to cancel the order or update the shipping address. We call these events 'interruptions'. The potential occurrence of interruptions can be anticipated but, unlike the other workflow events, they are never required to occur in order to successfully execute any process instance. Interruptions can also occur at any stage during process execution, and may therefore be considered as 'expected, asynchronous exceptions' during the execution of workflow processes. Every interruption must be handled, and the desired reaction often depends on the situation. For example, an address update may not be permitted after a certain point, where this point depends on the customer type, and a shipping charge or refund may be applicable, depending on the original and new delivery region. Therefore, a set of rules is associated with each interruption, such that if a condition is satisfied when the event occurs, a particular action is to be performed. This set of rules forms a policy to handle each interruption. Several workflow systems do facilitate the automatic enforcement of 'exception handling' rules and support the reuse of code fragments to enable the limited specification and maintenance of rules by non-technical users. However, this functionality is not represented in a formal, intuitive model. Moreover, we argue that inadequate consideration is given to the verification of the rules, with insufficient support provided for the detection of issues at design-time that could hinder effective maintenance of the process logic or interfere with the interruption handling functionality at run-time. This thesis presents a framework to capture, analyse and enforce interruption process logic for highly responsive processes without compromising the benefits of workflow technology. We address these issues in two stages. In the first stage, we consider that the reaction to an interruption event is dependent on three factors: the progress of the process instance with respect to the workflow model, the values of the associated case data variables at the time at which the event occurs, and the data embedded in the event. In the second stage, we consider that the reaction to each interruption event may also depend on the other events that have also been detected, that is, we allow interruptions to be defined through event patterns or complex events. We thus consider the issues of definition, analysis and enactment for both 'basic' and 'extended' interruption policy models. First, we introduce a method to model interruption policies in an intuitive but executable manner such that they may be maintained without technical support. We then address the issue of execution, detailing the required system functionality and proposing a reference architecture for the automatic enforcement of the policies. Finally, we introduce a set of formal, generic correctness criteria and a verification procedure for the models. For extended policy models, we introduce and compare two alternative execution models for the evaluation of logical expressions that represent interruption patterns. Finally, we present a thorough analysis of related verification issues, considering both the system and user perspectives, in order to ensure correct process execution and also provide support for the user in semantic validation of the interruption policies.

A system requirements specification (SyRS) defines a set of functionalities that a system is expected to fulfil. A requirement may be “it is always the case that actualFuelLevel is greater than or equal to 0” for an industrial system. Inconsistencies in a SyRS may require the system to be redesigned or reimplemented, which can drastically increase costs. With the increased size and complexity of SyRS it is important to assess new methods for verifying their correctness with respect to some criteria such as consistency. PROPAS is a tool for automated consistency checking of SyRS developed within the VeriSpec project, a cooperation between Mälardalen University, Scania and Volvo GTT. The tool is based on satisfiability modulo theories (SMT) techniques and operates on SyRS encoded in formal notation, that is timed computation tree logic (TCTL). In this thesis we extend the functionality of the PROPAS tool by implementing a type-inferencing mechanism such that variable types in SyRS can be automatically inferred. For validation, we apply the extended PROPAS tool on a set of industrial requirements. The results show that the type-inferencing mechanism can correctly infer the types of the variables from the set of requirements in most cases, while in the same time not introducing significant computational overhead to the existing solution.

Durant ma thèse, j’ai participé à une étude fonctionnelle qui a démontré que p120-RasGAP, une protéine appartenant à la famille GAP (GTPase-activating protein), est le médiateur cytoplasmique de l’éphrine lors de l’atténuation d’ERK1/2. Pour confirmer cela, j’ai réalisé une expérience de co-immunoprécipitation et j’ai démontré que p120-RasGAP s’associe au récepteur de l’éphrine, Eph3, quand celui-ci est activé par un ligand éphrine. Ce résultat indique fortement que les signaux FGF et éphrine convergent au niveau de Ras et qu’ils contrôlent de manière antagoniste son activité. Dès lors, j’ai analysé les autres événements de spécification cellulaire impliquant l’antagonisme FGF/éphrine. Chez l’embryon d’ascidie, le signal FGF est décrit comme inducteur du destin neural dans les cellules ectodermiques qui, en absence du signal FGF, adoptent le destin épidermique. L’induction neurale des ascidies a lieu au stade 32 cellules et se traduit par la spécification de quatre précurseurs neuraux (ERK+) parmi les 16 cellules ectodermiques. J’ai démontré que le signal éphrine/Eph/RasGAP antagonise le signal FGF pour générer une activation d’ERK1/2 de type tout ou rien parmi les cellules ectodermiques. Enfin, en collaboration avec Philip Abitua, doctorant dans le laboratoire du Dr. Mike Levine (UC Berkeley), nous démontrons que l’antagonisme entre les signaux éphrine et FGF est impliqué dans la régionalisation antéro-postérieure de la plaque neurale / During my thesis study, I was involved in functional studies to demonstrate that p120-RasGAP, a GTPase-activating-protein (GAP), is a cytoplasmic mediator of the ephrin-mediated ERK attenuation. To confirm this notion, I conducted a co-immunoprecipitation experiment and demonstrated that p120-RasGAP associates with an ephrin receptor, Eph3, when the latter is activated by an ephrin ligand in ascidian embryos. These results strongly indicate that FGF and ephrin signals converge at the level of Ras and control its activity antagonistically. Following this finding, I looked for other cell fate specification events controlled by the antagonism between ephrin and FGF signals. In ascidian embryos, FGF signals are known to induce neural fates in ectodermal cells which otherwise adopt epidermal fates. Ascidian neural induction takes place at the 32-cell stage, resulting in specification of specific four cells as ERK1/2-active neural precursors among 16 ectodermal cells. I was able to demonstrate that ephrin/Eph/RasGAP signals counterbalance FGF neural inducing signals to generate the ON-OFF response of ERK activation among the ectodermal cells. Finally, in collaboration with a PhD student in Dr. Mike Levine’s lab (UC Berkeley), the antagonism between ephrin and FGF signals plays a role in regionalisation of the neural plate along the anterior-posterior axis.

Chez les rongeurs, les interneurones (INs) corticaux sont issus de l’éminence ganglionnaire (EG) médiale (MGE) et caudale (CGE), expriment une combinaison de facteurs définis et migrent tangentiellement puis radialement pour atteindre leur position laminaire définitive. La diversité et la spécification des sous-types d’INs provenant de la MGE ont suscité de nombreuses études, en revanche les mécanismes moléculaires contrôlant la migration et la spécification des INs issus de la CGE demeurent toujours obscurs. Dans cette étude, les voies de migration de ces INs ont été examinées grâce à une lignée de souris rapportrices des interneurones issus de la CGE avant d’analyser le rôle de deux facteurs de transcription, COUP-TFI et COUP-TFII, hautement exprimés dans la CGE. Deux voies de migration non précédemment caractérisées ont alors été identifiées : une voie dorsale (CLMS) où les INs migrent vers l’EG latérale (LGE) et une voie ventrale (CMMS) où les INs migrent vers la MGE. Le CLMS et le CMMS ont donc été analysés, ainsi que la voie de migration caudale (CMS), à différents stades de développement et l’expression spécifique de certains gènes a pu être identifiée. En inactivant conditionnellement COUP-TFI et/ou COUP-TFII dans les INs, les voies de migration sont altérées ainsi que l’expression des marqueurs moléculaires. Comme probable conséquence, les souris mutantes adultes montrent une distribution altérée des sous-populations d’INs en particulier de celles issues de la CGE. Mon étude a donc permis d’identifier et de caractériser deux nouvelles voies de migration pour les INs provenant de la CGE et a montré que COUP-TFs contribuent à leur modulation. / In rodents, cortical interneurons (INs) originate from the medial (MGE) and caudal ganglionic eminence (CGE) according to precise temporal schedules, express a defined combination of factors, and reach their final laminar position through tangential and radial cell migration. The diversity and fate-specification of MGE-derived interneuron subtypes are well characterized however the molecular mechanisms controlling the migration and specification of CGE-derived INs are still vague. In this study, I have first investigated the migratory paths of cortical INs using a reporter line specific to the CGE, and then I have assessed the involvement of COUP-TFI and COUP-TFII, which are highly expressed in the embryonic CGE during development, in these paths. My data unravelled two major previously non-characterized migratory streams from the subpallium to the pallium: a dorsal stream (CLMS) in which CGE-derived cells migrate to the lateral GE (LGE), and a ventral one (CMMS) in which CGE-derived cells migrate to the MGE. I have characterized both streams and the already well-described caudal stream (CMS) during different stages of development and identified a series of genes expressed in the migrating cells. By inactivating COUP-TFI and/or COUP-TFII in the developing INs, these streams together with their molecular marker expression are perturbed. As a consequence, adult mutant mice have an altered distribution of interneuron subpopulations, particularly the ones derived from the CGE. Taken together, my study identified and characterized two novel CGE-derived interneuron migratory routes to the cortex and showed that COUP-TFs contribute in modulating these paths.

Nos dias atuais, a gestão da qualidade não pode mais limitar-se ao produto ou ao seu processo fabril, pois a abertura dos mercados exige uma preocupação com outros sistemas que dão sustentação à qualidade, entre eles os voltados à gestão da segurança e saúde dos trabalhadores nos seus postos laborais. Neste sentido, esta dissertação tem por finalidade apresentar uma proposta de adoção da especificação OHSAS 18000: Sistemas de Gestão de Segurança e Saúde Ocupacional em uma área de galvanoplastia. A proposta de implantação demonstra um modelo, que se utiliza da metodologia descrita pela Régie Nationale des Usines de Renault adaptado, aplicado à etapa de planejamento. Esta abordagem permite verificar tanto a percepção do usuário do posto de trabalho, quanto a do analista e propiciam à empresa a identificação dos riscos e hierarquização das medidas prioritárias a serem adotadas para a melhoria contínua nas condições de trabalho de forma sistêmica. Os resultados encontrados permitem observar um rol de necessidades que devem ser observadas para que organização esteja apta a implantar a especificação OHSAS. / Nowadays, quality management cannot be limited to the product itself or its manufacturing process, for the opening of new markets demands a growing concern with other systems which support quality and, among such systems the ones turned to security and health management of workers in their workplaces. Therefore this dissertation aims to introduce a proposal of adaptation of OHSAS specification-Occupational Health and Safety Management Systems in galvanism area. The implantation proposal shows a model that uses the methodology described by Régie Nationale des Usines de Renault, which was adapted and applied to a planning phase. This approach allows verifying perception not only by workplace user but also by its analyst and enables the company to identify risks and rank steps that have a prior clain to be systematically adopted for the constant improvement on workplace environment. As an outcome it can be seen a wide range of needs that have to be noticed so that the company is able implement OHSAS specification.

Nos dias atuais, a gestão da qualidade não pode mais limitar-se ao produto ou ao seu processo fabril, pois a abertura dos mercados exige uma preocupação com outros sistemas que dão sustentação à qualidade, entre eles os voltados à gestão da segurança e saúde dos trabalhadores nos seus postos laborais. Neste sentido, esta dissertação tem por finalidade apresentar uma proposta de adoção da especificação OHSAS 18000: Sistemas de Gestão de Segurança e Saúde Ocupacional em uma área de galvanoplastia. A proposta de implantação demonstra um modelo, que se utiliza da metodologia descrita pela Régie Nationale des Usines de Renault adaptado, aplicado à etapa de planejamento. Esta abordagem permite verificar tanto a percepção do usuário do posto de trabalho, quanto a do analista e propiciam à empresa a identificação dos riscos e hierarquização das medidas prioritárias a serem adotadas para a melhoria contínua nas condições de trabalho de forma sistêmica. Os resultados encontrados permitem observar um rol de necessidades que devem ser observadas para que organização esteja apta a implantar a especificação OHSAS. / Nowadays, quality management cannot be limited to the product itself or its manufacturing process, for the opening of new markets demands a growing concern with other systems which support quality and, among such systems the ones turned to security and health management of workers in their workplaces. Therefore this dissertation aims to introduce a proposal of adaptation of OHSAS specification-Occupational Health and Safety Management Systems in galvanism area. The implantation proposal shows a model that uses the methodology described by Régie Nationale des Usines de Renault, which was adapted and applied to a planning phase. This approach allows verifying perception not only by workplace user but also by its analyst and enables the company to identify risks and rank steps that have a prior clain to be systematically adopted for the constant improvement on workplace environment. As an outcome it can be seen a wide range of needs that have to be noticed so that the company is able implement OHSAS specification.

Context. The requirements analysis phase, as the very beginning of software development process, has been identified as a quite important phase in the software development lifecycle. Software Requirement Specification (SRS) is the output of requirements analysis phase, whose quality factors play an important role in the evaluation work. Readability is a quite important SRS quality factor, but there are few available automated approaches for readability measurement, because of the tight dependency on readers' perceptions. Low readability of SRS documents has a serious impact on the whole process of software development. Therefore, it's extremely urgent to propose effective automated approaches for SRS documents readability measurement. Using traditional readability indexes to analyze readability of SRS documents automatically is a potentially feasible approach. However, the effectiveness of this approach is not systematically evaluated before. Objectives. In this study, firstly, we aim to understand the readability of texts and investigate approaches to score texts readability manually. Then investigate existing automated readability approaches for texts with their working theories. Next, evaluate the effectiveness of measuring the readability of SRS documents by using these automated readability approaches. Finally, rank these automated approaches by their effectiveness. Methods. In order to find out the way how human score the readability of texts manually and investigate existing automated readability approaches for texts, systematic literature review is chosen as the research methodology. Experiment is chosen to explore the effectiveness of automated readability approaches. Results. We find 67 articles after performing systematic literature review. According to systematic literature review, human judging the readability of texts through reading is the most common way of scoring texts readability manually. Additionally, we find four available automated readability assessments tools and seven available automated readability assessments formulas. After executing the experiment, we find the actual value of effectiveness of all selected approaches are not high and Coh-Metrix presents the highest actual value of effectiveness of automated readability approach among the selected approaches. Conclusions. Coh-Metrix is the most effective automated readability approach, but the feasibility in directly applying Coh-Metrix in SRS documents readability assessments cannot be permitted. Since the actual value of evaluated effectiveness is not high enough. In addition, all selected approaches are based on metrics of readability measures, but no semantic factors are blended in readability assessments. Hence studying more on human perception quantifying and adding semantic analysis in SRS documents readability assessment could be two research directions in future.