News

Customization of OpenGoo... 01 Aug 2009

Pointmatrix is taking a part in customizing OpenGoo with more functionalities.OpenGoo is an easy to use Open Source Web Office.

It is a co...

BankersAvenue.com and Expedia Affiliate Network announce hotel reserva... 01 Jul 2009

BankersAvenue.com which is developed by PointMatrix, today accounces partnership with Expedia Affiliate Network(EAN).This leads Pointmatrix to ha...

Quick links

Select Page:



Software development process


Our company's primary goal lies in maintaining tried and true methods for every task. This allows us to improve both our overall productivity and service quality. For this purpose, our staff do their best to organise the seemingly unruly process of software development. We apply project management techniques to software development in order to always deliver our projects on time and within budget limitations, allowing us to meet customer's expectations in terms of functionality, costs and deadlines.

We have worked out a unique approach to a variety of tasks and activities that take place during the software development process. Thus in order to monitor software life cycles, we've set out a clear model for the software development process, which in its turn consists of the following stages:

Domain analysis

At this stage our professionals investigate the so-called "domain" for the provided software. Since we strongly believe that the more knowledgeable we are about the domain, the less the work required, our main objective lies in finding and gathering all required information.

Project elements analysis We analyse all the minuscule project details in the course of extracting its requirements. Our experienced software developers make sure that the requirements are not incomplete, ambiguous or contradictory. For this very purpose we tend to demonstrate live code quite frequently to our customer in order to reduce the risk that the requirements are incorrect.

We also carefully create specifications prior to application development, precisely describing the software that is to be developed.

Software architecture

Architecture is intended for making sure the software system will meet the end-product's requirements, as well as ensuring that future requirements can be addressed; in other words, a software framework for that solution.

In other words a software framework for that solution is being manufactured.

At this stage our professionals are ready to provide our customer with an abstract representation of the system based on the carried out pilot analysis results.

Our company considers this stage to be of paramount importance for any project's success. That is why we plan and subsequently report progress within the project environment by means of taking certain consecutive steps, such as:


  • project scope definition
  • appropriate methods for completing the project
  • defining tasks and the logical dependencies between them
  • an estimation of the time necessary for completing necessary tasks
  • necessary resources and cost allocation
  • total project cost assessment


Once established and agreed upon, the plan becomes our development team's baseline. Progress is usually measured against the baseline throughout the life of the project.

Coding

The development team assigned to the project works on developing the code itself.

Testing

Our software engineers are hard at work with testing the developed software. We see proper code compilation as a vital concern that must always be addressed.

Documentation

Our technical writers are busy with documenting the internal design of developed software for the purpose of future maintenance and enhancement.

Release Release of the tested product with all the functionality implemented and all the accompanying technical documentation attached.

Maintenance

Sometimes we have to cope with newly discovered problems or new requirements. That is why at this stage our specialists work on maintaining and enhancing the software. At this step, it is often necessary to add code that does not fit the original design.

PMIS makes use of this model during the project workflow and after the product release. As such, we regularly analyse the activity implemented to identify weaknesses and drive forth improvement. It also identifies strong points that can be developed further or integrated into common practice for our team.