The US States’ Governments partner with Seasia to Modernize, Automate and Upscale DMV processes

Shift future development efforts into a configuration approach

It is done to provide configurable and plug-in software components. The key areas of the architecture that will benefit from this approach are:

• Work flow - Through the use of Windows Workflow Foundation (WWF), business processes can be client-defined and easily updated and deployed with minimal software development required.
• Transport Mechanisms – With the use of Microsoft Communication Foundation (WCF), the transport layer between the client and the business services can be defined and stored in a configurable file format. The WCF provides DMV the capability to configure for any transport mechanism requirement without major impacts to the software application layers.

Windows Workflow Framework

It provides a workflow configurable solution. The extension of this framework allows the functional team to define the DMV workflow requirements and through configuration tools implement the changes to the DMV with minimal or no development requirements.

Business Rule Framework

It will integrate with the business model and extend validations, exceptions, and change the business model behavior.

The use of Microsoft’s Patterns & Practices

This application block involves the use of Caching, Cryptography, Data Access, Exception Handling, Logging, & Security. These off the shelf frameworks provide the foundation for the development teams and architects to provide a more robust framework for DMV.

Point of Sale Framework

This is the Center Stage solution and the first phase of the POS deployment is the standalone deployment. The final deployment is a seamless integration between the DMV and POS of the Center Stages product.

Integration

The primary approach is to use the Integration Capabilities of SQL server. SQL server integration services are used for Integration purposes. The integration needs of the DMV project for Vermont/Rhode Island do not justify an elaborate Enterprise Architecture Integration due to cost and time considerations. The DMV data was either pushed or pulled via ftp. So the best approach was a batch process via ftp/Integration Services to expeditiously process the information into the DMV. The new version of SQL Server 2005 provided improved features for Integration Services, Scheduling, and .NET integration. Additionally, after studying all the interfaces as well as the needs of data synchronization, SL service brokers were also evaluated. The decision is taken after completion of the requirements analysis phase.

SQL Server 2005 Database used for Development

new features provided by SQL Server 2005 and the .NET 2.0 Framework. One of these features is the use of event patterns with caching

The DMV follows an n-tier architecture approach using the latest design & development tools and frameworks. In addition to the tool sets, parallel development efforts focus on the following:

• Application Framework Designs - These designs are the foundation to the DMV and consist of the workflow, UI navigation, UI composition, business rules, and etc. frameworks.
• UI Prototype – The prototype follows the direction of the customers’ requirements and the changes as directed by the Seasia Consulting Business Analyst.
• Business Object Modeling – This approach also provides the business domain logical relationships and collaborations.

During the iteration process of the DMV, the main goal of the project process is to maintain data integrity on the Mainframe. This data migration effort needs to maintain integrity until the final deployment of the DMV and there is no longer a need for data from the existing mainframe application. SQL service Broker is evaluated to use for data synchronization between legacy and the new Application.
The Software Development Lifecycle (SDLC) processes of Seasia Consulting are followed by all the disciplines of the DMV. We have a deep knowledge base of DMV and great expertise in creating frameworks for DMV functionality in the past. DMV is used to harness the current design frameworks from previous DMV implementations. The following list of frameworks is refactored:

The use of .NET 2.0 Framework

This framework allows the use of new and updated features such as security, caching, data providers, SQL Server integration, etc. This framework, along with the new published application, blocked by Microsoft shortens the development lifecycle and provides more design extensibilities.