 |
Storyboard or Waterfall Model |
| |
The
exemplary Storyboard or Waterfall model follows a
systematic, sequential approach to software
development beginning with the Customer's software
requirements and progressing through analysis,
design, coding, testing and post development
warranty. It is considered as an ideal choice
after the user's software requirements are clearly
stated at the inception of the project.
|
|
Prototyping Model |
| |
This methodology defines a mechanism to handle
concept building and / or prototyping projects and
is used by Intelebiz in complex projects to
understand requirements in a better way, to reduce
design risks and to share the user interface with
the Customer. Concept building projects are
typically of an R&D type, where the goal is to
arrive at an optimal solution based on a short
description of requirements by the Customer.
'Throwaway' or 'Evolutionary' prototyping (Spiral
Model) are used depending on whether the model
would be discarded after use or would be adapted
after use until it eventually evolves into the
product.
|
|
Object
Oriented Model |
| |
Each Object Oriented Development Project that is
taken at Intelebiz may go through all or some of
the phases of the Software Development Life Cycle
(SDLC). This methodology is used to define the
activities and work products for each phase in the
project as work packets. The phases of execution,
the associated work products, verification and
validation criteria for each of the relevant
phases will be at par with this methodology.
|
|
Incremental Model |
| |
The Incremental model of development is an
evolutionary model that combines the elements of
the linear sequential model (Waterfall model) and
the iterative philosophy of Prototyping and is
considered ideal for a project that is complex by
nature having large business components and
interfaces with third party business applications,
requiring high availability, and tight security.
It also helps in managing the technology risks by
spreading the risk across successive increments.
This unique methodology has the distinct advantage
of quality assurance and functionality
demonstration at the end of each iteration. This
can be improved upon with successive iterations to
get the desired functionality.
|
|
Project Pricing Methodology |
| |
Fixed Price Model – In this model we need your
requirements to estimate the time and resources
involved to come to a fixed price. A project plan
is made and the payments are linked to important
deliverables. Any changes to the requirements are
seen as ‘Change Request’ and are charged for the
extra time required.
Resource Allocation Model– In this approach you
can provide us with the loose requirements. We
give you estimated time and resources needed. Then
a basic project plan is made. All changes made to
the requirements are included in the project’s
scope – the project plan is accordingly modified.
The resources used are billed on a monthly basis.
Programmer leasing-In this method you can lease
our programmers with the skills you require on a
monthly basis. The programmers will report to you
directly from our office in India via Internet
messenger or Phone and you will be able to do the
Project management yourself.
In the Project lifecycle, we use tools which
facilitate or effectively document the following
activities:
 |
Project Management and Planning (PMP) |
| |
|
|
Configuration Management (CM) & Version Controlling |
| |
|
|
System Architecture Design |
| |
|
|
Automated Testing |
| |
|
|
Bug Management |
|
| |
|
| |
|
back to top
|
