Methodology

Methodology

Dot Com Infoway follows a well-architectured software development methodology. Tailored to meet international standards and client expectations, our Methodology ensures proper risk management, seamless work flow and deadline-oriented development. It has built-in processes to monitor stringent adherence to quality, consistency in performance and accomplishment of project milestones.

Dot Com Infoway’s software development process spans effective lifecycle models like the Waterfall Model and the Agile Model. Our uniquely designed methodology helps us orchestrate the development processes in a highly productive, performance-enhancing way.

Our lifecycle models address the following phases of software projects:

UI Design Methodology

Dot Com Infoway follows a unique UI Design Methodology for application design and development. Our UI Methodology is in line with our key UCD principles that insist focusing on the below things before design of any application: defining of application’s business goals; thorough understanding of user requirements; assessment of competitiveness of the application designed; evaluation of the developed app based on user feedback and finally, creation of an application that offers a rich and complete user experience.

Two prominent models followed by us are Waterfall Model and Agile Model.

Waterfall Model

Dot Com Infoway follows Waterfall life cycle model which emphasizes sequential development and accentuates on a phase-by-phase progress. E.g. Requirement analysis followed by design, followed by code, etc. with established milestones, documents, and then, reviews at the end of each phase. There are no overlaps of phases in this model. Also, the entire scope of the project is addressed at each phase.

We strictly follow the below guidelines in Waterfall development Model:

Agile Model

Agile Modeling (AM) is a practice-based methodology for effective modeling and documentation of software-based systems. Agile Modeling (AM) is a collection of values, principles, and practices for modeling software that can be applied on a software development project in an effective and light-weight manner.

Dot Com Infoway adheres to the following principles of the Agile Model (AM):

Maintenance and Staffing Model:

Dot Com Infoway follows international-standard Maintenance Model and Staffing Model. Our unique and productivity-enhancing Maintenance/Staffing Model enables seamless development process and hampers-down technical havocs or organizational lapses, if any.

Dot Com Infoway follows a structured and well-defined Project Management Methodology.

As a step in structuring the project management & control, we use the simple breakdown framework which ensures the identification of project deliverable, planned tasks, budget and availability of resources. Most importantly, our .NET DevelopmentCloud ComputingSAASRuby-On-Rails and PHP Web Development technologies incorporates, well-structured project controls focusing various measured activities like nifty information flow, task performance analysis, key-out processes, risk mitigation, issue management, project scope alteration, schedule, and cost. Also, in our Java development, Java ME and Objective C application development projects, we continuously monitor the planned schedules, development costs, and resource availability to check the coherence of deliverable with your budget and quality expectations.

Project Planning:

We establish and maintain plans that define project activities.

Project Monitoring and Control:

The purpose of Project Monitoring and Control is to get a complete understanding of the project’s progress so that appropriate, corrective actions can be taken when the project’s performance deviates significantly from pre-defined plans.

Integrated Project Management:

We establish and manage the project and the involvement of the relevant stakeholders according to an integrated and defined process that is tailored from the organization’s set of standard processes.

Our Project Management Methodology helps us

Dot Com Infoway’s Project Management Process covers developing, monitoring and updating the SOW (Statement of Work), WBS (Work Breakdown Structure), Milestones, Schedules and Communication Plans; determining RAM (Responsibility Assignment Matrix); identifying risks involved; managing stakeholders; recommending corrective actions if there are any deviations in schedules or plans.

Our Project Management Process flow:

Dot Com Infoway’s Process Methodology is architectured towards streamlining organizational processes and accelerating productivity. We adhere to a well-defined performance and process metrics that ensure proper completion of projects.

Configuration Management

Configuration Management (CM) Process aims to establish and maintain the integrity of the work products of the project throughout the project’s lifecycle. The process includes identification of the product configuration, base-lining and systematic control of changes to the identified configuration items for the purpose of maintaining product/project integrity and traceability throughout the product/project life cycle. The work products placed under CM include the software products that are delivered to the customer (e.g. the Design document and the code). CM consists of five basic procedures: Configuration Item identification, base-lining, configuration control, configuration status accounting and Configuration Auditing.

Decision Analysis and Resolution

Decision Analysis and Resolution process follows a structured-decision making process to analyze possible decisions that evaluate identified alternatives against established criteria. A structured decision-making process can greatly reduce the subjective nature of the decision, and therefore, lead to a higher probability of selecting the solution that best fits the problem. This process describes how a structured decision-making technique should be applied for both technical and non-technical areas.

Measurement and Analysis

The Measurement and Analysis process area involves in specifying the objectives of measurement and analysis; specifying the measures, analysis techniques, and mechanism for data collection, data storage, reporting, and feedback; implementing the collection, storage, analysis, and reporting of the data; providing objective results that can be used in making informed decisions, and appropriate corrective actions.

Organization Process Definition

