Our Software Development Process

Our Motto - “Quality with satisfaction

Our software development module Tamagna Model referred here as T-Model approach concerned with 4 phases of software development:

  • T-PHASE 1

    Requirements collection can be ranked 1 among all the phases in any kind of software development environments. High clarity requirements will always result in good end product. This phase can be sub divided into small phases

    • T-R1
      • Understanding the process & procedures of a client
      • Collect initial requirements based on understanding company overview
      • The whole system view is based on the overview provided by the client.
      • The client may provide his own thoughts/idea, required enhancement required in customized application or a new software application
      • Keeping client as the master & his requirements at most priority we document all the requirements
    • T-R2
      • Once the overview / specifications of the system are gathered/collected, the segregation of major & minor requirements will be made accordingly
      • The requirements are classified based on complexity, immediate need basis, zero clarity requirement categories etc.
      • A detailed CRS (client requirement specification) would be documented and shared with client for feedback.
    • T-R3
      • We consider the feedback received from the client & accordingly make changes to the existing document
      • Tamagna can add up additional features to requirements as a quality process (providing surprise to client).
      • Every client will not be a technical person, but we make sure we explain the client very clearly what we have documented throughout the understanding of process & provide the same in the documentations too
      • Basically, this step adds up the details regarding the requirement or provides the better suggestions to the client based on his requirement.
    • T-R4
      • This step is basically an internal discussion with in our team in Tamagna
      • Meetings, discussions, suggestions, enhancements, improvements etc are done with in different teams like- BD, Analysis, Testing, Design
      • To arrive at a decent clear solution we make sure every individual in the team will be made to express their thoughts towards the better approach  T-R5
    • T-R5
      • During this phase we make sure that the client is 99% satisfied with the requirements & the analysis document we have shared
      • The complete detailed approach is structured and will be shared with client for approval
      • The steps listed above can be repeated to obtain- T-R5
    • Specification Area
      • The steps T-R1 and T-R2 is basically considered as requirement specification area; why we have used this nomenclature - In these two steps whole team working with all the above steps specified will get an complete idea of the application & clear requirements, logic to build the application beyond expectations, what additional aspects needs to be added, what actually the client expectations would be, can all these expectations be met 100% - concluding it through a feasibility study.
    • Planning
        This phase is based considering T-R3, T-R4, and T-R5.
      • Total man hours required
      • Hardware and software specifications
      • Risk factor- lack of time, resource management
      • The cost oriented planning- cost/hour, cost/resource, man/month etc.
      • Which technology/platform suits in as per client requirement specifications & our analysis, database to be used etc.
      • goals to be met
      • Management risks and approaches.
      • Planned or unplanned failures occurred, time management, resource replacement, schedule management, client / vendor benefits etc.
    • Verification and Validations:
      • Basically done at T-R4; concerned with meetings, discussions, suggestions etc.
      • Verifications and validations of the requirements are met.
      • Discussions are carried out & the same will be verified with the Tamagna team & client
    • T-Design
      • The most important step need to be considered in all phases (T-R2, T-R3, T-R4, T-R5)
      • The design is associated with the requirements
      • A generalized template need to be followed based on the design requirements - upon addition or deletion of any requirements it shouldn’t affect on previous design structure
      • Design process is carried out considering the below mentioned aspects
      • Data flow/data collected/predictions based on the requirement.
      • Design based on UI, based on requirements
      • Database designs, corresponding to requirements gathered.
      • The fields associated with the application, different forms or pages required, mandatory, non-mandatory fields, length of each fields, different data types fit in to those fields etc.
      • The relational diagrams; the relations between different modules or sub systems identified, interdependency between modules
      • Hence, the T-Design is a complete conceptual approach of the system you like to build, the different relations; data flow etc can also be identified.
    • T-System Architecture
      • Can be started based on T-R5 and T-Design.
      • We would consider the whole system Architecture design that needs to be developed- a complete blue print.
      • Finalizing the different classes, interfaces, framework, libraries need to be used
      • A detailed class diagram is designed indicating different classes’ w.r.t each module.
      • All methods, fields, other relevant details required for the development is finalized along with the folder structure, UI design, database etc.
      • We consider this step to be very important & crucial since the whole development process is based on this step
  • T-PHASE 2
    • Based on the T-System Architecture we need to start the development process accordingly
    • Predefined rules to be followed for the development process
    • Coding standards- documentations, comments etc need to be followed as per standards & goals set
    • Naming conventions need to be followed as per discussed during architecture design phase
    • Simultaneously white box (developer side) testing need to be carried out for accuracy in coding and high performance.
  • T-PHASE 3
    T-System Testing
    • The testing process can be carried out corresponding from (T-R2, T-R3, T-R4, T-R5) steps, by finalizing different test cases, testing documents, Framework for automated costing, the best approach required for testing the application, different types of flaws occurrences etc. bug reporting
    • Based on the T-Development, CRS- testing can be carried out.
    • The different types of testing should be finalised based on applications & client requirements
    • Client side testing/User acceptance testing will be considered during the release on beta version – Any bug found will be fixed & final version will be deployed
  • T-PHASE 4
    T-Support, Maintenance, Service
    • Upon finalizing T-PHASE2 and T-PHASE3, the detailed help document, training document, Maintenance records are created & shared with client as per their requirement
    • 24/7 Troubleshooting, support is provided based on client needs

T-Teams working in each phase are as follows:

  • T-PHASE 1
    • Business Development Team
    • Analysis Team
    • Testing Team
    • Database designers
    • UI Designers
    • Project Manager, Architect
  • T-PHASE 2
    • Database Developer
    • Software Developer
    • Test Engineer
  • T-PHASE 3
    • Test Engineer
    • Software Developer
  • T-PHASE 4
    • Service Engineer
    • Technical Support
    • Business Development Teamt
    • Marketing Team
    • Trainers

T-Documents associated with each PHASE

  • Complete documentation in standard format
  • Version control to be used for every upgraded document or changed document
  • Documents need to be reviewed by concerned higher authority signed and even notify corresponding to any changes.
  • Generalized template need to be designed for collecting client requirements which will help in improving quality of the interaction with client.
  • All the documents, backups, conversations need to be maintained in a repository in any format for future references.
  • Client interaction, meetings- quality of the interaction can be improved by adopting some effective ways of making notes.
    • A voice recording system is setup on each meeting with client for further reference and understanding.
    • A video recording, call recording, images associated with any client requirements are collected or recorded on meetings (which in turn helps in avoiding miscommunications and self improvement)
    • A detailed note either written using pen & paper/word document
    • All the above recordings can be added in to client repository folder for future references.

Copyrights © Tamagna Technologies Pvt Ltd   All Rights Reserved.