Beruflich Dokumente
Kultur Dokumente
Employees in Software 31
Development
Services Offered • Development Services for the entire Product Life Cycle– “concept to
completion”
• Website Design and Development
• Hosting Services
• Product R & D, Development and Verification.
• Training Provider
Domain Expertise • MS Technology
• Java
• Database
• Testing
Equity Structure Privately held by the Director of Soft Polynomials (I) Pvt. Ltd.
Sales (FY 2003-04) Rs.4.2 Million
(FY 2004-05) Rs.7.3 Million
(FY 2005-06) Rs.9.7 Million
(FY 2006-07) Rs.11.9 Million
(FY 2007-08) Rs.14.0 Million
Financially Sound Profitable for all 8 years of existence. Debt free with significant real assets and
deep access to capital. Good track record of investing in people and
infrastructure for the long term.
Locations Development offices in Nagpur.
Quality Standards Soft Polynomials uses Quality Assurance methodologies and practices at all steps
in its projects, aiming to deliver error-free software applications.
This commitment to quality is Soft polynomial's core objective as we believe this
is the only way to ensure total customer satisfaction.
During the system study, effort and resource estimates will be made. At the end of system study stage, a
detailed project plan will be done outlining the important milestones and deliverables. We propose
weekly status reports and weekly conference calls with your team to track the status of the project.
We can execute this project on a Time and Material basis. Following are the resources depending on the
level of experience:
1.3 Resources
Resource No. of Employee
5+ Years Experienced Engineer 4
2-5 Years Experienced Engineer 7
<2 Years Experienced Engineer 10
Trainee Engineers 10
2 Contact Information
Shashikant M Deshpande
Soft Polynomials (I) Pvt. Ltd.
3rd, North Bazaar Road, Gokulpeth,
Nagpur- 440010
Tel: +91 0712-2556808
Fax: +91 0712-2556808
Email: smd@softpolynomials.com
3 Appendix A
3.1 Infrastructure Information
We believe that excellent infrastructure is necessary to create an environment that fosters learning and
innovation in employees.
Connectivity
The following connectivity exists at Soft Polynomials:
Internet Connectivity and Bandwidth: We have one 2 MBPS leased line and 4 broadband connections
for Internet connectivity.
Phone Service: We have Lucent’s Definity EPABX system, which is capable of handling 25 digital
extensions, and ISDN connectivity.
Video Conferencing: We have an ISDN and IP-based video conferencing set up.
FTP Sites: We maintain two secure ftp servers for large incoming and outgoing file transfers.
Firewall/Router Infrastructure: We have CISCO Router for Internet connectivity with two Ethernet
ports, four serial ports, and an ISDN port.
The Rational Unified Process (RUP) model spans a project into four phases, during its life cycle from
conception to completion. The Soft Polynomials Standard Process (SPSP) based on the guidelines of
RUP, details the plan, activities to be carried out, reviews, and artifacts to be created for each of the four
project phases.
Inception Phase: The first phase of the project life cycle is the inception phase wherein the project
scope is identified.
Elaboration Phase: The second phase is the elaboration phase wherein the scope and method of
implementing the life cycle, including alternatives to be attempted are clearly detailed.
Construction Phase: The third phase is the construction phase wherein the actual coding is carried out
to implement the decided alternative design.
Transition Phase: The last phase is the transition phase wherein the RTL Coding is delivered to the
verification team and then on to the client. Support is provided it until FPGA Kit or Synthesis is over.
Usually the hardware is classified as a separate project for maintenance, once it is accepted and is in
production.
Each phase may be optionally divided into iteration, in case Soft Polynomials plans to identify a
set of deliverables spaced out within the time span of the phase. Usually there will be at least one
milestone for each phase or iteration as the case may be.
Throughout the development process, Soft Polynomials creates a set of artifacts that are available
at the project site on a selectively sharable basis. It engages in the following six best practices
methodology proposed by RUP:
Develop Iteratively
Manage Requirements
Use Component Architectures
Model Visually
Continuously Verify Quality
Manage Change
Project Team
Soft Polynomials assigns an Executive (Exec-in-charge), typically a Vice-President, to take the
complete ownership of the account and the project. The Exec-in-charge is responsible for all the aspects
of the project, including technical aspects, project execution, customer management, personnel issues at
our end, invoices, contracts, etc.
Soft Polynomials allocates a Technology-in-charge (TIC) and Delivery-In-Charge (DIC) to a
project. TIC is responsible for ensuring that all the key technical insights into the project are delivered.
The DIC carries out all day-to-day execution, regular client communication, local executive liaison, and
schedule management. The DIC is responsible for all project management issues. At the start of the
project, Soft Polynomials identifies a “second-in-command” project lead. This person is under constant
development to ensure that the project is fully devoid of any risk owing to single person dependence.
Soft Polynomials staffs the rest of the team with engineers possessing complementary skills. This is done
considering the complexity and the skill requirements of the project, as well as team dynamics.
Individuals on the team are allocated exclusively to a project and do not work on more than one project at
a time. We have a team of support staff available across the company.
Project Management
Projects undertaken by Soft Polynomials are categorized either as development, verification or support
type. A typical project is likely to have more than one sub-projects under it, each can be of a different
type.
Typical project execution cycle is described below:
The project gets initiated during the Project Initiation stage wherein an Executive-In-Charge and CRM
are identified. A meeting takes place between stakeholders and Project team members. The customer
acceptance criteria, project phases, milestones are discussed and documented. Requirements are
collected, analyzed and understood by the Delivery-In-Charge during the Requirements Management
process. These are documented in Software Requirements Specifications and sent to customer for
approval.
Projects at Soft Polynomials are managed and controlled through Project Planning processes. During
planning stage, a Life cycle Model is selected; estimation and scheduling activities are carried out. The
Project Environment Setup focuses on tools to be used for configuration management, design
development and verification. Role specific responsibilities within the project are identified by Delivery-
In-Charge. Tasks to be performed are detailed down and scheduled. The project specific training
requirements are identified and necessary Training is scheduled.
The project is taken through the Design stage where system architecture is defined based on Standards.
Based on the project’s requirements, the traceability of requirements up to the design and testing is
ensured.. The project team executes the project during the Implementation process. Reviews are planned
from time to time based on project requirements. Normally peer reviews are planned during design and
implementation phase.
The verification process ensures adequate quality control before the project delivery. Based on the
customer requirements, different types of testing are planned. The traceability is maintained through out
the project execution, a matrix is typically used to trace the requirements up to the release of the software.
Adequate in-process testing, integration testing and testing at release level ensure quality delivery
Projects at Soft Polynomials are tracked and monitored at a predefined frequency by Delivery-In-Charge
through the Project Tracking process. Typically three levels of project reviews are planned – 1: internal to
the project teams, 2:Delivery – in – charge reviewing the project at a periodicity defined based on
project’s requirement, and 3: a review by Seniors management based on the summarized report on the
data collected during project execution and the measurements done. Exec-in-charge tracks the project’s
costs. At the minimum, at every milestones assessment and at the time of project closure the costs are
tracked.
Any changes that are to be implemented are carried out through Change Management process. During
this process changes to be incorporated are handled by the CCB (Change Control Board) comprising of
the TIC, DIC and the Exec-In-Charge.
During entire project execution cycle Configuration Management activities are planned. Every project is
expected to use tools for managing the configuration depending on the client and synchronization needs.
Audits are undertaken by auditors who are trained in auditing and not directly responsible for the
functions being audited. Non-conformance observed is brought to the attention of the person responsible,
and is recorded, documented and subject to timely corrective action to ensure full rectification.
Conference calls between client’s team and Soft Polynomial’s team are usually scheduled with a frequency
of once or twice a week. The time selected is usually late night for us, and early morning for client (and
sometimes vice-versa). The team gives a lot of importance to conference calls and makes sure that issue
list is managed and carried forward from call to call. Delivery-In-Charge is responsible for managing
issue list and actions taken, overseen by Offshore Manager. Both Video and Audio conference facilities
are available.
Usual issues are managed over email communication. The weekly conference calls ensure status
reporting, closing of issues, and identification of risks and escalation points. The team members also use
the Instant Messenger facility for communicating with their counterparts in the US facility. This helps in
Soft Polynomials typically has three communication channels with the client. The Exec-in-charge has a
one-on-one phone call with his counterpart every other week, or more often as required or desired. The
Exec-in-charge also sends a once-a-month management report of the activities on our end. This report
describes the activities carried out by the team during the month and the plan for the next month.
The Module Leader is responsible for a set of structured communication between the two teams. The
typical activities are: