Here is my understanding of how enterprises specify, deliver and manage process-centric applications:
The main roles include:
Business analyst or consultants interact with business users to gather the requirements of the business process. They often use tools like Microsoft Word, Visio Diagrams and mock-ups of HTML screens to capture those requirements. They are not expected to be technical or understand programming constructs.
A corporate developer is then responsible for mapping the specification into design and implementation and tying the logical flow with the actual applications, portals and services. A new level of detail and variability is introduced here: data transformation, exception management, timeouts, business transactions, etc...
Finally business users need activity monitoring and business reporting.
The main tasks involved include:Specification (owned by business analyst)
Implementation (owned by corporate developer)
Delivery and administration (owned by ops)
Activity monitoring (for business users)
Customization and adaptbility (rapid cycle business user, business analyst, corporate developer)
I would appreciate feedback to this picture.
This model is fundamentally correct. I would add that each phase you discuss can be drilled into more detail. The larger the project, the more carefully the phases and tasks are segmented. The smaller the project, the more blurred the phases and roles.
Dig Deeper on Dynamic case management and smarter process applications (SPAs)
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.