Organization Process Definition is developing and maintaining a usable set of software process assets that improve process performance across the projects. Depending upon the implementation of Organization Process Definition, the organization’s software process assets may be collected in many ways. For example, the descriptions of the software life cycles may be an integral part of the organization’s standard software process or parts of the library of software process-related documentation may be stored in the organization’s software process database. The organization’s software process assets are available for use in developing, implementing, and maintaining the projects’ defined software processes.

Dot Com Infoway’s Organization Process Definition helps establish and maintain a usable set of organizational process assets which includes Process for Process Development, Policies, Organizational Standard Processes, Project Specific Processes, Life Cycle Models and Organizational Repository.

Organization Process Focus

Organization Process Focus involves developing and maintaining an understanding of the organizations’ and projects’ software processes to assess, develop, maintain, and improve these processes. This process provides long-term commitments and resources to coordinate the development and maintenance of the software processes across current and future software projects via a group such as a software engineering process group. This group is responsible for the organization’s software process activities. It is specifically responsible for the development and maintenance of the organization’s standard software process and related process assets (as described in the Organization Process Definition process area), and it coordinates the process activities with the software projects.

The process aims to plan and implement organizational process improvement based on understanding of current strength and weaknesses of the organization’s process and process assets.

Organizational Training

Organizational Training includes training to support the organizations strategic business objectives and to meet the tactical training needs that are common across projects and support groups. Effective training requires assessment of needs, planning, instructional design, and appropriate training media (e.g., workbooks, computer software), as well as a repository of training process data. As an organizational process, the main components of training include a managed training-development program, documented plans, personnel with appropriate mastery of specific disciplines and other areas of knowledge, and mechanisms for measuring the effectiveness of the training program.

The training activities will be performed by the Training Group, Project Manager and the SPG. The Training Group will consist of the Manager – Training & Development (HR), Training Coordinator (HR), and the Trainer.

Process and Product Quality Assurance

This Process is intended to determine systematically and independently whether quality activities and related results comply with planned arrangements or whether these arrangements are suitable to achieve these objectives. This process also concentrates mainly on assessment and involves Internal Quality Audits on all Projects, Support functions, Senior Management, etc., for process compliance against the established Quality Management System.

Product Integration Process

The Product Integration process covers all types of projects and includes identifying product components to be integrated, understanding internal and external interfaces of all product components, identifying best integration sequence, ensuring interface compatibility, assembling the product components and delivering the product as a package. The process achieves complete product integration through progressive assembly of product components, in one stage or in incremental stages, according to defined integration sequences and procedures.

Project Management

The Project Management Process covers the Project Planning, Project Monitoring & Control, and Integrated Project Management processes. Project Planning establishes and maintains plans that define project activities. Project Monitoring and Control provides an understanding of the project’s progress so that appropriate corrective actions can be taken when the project’s performance deviates significantly from the plan. Integrated Project Management helps monitor and manage project according to an integrated and defined process that is tailored from the organization’s set of standard processes.

Requirements Management

Requirements Management involves establishing and maintaining an agreement with the customer on the requirements for a project; managing changes to requirements; ensuring consistency between the requirements; the project plans and work products, and maintaining bi-directional traceability for requirements and work products. Requirements Development Process involves transforming the stakeholders’ requirement-driven view of desired services into a technical specification for the products that deliver those services.

Risk Management

Risk Management process describes the practices, procedures, and guidelines that, when implemented, would assist the organization to develop and execute a Software Risk Management Plan. The objective of this plan is to identify risks that occur in an organization as early as possible and describe ways on revising the development strategy to mitigate those risks.

Supplier Agreement Management

This Process focuses on managing the acquisition of products from suppliers by raising the indent, evaluating the suppliers/vendors; purchase orders, receiving the purchased goods and inspecting it, and maintaining purchased goods while they are available in the stock.

Technical Solutions

The Technical Solution process area is applicable at any level of product architecture and to every product, product component, and product-related lifecycle process. Throughout the process areas, where we use the terms product and product component, their intended meanings also encompass services and their components.

Verification and Validation

Verification is to ensure that selected work products meet their specified requirements. The specified requirements are not only found in requirements specification documents but also in functional specifications, architecture and design models, and test cases and so on. Verification is generally an incremental process, starting with product-component verification and usually concluding with verification of fully assembled products.

Validation is to demonstrate that a product or product component fulfills its intended use when placed in its intended environment. Validation may be performed in the operational environment or simulated operational environment. Coordination with the customer on the validation requirements is one of the most essential elements of this process area.

In general, verification and validation activities would be performed continuously during the development of a software component of system.

he UI Design methodology followed at Dot Com Infoway is based on the following UCD principles:

Define business goals:

Define target users and application objectives. Set quantifiable business goals.

Understand users:

Gain thorough understanding of the users and the users’ environment to ensure that the solution meets user’s needs.

Assess competitiveness:

Identify the main competitors and study their solutions.

UI Development Methodology

Design for the complete user experience:

Design everything a user perceives about the application to provide an engaging experience to the user.

Evaluate designs:

Gather user feedback early using prototypes and use this feedback to drive the design and development of the application.