Speeple News Search

Sign Up! | Tags | Domains | Statistics | Options | Advanced Search

Tags » Project And Program Management

Related tags: agile development, analysis, architecture and oo design, bpm, coding tips and tricks, enterprise architecture, joe freeflier, personal and humor, soa, standards

  1. The business value of elegant design

    The business value of elegant design

    msdn.com » Inside Architecture - Nov 3, 2008

    In my last post, I highlighted the design process, suggesting that designers and architects should consider using creativity, in addition to methods and patterns, to build a truly useful system. In this one, I'd like

    Also tagged: analysis, architecture and oo design

  2. Non-Functional Requirements: the "All-Other" classification

    Non-Functional Requirements: the "All-Other" classification

    msdn.com » Inside Architecture - Oct 15, 2008

    I've seen various taxonomies of requirements. Like all taxonomies, any set of requirement types exists to classify or partition requirements into coherent groups for further analysis. Most break down the list of

    Also tagged: analysis

  3. Understanding Governance as Decision Rights

    msdn.com » Inside Architecture - Oct 4, 2008

    Todd Biske, whom I respect for his writings on SOA, seemed to miss the mark in his recent blog post about SOA Governance and Decision Rights. In that post, he said: if you focus on education, you can allow individual

    Also tagged: enterprise architecture, soa

  4. Preventing Ownerless Activities -- the "Blame the Computer" process modeling antipattern - part 2

    msdn.com » Inside Architecture - Jul 8, 2008

    In a prior post, I described a process modeling antipattern which I called "Blame the Computer." The feedback helped me to realize that there's a deeper problem that we need to consider: alignment of ownership between

    Also tagged: bpm

  5. Process and IT budget... owned by the same person?

    msdn.com » Inside Architecture - Jul 6, 2008

    In a prior post, I described a process modeling antipattern which I called "Blame the Computer." The feedback helped me to realize that there's a deeper problem that we need to consider: alignment of ownership between

    Also tagged: bpm

  6. The Usefulness of the Use Case?

    msdn.com » Inside Architecture - Jun 17, 2008

    I'm a big fan of use cases. Great for describing how software is used, and puts context around the use of functionality that helps software developers to create solutions that will actually fit into human

    Also tagged: analysis

  7. The non-overlapping responsibility set: Solution Architect and Enterprise Architect

    msdn.com » Inside Architecture - Jun 9, 2008

    Recently, Mike Walker posted a blog entry on the difference between Enterprise Architect and Solution Architect (sometimes called Application Architect). I think this is an interesting space, because I believe that

    Also tagged: enterprise architecture

  8. The non-overlapping responsibility set: Solution Architect and Enterprise Architect

    msdn.com » Inside Architecture - May 30, 2008

    Recently, Mike Walker posted a blog entry on the difference between Enterprise Architect and Solution Architect (sometimes called Application Architect). I think this is an interesting space, because I believe that

    Also tagged: enterprise architecture

  9. Example of modeling requirements in a process diagram

    msdn.com » Inside Architecture - May 22, 2008

    We use process models for lots of things. One is simply to understand the processes we have and to analyze them looking for opportunities to improve. But in IT, we have another good reason: to better understand

    Also tagged: analysis, bpm

  10. Leaving technology out of requirements gathering

    msdn.com » Inside Architecture - May 17, 2008

    I'm going to suggest a minimal way to gather requirements, one that produces a (minimum) requirements document in an iterative and agile manner. A little background In the systems space, it is common to write up a

    Also tagged: analysis, bpm

1  2  3  4  5  6