Since 1982, Information Concepts has developed complex-database oriented applications for the Public and Private sectors.  Leveraging our customers IT investments, we build applications which allow them to meet their organizations goals. Solutions are developed in .Net, Java, and SQL Databases.

We have fine-tuned its development methodology which has allowed it to develop quality products in a predictable, scalable manner. To develop quality solutions on a timely basis, our development process has the following foundations:

Defined Requirements – Our planning methodology allows us to clearly define the projects requirements through building visualization (prototypes) with multiple iterations with the client. As system requirements start to stabilize, the requirements are documented in detail.

Clearly Defined Modules – Once requirements are locked down, the system is further defined through a design process which breaks the system into small, easily developed, components; these components may be a screen, stored procedure, or a business object. Each component is defined by the project team as a single unit which can be developed within a day or two and can be independently tested.

Common Business rules are defined as objects and stored procedures which can be developed and tested independent of the processes consuming the rules, such as a user interface, web service, or other system process.

Technical Walkthrough – Before one line of code is developed, we perform a detailed technical walkthrough with our senior technical team and any developer who may be involved in the project. This walkthrough is a group meeting which reviews in detail, every screen, report, and process to determine if the system is architecturally sound. Each screen and report is reviewed to insure it maps against the physical database. Every business process is reviewed to map to the requirements document.

Strong Project Management – Our teams of Project Managers and Business Analysts are focused on delivering a quality product on a timely basis; this influences our development methodology by insuring that we understand the state of the development effort at any time. We track the status of the development effort, and capture all issues associated with the build such as unit testing issues, enhancement requests, and assignment status.

Our PM teams works closely with the developers to help answer questions about the functionality of the system and provide a functional overview to help understand the application.

Reuse of Standard, Tested Components – utilize proven, tested components for validation, security, and standard user interface controls to help speed development and testing. If necessary, we will purchase modules, with client authorization, for standard user interface controls. Information Concepts-developed components for Security and Validation are delivered to the client with full source code.

We have developed two meta-data driven components which have reduced our time to market during development:

  • The security framework allows us to deploy role-based security based on meta data in the database, which at run time, turns on functions and fields to which a user has access.
  • The Database-driven grid control renders an HTML Grid with ASP.NET based on meta data in the database, which at run time, renders a grid on the screen. If the system needs to be modified to add a field or change the grid behavior, no software changes are necessary.

By using standard controls, our development and testing time is reduced significantly. This also reduces the maintenance costs for the system over time.

Use of Skilled Developers – Information Concepts employs a staff of proven developers with at least 3 years of development experience. When a new members of our team is hired, they work with members of our senior staff who mentor the new hire.

Small Teams of up to 8 People – We develop applications in small teams, usually no more than 8 people to a team. For large projects, we create multiple independent teams. These teams may focus on system feeds, sections of the user interface, or reporting.