Proceedings of the 4th International Workshop on Twin Peaks of Requirements and Architecture - TwinPeaks 2014, 2014
ABSTRACT The disciplines of requirements engineering (RE) and software architecture (SA) are fund... more ABSTRACT The disciplines of requirements engineering (RE) and software architecture (SA) are fundamental to the success of software projects. The synergistic relationship between these two disciplines has long been acknowledged by both academicians and practitioners alike. To build successful and cost-effective software systems, we must understand and leverage the linkages between functional and architectural requirements. We discuss a knowledge-assisted approach that establishes traceability between functional and architectural requirements. The approach classifies requirements into the problem context (functional) and a solution (architectural) context. The functional context is called Functional Requirement Viewpoint (FRV). The architectural context is further categorized into three sub-contexts namely the Functional Architecture Viewpoint (FAV), the Technical Architecture Viewpoint (TAV) and the Deployment Architecture Viewpoint (DAV). Though the approach separates the problem domain and the solution domain explicitly; it facilitates development of requirements and architectural specifications concurrently; appreciating the necessary interplay between the two.
2013 28th IEEE/ACM International Conference on Automated Software Engineering (ASE), 2013
ABSTRACT Identifying system use cases and corresponding validations involves analyzing large requ... more ABSTRACT Identifying system use cases and corresponding validations involves analyzing large requirement documents to understand the descriptions of business processes, rules and policies. This consumes a significant amount of effort and time. We discuss an approach to automate the detection of system use cases and corresponding validations from documents. We have devised a representation that allows for capturing the essence of rule statements as a composition of atomic ‘Rule intents’ and key phrases associated with the intents. Rule intents that co-occur frequently constitute ‘Rule acts’ analogous to the Speech acts in Linguistics. Our approach is based on NLP techniques designed around this Rule Model. We employ syntactic and semantic NL analyses around the model to identify and classify rules and annotate them with Rule acts. We map the Rule acts to business process steps and highlight the combinations as potential system use cases and validations for human supervision.
2013 4th International Workshop on Product LinE Approaches in Software Engineering (PLEASE), 2013
ABSTRACT Producing timely and customer oriented products is a key determinant for the success of ... more ABSTRACT Producing timely and customer oriented products is a key determinant for the success of any product-based business. Product requirement elicitation and configuration practices therefore play a major role in taking products to market efficiently. Knowledge of the existing generic product is crucially important while creating its variants. In this paper, we discuss an ontological representation of product primitives for a knowledge-assisted requirements configurator and illustrate its use for a financial product suite
The aim of Requirements Engineering (RE) is to collaboratively evolve the initial uncertain and a... more The aim of Requirements Engineering (RE) is to collaboratively evolve the initial uncertain and ambiguous understanding of a business problem into features and attributes of software system. Reaching a common level of understanding of a problem domain is one of the key challenges that the software vendors and customers face during requirements definition. Stakeholders involved in RE attempt to achieve this common goal through communication and knowledge sharing. Frequent exchanges and transfer of knowledge ...
The application of nanotechnology in the agricultural sector is likely to facilitate and frame th... more The application of nanotechnology in the agricultural sector is likely to facilitate and frame the next stage of development of genetically modified crops, precision farming techniques (remote and local sensing), remediation (water treatment plants, pesticide removal from ground water), nano-sensors, nano-agricultural chemicals and most importantly designing smart delivery systems for nutrients and pesticides[1]. Although most of these applications are still in their infancy, they have a great potential to revolutionalize the entire agricultural value chain [2]. The wide spectrum of applications has resulted into emergence of multiple stakeholders such as nano-agriculture researchers, practitioners (agriculturists/ farmers), manufacturers and regulatory bodies. They would be seeking and using knowledge in this nascent area from different perspectives such as research and technology, consumer safety, environmental impact and ethical, legal and social implications. No informatics platform exists to cater to the knowledge needs of various stakeholders in this field. To address this gap, we have developed an intelligent Nano-Agriculture Informatics System (NAIS), wherein these stakeholders can carry out multiple activities of their interest. NAIS incorporates a collaborative and semantically guided process to facilitate knowledge-based activities.
Domain knowledge edge is crucially important in the requirements definition. Requirement analysts... more Domain knowledge edge is crucially important in the requirements definition. Requirement analysts are not necessarily domain experts and domain knowledge in an organization is not easily visible and accessible to them. The increasing complexity of software requirements coupled with pressures to reduce time to market have underlined the necessity for a structured mechanism to help the requirement analyst ‘jump-start ’ projects (re)using domain knowledge. Most Requirements Engineering (RE) methods treat the requirements engineering exercise as something that begins from nothing and assume a ‘clean slate ’ approach which outlines a series of steps to define, analyze, specify and validate requirements collaboratively with relevant stakeholders. We propose a method and framework to enable Knowledge assisted Requirements Evolution (K-RE). K-RE starts with a seed requirement specification. The seed contains structured domain knowledge as represented by core elements such as business events, actions and decisions (as captured in business processes), constraints, and analysis patterns derived from various resources. Each time a new software application is to be developed; we start with this seed specification and ‘evolve’ it by way of altering and/or adding to the core to get to the final requirement specification. This is done in a semantically assisted way. The semantic assistance comes from ontologies that can be created, maintained and evolved collaboratively and a context-sensitive alert mechanism that provides online alerts as a requirement analyst evolves her specification from the seed. Each new exercise of requirements definition thus, becomes an evolution of a pre-existing structured domain knowledge base tailored to suit specific projects.
The Role of Data Use Agreements in Specifying Legally Compliant Software Requirements………………………………... more The Role of Data Use Agreements in Specifying Legally Compliant Software Requirements………………………………………………………………………………………….1 Jessica D. Young, Annie I. Antón, Laurie Williams, Paul Otto ... Governance and Accountability in the New Data Ecology……………………….......................5 Travis D. Breaux, Thomas A. Alspaugh ... Compliance Management with Measurement Frameworks……………………………………. 15 Andre Rifaut ... A Systematic Review of Goal-oriented Requirements Management ...
Proceedings of the 4th International Workshop on Twin Peaks of Requirements and Architecture - TwinPeaks 2014, 2014
ABSTRACT The disciplines of requirements engineering (RE) and software architecture (SA) are fund... more ABSTRACT The disciplines of requirements engineering (RE) and software architecture (SA) are fundamental to the success of software projects. The synergistic relationship between these two disciplines has long been acknowledged by both academicians and practitioners alike. To build successful and cost-effective software systems, we must understand and leverage the linkages between functional and architectural requirements. We discuss a knowledge-assisted approach that establishes traceability between functional and architectural requirements. The approach classifies requirements into the problem context (functional) and a solution (architectural) context. The functional context is called Functional Requirement Viewpoint (FRV). The architectural context is further categorized into three sub-contexts namely the Functional Architecture Viewpoint (FAV), the Technical Architecture Viewpoint (TAV) and the Deployment Architecture Viewpoint (DAV). Though the approach separates the problem domain and the solution domain explicitly; it facilitates development of requirements and architectural specifications concurrently; appreciating the necessary interplay between the two.
2013 28th IEEE/ACM International Conference on Automated Software Engineering (ASE), 2013
ABSTRACT Identifying system use cases and corresponding validations involves analyzing large requ... more ABSTRACT Identifying system use cases and corresponding validations involves analyzing large requirement documents to understand the descriptions of business processes, rules and policies. This consumes a significant amount of effort and time. We discuss an approach to automate the detection of system use cases and corresponding validations from documents. We have devised a representation that allows for capturing the essence of rule statements as a composition of atomic ‘Rule intents’ and key phrases associated with the intents. Rule intents that co-occur frequently constitute ‘Rule acts’ analogous to the Speech acts in Linguistics. Our approach is based on NLP techniques designed around this Rule Model. We employ syntactic and semantic NL analyses around the model to identify and classify rules and annotate them with Rule acts. We map the Rule acts to business process steps and highlight the combinations as potential system use cases and validations for human supervision.
2013 4th International Workshop on Product LinE Approaches in Software Engineering (PLEASE), 2013
ABSTRACT Producing timely and customer oriented products is a key determinant for the success of ... more ABSTRACT Producing timely and customer oriented products is a key determinant for the success of any product-based business. Product requirement elicitation and configuration practices therefore play a major role in taking products to market efficiently. Knowledge of the existing generic product is crucially important while creating its variants. In this paper, we discuss an ontological representation of product primitives for a knowledge-assisted requirements configurator and illustrate its use for a financial product suite
The aim of Requirements Engineering (RE) is to collaboratively evolve the initial uncertain and a... more The aim of Requirements Engineering (RE) is to collaboratively evolve the initial uncertain and ambiguous understanding of a business problem into features and attributes of software system. Reaching a common level of understanding of a problem domain is one of the key challenges that the software vendors and customers face during requirements definition. Stakeholders involved in RE attempt to achieve this common goal through communication and knowledge sharing. Frequent exchanges and transfer of knowledge ...
The application of nanotechnology in the agricultural sector is likely to facilitate and frame th... more The application of nanotechnology in the agricultural sector is likely to facilitate and frame the next stage of development of genetically modified crops, precision farming techniques (remote and local sensing), remediation (water treatment plants, pesticide removal from ground water), nano-sensors, nano-agricultural chemicals and most importantly designing smart delivery systems for nutrients and pesticides[1]. Although most of these applications are still in their infancy, they have a great potential to revolutionalize the entire agricultural value chain [2]. The wide spectrum of applications has resulted into emergence of multiple stakeholders such as nano-agriculture researchers, practitioners (agriculturists/ farmers), manufacturers and regulatory bodies. They would be seeking and using knowledge in this nascent area from different perspectives such as research and technology, consumer safety, environmental impact and ethical, legal and social implications. No informatics platform exists to cater to the knowledge needs of various stakeholders in this field. To address this gap, we have developed an intelligent Nano-Agriculture Informatics System (NAIS), wherein these stakeholders can carry out multiple activities of their interest. NAIS incorporates a collaborative and semantically guided process to facilitate knowledge-based activities.
Domain knowledge edge is crucially important in the requirements definition. Requirement analysts... more Domain knowledge edge is crucially important in the requirements definition. Requirement analysts are not necessarily domain experts and domain knowledge in an organization is not easily visible and accessible to them. The increasing complexity of software requirements coupled with pressures to reduce time to market have underlined the necessity for a structured mechanism to help the requirement analyst ‘jump-start ’ projects (re)using domain knowledge. Most Requirements Engineering (RE) methods treat the requirements engineering exercise as something that begins from nothing and assume a ‘clean slate ’ approach which outlines a series of steps to define, analyze, specify and validate requirements collaboratively with relevant stakeholders. We propose a method and framework to enable Knowledge assisted Requirements Evolution (K-RE). K-RE starts with a seed requirement specification. The seed contains structured domain knowledge as represented by core elements such as business events, actions and decisions (as captured in business processes), constraints, and analysis patterns derived from various resources. Each time a new software application is to be developed; we start with this seed specification and ‘evolve’ it by way of altering and/or adding to the core to get to the final requirement specification. This is done in a semantically assisted way. The semantic assistance comes from ontologies that can be created, maintained and evolved collaboratively and a context-sensitive alert mechanism that provides online alerts as a requirement analyst evolves her specification from the seed. Each new exercise of requirements definition thus, becomes an evolution of a pre-existing structured domain knowledge base tailored to suit specific projects.
The Role of Data Use Agreements in Specifying Legally Compliant Software Requirements………………………………... more The Role of Data Use Agreements in Specifying Legally Compliant Software Requirements………………………………………………………………………………………….1 Jessica D. Young, Annie I. Antón, Laurie Williams, Paul Otto ... Governance and Accountability in the New Data Ecology……………………….......................5 Travis D. Breaux, Thomas A. Alspaugh ... Compliance Management with Measurement Frameworks……………………………………. 15 Andre Rifaut ... A Systematic Review of Goal-oriented Requirements Management ...
Uploads