Application Development & Re-Engineering Guidelines
The primary goal of the Software Development and Re-engineering Guidelines is to ensure the development of Common Application Software (CAS) that can be configured to meet the needs of various states and departments without modifying the application’s core code, allowing for faster deployment and saving time, effort, and money.
As a result, apps must follow criteria to ensure that they’re standardized and cross-state compatible. This requirement has resulted in the creation, development, and deployment of a productized cloud-enabled application that can be used in a variety of ways.
Service Location Transparency
This refers to a service’s capacity to be used by Service Consumers independent of its physical location, such as being available on the cloud.
Service Granularity
Service In a service operation, granularity refers to determining the best scope of business functionality. To ease error detection, recovery, and general design, each service operation should preferably complete a single transaction (this means that the Service operation is granular). Furthermore, each service operation corresponds to a single business function, even though if a single operation can provide various functions without increasing design complexity or message sizes, this can genetically decrease implementation and usage costs (here, each service operation is generalized and interoperable for multiple functions, making it granular).
Application Design For Occasionally Connected System
Applications may be configured to use a local persistent store/cache simply for the sake of offline capability and later sync as and when connectivity is restored for the limited proportion of functionality that requires “occasional disconnected/offline” actions. As connectivity grows more common, such offline capabilities will become less necessary.
