Submitted by dominique de cooman on Tuesday, June 25, 2013 - 13:09.Business Process analysis

To start a business process analysis we first sit down with everyone involved to discover the business needs. This is done in a stakeholder analysis.It is a technique you can use to identify and assess the importance of key people , groups of people , or institutions that may significantly influence the success of your activity or project. This step will reveil your business needs and what is possible within budget. We ll talk with all the people involved: application users, business stakeholders, technical people, ... and discover how all the different elements will influence the application being designed.

We will create a swot analysis concerning your business using a content management system. This will reveal why you need it.

After the swot analysis is done the next step is to create a conceptual and functional analysis. This functional analysis will come up with the information architecture and feature selection and will produce wireframes. These wireframes will be accompanied by functional text explaining what all elements on the elements of the content management system are doing. The concept needs to meet a range of criteria including usability, accessibility, attractiveness, findability, credibility, value and usefulness.

The business process analysis essential to discover the true need for an application. This will reveal if a content management system is needed and if it will be able to deliver value. Don't just pay to have a system. Be sure it automates things, generates revenue, reduce costs.

Implementation of the process

The creation of technical analysis will be needed which will be a document for the drupal develoment team to start creating the drupal application. Developers will exactly know what to build and how to build into the content management system.

With the technical document we can start the implementation. Learn how development is done.

When the implementation is done the process does not stop we measure the results and use this data to improve the process. The cycle starts again. Each iteration of the cycle will result in the discovery of more revenue, more efficient processes and reduced costs.

Mission of the business analyst

The software architect his job is to sit down with the people how know the business, he has the ability to work with business analysts by doing a business process analysis in function of software needs.

Being a Software Architect I can not only design the application but I can also make sure development goes as planned. I can followup on how the application is being made and if the application is up to standards) I can assist teams with training and leading. Like an architect reviewing a building until completed a software architect does the same thing for the application.

Creating value & reducing costs

Having done the total analysis consisting of the business, functional, conceptual and technical analysis with drupal a focus on drupal cms ensures that no valuable resources are wasted on creating certain functionality. A challenge often existing when working with different parties involving people with different skills. Although drupal should not influence the design process, not knowing what a cms like drupal can do out of the box will often cause complicated solutions that were already available. This could result in functionality being implemented in a cost ineffectif way. Knowing drupal give us the opportunity to consider alternatives for attaining the same business goal.

Development will be much smoother and cleaner when all levels of analysis are done with drupal in mind. The developers will end up with a straight forward technical analysis.

Creating the complete analysis also eliminates time consuming communication between the involved parties. Often lots of miss communications happens between partners that don't really know each others business. Functional/conceptual people often are not fully aware how developers operate and vice versa. Also a gap can exist between business, functional and technical. This problem is completely eliminated since all three terrains are well understood by the same party.

This will reduce the development and maintenance cost of the solution. Lowering the level of custom coding and increasing communication efficiency will lead to an increase in usefulness of the solution and deliver extra value to its business goal.

Tags: analysisdrupal_taxonomy: Drupal Planet