Methodology
|
 Leadership
Srest Information Technology (SRest) is a leading provider of end-to-end
web-based solutions to enterprises worldwide.
SRest technology to increase the speed at which organizations innovate.
|
|
| USA
: 732.325.3748 |
UK
: 758.360.0739 |
|
| (INDIA)
MUMBAI : 959.483.7268 |
(INDIA)
MANDSAUR : 942.478.0371 |
|
|
Our Methodology |
Software engineering is the practice of using selected 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).
Srest has been using a standardized and refined software development methodology
which is solid and clearly defined, yet flexible to meet the individual needs of
diverse custom solutions. This methodology represents a powerful combination of
the best industry-proven practices and leading standards, and is focused on
streamlining the development process to increase return on investment and compress
time-to-market. SRest’s methodology is applied successfully to medium- to large-scale
custom
application development projects and involves the following phases:
|
|
|
PHASE A and PHASE B
|
PHASE A - PROJECT REQUIREMENTS CAPTURE:
Our Business Consultants conducts Joint Application Development (JAD)
sessions with the client. At this phase we work closely with you and
discuss all the details about your current practices, business objectives
and marketing goals, ensuring we thoroughly understand all project
requirements. Through gaining insight into your needs and strategic
challenges we define the project scope along with the technologies and
the application development approach thus setting the foundation of a
successful implementation in the most efficient manner possible while
effectively managing risks and maintaining high quality of the final
software product.
PHASE B - TECHNICAL ARCHITECTURE
Our Technical Architects advise the client on options available to him with
respect to architectural approaches and technology solutions for project implementation.
|
|
|
PHASE C and PHASE D
|
PHASE C - PROPOSAL & CONFIRNMATION:
Based on the architecture and technology chosen, the development team of
Programmers, graphic designers and project managers draft a development
plan for the project. A detailed Proposal document that incorporates the
key elements with cost and time estimates.
PHASE D - INCREMENTAL DEVELOPMENT:
This is the stage where the project is actually off the ground. Srest builds
the application in progressive phases or increments. Incremental delivery
permits experimentation of complex
solutions during the course of development. This approach facilitates
modifications through hands-on exposure to the delivered increment.
Throughout the application development process intermediate deliverable are
provided to the customers according to the scheduled milestones allowing them
to track the implementation progress. The milestone deliverable for each sub-system,
sub-element or module can be reviewed by the customers for verification against their
business requirements, ensuring the end product will meet the original objectives.
The intermediate deliverable review
can also help to discover a problem or flaw at
early stage of the development before the application
evolves into a complete product,
thus lowering the costs of corrections.
In order to early discover some trivial logic errors,
software engineers perform unit tests right after the
completion of code programming.
Individual classes are tested to ensure reliability and functionality
within a unit level. Furthermore, when a few programs within a module
pass the unit tests, they are combined together for modular function tests.
After a few modules
undergo the module function tests, they are integrated
and tested together to ensure sufficient execution and compliance with the
requirements after integration. Eventually, the whole system is used for
system testing and it passes functional testing, performance testing, and
stress testing to ensure all requirements are met. The outcome is an Alpha
Release of the software product which can be provided to the customer
for the review.
|
|
|
PHASE E and PHASE F
|
PHASE E -QA TESTING & BETA RELEASE:
QA Testing & Beta Release includes extensive QA testing; the code will be
reviewed and validated for consistency and functionality. Responsibilities of
the QA team are to detect any deviation from the quality procedures and ensure
all requirements and specifications are properly considered and met. Any errors
and bugs are detected and fixed; all required changes will be made to ensure
compliance with the requirements. After the system passes successfully rigorous
tests and is approved by the QA department, Beta Release is provided
to the customer.
Beta Release is deployed in the final environment at the customer's side for additional
test and review within a certain period as specified in the Project Plan at earlier phase.
During this stage we gather feedback from the customer
and conduct final testing and debugging based on the appropriate customer's feedbacks.
The approved and accepted Beta Release evolves into the Final Release and the project
implementation phase proceeds with the Final Release Delivery stage.
PHASE F -INSTALLATION & TRAINING:
Once the final application is installed, configured, and launched at the deployment site,
comprehensive training is extended to the client's IT/ MIS personnel. The end-users are
trained to use the application effectively. We follow-up activity for close monitoring of
the system performance to provide immediate response to the issues and ensure complete
customer's satisfaction.
Once the completed software solution is deployed, Srest provides
ongoing support during a pre-defined period if time after the final delivery.
During this period, any programming error or bug detected is
corrected with no additional cost.
Srest employs its methodology to ensure all projects meet the following objectives:
1. Cost is minimized
2. Quality is maximized
3. Communication is concise
4. Schedules are met
|
|
|
|
