We Develop

  • Web Applications - Rich, user friendly internet-facing web applications.
  • Mobile Web Applications - Web applications optimised for display and interaction on mobile devices.
  • Business Applications - Enterprise Intranet portals.


  • Microsoft ASP.Net MVC - A patterns-based application development framework for building dynamic websites that enables a clean separation of concerns and that gives you full control over mark-up for enjoyable, agile development.
  • Microsoft Entity Framework - An object-relational mapper that enables .NET developers to work with relational data using domain-specific objects. It eliminates the need for most of the data-access code that developers usually need to write. This technology is database agnostic, allowing it to be employed against a variety of extant environments.
  • SQL Server - A comprehensive and scalable data platform that includes enhanced security and management features.


Cambridge Software Engineering uses Microsoft Solution Framework (MSF) as the basis for software development methodologies. Utilising this approach has a number of significant benefits, including:

  • It is an industry recognised development approach.
  • It is continually being evolved.
  • It is geared towards developing for Microsoft Windows platforms and software.
  • It has been closely integrated into the latest Microsoft Development Tools such as Visual Studio and Team Foundation Server.

As a development methodology it contains a number of key principles including:

  • Best of both Agile and Structured development methodologies
  • Product focussed mind set
  • Focussed on delivering business value
  • Stay agile and expect change
  • Invest in Quality
  • Learn from All experiences


MSF concentrates its efforts on delivering versioned software; each spiral or iteration providing a means of obtaining customer feedback and creativity. The iterations consist of the following phases:

  • Envisioning: Provides a means of unifying the project team behind a common vision. The team must have a clear vision of what it wants to accomplish. This vision document is likely to be defined once, and reviewed briefly during subsequent iterations.
  • Planning: Where the bulk of the planning for the project is completed. Most of the plans are constructed by Release Management as a large portion of these plans relate to how the solution is to operate within its expected environment.
  • Development: Where the team accomplishes most of the build of solution components for the specified Usage Scenarios. This may mean temporary components to be thrown away during subsequent iterations. Some development work may continue into the stabilisation phase in response to testing.
  • Stabilisation: Conduct testing to validate the developed solution against the specified Usage Scenarios. The team focuses on resolving or triaging bugs and preparing the solution for release.