Dial Nine Software Technologies’ development processes and procedures have been developed over many years and have been fine tuned and road tested in literally hundreds of development projects. The company uses a combination of proprietary and best-of-breed development tools and methodologies to achieve the highest level of quality and delivery.
Dial Nine Software Technologies Limited software development methodology focuses on IBM's RUP (Rational Unified Process), XP (Extreme Programming) and Agile methodologies. Hallmarks of the company's approach include:
* A self-contained software delivery to the customer every three to four weeks. Many small deliveries allow the customer to see the progress of the project at regular intervals. It also allows the client to identify issues early in the development lifecycle, and makes it easier to introduce changes where necessary.
* Close, daily participation between the client and the development staff.
* Flexibility
* Quality
Dial Nine Software Technoglogies Limited development processes adhere to the Software Engineering Institute's (SEI) Capability Maturity Model (CMM). The Capability Maturity Model for Software (CMM) provides standardised procedures and processes to ensure that projects are delivered to client requirements, on-time and within budget. CMM is universally recognized standard in the software industry.
Typical Software Development Deliverables
During the lifecycle of the project the client can expect the following deliverables:
* Requirements Documents
* Business Use Case
* Software Design Specifications
* Project Schedule
* Cost Estimate
* Contract of Work
* Prototype
* Test Cases
* Use Cases
* Weekly Milestone Reports
* Software delivery every 3-4 weeks
* Project Review
RUP Overview
 RUP Phases Overview
RUP is broken down into five phases of development:
Inception Phase
The business case is established in this phase. This includes context, defining successful outcomes, and budget. The following items are produced in this phase: primary use case, project plan, risk assessment, and project description.
Terminology:
A use case describes how a user (actor) will use the system to achieve a specific goal.
A business use case is a technology free description of the process a user (actor) will follow to achieve a specific goal.
Learn more about Use Cases here...
Elaboration Phase
Architecture prototype
Overall development plan
Use cases are completed.
Business case and risk overview are reviewed.
Construction Phase
Development phase
Transition Phase
This phase includes end-user training and beta testing.
Production Phase
Project deployment.
Disciplines
The tasks and activities of the project members are broken down into types of activity, and these are referred to as
Disciplines There are two types of disciplines Engineering and Support. Engineering Disciplines:
* Business Modeling
* Requirements
* Analysis & Design
* Implementation
* Test
* Deployment
Support Disciplines:
* Configuration and Change Management
* Project Management
* Environment
Contact the company here to discuss your Application Development requirements with a consultant. | 
