Patterns for service-oriented information exchange requirements

Service-Oriented Computing (SOC) is an emerging computing paradigm that supports loosely-coupled inter-enterprise interactions. SOC interactions are predominantly specified in a procedural manner that defines message sequences intermixing implementation with business requirements. In this paper we present a set of patterns concerning requirements of information exchange between participants engaging in service-oriented interactions. The patterns aim at explicating and elaborating the business requirements driving the interaction and separating them from implementation concerns

Smart cards: State-of-the-art to future directions

The evolution of smart card technology provides an interesting case study of the relationship and interactions between security and business requirements. This paper maps out the milestones for smart card technology, discussing at each step the opportunities and challenges. The paper reviews recently proposed innovative ownership/management models and the security challenges associated with them. The paper concludes with a discussion of possible future directions for the technology, and the challenges these present

Enterprise strategy requirements engineering framework : towards completeness of system requirements

University of Technology, Sydney. Faculty of Engineering and Information Technology.Empirical evidence shows that the success of a project depends on the completeness of system requirements. Although requirements engineering literature demonstrates how important strategic business goals are for the development of requirements models, it does not examine their effect on the completeness of system requirements. The objective of this research is to propose and test a framework that shows the influence of strategic business requirements on the completeness of system requirements. The framework integrates strategic business requirements with the functional requirements, non-functional requirements and completeness of system requirements to measure their direct and indirect influence. This framework (the Enterprise Strategic Requirements Engineering Framework) has been evaluated and validated by two studies. In the first study, business analysts collected lists of requirements from system stakeholders. In the second study, business analysts assessed those lists in terms of their completeness. More than 100 business analysts with varying degrees of experience participated in these studies. Structured equation models were used to analyse the data in order to show the effects of strategic business requirements on the completeness of system requirements. The results support the proposed framework and show that it is a true representation of the relationship between strategic business requirements, functional requirements, non-functional requirements and the completeness of requirements lists. This thesis contributes to the field of requirements engineering in various ways. It highlights the importance of collecting a list of strategic business requirements and it demonstrates why this should be treated as an individual list, rather than simply a sub-set of a list of non-functional requirements. The results also show that strategic business requirements influence both non-functional and functional requirements, as well as the completeness of system requirements. Finally, the research found that business analysts play a critical role in capturing requirements. The results show that novices did not approach many stakeholders and did not consider any business strategy requirements, whereas more experienced business analysts collected requirements from many stakeholders, including senior management, where strategic business requirements were available. This framework will be extremely valuable in giving support to the many approaches that highlight the importance of strategy. It clarifies the importance of collecting strategic business requirements and it will be valuable for the education of requirements engineers, business analysts and others who perform the task of collecting requirements

Strategic Business Requirements for Master Data Management Systems

Master Data Management (MDM) is of increasing importance because it is seen as a promising approach in companies torespond to a number of strategic business requirements, such as complying with an increasing number of regulations,supporting internal and external business process integration, and establishing a “360-degree-view on the customer”. As aresult, software vendors such as IBM, Oracle, SAP, and TIBCO are offering MDM application systems. However, the usercommunity feels a significant mismatch between their own strategic requirements and the functionality currently offered bythe software products. As the Information Systems (IS) research community has remained silent so far regarding this researchproblem, the research presented in this paper makes intensive use of knowledge from the practitioners’ community in order todesign a framework for strategic business requirements to be met by MDM systems. As an outcome of a design-orientedresearch process, the framework is an artifact which advances the scientific body of knowledge while at the same timeproviding benefit for practitioners. The framework includes seven design principles which are translated into 23requirements. The requirements form a baseline for internal and external communication in companies and for the design ofconcrete MDM systems

Requirement-driven creation and deployment of multidimensional and ETL designs

We present our tool for assisting designers in the error-prone and time-consuming tasks carried out at the early stages of a data warehousing project. Our tool semi-automatically produces multidimensional (MD) and ETL conceptual designs from a given set of business requirements (like SLAs) and data source descriptions. Subsequently, our tool translates both the MD and ETL conceptual designs produced into physical designs, so they can be further deployed on a DBMS and an ETL engine. In this paper, we describe the system architecture and present our demonstration proposal by means of an example.Peer ReviewedPostprint (author's final draft