| |
|
| Development Approach |
|
| iLink has implemented a project management structure to mitigate differences and to address Risk Factors and take advantage of the cost / resource advantages. This methodology applies to nearly all of our client engagements, including the subject engagement with BL, although some phases of the methodology will not be as important to the project (for example UI design) as others. |
|
| The diagram below illustrates our model to manage various phases of the project from the needs analysis phase to deployment and training and ongoing support and maintenance. |
|
 |
|
| Once the project is initiated, we further analyze requirements, design the necessary support systems, and prepare the development environment and testing environment. The development environment includes: |
|
- Setting up the production environment, which matches the hardware and software requirements for the projects.
- Defining the testing environment in accordance with the test plan. This stage includes setting up a testing environment specific to the project. We will configure if necessary, the different versions/types of browsers across different platforms.
- Setting up the version control repository.
- Setting up the bug and incident trackers with client access provisions.
|
|
| This first step is followed by design and architecture creation, customizing design standards, design reviews and approval, development, testing, QA and acceptance. The team coordinates with each other and collaboratively moves the project through each of these steps. |
|
| Our generic process constructs have specific documents that cover client responsibilities, client communication & reporting, and change management. |
|
| Requirement Analysis |
| |
| Each project starts with needs analysis to develop the formal Statement of Work. The functional expert meets with the client and gathers information, and if necessary revises the Proposal and Cost Estimate. During this phase we will refine our understanding of the project requirements, study existing legacy applications, and determine a reliable architecture by making key decisions on software architecture and design layouts. In this step, we will determine UI navigation, which is crucial for any application. Each choice we make in the architecture will influence the performance, scalability and the future scope for development. |
|
 |
| Have a business inquiry? Fill in the form below and we will get back to you shortly |
|
 |
| iLink's Product Engineering Differentiators |
|
| iLink specializes in Software Product Engineering with it's vast experience working with ISVs not only in the enterprise world but also in the consumer world. |
| Read more >> |
|
| |
| Why iLink for your Product Lifecycle Management? |
|
| iLink's Product Lifecycle Management services have consistently helped software product companies get maximum ROI out of their mature product lines while they focus on the R&D of newer products. |
| Read more >> |
|
| |
|
|
| The Requirements Analysis schematic shown below explains our methodology during this phase. |
|
 |
|
| Design Phase |
|
| Along with UI design, database and class design is also done (see figure below). In this phase, high level and low-level design documents are created, reviewed and approved. In certain projects, the low level, high-level design document would be combined into one design document. The design document would describe architecture, classes, class interactions, and data and control flow and database design elements. |
|
| Regarding Design Templates, iLink will present three designs based on Client feedback (each design showing three page views). There will be three rounds of comps to refine and finalize design. |
|
| Development Phase |
|
| After UI and system design, this phase begins with the setting up of the development environment. The project is divided into various coding tasks by functionality or the language/technology of the task and is allocated to individual developers. Developers are responsible for unit testing their individual code. Code review takes place periodically during the execution of the project. |
|
 |
| Design Process |
|
 |
| Code Development Process |
|
|
|
| Quality Assurance (QA) Planning / Testing and Delivery |
|
| We employ a rigorous QA methodology. We implement the following QA tasks and activities at appropriate times throughout the duration of the project: |
|
- Design Review
- Code Review
- QA Planning
- Unit Testing
- Integration and System Testing
- Regression Testing
|
|
| Testing will be performed in both manual and automated ways. Automated testing using software to discover broken links and facilitates regression testing. QA is a vital part in the UI development cycle. |
|
 |
| QA Planning |
|
 |
| QA & Delivery |
|
|
|
| Testing and Acceptance Criteria |
|
| All the Test Cases delineated in the Test Plan created by iLink and reviewed by the Client shall validate the final system for acceptance. When all these Test Cases have successfully passed during the Acceptance Testing, the prototype shall be deemed to be accepted by the Client as completed. |
|
| The test plans and test cases would be prepared by iLink and would be wholly based on the finalized Requirements Document (RD) prepared at the start of the project. Test cases would be reviewed by the Client before the start of the system testing by iLink. |
|
| Acceptance testing shall be completed and feedback provided to iLink within one week of iLink making the final deliverable. |
|
| Training and Documentation |
|
| iLink is able to offer a variety of training options to our clients, including on-site, off-site, and webinar-base environments. We provide documentation of every phase of the project cycle including user documentation for every feature developed. It is our intention to help the Client become the expert of their solution as quickly as possible. |
|
|
|
