|
Our Development Methodology
|
|
| A robust software engineering development process follows a fairly well established set of steps. Our firm follows the same basic steps to reduce overall development cost, integration issues, and schedule risk. While some companies follow the ad-hoc build and fix style, we have provided many clients with exceptional systems, on time, and on budget using our more professionally disciplined approach. This translates into a commitment to you that you can rely on. VVS Inc. will make the project successful. | |
| Our Methodologies
|
|
|
Business Requirement Identification |
VVS Inc. identifies the requirements needed by the "business" for the specific software to be successful from a deployment perspective. This initial step ignores architectures, methodologies, languages, and other design specific boundaries. It focuses on the critical functions, look and feel, and operational characteristics the software must exhibit for the product to be successful. |
|
|
|
|
Enterprise Requirement Identification |
We then identify requirements that transcend a specific product or product line. These requirements may identify operational capabilities that need to be exhibited in your system so it can integrate with other tool suites in your infrastructure. |
|
|
|
|
High Level Architectural Requirement Identification |
We identify requirements that will drive the overall design of the software solution in the context of business and enterprise requirements. The architecture of the software can drive the structure of the design solution. The architecture will drive the simplicity, expandability, upgrade-ability, and maintainability of the code over its lifetime. This key step helps insure that the planned future phases of development will have the hooks necessary in the base architecture. |
|
|
|
|
High Level Design |
Using the requirements gathered, we identify all the elements of the design. This includes test features, look and feel, database schemas, protocols, languages, object definitions and their initial methods, design partitioning, and all the other details needed to completely identify how the implementation of the design should behave. |
|
|
|
| Implementation | Using the design and the requirements, our staff creates code that embodies the features and characteristics necessary to satisfy all the requirements. |
|
|
|
| Integration | We then combine the implementation code in a single environment that replicates the expected production environment. Test the implementation to see if it satisfies all the requirements including failure/error handling. At the end of this step, a configuration of all the code, the environment, and documentation will exist under configuration management and be ready for deployment (shrink wrapped). |
|
|
|
|
Testing |
We then perform an independent set of tests based on a test plan that encompasses all the requirements and any other reasonable things that might occur that were not specified in the requirements. Verify all the documentation that outlines the requirements, architecture, design, implementation, and test results is complete and stored in a configuration management system. |