|
|
Overview :-
IbleSoft employs a flexible set of methodologies in application development, maintenance and integration, based on client’s needs and the organizational requirements. In determining a particular methodology for a given project, IbleSoft takes the following issues into consideration:-
- Into what stage of development is the project currently is in.
- To what level of detail are the requirements initially specified.
- To what extent the requirements are likely to change during the execution of the project.
- What’s the level of interaction between the client team and IbleSoft team.
- The time allocated for the project before its delivery.
Some of the most common methodologies IbleSoft employs include:
Software engineering is the practice of using selected process techniques to improve the quality of a software development effort. This is based on the assumption, subject to endless debate and supported by patient experience, that a methodical approach to software development results in fewer defects and, therefore, ultimately provides shorter delivery times and better value. The documented collection of policies, processes and procedures used by a development team or organization to practice software engineering is called its software development methodology (SDM) or system development life cycle (SDLC).
We support activities throughout the development effort such as:
• Configuration management (version identification, baseline management and change control)
• Requirements management and tracability
• Quality management (quality assurance, quality reviews, defect tracking)
• System engineering reviews (requirements review, prelim. and critical design reviews, etc.)
• Support environment (development tools, libraries, files management, data management)
Top^
Spiral Methodology:-
While the waterfall methodology offers an orderly structure for software development, demands for reduced time-to-market make its series steps inappropriate. The next evolutionary step from the waterfall is where the various steps are staged for multiple deliveries or handoffs. The ultimate evolution from the water fall is the spiral, taking advantage of the fact that development projects work best when they are both incremental and iterative, where the team is able to start small and benefit from enlightened trial and error along the way.
The spiral methodology reflects the relationship of tasks with rapid prototyping, increased parallelism, and concurrency in design and build activities. The spiral method should still be planned methodically, with tasks and deliverables identified for each step in the spiral.
Top^
Rapid application development:-
Rapid Application Development (RAD) is a software development methodology that focuses on building applications in a very short amount of time; traditionally with compromises in usability, features and/or execution speed. The term has recently become a marketing buzzword that generically describes applications that can be designed and developed within 60-90 days, but it was originally intended to describe a process of development that involves application prototyping and iterative development
Waterfall Methodology:-
All projects can be managed better when segmented into a hierarchy of chunks such as phases, stages, activities, tasks and steps. In system development projects, the simplist rendition of this is called the "waterfall" methodology, as shown in the following figure:
In looking at this graphic, which was for major defense systems developments, please note this presumes that the system requirement have already been defined and scrubbed exhaustively, which is probably the most important step towards project success. Nevertheless, the graphic illustrates a few critical principles of a good methodology:
• Work is done in stages,
• Content reviews are conducted between stages, and
• Reviews represent quality gates and decision points for continuing.
The waterfall provides an orderly sequence of development steps and helps ensure the adequacy of documentation and design reviews to ensure the quality, reliability, and maintainability of the developed software.
Maintenance Methodology :-
For the maintenance of existing products which includes but is not limited to bug fixes and trivial enhancements IbleSoft uses Maintenance methodology. This facilitates express knowledge transfer of existing systems and activities of relevance to maintenance. This also includes the flexibility to include client and transparency to the client into the maintenance models. This encircles phases for scope definition, information gathering, conversion, and enduring maintenance.
Top^
|
