Skip to main content

What you will never about online school management software

 No body wants to buy a product that will not add value to his life. Reason why we make purchases it’s simply to satisfy a particular need, but the irony of whole thing, is simply, software markets are filled with too many junks that promises so much and accomplish so little and some nothing. Software is a technical product, as such it needs, not just having a basic knowledge of what a software can do to make a better purchasing decision  that you won’t  regret. Quickly i will show you ways to identify horrible school management software.

1. It can do every thing

Every good product, does few things and exceptionally well too.That’s why your ear is meant only for hearing and your eyes for seeing. A great school management software, solves a particular problem exceptionally well and also provides great user experience and as such gives great return on investment.

2. It’s Complex

Complexity can mean different things, but in this context, means the ease  at which you get things done with the software. How many steps do you have to take to accomplish a task in the software, if the steps are more for just one task, it signals complexity. Every complex systems makes it difficult to learn, and also makes you prone to making many mistakes even after getting trained on how to use it.

3. No Documentation

Documentation in this context means, an online self help page that will guide you on how to solve most of the technical problem you might run into, in the course of using the service. The truth is, if the school software has not documentation, the software company offer little or no after sales support for their product. Without support, your school management software will put you into dilemma, leaving you to figure out the way out of every technical glitch, which can possibly lead to loss of time and in most cases heavy data loss, that ultimately lead to possible system failure.


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…