- Software architecture Software design and architecture
Software is released under a four part version number: MAJOR.MINOR.RELEASE.BUILD.
Major
Business oriented version of the product, marketing defined number. Each product version should increment the "major" version, as the business decides that it takes the product to a next level
Minor
Milestone oriented version, unique number within the scope of the major defining a version that presents a different interface to the users or other system modules.
Release
Task oriented version, unique release number within the scope of the minor. Each task done should increment the "release" version as it only improves the product within unchanged external interfaces.
Build
compilation based number, unique build number within the scope of the release. Each commit pushed should increment the "build" number as technically its a different build.
- Our Strategy
The first meeting
Understanding requirements
Together with the client we define the business case driving the customer needs. Specification of business requirements are subseqently used in rapid prototyping
The second step
Prototyping solution
Within just weekds the customer is involved in a series of prototyping sessions to gather feedback and improve the software model and the user experience using incremental steps in implementation and architecture.
Ongoing maintenance
Software maintenance
Customer receives a long term guarantee of ongoing cooperation and maintenance of the delivered software to ensure that the whole solution grows in tune with evolving business requirements.