About Us

The solutions architect is primarily employed to help and support program and project managers in the design, planning and direction of specific implementation projects. The enterprise architect has more strategic and cross-organizational concerns, and strives to optimize solution delivery across the organization. The work of a solutions architect may or may not be governed by an enterprise architecture function. The influence of the enterprise architect team on solution architects depends on an organization's policies and management structure. So, the extent to which a solution architect's work realises an enterprise architect's road maps will vary widely in different contexts.

Engineering Team is responsible for research and development and of any team project, in that all members of the team be assigned a given role for the team. Team Leader must be responsible for overseeing all aspects of the team project; holds the tie-breaking vote. Technical Lead experts on all technical aspects of the project, in particular the hardware and software used for development. Designer designs the project and breaks the project into smaller pieces for the programmers. Lead Programmer Needs to have an understanding of the project as a whole; organizes all of the other programmers. Technical Writer Writes all documentation for the project. Configuration Management Maintains the code base for the project; could include CVS responsibilities.

DBAs are also known by the titles database coordinator or database programmer, although a database programmer requires more advanced skills in SQL programming than a DBA may have, and database programmers may not have and do not require the skills of database administration, backing up, restoring, monitoring or tuning to do their job well. The role integrates closely with the other jobs of database analyst, database modeller, programmer analyst, and systems manager. Some organizations have a hierarchical system of database administrators

Some software testing tasks, such as extensive low-level interface regression testing, can be laborious and time consuming to do manually. In addition, a manual approach might not always be effective in finding certain classes of defects. Test automation offers a possibility to perform these types of testing effectively. Once automated tests have been developed, they can be run quickly and repeatedly. Many times, this can be a cost-effective method for regression testing of software products that have a long maintenance life. Even minor patches over the lifetime of the application can cause existing features to break which were working at an earlier point in time.