IMAGE INFOSOFT PVT. LTD.
Company Profile
Below are key features of Image infosoft System Utilities which lead us to strengthen:
High competence
High professionalism of our employees is supported with collected knowledge base on technologies being used, and also unique scheme of management and communication within the company. As a result, we are able not only carry out complete development of new technologies and custom development, but also to render the fast and qualified technical support of any level, to render consultations on resolving difficult problems, to give unique technical knowledge through automated Knowledge Base site.
Consistent product development
We never stop our development for particular product if we believe there are other important features customers expect from us. It is usual practice when development department investigates and writes further technologies for next version of a product even sales and marketing departments yet prepares previous version for release. We always share current product improvements with our customers as soon as they become available, we can release minor updates several times between consequent versions.
Customer care
We understand that technologies in the field we share can be uneasy in use and therefore our company aspires to help customers in resolving their problems. First of all, it means the convenient, clear and intuitive interface in which we try to take the most of modern wizards. If a problem or a question arises, the user can try to find the answer with Knowledge Base by his/her own or contact support service for the quick and qualified consultation. Any user is always capable to receive the latest product update online and be confident that he/she uses leading technologies developed up-to-date.
Complete business cycle
Image Infosoft Utilities involves complete business cycle: development of unique technologies and building convenient appliances, quality assurance, technical support, distribution, publishing and licensing. This sheaf allows us not only to release competitive products at the reduced cost, but also to answer extremely dynamically to ever-changing demands of market.
Now Image Infosoft Utilities are 14+ professionals working as a solid team and is ready for further expansion. Currently our marketing activities include India, ,Canada, USA . Besides developing and marketing own products we are open for and have wide experience in: licensing, mutual development, custom development and releasing software development kits.
Systems Development Life Cycle
Image Infosoft has been following the different Software development models, as per the customer’s system requirements. Following are the SDLC modelscommonly been made use of, most of the times it’s a combination of various models, due to ever changing business needs as well our maturity to cater to customers from the same vertical and domains.
Systems Development Life Cycle Model
The Systems Development Life Cycle model was developed as a structured approach to information system development that guides all the processes involved from an initial feasibility study through to maintenance of the finished application. SDLC models take a variety of approaches to development. Some of these life cycle models include:
The Waterfall Model
A classic SDLC model, with a linear and sequential method that has goals for each development phase. The waterfall model simplifies task scheduling, because there are no iterative or overlapping steps. One drawback of the waterfall model is that it does not allow for much revision.
Rapid Application Development (RAD)
This model is based on the concept that better products can be developed more quickly by using workshops or focus groups to gather system requirements.
Joint application development (JAD): This model involves the client or
end user in the design and development of an application, through a series
of collaborative workshops called JAD sessions.
Prototyping Model
In this model, a prototype (an early approximation of a final system or product) is built, tested, and then reworked as necessary until an acceptable prototype is finally achieved from which the complete system or product can now be developed.
Reuse Model
This model is a combination of RAD and Iterative Prototyping Model.
Ad Hoc Model
This model of development combines the features of all the
development model as this model is based on the expertise of the team on
very complex, expensive, and R7D sort of projects.
Software Development for Fresh Development
Fresh Development
This is a complicated process, as it requires careful planning and execution to meet the goals.
The different phases in the development process include
• The actual writing of code,
• Preparation of requirements and objectives,
• The design of what is to be coded
• Confirmation that what is developed has met objectives.
The different phases involved in Software Development are as follows:
1) Identification of required software
2) Analysis of the software requirements
3) Detailed specification of the software requirements
4) Software design
5) Programming
6) Testing
7) Maintenance
For such a development Image Infosoft follows the Waterfall model with the Iterative
Model. Although Waterfall model is the base of all the software development models.
The Waterfall Model
Although the Waterfall Model is the earliest method of structured system
development, Image Infosoft still follows this model, as it most closely resembles a
"generic" model for software development.
At every stage of the feasibility is carried out, in case there are new
additions from the client. Every stage needs to be iterated.
System Conceptualization
All the aspects pertaining to the business
function / process are determined with relationship of one goal with the
other, these aspects are incorporated into the system.
Systems Analysis
Image Infosoft team is formulated for the gathering of the
system requirements, with the goal of determining how these requirements
shall be accommodated in the system. Extensive communication and
interaction takes place between the client and Image Infosoft Team.
System Design
Once the requirements have been collected and analyzed,
it is necessary to identify in detail how the system shall be constructed to
perform necessary tasks. More specifically, the System Design phase is
focused on the data requirements (what information shall be processed in
the system?), the software construction (how shall the application be
constructed?), and the interface construction (what shall the system look
like? What standards shall be followed?).
Coding
This step involves the creation of the system software.
Requirements and systems specifications from the System Design step are
translated into machinereadable computer code.
Testing
As the software is created and added to the developing system,
testing is performed to ensure that it is working correctly and efficiently.
Testing is generally focused on two areas: internal efficiency and external
Effectiveness
The goal of external effectiveness testing is to verify that the
software is functioning according to system design, and that it is
performing all necessary functions or subfunctions.
The goal of internal testing is to make sure that the computer code is efficient, standardized,and well documented. Testing can be a laborintensive process, due to its
iterative nature.
3.3 The Development Process for OOPS / Component Development
The Reuse Model
The basic premise behind the Reuse Model is that systems should be built
using existing components, as opposed to custom building new
components. The Reuse Model is clearly suited to Object Oriented
computing environments, which have become one of the premiere
technologies in today's system development industry.
Within the Reuse Model, libraries of software modules are maintained that
can be copied for use in any system. These components are of two types:
procedural modules and database modules. When building a new system,
the developer shall "borrow" a copy of a module from the system library
and then plug it into a function or procedure. If the needed module is not
available, the developer shall build it, and store a copy in the system
library for future usage. If the modules are well engineered, the developer
with minimal changes can implement them.
Figure 3. Reuse Model
The Reuse Model consists of the following steps:
• Definition of Requirements: Initial system requirements are collected.
These requirements are usually a subset of complete system requirements.
• Definition of Objects: The objects, which can support the necessary
system components, are identified.
• Collection of Objects: The system libraries are scanned to determine
whether or not the needed objects are available. Copies of the needed
objects are downloaded from the system.
• Creation of Customized Objects: Objects that have been identified as
needed, but that are not available in the library are created.
• Prototype Assembly: A prototype version of the system is created
and/or modified using the necessary objects.
• Prototype Evaluation: The prototype is evaluated to determine if it
adequately addresses customer needs and requirements.
• Requirements Refinement: Requirements are further refined as a more
detailed version of the prototype is created.
• Objects Refinement: Objects are refined to reflect the changes in the
requirements.
The Development Process for Porting and Migration Projects
The Ad hoc Model
In Porting and migration projects the processes are unpredictable due to
the constantly changing or modified work progresses. Schedules, budgets,
functionality, and product quality are generally (inconsistent).
Performance depends on the capabilities of individuals and varies with
their innate skills, knowledge, and motivations. There are few stable
software processes in evidence, and performance can be predicted only by
individual rather than organizational capability. The delicately working
team figures out the changes that have to be made to the existing code
and does the necessary development. Here the task is more like a
Research and Development work, depending upon the complexities of the
work involved.