|
SEMAT (Software Engineering Method and Theory) is an initiative to reshape software engineering such that software engineering qualifies as a rigorous discipline. The initiative was launched in December 2009 by Ivar Jacobson, Bertrand Meyer, and Richard Soley.〔http://www.semat.org〕 At the start of the initiative the founders wrote a call for action statement〔http://www.drdobbs.com/architecture-and-design/222001342〕 and a vision statement.〔http://blog.paluno.uni-due.de/semat.org/wp-content/uploads/2012/03/SEMAT-vision.pdf〕 The initiative was envisioned to be a multi-year effort working in parallel to bridge the gap between the developer community and the academic community and create a community giving value to the whole software community. The work is now structured in four different, but strongly related areas: The Practice area, The Education area, the Theory area and the Community area . The Practice area primarily addresses practices. The Education area is concerned with all issues related to training for both the developers and the academics including students. The Theory area is primarily addressing the search for a General Theory in Software Engineering. Finally the Community area works with setting up legal entities, creating websites and community growth. It was expected that the Practice area, the Education area and the Theory area would at some point in time integrate in a way of value to all of them: the Practice area would be a “customer” of the Theory area, and direct the research to useful results for the developer community. The Theory area would give a solid and practical platform for the Practice area. And, the Education area would communicate the results in proper ways. A significant number of world-class experts in the field of software engineering endorse the initiative's Call for Action.〔http://www.drdobbs.com/architecture-and-design/the-semat-initiative-a-call-for-action/222001342〕 The signatories include Scott Ambler, Dines Bjørner, Barry Boehm, Erich Gamma, Ken Schwaber etc. The initiative is also supported by corporations such as IBM, Microsoft, Ericsson, ABB and Samsung, and academic institutions such as Peking University, Chalmers University of Technology, Florida Atlantic University, Wits University and KAIST. Some of the signatories are known in the field for well established software engineering models or methods, which are not always compatible. Yet the consensus on the initiative shows that they agree with the importance of refounding software engineering. ==The Practice Area== The first step was here to develop a common ground or a kernel including the essence of software engineering – things we always have, always do, always produce when developing software. The second step was envisioned to add value on top of this kernel in the form of a library of practices to be composed to become specific methods, specific for all kinds of reasons such as the preferences of the team using it, kind of software being built, etc. The first step is as of this writing just about to be concluded. The results are a kernel including universal elements for software development – called the Essence Kernel, and a language – called the Essence Language - to describe these elements (and elements built on top of the kernel (practices, methods, and more). Essence, including both the kernel and language, has been published as an OMG standard in beta status in July 2013〔http://www.omg.org/spec/Essence/1.0/Beta1/〕 and is expected to become a formally adopted standard in early 2014. The second step has just started, and the Practice area will be divided into a number of separate but interconnected track: the practice (library track), the tool track are so far identified and work has started or is about to get started. The practice track is currently working on a Users Guide to help software practitioners/students, practice/method authors and tool builders in the use of Essence. This guide will contain scenarios demonstrating how teams can use the Essence kernel to assess where they are and where they need to focus next independent of their chosen method and life cycle. Scenarios are also being developed to show teams how they can assess their current practices looking for gaps and potential overlaps. The Users Guide will also contain a practice development guide to help both practice authors and practitioners create and update practices and methods. 抄文引用元・出典: フリー百科事典『 ウィキペディア（Wikipedia）』 ■ウィキペディアで「SEMAT」の詳細全文を読む スポンサード リンク
|