No abstract

Abstract-This paper presents how business and IT requirements are captured with the Systemic Enterprise Architecture Methodology (SEAM). The method is applied to the Car Crash Management System (CMS) -Software Product Line (SPL) case study. The existing business situation is analyzed. We identify the problems and list relevant solutions. We select one of these solutions for which we define the business and the IT requirements. We then present the two components of SEAM used in this paper, goal-belief and behavior modeling. We end the paper by presenting the systemic foundations of SEAM.

Business rules are everywhere. Some of these rules are implicit and thus poorly enforced, others are written but not enforced, and still others are perhaps poorly written and obscurely enforced [1]. In this work, we propose an interactive, simulation-driven approach for the discovery of business rules. The rules are first specified in a natural language, then translated to the Alloy specification language. The Alloy Analyzer tool is used as a platform for rule simulation and discovery: it provides a domain specialist with an instant feedback, helping her to detect the issues with the existing business rules and to discover new rules in a systematic way.

Abstract:Business-IT alignment is complicated because of the need to align multiple business and IT points of view. A philosophical foundation can help generate methods that bring together these disparate viewpoints in a common model that all stakeholders can agree upon. In this paper, we describe the philosophical foundations of the Systemic Enterprise Architecture Methodology (SEAM) and show how it can help business-IT alignment with the example of a concrete business process. These foundations are applicable to other methods as well.

No abstract