True Expertise - pricipals are proficient in IT products and services delivery

 Skills and capabilities of people - professionals, dedicated full-tiume to capability groups help develop knowledge and assets for clients across all the industries we serve

 Dominance of technologies from a users' point of view

 Manageable size - do not have to support a large overhead

 Price - price-competitive solutions and services that improve performance
We have multiple NAICS codes, reflecting the variety of services we offer.

Technik brings forth a mature full-lifecycle development methodology that is specialized for our government customers to address Government-wide mandates such as Section 508 compliance, Federal Enterprise Architecture (FEA), and various DoD and Civilian Agency Information Security requirements.

Our approach is to leverage an iterative and rapid application development methodology that can be customized to align directly with the customer’s unique requirements and acceptance criteria.


During the tRIP development process, our project team specifies the system objectives, builds and delivers a series of partial and increasingly complete implementations. These iterations, yield working deliverables. The composite of these deliverables comprises the final product. tRIP encompasses six major phases (described below) that cover the entire development project life cycle and guide our project teams from concept through delivery. Each phase maps closely to the various phases of the Rational Unified Process (RUP). The remainder of this section explains each of the six phases, identifying its corresponding RUP phase and deliverables. It is important to note that our methodology is flexible, providing our development teams with the ability to easily adapt to individual customer requirements.

1. Business Engineering
Understanding the needs of the business
During this phase, Technik consultants work closely with the client to produce a “Blueprint” that includes the team’s findings and recommendations custom-tailored to the client’s Business requirements. The Blueprint is developed based on review of the client’s business objectives, technical environment, and existing investments. The Blueprint provides executive-level information needed to plan, prioritize, budget, and execute an organization’s Business initiative.

2. Requirements Translation
Translating business need into the behaviors of an automated system
This phase maps to the RUP’s “Inception” phase. During this phase, a detailed set of documents mapping the client’s objectives to their functional and nonfunctional requirements is produced. Functional requirements are used to express the behavior of the system, specifying both the input conditions and planned output conditions. Non-functional requirements include usability, reliability, scalability, performance, security, and availability.

3. Analysis and Design
Translating requirements into a software architecture
During this phase, which maps to RUP’s “Elaboration” phase, a well-defined set of design documents that address how the system objectives will be met in a rapid application development process is developed. The project team determines best-fit Web technologies that meet functional and nonfunctional requirements, deadlines, and budget constraints.

4. Implementation
Creating software that fits within the architecture and has the required behaviors
During this phase, which maps to RUP’s “Construction” phase, a series of application modules that have been unit tested are integrated with each other to provide an executable. During this phase, concepts become operational software solutions.

5. Staging and Testing
Ensuring that the required behaviors are correct, and that all required behaviors are present
During this phase, which maps to RUP’s “Transition” phase, we confirm that application modules function properly and meet the requirements set forth during the business engineering phase.

6. Project Rollout
Everything needed to roll out the project
During this phase, a fully functioning system and/or application meeting the client’s business objectives, deadlines, and budget is launched. Final deliverables may include user, administrator, and operations manuals; online help; a distribution and installation plan; and an optional training manual.

Iterative Reassessment
Throughout the process, continuous reassessment remains the key to successful application deployment. Associated deliverables may include refinements to any previous deliverables such as project plan and risk factors/mitigation plan or other adaptations in technical and functional areas to proactively address the often rapidly changing customer’s Business environment.

About Us  |  Services   |  Clients   |  Careers   |  Contacts
Copyright © 2005, Technik Inc. All Rights Reserved.
Home  |  Services  |  Contacts