IMSF: Infinite Methodology Set Framework
Software development is usually an integration task in enterprise environment - few software applications work autonomously now. It is usually a collaboration of heterogeneous and unstable teams. One serious problem is lack of resources, a popular result being outsourcing, ‘body shopping’, and indirectly team and team member fluctuation. Outsourced sub-deliveries easily become black boxes with no clear development method used, which has a negative impact on supportability. Such environments then often face the problems of quality assurance and enterprise know-how management. The used methodology is one of the key factors. Each methodology was created as a generalization of a number of solved projects, and each methodology is thus more or less connected with a set of task types. When the task type is not suitable, it causes problems that usually result in an undocumented ad-hoc solution. This was the motivation behind formalizing a simple process for collaborative software engineering. Infinite Methodology Set Framework (IMSF) defines the ICT business process of adaptive use of methods for classified types of tasks. The article introduces IMSF and briefly comments its meta-model.
Keywordsframework IMSF methodology process software engineering
Unable to display preview. Download preview PDF.
- 1.Chrissis, M.B., Konrad, M., Shrum, S.: CMMI(R): Guidelines for Process Integration and Product Improvement, 2nd edn. SEI Series in Software Engineering. Addison-Wesley Professional, Reading (2006)Google Scholar
- 2.Essential Unified Process (EssUP) web site in (November 2008), http://www.ivarjacobson.com/products/essup.cfm
- 3.Antipatterns in November 2008 (2008), http://www.antipatterns.com/
- 4.Brown, W.J., McCormick, H.W., Thomas, S.W.: AntiPatterns in Project Management. John Wiley & Sons, Chichester (2000)Google Scholar