[Home] [Industries] [Keys to Success] [Software] [People] [Culture] [Opportunities] [Contact Us]

Software

BHI's successful software development process is based on commitment to principles and our ability to apply the right methodology.

Software Development Phases

We believe these project phases are essential:

Analysis To build the right software, BHI spends 20% of the project's life making sure that we understand the problem and the solution from your perspective. In this phase we document the functionality, usability, reliability, performance and supportability requirements, and we develop a user interface prototype.

Design The Design phase accounts for about 15% of the project. We determine how the software architecture will meet all criteria of the documented requirements. Typical architectures at BHI involve a graphical user interface, a relational database, an application layer, and a data communications layer.

Implementation The Implementation phase involves developing the code that begins to give form to your software application. It typically accounts for 40% of the development process.

Test The Test phase, including system test and an alpha-test or beta-test, ensures that the software meets previously defined requirements. During this phase, the development lifecycle is completed and an assessment of the process is performed.

Technology Transfer Finally, in the Technology Transfer phase, BHI makes sure that you can use and maintain the software we develop. Effective development practices, along with early involvement from the recipients of the technology, allows this process to go smoothly-and ensure the long-term success of your project.

BHI Software Principles

At BHI we employ the following principles to maximize customer returns and to generate a high level of trust in our relationships.

Timeliness Effective software should be developed and deployed within six to twelve months. Additional functionality can be put in new versions and evolve over time.

Functionality Get as much of your product as possible to market as quickly as possible. Capitalize on the window of opportunity to position yourself as a leader in your arena.

Feedback The timely deployment of your software yields information about what to incorporate into the following version - information that can be obtained only by having real users in a production environment.

Requirements Accurately defining project requirements is the single most important factor determining success. It should account for 20% of the project time line.

Expectations Once it is determined that a change is needed, an Engineering Change Order (ECO) maintains mutually agreed-upon requirements and ensures that project expectations are met.

[Home] [Industries] [Keys to Success] [Software] [People] [Culture] [Opportunities] [Contact Us]