I think IBM uses two step process: Business Component Modeling and Service Oriented Architecture and Modeling. Each step has method and steps. See IBM sysems journal website.
In my engagement with a billion dollar SW project, I apply Mintzburg's Five in Five to model the configuration of the organization and then componentize the organization that is used as input to SOAM to map business intent to IT. Busically I use modified Zachman framework to build five artifacts: Business architecture (Mintzburg's theory), data architecture, Component architecture (Zachman uses Applications here), SOAM, and implementation plans. Jerry Zhu --- Brian Mikesell <[EMAIL PROTECTED]> wrote: > Jason, > > I'm tasked with the same thing you are, and we, too, > are largely an > IBM shop, so maybe we can help each other out on > this task. > > The approach I'm taking is to define at a very high > level what our > most common use cases are. These come down to > pretty simple message > exchange patterns such as request/reply, one way, > notification, etc. > > > Out of those patterns, request/reply is our most > common, so that's > where I'll focus first. > > A reference architecture must satisfy your major use > cases and your > non-functional requirements, so I try to define a > logical component > model that satisfies these requirements. Major > architectural elements > (such as an enterprise service bus) emerge as you > look harder at the > non-functionals. Once you get to a certain level of > maturity with > your component model, run your use cases through the > component > diagram. I'm taking an iterative approach, so I get > to a certain > point, run use cases through, review that with a > larger group, and > make appropriate changes. > > Let me know if that's in-line with your approach. > I'm interested in > other ideas. > > Brian > > --- In > [email protected], > Jason Lenhart > <[EMAIL PROTECTED]> wrote: > > > > Hello and thank you for starting such a wonderful > > group, > > > > I am tasked with creating a SOA Reference > Architecture > > for my organization. > > > > In reading the OASIS 'Reference Model for Service > > Oriented Architecture' has the concept I really > > latched onto about 8 months ago (prior to me > receiving > > this assignment). > > > > Essentially that a Ref. Arch is to identify > abstract > > solutions to the problem domains in my > organization. > > > > That being said - I work in a very large > organization > > and we have a ton of problem domains (but I > suppose > > they can be derived easily down to architectural > > patterns). I was wondering if anyone had any > > direction on this. I also believe that the intent > of > > this is to outline how our current suites/toolsets > > will align (we are an IBM shop). > > > > Any direction is appreciated. > > > > Thank you in advance, > > > > Jason > > > > __________________________________________________ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam > protection around > > http://mail.yahoo.com > > > > > > > > __________________________________________________ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com ------------------------ Yahoo! Groups Sponsor --------------------~--> See what's inside the new Yahoo! Groups email. http://us.click.yahoo.com/2pRQfA/bOaOAA/yQLSAA/NhFolB/TM --------------------------------------------------------------------~-> Yahoo! Groups Links <*> To visit your group on the web, go to: http://groups.yahoo.com/group/service-orientated-architecture/ <*> To unsubscribe from this group, send an email to: [EMAIL PROTECTED] <*> Your use of Yahoo! Groups is subject to: http://docs.yahoo.com/info/terms/
