Jonathan Huxley :: Consulting

The critical foundation of any successful project implementation is a thorough requirements analysis. This lays the groundwork for an efficient and effective solution that meets targeted business objectives. Business Requirements Consulting engagements work with stakeholders across all levels and functions of a client company to:

• Articulate project objectives
• Understand business requirements
• Evaluate data needs and sources
• Establish project and solution success criteria

People and process come before software. Implementing a software solution around an inefficient process only enables the organization to do the wrong things faster. A critical examination of business process and the information needed to achieve business goals is the key to deriving real business benefit from Business Intelligence. In many cases, much of the solution is in the process, not the technology. Because of this we remain technology agnostic until the requirements analysis and logical design phases are complete.

Upon delivery of a successful Business Requirements phase the project can move into a logical design phase where the architecture (software and hardware and middleware considerations) is defined and upon completion of the design phase construction can begin. Business Requirements Analysis (also known as Discovery) typically accounts for 10% of a project budget.

<< Back

Key words: Linux (Red Hat / CentOS / Debian), UNIX, SOLARIS, PHP, Perl, Python, C++, Java, JavaScript, AJAX, PostgreSQL, MySQL, BerkleyDB, InnoDB, Tomcat, Apache, Lighttpd, Memcached, PostGIS, Slony, Zend Platform, GeoSer ver, Lucene, SOLR, SOAP, ReST, AMF, XML, JSON, GeoJSON, Zend Framework, CakePHP, Model-View-Controller.


		Home \| About \| Technologies \| Contact

	The critical foundation of any successful project implementation is a thorough requirements analysis. This lays the groundwork for an efficient and effective solution that meets targeted business objectives. Business Requirements Consulting engagements work with stakeholders across all levels and functions of a client company to: • Articulate project objectives • Understand business requirements • Evaluate data needs and sources • Establish project and solution success criteria People and process come before software. Implementing a software solution around an inefficient process only enables the organization to do the wrong things faster. A critical examination of business process and the information needed to achieve business goals is the key to deriving real business benefit from Business Intelligence. In many cases, much of the solution is in the process, not the technology. Because of this we remain technology agnostic until the requirements analysis and logical design phases are complete. Upon delivery of a successful Business Requirements phase the project can move into a logical design phase where the architecture (software and hardware and middleware considerations) is defined and upon completion of the design phase construction can begin. Business Requirements Analysis (also known as Discovery) typically accounts for 10% of a project budget. << Back Key words: Linux (Red Hat / CentOS / Debian), UNIX, SOLARIS, PHP, Perl, Python, C++, Java, JavaScript, AJAX, PostgreSQL, MySQL, BerkleyDB, InnoDB, Tomcat, Apache, Lighttpd, Memcached, PostGIS, Slony, Zend Platform, GeoSer ver, Lucene, SOLR, SOAP, ReST, AMF, XML, JSON, GeoJSON, Zend Framework, CakePHP, Model-View-Controller.

Copyright © 2008 Jonathan Huxley \| Site map \| RSS feeds