InmarSoft.Com :: Software development company
Home Site Map
About Us Services Solutions Development Portfolio Contacts
DEVELOPMENT Project-Based Methodology
Project Methodology
Team Methodology
This methodology is based on iterative approach to software development process and is broken into phases each concluding in a certain point in time with certain work project products and software product deliverables. Each phase consists of a number of iterations which are planned, controlled and analyzed.
PHASE 1:   Analysis and Requirements
Knowledge of subject domain and technological processes is necessary for development of program systems that meet all customers' requirements.

Specialists at InmarSoft closely cooperate with a customer to gather the most precise software requirements, describe the old architecture, scope the project and identify critical issues.

The following documentation is created on this phase:

Software Requirement Specification

The purpose of this document is to present the requirements: a complete listing of what the customer expects the system to do, as well as any required constraints by which the system must abide. The SRS should include both functional and nonfunctional requirements.

Project Proposal

Project proposal is a result of project requirements analyze. This document contains the work content estimation, costs and time sequencing of the project. On the basis of project proposal will be taken a decision about project start, number of development team members and etc.

Project Plan

Project plan defines the dates, milestones, tasks and deliverables that will drive the project. It defines who is responsible for doing what, and by when. The main objective of the project plan is documenting the assumptions and decisions, help in communication between all the concerned parties and documenting the aims, costs and time sequencing of the project.

Software Architecture Document

The SAD provides a comprehensive architectural overview of the system, using a number of different views to depict different aspects of the solution. It is intended to capture and convey the significant architectural decisions which have been made regarding the system.

PHASE 2:   Design Document creation
Correct architecture and system concept design is critical for project success. After finishing the analysis, system design phase begins. System component-software architecture and development environment are defined in this stage. On system design phase we consider all opportunities to reduce duration of the following project implementation and maximize its effectiveness.

The following documentation is created during this phase:

Design Document

Design document is a description of a software product that is written in order to give a software development team an overall guidance of the architecture of the software project. It is a comprehensive software design model consisting of four distinct but interrelated activities: data design, architectural design, interface design, and procedural design.
PHASE 3:   Implementation
The standard implementation process consists of prototyping, coding, modular and system testing. On the implementation phase we use an iterative approach that enables us to ensure the required system reliability.

The following documentation is created during this phase:

Test Plan

Test plan is a document describing the scope, approach, resources, and schedule of intended testing activities. It identifies test items, the features to be tested, the testing tasks, who will do each task, and any risks requiring contingency planning.

System Test Cases

Test cases are tests that exercise various important functions of the software. Such test cases utilize known inputs, and enable comparison of the actual output received with the expected correct output. Test cases are intended to expose bugs, limitations and programming errors of all sorts before a program is deployed.
PHASE 4:   System testing
Since such software system characteristics like reliability, scalability and efficiency are increasingly more required by customers in the last time the system testing phase takes on critical significance for the project success. The produced software passes several tests according to the international quality management system before release. The following operations have to be done in this stage:
Test cases running
Bug Fixing
Change request review
Update test cases
Update Design Document

The following documentation is created on this phase:
Test Cases
Test Log sheet
Approved Change Requests
Updated Design Document

PHASE 5:   Acceptance/ Deployment
Once system has been developed, its implementation in the onsite IT environment and integration with the old business applications begins. We provide our customers with all necessary documentation, technical support and system maintenance.

The following documentation is created on this phase:
Sign Off on Acceptance
List of QA bugs
User Manual
Installation/Release Notes

Copyright © InmarSoft 2007-2019 About Us   ::   Services   ::   Solutions   ::   Development   ::   Portfolio   ::   Contacts