Sections
---------------------------------------------------
FAQ
News
Awards
Developers
Translators
Community
Testimonials
License
Release notes
Project Docs
Support Hindawi
Learning Resources
---------------------------------------------------
Hindawi Online
Videos
Papers
Manuals
Books
Students
Teachers
Schools
Authors
Specs
Fellowship
Related Projects
---------------------------------------------------
IndSoftEx
IndSilicon
IndRobota
IndSuperComp
TransEg
Martian Desire
Talk Ease
Telemedicine
Legal DSS-ES
|
IndSoftEx
----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
India Software Exchange shall be a community
based software-services model, which can possibly generate numerous new ICT
jobs and prevent India losing jobs to more low cost locations, while ensuring
that the overall gains of our software professionals is improved by minimizing
marginal-costs in delivering software services.
Let us suppose we are in a 2012AD (four years
from now), the first mile-stone year in achieving the target of making India an ICT superpower. By then
we are sure ICT shall stand for Indian Cottage Technology, for indeed, that
is what we envision - to make Information and Communication Technology a
literal 'cottage' industry in India which shall cater solutions
globally, and provide at least some major relief to the unemployment
situation. That would be akin to the electronics industry in China today.
A person, say, in the USA needs a piece of software for
his new startup. He logs onto the IndSoftEx website, posts his requirement in
the standard format available there, and pays the prescribed fees online (say
an advance, with balance to be cleared as and when the final settlements are
done). This requirements' document is in a restricted-grammar format and can
be translated into an Indic language with existing technology. The Indic
requirements' document is then provided to an Indic developer as per turn,
who may accept or refuse the task; in the latter case, it is handed over to
the next developer in queue. The Indic developer then proceeds with the
standard software engineering steps of analysis, coding, testing, etc. He
certainly codes in Indic programming languages and also does the analysis and
testing in Indic. Where input from the end user is needed in the development
process, the developer provides the English source code, which as the authors
have pointed out is readily generated by the Hindawi compiler system (which
by then shall certainly have improved a lot). As about the English text
messages contained in the program; they are converted back into English by
the translation process at the Software Exchange. (Machine translation is the
piece of technology the authors are focusing my development efforts on now,
but for restricted-grammar this has been achieved.) The end product is
finally provided to the person in the USA, with complete source,
variable names, documentation etc. in English. Further work may be handled by
either a traditional (English) or an Indic developer.
As an aside, we have only skimmed through the
description of this scenario. We have already worked on aspects such as what
changes to the currently practiced software metrics may be needed. Besides, a
few new positions may need to be created, and this person-centric scenario
should be viewed as a team-centric one.
|
