Iterative Delivery Model

Our custom solutions are crafted using a disciplined delivery process that includes overall quality assurance, configuration management and measured analysis.

The major phases are:

  •  Requirements
  •  Design
  •  Development
  •  Testing and Acceptance.

The benefit of this method is to deliver a system through small iterative cycles in short periods of time, allowing software developers to take advantage of what was learned during development of earlier parts or versions of the system.  Learning comes from both the development and use of the system

  Requirements Phase

Our approach is to use small teams where all the members are involved in the requirements phase. We believe this approach contributes to the development of requirements that are “On-Target” in terms of customer focus.

When a customer requests an interactive dashboard, our approach is to target all that is easily achievable with our rich visual web-enabled views and include the capability to create printable reports, multi-page documents and multi-slide presentations.

The requirements developed in this phase will be sufficiently documented and validated prior to preliminary design. Each requirement with related artifacts will be captured and routed for approval before any design work begins. Ultimately, the list of requirements will be managed and negotiated with priorities, measurable goals and achievable schedules.

 Design Phase

Similar to the requirements phase, our approach is to use small experienced teams where all members are involved in the design phase with focus centered on the user.. The design phase identifies back-end architectures, front-end User Interfaces (UI), and the needed services to connect between the two.

User Interface (UI) “wireframe design” are our first tem toward delivery stunning and usable interfaces. A wireframe is also known as a page schematic or screen blueprint that represents a skeletal framework of the website for visual interface.

UI wireframes connect the underlying application architecture to what the user sees via a visual design and visual flow. UI wireframes establish functionality and relationships between different components of the web application. It is the first tangible product of the proposed website or web-enabled tool that can be communicated between stakeholders, end users and developers to ensure the requirements and objectives are met through design.

Data Analysis, logical data design, and web services will be completed by ANSOL’s Web Interface development experts development includes database technologies used, program and data structures, rules, and database interfaces.

Our SharePoint solutions leverage years of experience working with the SharePoint Platform covering SharePoint 2007, SharePoint 2010, and SharePoint 2013 in highly restrictive multi-tenet environments.

 Development Phase

SharePoint solution development will depend on needed functionality.  Our priority is to use Out-of-the-box features when possible keeping custom code, maintenance, costs, and deployment times to a minimum.

Our NMCI approved rich client tools bring fast, highly interactive visuals to the solution.  These will developed utilizing industry standard practices. Our development team is engaged with the latest SharePoint technologies and develops at a fast and focused pace. Their methodology includes proper risk management and seamless, deadline-oriented work flow. The seasoned development team is capable of delivering tested incremental releases on 2 week cycles.

All data, data models and code are engineered with long term manageability, operational costs, and future extendibility in mind.

 Testing Phase

Testing is closely tied with our Configuration Management and source code change history.

Frequent incremental builds with focused test plans can be executed in short periods of time further reducing overall development costs and time. We track all source code changes and report all affected components for each new build. A summary of functionality and past test history is fully documented. A two-week build schedule allows this list to remain very manageable and enables a sustained rapid iterative cycle.

 Acceptance Phase

Each incremental build brings new functionality. A two-week build cycle will allow increased communication between stakeholders, end users and the development team. New functionality would be moderate, enabling proper reviews without significantly impacting end users and stakeholder’s schedules. Moreover, this relatively quick build cycle helps ensure the coding stays aligned to requirements, where any deviations can be quickly identified and corrected.

Each new build measures functionality against requirements and wireframe designs. A senior team member will conduct a review with stakeholders and end users. When web-enabled processes are used for the first time they reveal new beneficial processes or analytical views that once recognized often become desired. Our agile and extendable products allow flexibility in managing risks and supporting new requirements as they develop, where frequently these new ideas are fed in as requirement for the next build update.