Techout Solutions, founded in 2012 as a US-Bangladesh joint venture, provides enterprise-level IT solutions with a focus on quality assurance and cost-effectiveness through an innovative offsite/offshore development model. The company offers core services including software development, web development, and internet marketing, utilizing technologies such as ASP.NET, Java, and PHP. Their operational model includes an offsite center in Baltimore and an offshore team in Bangladesh, facilitating effective communication and quality assurance throughout the project lifecycle.

1. A Short Introduction
To Our Services and Processes

2. COMPANY
About Us:
 TechOut Solutions – founded in 2012 as a US-Bangladesh joint venture – assists US
based clients with the design, development, and deployment of enterprise level IT
solutions with a keen focus on quality assurance.
 By using our innovative offsite/offshore development model TechOut Solutions is able to
deliver unparalleled value to our customers by reducing the risks traditionally associated
with offshore development.
 Our Mission: To become a trusted partner for our clients by providing them with low cost,
high quality, and faster time-to-market software solutions.
SERVICES
Core Services:
 Our offshore development team works in three core areas: Software Development, Web
Development, and, Internet Marketing.
 Software Development Services: Custom Software Development, .NET Application
Development, Software Development in C/C++, and Mobile Application Development for
Apple and Android.
 Web Development Services: ASP.NET Development, PHP/MySQL (LAMP)
Development, Java Web Application Development, and Mobile Web.
 Internet Marketing Services: Search Engine Optimization, Social Media Marketing, and
Pay Per Click Management.
Technologies:
 ASP.NET, C#.NET, C/C++, VB.NET, JavaScript, Ajax, Ruby on Rails, JQuery.
Objective C, Java - J2SE, JSP-Servlet, J2EE, EJB3, J2ME, PHP, .NET Framework,
XNA, Spring MVC, .Net MVC Struts, iPhone, Android and Windows phone, MS SQL
Server, Oracle, MySQL

3. OPERATIONAL MODEL
Offsite/Offshore Development Model:
TechOut Solutions (TOS) uses an innovative offsite/offshore development model. In this
model, TOS operate an offsite, close proximity center (in Baltimore MD) to our clients – and- a
offshore development center in Bangladesh. The offsite center acts as a mediator between the
client and the offshore development center. In this scenario the offsite team handles ~20-30% of
the total work with the offshore team managing the remainder.
Tasks accomplished by the offsite team include:
 Collecting and analyzing initial information from the client, such as: Business
Requirements, Technical Specifications, and Design Documents.
 Planning and communicating project specifications to the offshore development team
manager.
 Responsible for communicating critical project information with the client throughout the
entire development lifecycle.
 Responsible for setting up timeline for project completion and ensuring on time delivery
of the final product.
 Responsible for quality assurance testing of applications prior to delivery.
Tasks accomplished by the offshore development team include:
 A project manager is selected and he is then responsible for reviewing all mission critical
documents and requirements received from the offsite team
 Assigning specific developers to the project and establishing the set of technologies to
be employed
 Ensuring that the final deliverable meets the expectations, and, matches the
specifications as established by the client
 Maintaining a continuous communication channel with the offsite team
 Providing ongoing technical and operational support to the client
The benefits of using an offsite/offshore development model are:
 Ability to quickly respond to changes in client requirements
 Reduced risk of communications gaps since the client need only communicate with the
local offsite center and not the offshore development team
 Client reduces cost by having work completed offshore in Bangladesh where resources
such and skilled labor are comparatively cheaper.

4. SOFTWARE DEVELOPMENT PROCESS
Our development process strictly adheres to industry established quality guidelines and best
practices. We present a brief description below of a typical project lifecycle, from ideation to
implementation.
Initial discussions and agreement:
The first step starts with TOS receiving high-level requirements from the client regarding the
project. A tentative project timeline and cost schedule is then provided to the prospective client.
If the client finds the timeline and estimated cost favorable it would result in the signing of an
agreement handing the project over to TOS.
Requirements Management:
After the contract is signed and the initial requirements and technical/design documents are
gathered from the client then the final User Requirements are generated, signed-off on by the
client and forms the basis for the project foundation. The requirements are then analyzed in
preparation for further estimates and design activities.
During the requirements phase the Quality Assurance (QA) team members are involved in
testing the requirements for validity, consistency, completeness, etc.
Design:
Requirements analysis is followed by design. The design is usually done in two stages: high
level and detailed level. The High Level design uses the User Requirements to derive the
system architecture, application framework, interfaces, functional decomposition, dependencies,
object design (excluding detailed descriptions), etc. The units, arrived at during the High Level
Design decomposition, are further detailed in our formatted Detailed Design document. Detailed
design includes details of the application framework, usage of architecture, object and class
descriptions, etc.
During this phase the QA team starts the development of test cases which continue on while the
development team is coding (next phase).
Coding:
Detailed Design documents are used for writing code and unit testing modules. TOS follows
industry established coding standards unless the client has its own coding standards and
desires that they be followed. The code is then reviewed by senior developers to ensure its
quality after certain iterations.

5. Software Integration and development testing:
Unit tested code is integrated together periodically to obtain sub-systems and the system. Sub-
system and system testing is performed by our separate testing team. The focus is to verify and
validate the functioning of the sub-systems and system and also to perform the test cases
developed earlier. During testing the test cases are further refined and bugs reported through
our bug tracking tool.
Test phases:
Once development is complete the product is then handed over to the QA team for verification
and validation. Typically the phases consist of Final Integration Testing, System Testing and Pre
Acceptance Testing. The tests are conducted through a mixture of manual tests and using
automated test tools such as QTP, LoadRunner, and Selenium.
Product Support Documentation:
During the testing phase various supporting documents are developed according to the client
requirements. These are typically user manuals, installation and configuration manuals.
Installation, Acceptance and Changeover:
The system is then installed at client site (if required) and the client performs the agreed upon
acceptance testing to accept the system and puts the accepted system in operation.
Maintenance and Support:
With the system up and running, the maintenance and support phase starts. During this, the
system is supported as per the terms of warranty in the contract with the client. In this period
issues are tracked and resolved based on the contact.