Documente Academic
Documente Profesional
Documente Cultură
From Wikipedia, the free encyclopedia Not to be confused with Methods engineering, a subspecialty of Industrial engineering
Example of a Method Engineering Process. This figure provides a process-oriented view of the approach used to develop prototype IDEF9 method concepts, a procedure, and candidate graphical and textual language elements[1]. Method engineering in the "field of information systems is the discipline to construct new methods from existing methods".[2] It focuses on "the design, construction and evaluation of methods, techniques and support tools for information systems development".[3] Furthermore method engineering "wants to improve the usefulness of systems development methods by creating an adaptation framework whereby methods are created to match specific organisational situations".[4]
Contents
[hide]
1.1 Computer Aided Method Engineering 1.2 Method tailoring 1.3 Situational method engineering 2.1 Knowledge engineering approach 2.2 Method language design process 2.3 Graphical language design 2.4 Method testing 2.5 Formalization and application techniques
[9]
. Example tools for meta-process modeling are represented in Rolland (1997). A Primer for Method Engineering [10].
This enables the creation of development methods suitable for any development situation. Each system development starts then, with a method definition phase where the development method is constructed on the spot.[4] In case of mobile business development, there are methods available for specific parts of the business model design process and ICT development. Situational method engineering can be used to combine these methods into one unified method that adopts the characteristics of mobile ICT services.
This image provide a general overview of the IDEF Method engineering processs approach. According to this approach there are three basic strategies in method engineering:[1]
Reuse : one of the basic strategies of methods engineering is reuse. Whenever possible, existing methods are adopted. Tailormade : find methods that can satisfy the identified needs with minor modification. This option is an attractive one if the modification does not require a fundamental change in the basic concepts or design goals of the method. New development : Only when neither of these options is viable should method designers seek to develop a new method.
task accomplishment and basic apprenticeship support to novice practitioners, and developing a language(s) of expression. Method application techniques are then developed outlining guidelines for use in a stand-alone mode and in concert with other methods. Each element of the method then undergoes iterative refinement through both laboratory and field testing.[1]
desired information content. With this general understanding, previously developed graphical language structures are explored to identify potential reuse opportunities. While exploring candidate graphical language designs for emerging IDEF methods, a wide range of diagrams were identified and explored. Quite often, even some of the central concepts of a method will have no graphical language element in the method.[1] For example, the IDEF1 Information Modeling method includes the notion of an entity but has no syntactic element for an entity in the graphical language.8. When the language designer decides that a syntactic element should be included for a method concept, candidate symbols are designed and evaluated. Throughout the graphical language design process, the language designer applies a number of guiding principles to assist in developing high quality designs. Among these, the language designer avoids overlapping concept classes or poorly defined ones. They also seek to establish intuitive mechanisms to convey the direction for reading the schematics.[1] For example, schematics may be designed to be read from left to right, in a bottom-up fashion, or center-out. The potential for clutter or overwhelmingly large amounts of information on a single schematic is also considered as either condition makes reading and understanding the schematic extremely difficult.[1]
Computer-aided software engineering Configuration management MetaCASE tool Metadata modeling Meta-Process Modeling Method Framework for Engineering System Architectures ISO/IEC 24744
[edit] References
1. ^ a b c d e f g h i j k l m n o p q Richard J. Mayer and others (1995). Information Integration for
Concurrent Engineering (IICE) Compendium of methods report Air Force Material Command, Wright-Patterson Air Force Base, Ohio. p.7-10.
2. ^ F. Harmsen & M. Saeki (1996). "Comparison of four method engineering languages".
In: Sjaak Brinkkemper et al. (eds.) Proceedings of the IFIP TC8, WG8.1/8.2 working conference on method engineering on Method engineering : principles of method construction and tool support: principles of method construction and tool support. January 1996, Atlanta, Georgia, United States. p.209-231
3. ^ Sjaak Brinkkemper, Method engineering: engineering of information systems
development methods and tools. Journal of Information & Software Technology, Vol 38, n4, pp 275-280 (1996)
4. ^ a b Colette Rolland (2008) Method Engineering: Towards Methods as Services. Keynote
the 10th International Conference CAiSE'98, B. Lecture Notes in Computer Science 1413, Pernici, C. Thanos (Eds), Springer. Pisa, Italy, June 1998.
6. ^ S. Kelly, K. Lyyttinen, M. Rossi. Meta Edit+: A fully configurable, multi-user and
multi-tool CASE and CAME environment, Proc. CAiSE'96 Conf., Springer Verlag, 1996
7. ^ F. Harmsen, S. Brinkkemper, Design and implementation of a method base
management system for situational CASE environment. Proc. 2nd APSEC Conf., IEEE Computer Society Press, pp 430-438, 1995
8. ^ G. Merbeth. Maestro II- das intergrierte CASE-system von Softlab, CASE systeme and
international conference and workshop on database and experts system application, DEXA97, Toulouse, 15 September 1997
10. ^ C. Rolland. A Primer for Method Engineering. Proceedings of the INFORSID
Conference (INFormatique des ORganisations et Systemes d'Information et de Decision), Toulouse, France, June 10-13, 1997.
11. ^ a b Aydin, M.N., Harmsen, F., Slooten, K. v., & Stagwee, R. A. (2004). An Agile
Information Systems Development Method in use. Turk J Elec Engin, 12(2), 127-138
12. ^ Abrahamsson, P., Warsta, J., Siponen, M.T., & Ronkainen, J. (2003). New Directions
methodology construction". In: Cotterman, Senn (eds.) Systems Analysis and Design: A Research Agenda. Wiley, Chichester. pp. 257268.
Sjaak Brinkkemper, Kalle Lyytinen, Richard J. Welke (1996). Method engineering: principles of method construction and tool support : proceedings of the IFIP TC8, WG8.1/8.2 Working Conference on Method Engineering 26-28 August 1996, Atlanta, USA. Springer. ISBN 041279750X Sjaak Brinkkemper, Saeki and Harmsen (1998) Assembly Techniques for Method Engineering, Advanced Information Systems Engineering, Proceedings of CaiSE'98, Springer Verlag Ajantha Dahanayake (2001). Computer-aided method engineering: designing CASE repositories for the 21st century. Idea Group Inc (IGI), 2001. ISBN 1878289942 Brian Henderson-Sellers, Jolita Raylte and Sjaak Brinkkemper eds. (2008). Situational method engineering : fundamentals and experiences. New York : Springer, 2008 Brian Henderson-Sellers, C. Gonzalez-Perez and Donald Firesmith (2004) Method Engineering and COTS Evaluation in: ACM SIGSOFT Software Engineering Notes archive. Vol 30, Issue 4 (July 2005). Manfred A. Jeusfeld, Matthias Jarke and John Mylopoulos eds. (2009). Metamodeling for Method Engineering. mitpress. ISBN 0-262-10108-4
View page ratings Rate this page What's this? Trustworthy Objective Complete Well-written I am highly knowledgeable about this topic (optional) Categories:
Bottom of Form
Toolbox
Main page Contents Featured content Current events Random article Donate to Wikipedia Help About Wikipedia Community portal Recent changes Contact Wikipedia
Interaction
Print/export
This page was last modified on 14 June 2011 at 15:41. Text is available under the Creative Commons Attribution-ShareAlike License; additional terms may apply. See Terms of use for details. Wikipedia is a registered trademark of the Wikimedia Foundation, Inc., a non-profit organization. Contact us Privacy policy About Wikipedia Disclaimers Mobile view