NTIS

» Home arrow Capabilities arrow Methodology arrow Implementation Approach
  • Decrease font size
  • Default font size
  • Increase font size
Implementation Approach Print
Article Index
Implementation Approach
AAA vs. Custom Development
AAA vs. Packaged Solutions
AAA Phases

Our Application Assembly Approach (AAA) is a faster and less expensive way to meet your IT business objectives more closely. Instead of choosing from the “build versus buy” options (building from scratch or buying an “off the shelf” package that is very costly), you can consider a third alternative: assembling your application from pre-constructed, tested, and proven open source components. Once we assemble the components, we “customize around the edges” as needed to deliver a solution that exactly fits your enterprise´s end users´ needs.

Overview

For years, companies followed an application integration approach using commercial components to build business applications. But the wide availability of open source components changes the nature of the assembly approach and makes it even more compelling to pursue. If you use open source components, you are free to choose from thousands of available projects, most of which are accessible through a simple download procedure. You can quickly acquire the components you need without engaging in a formal purchasing process and you can prototype and test without committing large investments in software licenses. Using open source allows you to deploy the solution without up front or ongoing license fees.

Beyond expediency of acquisition and reduced cost, the key reason why open source software components are ideal for the  assembly approach relates to the typical open source component architecture. Open source components are designed, developed, and tested in a highly modular way – the pieces are meant to be put together in assembly fashion. Open source projects anticipate customization, so processes like unit testing are built-in. Many open source components are built on top of other open source components. This is possible because open source components have well-defined interfaces and promote and follow standards. Real-world example code is widely available.

Why Application Assembly Approach?

  • Custom development effort is focused on your unique business differentiators
  • Open source components provide the common functionality
  • The approach is proven, iterative, and fast-paced

When does it make sense to use Application Assembly Approach?

  • You have unique business requirements
  • The system is core to your business and is a business differentiator
  • The system requires integration with your enterprise infrastructure or existing applications
  • End user productivity is important – a system that does not require work-arounds is critical
  • Requirements are likely to continue to change over time
  • Deadlines are tight and you need to pull together a solution quickly