Philosophy


We encourage the following within our teams

philosophy

Open Standards

Existing open standards if exists will be implemented within all projects. An open standard is one that conforms to the following definition.

  • it should be maintained by a non-commercial organization
  • participation in the ongoing development work is based on decision making processes that are open to all interested parties.
  • open access: all may access committee documents, drafts and completed standards free of cost or for a negligible fee.
  • It must be possible for everyone to copy, distribute and use the standard free of cost.
  • The intellectual rights required to implement the standard (e.g.essential patent claims) are irrevocably available, without any royalties attached.
  • There are no reservations regarding reuse of the standard.
  • There are multiple implementations of the standard.

When no such standards exists then best practice standards after collaboration will implemented till global or industry standards are established. When there are competing standards, then one will be chosen till one standard becomes more globally accepted. The following is a list of various global standards or trends

Open System Integration (Service-Oriented Architecture)

SOA is an architectural style for building software applications that use services available in a network such as the web. It promotes loose coupling between software components so that they can be reused. Applications in SOA are built based on services. A service is an implementation of a well-defined business functionality, and such services can then be consumed by clients in different applications or business processes. SOA allows for the reuse of existing assets where new services can be created from an existing IT infrastructure of systems. In other words, it enables businesses to leverage existing investments by allowing them to reuse existing applications, and promises interoperability between heterogeneous applications and technologies. SOA provides a level of flexibility that wasn’t possible before in the sense that: Services are software components with well-defined interfaces that are implementation-independent. An important aspect of SOA is the separation of the service interface (the what) from its implementation (the how). Such services are consumed by clients that are not concerned with how these services will execute their requests. Services are self-contained (perform predetermined tasks) and loosely coupled (for independence) Services can be dynamically discovered Composite services can be built from aggregates of other services SOA uses the find-bind-execute paradigm

Process Automation

What is process automation? There’s a simple process automation definition stating that process automation is a series of solutions to let a company simplify process management by integrating software, hardware, workflows and resources into a single system that provides plenty of process automation benefits, such as reduced waste, mitigated risk of failure, and optimized use of resources. The process automation aim consists in achieving minimized durations of the process cycle

Training

Training needs to be scoped in all projects. It could be any of the following

  • 3rd Party Suport
  • Peer training by Project members
  • Support Groups (mailing lists,web forums,news groups..)
  • Commercial Support

Support & Documentation

Project members will provide a Support Ticketing system that will deal with system defects but not new features and enhancements.

Leave a comment