Preethu Rose Anish

Learn More
Large IT vendors execute thousands of projects in a variety of business domains and environments. Over the years, they end up repeatedly developing and deploying systems for a given domain in the same country, sometimes even for the same company. It would save them a lot of cost and effort if they could reliably depend on their past experience and draw(More)
—Software architects are responsible for designing an architectural solution that satisfies the functional and non-functional requirements of the system to the fullest extent possible. However, the details they need to make informed architectural decisions are often missing from the requirements specification. An earlier study we conducted indicated that(More)
Failure to identify and analyze architecturally significant functional and non-functional requirements (NFRs) early on in the life cycle of a project can result in costly rework in later stages of software development. While NFRs indicate an explicit architectural impact, the impact that functional requirements may have on architecture is often implicit.(More)
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(More)
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(More)
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(More)
Software requirements specifications (SRSs) often lack the detail needed to make informed architectural decisions. Architects therefore either make assumptions, which can lead to incorrect decisions, or conduct additional stakeholder interviews, resulting in potential project delays. We previously observed that software architects ask Probing Questions(More)
Nanotechnology research and development in the agri-food sector is likely to facilitate and frame the next stage of development of genetically modified crops, chemical pesticides and design of less calorie-dense foods [1]. However, unlike other established domains, nanotechnology research and development has triggered serious calls for effective(More)
[Context and Motivation] Requirements specifications often lack the details needed by software architects to make informed architectural decisions. Lacking such details, the architects either make assumptions or go back to business analysts for clarifications or conduct additional stakeholder interviews. This may result in incorrect requirements and project(More)