Software on demand

Software on demand development steps:

1. Customer software solution market analysis

Market analysis in performed on basis of company interview, where the applications/services needed for the company are selected. Market analysis focuses on including all relevant functionalities custom software application should have. From numerous vendors we choose 3 providers, which at most fully match the clients expectations.

    2.   User requirements – system analysis

Based on market analysis with help of strucutred interviews we define the company operations - system analysis and which requirements company actually needs - user requirements which complement each other.  First we perfrom the system analysis and later we define user requirements for software on demand.

3. Functional specifications

We take user requeirements as an input to functional specification which describes the application behaviour from user perspective. Functional specification is basis for project acceptance and completion.

4. System architecture

Based on functional specification we propose system architeture that enables system implementation. This phase usually consists of pilots where client gets a first rough glimpse of structure and outlook of the proposed system/application. Once the system architecture is confirmed by the client, the system implementation starts. 

5. System implementation

Usually most long lasting and time consuming step at creation of software on demand is system implementation. But in order not to keep client waiting too long to see the results, parts of system being developed is shown to client for partial testing purposes. By using partial testing client and provider gets feedback on development fast.

6. System testing

Once the system is implemented, the thorough testing takes place where system is being stabilized. We differentiate among several sort of testing such as: internal development testing, internal production testing, client testing on test environment.

Once the client confirms that system is functionally and qualitative appropriate we move onto system documentation.

7. System documentation

Technical system documentation is being created during the system implementation, user documentation usually is created after the end of system implementation and testing. Once both documentation are done, we continue with system deployment.

8. System deployment

Documentation and approved system is being deployed onto client production environment with predefined time intervals. Most importnat at deployment is that again the correct system functions is checked and client personell is properly educated for system usage.

9. System maintenance

Once the system is being used, it should be maintained regularly. Always there is the possiblity that end client performs the maintenance itself, but based on experience we recommend that specilized team of experts who developed the system also maintains it. This also proved to be most efficient way to maintain the system.

10. User support

If client demands  the user support, the call center is setup where company experts reply to user questions at system usage. Possible are different levels of user support..

11. System upgrades

System during operation needs usually many upgrades dur to business/legislation/technogy changes in system lifetime. Expert team based on client requests for system upgrade prepares the techically adequate solution which upgrades the current system.