Since inception, ICONMA has honed
its skills in the art of software development. As in the case of our
methodology, software development follows a comprehensive pattern.
Requirements are analyzed, parameters set and action plans are evolved.
Quality issues are addressed with actual on-the-job testing and user
friendliness is taken into account. Every detail is important for
us & every software is our masterpiece.
Software products are an edge with ICONMA
and we strive to maintain the edge by exceeding our clients' expectations.
ICONMA has achieved consistent
growth and excellence through adherence to high standards of quality
and service to our customers.
Our development process allows us to guarantee |
| |
  |
On-time completion
of the project |
|
Delivery of a high-quality
system meeting your business requirements |
|
Development of a flexible, easy to use
and modify (in case you need some enhancements in future) system. |
| |
|
|
Software
Requirements Analysis and Management
After the initial step of team formation, we do a thorough needs analysis
of customer requirements including determining needs (elicitation),
addressing how those needs need to be addressed (triage) and documenting
the desired external behavior of the systems (specification). Allocated
Requirements Review Managing Systems Requirements Allocated to Software
Policy
Software Project Planning
Planning is a critical phase, which involves creating high-level architecture,
delivery and deployment schedules for software development, information
and capacity architecture, and third-party integration. |
|
Software
Development Plan |
|
Software Estimates
Procedures |
|
Project Schedule |
|
Software Life
Cycle Definition |
|
Software Planning
Data |
|
Software Project
Activities and Commitments |
|
Software Engineering
Facilities and Support Tools Plan |
|
| |
| Software
Project Tracking and Oversight |
|
Revision
of Software Development Plan |
|
Peer Review
Plans |
|
Change Requests
and Problem Reports Procedure |
|
Formal Reviews
of Selected Milestones |
|
Project Tracking
and Recording Procedures |
|
| |
| Software
Quality Assurance |
|
Software
Quality Assurance Plan |
|
Policy for
Implementation of SQA |
|
Deviations
in Software Activities and Software Work Products Procedure |
|
SQA Participation
Procedure |
|
SQA Reports |
|
SQA Reviews
Procedure |
|
| |
| Software
Configuration Management |
|
SCM
Activities Plan |
|
SCM Policy |
|
Changes to
Baselines Procedure |
|
Software Baseline
Library Product Creation and Release Control Procedure |
|
Configuration
Items/Units Status Review Procedure |
|
Standard Software
Configuration Management Reports |
|
Baseline Audits
Procedure |
|
| |
Testing
After the various components are developed, they are integrated and
rigorously tested as a complete solution. Application behavior is
compared with the initial specifications and any deviations are identified
and corrected. |
|
Specification
Testing |
|
Functionality
Testing |
|
Integration
Testing |
|
Stress/Real-world
Testing |
|
| |
Implementation
After the project is completed, it is deployed across an enterprise
by working closely with its internal IT team and training is imparted
to the end-users of the system. |
|
Enterprise-wide
Deployment |
|
End-user Training |
|
System/Helpdesk
Training |
|
Documentation
Handover |
|
| |
Maintenance
Our maintenance phase covers system health maintenance including database,
application and network maintenance. Required application feature
enhancements are planned at this stage, and are developed and executed
as and when appropriate. |
|
System
Health Maintenance |
|
Feature/Application
Enhancements |
|
| |
