tag:blogger.com,1999:blog-8607988883206610762.post7678416582413857502..comments2008-11-12T23:35:59.700-08:00Chung Wuhttp://www.blogger.com/profile/14030653899644168555noreply@blogger.comBlogger2125tag:blogger.com,1999:blog-8607988883206610762.post-68421813136862230322008-11-12T23:35:00.000-08:002008-11-12T23:35:00.000-08:00Thanks for your feedback.<BR/><BR/>I am not sure why application lifecycle management is unrelated from methodologies. Methodology, as defined by the Webster dictionary, is a body of methods, rules, and postulates employed by a discipline : a particular procedure or a set of procedures. Since Application Lifecycle Management is a discipline, Application Lifecycle Management methodologies would be the body of methods, rules, and postulates to carry out application management.<BR/><BR/>Application Lifecycle Management definitely has people and process elements. Someone has to carry out the tasks steps by steps in order to accomplish various objectives afterall.<BR/><BR/>As to whether development processes are different from operational processes. They are different, but should be related. For example, requirement analysis is one of the earlier phases of most application development processes. In addition to defining functional requirements, service level requirements should be considered at around the same time. I have seen too many application development projects not taking operational requirements into account during development phases, and end up with software that's not very manageable.<BR/><BR/>The processes that you mentioned are not exclusive of each other. Some of these processes are stronger in one domain, while others are stronger in other domains. They can be used in conjunction. With that said, I feel that ITIL v3 is probably one of the more comprehensive process frameworks out there today.Chung Wuhttp://www.blogger.com/profile/14030653899644168555noreply@blogger.comtag:blogger.com,1999:blog-8607988883206610762.post-36365993597484017912008-11-12T22:55:00.000-08:002008-11-12T22:55:00.000-08:00I think Application Lifecycle Management is different from methodologies; it is only related with application-side, not the people or process side. Development and implementation is very differenet processes and I think should be approached with different process methodologies. <BR/><BR/>Let me try to border process lines:<BR/>1- Development: RUP,Agile,XP,Software Factory etc.<BR/>2- Project(Implementation): Oracle AIM,SAP ASAP,MS RIM etc.<BR/>3- System Management: ITIL, MOF,COBIT etc.<BR/>4- Quality: CMMI,ISO etc.<BR/><BR/>I am not sure about that one methodology for all aspects is possible or needed.Ibrahim Leventhttp://www.blogger.com/profile/10129848174098327267noreply@blogger.com