We claim to be different, as the way we execute software projects is very unique & efficient. We are fast, responsive, deliver quality solutions & do knowledge management for our customers. |
|
| All our projects are executed via our web based office Web Collaborator. This is the process we follow: |
|
-
Customer provides their problem statement by filling up a project questionnaire created by TelluSys.
-
Our project managers/architects analyze the questionaire to create a document of understanding (DOU) if things are not completely clear, other wise an initial requirement analysis & proposal is sent to customer with solution/time/cost analysis.
-
Once initial approval is obtained, we initiate the project in Web Collaborator & client only access is provided to the customer. The project is now continued in Web Collaborator.
-
We create Project plan, Use cases & test plan document & upload those in Web Collaborator & get it approved by customer to start the software development.Test plan approved by customer is used at User Acceptance Testing to ensure customer gets what they asked for.
|
| Our Typical SDLC Process is as below: |
|
| 1. Project Planning |
|
This effort will be done by a project manager to come up with a project plan & manage the overall project using Web Collaborator (BP). Deliverable at this point will be project plan defined in Web Collaborator & customer status website created. All documents will be stored in BP will also get electronically approved via BP. Invoicing for the projects can also be done via BP. |
|
| 2. Initial Requirements Analysis & architecture selection (Optional & depends upon project complexity) |
|
This part involves efforts done by a Technical Architect to nail down high level functional & non-functional requirements. A document walkthrough will be done with the customer & will need to be approved by the customer. Deliverable at this point will be an architecture document |
|
| 3. Requirements Analysis |
|
This part of the project involves a business analyst to look at customer requirements, analyze them, and translate them into a System Requirements Specification document or SRS. A document walkthrough will be done with the customer & will need to be approved by the customer & once approved it will be passed to design teams for functional design. Deliverable at this point will be an SRS document |
|
| 4. QA test planning |
|
This part involves efforts done by QA testers to come with QA test plan or QTP on the basis of FDD and TDD & get them approved by Functional/Technical team. Deliverable at this point will be a QTP document |
|
| 5. Functional design |
|
This part involves efforts done by software designers & GUI designers to come up with almost final screen shots of the proposed application/system & business logic, validations, algorithms etc. in the form of a Functional Design Document or FDD. A document walkthrough will be done with the customer & will need to be approved by the customer. Deliverable at this point will be a FDD |
|
| 6. Technical design |
|
This part involves efforts done by software designers & programmers to come up with database design, software component design etc in the form of a Technical Design Document or TDD. A document walkthrough can be done with the customer, but not required. Deliverable at this point will be a TDD |
|
| 7. Software coding & unit testing |
|
Efforts done by software developers to create & unit test the software. |
|
| 8. Integration testing |
|
Efforts done by software developers to test their software when put together with others |
|
| 9. QA testing |
|
Done by QA testers to test the software for security, functions & other areas as per QTP document. |
|
| 10. Customer/User acceptance Test |
|
In this part the created application/product is tested by customer or its users to accept it. We will have one or more of our testers involved with customer to get the acceptance testing done. Deliverable at this point will be a UAT document signed by us & customer. |
