Home > IT Solutions > Web Application Solutions > Quick Prototype
Techindia offers quick prototype for projects with minimum turnaround time.
The Prototype phase consists of the following tasks:
a. Project Architecture design and Compliance phase:
The aim is to hold the working module as soon as practical, with the obvious proviso that needs to have some significant development of the project architecture in order to ensure a feasible prototype for review.
In accordance with the project requirement a architecture outline is drawn based on the project fulfillment,
to check whether it can..
Supports the stated strategy and future directions
Adheres to the stated standards and functionality
Adheres to the stated principles; for example:
Open wherever possible and appropriate
Strategies for collaboration, resource sharing, and other synergies across multiple architecture teams.
An Architecture Compliance reviews, is then performed with the senior management group in relating to various aspects of the project architecture.
The organization of the questions includes the basic disciplines of system engineering, information management, security, and systems management.
Following checklists are reviewed in detail based on inputs provided by the specific project group.
Hardware and Operating System Checklist
Software Services and Middleware Checklist
Applications Checklists
Information Management Checklists
Security Checklist
System Management Checklist
System Engineering/Overall Architecture Checklists
System Engineering/Methods & Tools Checklist
b. GUI Development phase
During this phase the host panels are processed through Techindia's Standard Conversion Environment (SCE).
The corresponding GUI screen for each host panel is developed, using the Knowledgebase to enforce the established GUI standards.
Each member of the development team is assigned a subset of panels to be developed, in accordance with the multi-developer
environments and processes that have been established. A consolidated runtime is created on a periodic basis to allow QA to occur in parallel.
c. Knowledgebase Configuration
The Knowledgebase Configuration involves the setup of the Development Kit's rules, based on the GUI guidelines and standards adapted, to
enable a rapid conversion of the host panels to their corresponding GUI screens.
d. Prototype Development
This consists of the development of one Host Application process or transaction (typically less than 20 screens) that can be deployed to a
subset of end-users/executives for feedback and signoff on GUI standards. During development, the Knowledge base is configured, and the
foundations for "full-scale" development are set in place. The prototype is typically also used to gain "buy-in" from the end-users/executives
prior to beginning a full-scale development effort
