Emerging Technology Expertise
We bring expertise in .NET, J2EE, LAMP stack, and Service Oriented Architectures. We also bring an attitude that has made it a religion at Aditi to design before you code, thinking through aspects of scalability, security, robustness, and simplicity.
Technology
Aditi brings strong experience and expertise on diverse platforms such as .NET, J2EE, LAMP stack, and numerous technologies such as Digital Rights Management, CRM, Business Intelligence / Data Warehouse, eCommerce, Knowledge Management, and Infrastructure.
Architecture
Coming up with a robust architecture involves numerous technical and business considerations. Aditi understands them and helps our clients build successful and long lasting architectures. Below are a few architectural and design aspects that we hold in high standards.
Scalability: What are the scalability parameters we need to support - number of users, both named and concurrent, number of transactions, type of transactions, size of data, type of data, rate of growth, type of usage, criticality of failure, etc.? What are the current and projected estimates, and how will the architecture evolve to support them?
Performance: What is the ideal and acceptable performance? What are the tradeoffs we need to make? What are the other tradeoffs we need to make between responsiveness and performance?
Reliability: How do we ensure our system performs reliably? What are the error control and tracking mechanisms we can build, that helps prevent failures and/or provide us with enough information to fix any problems quickly? What are the availability requirements? How should they be divided between hardware and software? What will the platform offer and what needs to be built into the application?
Security: What are the internal and external security measures the system needs to take care of? How will we know when there is a breach? If we have a transactional system, how can we ensure auditability, confidentiality, and accountability for each transaction? How much security is enough given the cost, time, effort, and usability constraints?
Extensibility: How can we make it easy to extend the system in future? What are the design considerations? What internal and external APIs have to be offered? What languages and platforms should they support? What tradeoffs need to be made to provide extensibility while keeping simplicity and time-to-market in mind?
Integration: What 3rd party systems do we need to integrate with? What are the architectural and design considerations for enabling such integration? What interfaces need to be exposed to enable seamless integration for data and workflow?
Portability: What platforms, environments or languages do we need to support today, in the near future, and in the long term? How flexible is our architecture and design to migrate to a new platform? Should business need mandate such move?
Installation: What are the platform variations we need to accommodate? What tracking mechanisms can we build so that we can trace problems quickly?
Configuration: What are the configuration options to be made available?
Upgrade: How and when the upgrades will be done? How will we ensure system integrity across upgrades? What is the expected time for upgrades and how will we ensure that the system will perform the upgrades within that time period?
Release Management: What are the various system deliverables for each release? What elements can we design-in, that accelerate release management schedule for successive releases?
3rd Party Software: What 3rd party software do we depend on? How do we co-ordinate our release cycles with theirs? How do we ensure any problems in their software do not affect the stability of our system?
OEM Licensing: If our software is licensed to OEMs for incorporation into their systems, how do we ensure they are easy to embed into their systems? How do we co-ordinate our release cycles with theirs? How can we handle problems gracefully within our system, when operating within our licensee environments?
|
