done (know-why), what concepts are used (knowwhat) and who is responsi - PDF document

done (know-why), what concepts are used (knowwhat) and who is responsible (know Maxime Bernaert and Geert Poels their know-why by asking why-questions (justification) and how-questions (refinement). Alternatives can be expressed by OR-refinements, conflicts by conflicting goals, and obsta e an SMEÕs business architecture. In the case study, the SMEÕs CEO was very satisfied with the way in which KAOS and Objectiver enabled him to analyse his enterprise and to document both know-how and know-why. However (Goal Tree)!Know-Who!(Responsibilities)Know-What !(Objects) Maxime Bernaert and Geert Poelsin goal models, knowwhat in object models and knowwho in responsibility models, and to make sure these modelsare aligned to achieve internal consistency and traceabilityThe paper describestherelevant characteristics of SMEs and their CEOandevaluates KAOS in terms of how well itaddressthespecific characteristics and needsof SMEs. An example illustrates how KAOS can be used in an SMEand a case studygathers questions of SMEÕs CEO regarding KAOS and its tool Objectiverwhile building his own modelsTheexample given forexistingdelivered some insightsFirst, the KAOS goal model enables SMEs to documenttheir knowwhy by asking whyquestions (justification) and howquestions (refinement).Alternatives can be expressed by ORrefinements, conflicts by conflicting goalsand obstacles can be analysed and resolved to make the goal model more robust. Second, SMEsÕ knowhow be expressed by means of a KAOS operation model, which hasthe extra advantage that the rationale behind the processes be expressed by linking the operation model with the goal model via operationalization links. In this way, bidirectional traceability between problem and solution spaces is being assured. Third, an SME can make an internal or external agent responsible for goals and for performing operations. Fourth, the KAOS object model providesa commonglossary.This exampleshowed that KAOS, as it was originally developed to be usein softwaresystem developmentprojects, has the ability to document and analyse an Õs business architecture.In the case study, the SMEÕs CEO wasvery satisfied with the way in which KAOSand Objectiver enabled him to analyse hisenterprise and to document both knowhow and knowwhyowever, when building his modelhe had some questions thatprovideus with material to work on in furtherresearchFigure Structure of the four submodels of CHOOSEAfter the publication of this paper, the results have lead to the development of the CHOOSE approachFigure , which will be published in the special issue of Informatieon architecturein November, 2011 To be published as ernaert, M. (2011): De Zoektocht naar KnowHow, KnowWhy, KnowWhat en KnowWho: Architectuur voor Kleinere Bedrijven in Vier Dimensies. In: InformatieSdu Uitgevers bv (2011),http://www.informatie.nl/ (Goal Tree) Know-Who!(Responsibilities)! Know-What !(Objects)! Know-How !(Processes)! Relationships! Goal Actor Process Object 16 TheQuest for KnowHowKnowWhy, KnowWhat and KnowWho: Using KAOS for Enterprise ModellingMaxime Bernaert andGeert PoelsDepartment of Management Information Systems and Operations Management Faculty of Economics and Business Administration, Ghent University, Tweekerkenstraat 2, B9000 Ghent, BelgiumAbstract.hile the field of information systemsengineeringis largelyfocussedon developing methods for complex problems and largeenterprises, lessis to specifically address the needs ofsmaller organizationslike small and medium sized enterprises (SMEs, although they are important drivers of economyThese needs include a better understanding of theprocesses(knowhow)why things are(knowwhy), what concepts are used (knowwhat) and who is responsible (knowwho)In this paperthe KAOSapproachis evaluated not only useful for developing software projects, but with the potential to be used for developing a business architecture or enterprise model. An example of KAOS is given, by way of illustration, and KAOS wasappliedin a case study by an SMEÕs CEOwhich resulted ina set ofquestions for further researchKeywords:Requirements Engineering, Business Process Management, Small and Medium Sized Enterprises, Goal Modelling, KAOS, Business Architecture, Enterprise Architecture, Enterprise ModellingThis paper has been published as: ernaert, M. and Poels, G.(2011): The Quest for KnowHow, KnowWhy, KnowWhat and KnowWho: Using KAOS for Enterprise Modelling. In: Advanced Information Systems Engineering Workshops,C. Salinesi and O. Pastor, LNBIP pp. , SpringerVerlag Berlin Heidelberg (2011)Smaller organizati, like small and medium sized enterprises (SMEs), require proper systems to fulfil their information and automation needs, but their first concernare organizational issues, with IT as a means for achieving business objectives. While most of the effortin the field of information systems engineering is focused towards complex problems and largeenterprises, the specific needs and problems of smaller enterprises are often forgotten.The problemwe specifically look atin SMEs arethe need for tter documentation, understanding, and analysis of the processes(knowhow), why thingsaredone (knowwhy), what concepts are used (knowwhat) and who is responsible (knowwho), taking into account the specific characteristics of SMEs that may impose constraints on potential solutions.In this paper, the goal oriented requirements engineering technique KAOS is proposed as a solution to document SMEsÕhow in process models,why 15