Skip to main content

Epic formula to know how much school management software really cost.

 Software pricing can be tricky especially if your are a  newbie in the system. Countless time people often feels that they know don’t what they are paying for. Pricing model are low on start but accrues over time making us feel trapped in something we don’t even understand how it works. Quickly i will show you all the school management software pricing model and their benefits, so you can make the right choices.

1. Per student

Most school management vendor uses this model. Mostly in Nigeria, schools pays a specific fee on each students per term, to gain access to the software. With this model, school will bother less about maintenance and updates, and focus really on what matters. This model makes the vendor more proactive in responding to support, because of the ongoing relationship between the vendor and the school, that gives school much right to terminate the program any time it feels it’s purpose is no longer served.

2. Monthly

In monthly payment, you pay a specific amount every month. This model is very tricky. Schools don’t understand how the cost are measured, this make them prone to sudden price hike that may not be attributed to anything. The advantage of this model, it comes with full support, like Per Student. Schools will worry less about maintenance and update because they are controlled by the vendor.

3. One Time

You own the software. In this model you outrightly buys the software from the vendor. To buy software outrightly cost much at first but it’s cost effective over time, because you don’t have any accrues payment over time. In this model, your school takes care of most of maintenance and the update are not regular. Support also might not be very proactive, because the vendor feels he has handed everything over to your school.

There are really no easy model, all have it’s disadvantage  which ranges from cost to maintenance but i recommend Per Student model, you are not left to maintain and support the software all by yourself, you just leave that to the vendor so you can focus on doing your job better.


Popular posts from this blog

How to do partial update for HTTP APIs in ASP.NET CORE MVC with JSON Patch

JSON Patch is a format for describing changes to a JSON document. It can be used to avoid sending a whole document when only a part has changed. When used in combination with the HTTP PATCH method, it allows partial updates for HTTP APIs in a standards compliant way. A JSON Patch document is just a JSON file containing an array of patch operations. The patch operations supported by JSON Patch are “add”, “remove”, “replace”, “move”, “copy” and “test”. The operations are applied in order: if any of them fail then the whole patch operation should abort.
The JSON Patch supports the following operations:
Add - Adds a value to an object or inserts it into an array.Remove -  Removes a value from an object or array. Replace - Replaces a value. Equivalent to a “remove” followed by an “add”. Copy - Copy a value from one location to another within the JSON document. Both from and path are JSON Pointers. Move - Move a value from one location to the other. Both from and path are JSON Pointers. Test - Te…

How to implement RESTful API Versioning in ASP.NET Web API 2 using IHttpRouteConstraint

The only thing constant in life is change, and that is proved everyday in our industry, API’s are cool to extend the functionality of your application and expose it to other developers. The cool thing about IT and software, it’s that things changes quite rapidly and so it’s the technology, hence technology can change and the needs of your organisation can change, hence in order to keep serving this evolving needs and keep been relevant, your api might need to change also. Small changes can be accommodated within the initial version, but changes that will risked breaking the existing code, will required the need for versioning.

Implementing a custom IHttpRouteConstraint

According to msdn, a IHttpRouteConstraint simply Represents a base class route constraint. What then is a route constraint? A route constraint simply gets or sets a dictionary of expressions that specify valid values for a URL parameter.

publicclassApiVersionRouteConstraint : IHttpRouteConstraint


How to implement multi-tenancy with subdomains using Route Constraint in ASP.NET MVC

According to Wikipedia, The term "software multitenancy" refers to a software architecture in which a single instance of software runs on a server and serves multiple tenants. A tenant is a group of users who share a common access with specific privileges to the software instance. With a multitenant architecture, a software application is designed to provide every tenant a dedicated share of the instance - including its data, configuration, user management, tenant individual functionality and non-functional properties. Multitenancy contrasts with multi-instance architectures, where separate software instances operate on behalf of different tenants. By giving companies, access to a tenant through a subdomain of choice, will help to personalise the experience more and gives a sense of ownership to each tenant. This will go along way to bring consistency in there branding.
Implementing Route Constraint
You use route constraints to restrict the browser requests that match a partic…