TechNarts methodology is a well-defined method that follows project based change and has proven its success. Starting with the acknowledgement of customers, it continues to define all tasks and processes algorithmically by presenting a strictly mathematical approach. Using this methodology, systems are addressed instead of projects and solutions are generated successfully.


All projects begin by gaining a comprehensive understanding of the customers. While clients may sometimes be an institution, firm or corporation, they may also be an individual person or just one section belonging to a legal entity. In this process business infrastructure is identified by defining all the tasks and processes related to the customer. This step is the most time consuming and most important step for projects. Thus, the needs of customers are thoroughly determined.

Definition & Description

After determining the long-term requirements of the customer, the long, medium and short-term goals are defined by taking the whole system into consideration. All targets are divided into stages and the general plan is prepared.


Project analysis is done in accordance with the general plan. All transactions related to the Project are examined in detail and documented. Project starts with the customer approval of all submitted analysis documents. The process of analysis consists of the following steps:


  • Project Definition
  • Project Configuration
  • Presentation and Approval of the Project
  • Project Initiation


Reports of the Resources, budget and time schedule are prepared and submitted for approval of the customer. The process of planning consists of the following steps:

  • Scope Definition
  • Event Identification
  • Resource Planning
  • Process Duration Estimates
  • Cost Estimate
  • Cost Budgeting
  • Project Logic Diagram
  • Quality Planning
  • Risk Identification
  • Risk Quantization
  • Risk Response Development
  • Organizational Planning
  • Supply Planning
  • Personnel Procurement
  • Communications Planning


The level of complexity of the application is determined in terms of integration, security, performance, databases, platforms, specifications, scalability, modularity and maintenance. The project is designed in accordance with these guidelines and a project design document is prepared. After everything related to the project is clarified, an expert team is selected according to the project’s needs. This team may include in house or outsource members; it may also include freelance team members. The only criteria while creating the team is the project basis expertise. The end of the design process is established once the whole team, including the customer(s) has had the opportunity to comment upon and potentially adapt the design ensuring full alignment of the team throughout the project.


All processes before the development stage ensure this stage to be more clear, constant, consistent and easier to be completed. Considerations during the development stage are:

Being sure that detailed designs are compatible with the high-level design. By organizing the system logically, distribution of the resources and reusable areas are simplified.

Good coding practices and guideline applications are used. Design and code reviews are performed at appropriate times to determine complex areas.

Development of good communication within a team structure is created. Project communication plan is put into practice.

Early allocation of responsibilities such as database installation and conversion and all other areas are determined.

Promotion points and guidance teams are created. Control points for new team members are created and assessments are completed.

Design objectives relating to security, performance, portability, scalability, modularity, maintenance and reuse issues are proposed and applied.


Testing is the most important part of the implementation phase. It provides the last controls that ensure the quality of the system to be delivered. Test scenarios should check not only the expected functionality of the site but also all possible functionality and behavior. It determines that the system is ready for the production stage by ensuring thorough checking of all application steps and processes.


After the implementation phase, the system is implemented in accordance with operational needs. It also ensures provision of maintenance at regular intervals and future analysis of needs, for the use in the process of “Renewal and Improvement”.

Renewal and Improvement

Within the project life cycle, making improvements in the system becomes mandatory for reasons such as expansion of the customer’s needs and advancing technology. In this case, the documentation of the steps of recognition and identification must be updated and targets should be re-formed. Thus, each component of the system should be renewed and improved parallel to the renewal and improvement of the system overall.