The focus of SolTech’s approach in the Discovery Phase is to initially identify the overall business requirements of the solution through interviews with stakeholders and subject matter experts. These findings are then used to translate business requirements into a unified set of functional requirements.  A key success factor in the Design Phase is to obtain a consensus from stakeholders regarding the features of the new process before progressing to the Design Phase.

In order to reduce costs, clients will sometimes produce detailed requirements documents using their own in-house resources. In these cases, SolTech's focus in the Discovery Phase is to ensure a clear and concise understanding of the functional specifications of the application. Once an understanding is reached, the following steps are taken: documentation of clarification questions & answers are defined, integration techniques, team responsibilities, as well as recommendation of technical solutions.

•    Interviews with key stakeholders
•    Review of legacy applications
•    Document gaps in the existing processes
•    Document business requirements identified by each group
•    Translate various business requirements into a single set of functional requirements for the system
•    Documentation of clarification questions and answers
•    Discussions between SolTech and Client
•    Definition of integration techniques and team responsibilities
•    Recommend a technical solution and approach for implementing functional requirements

Phase Deliverables:
•    Business requirements document / Clarifications Document
•    Functional requirements document / Integration Flow Diagram
•    Identification of Roles and Responsibilities between the joint vendor team
•    Review with Project Management and Stakeholders for Consensus

Based upon the approved functional requirements from the discovery phase, the definition phase focuses on moving beyond requirements and giving shape to the solution. This phase is very interactive with the involvement of stakeholders and technology management. Here we design the User Interface, review for consensus then add the non-visual business logic definition for final review and sign-off.  The deliverables from the Definition phase identify the system requirements and high level application design in a way that can be reviewed and approved by the stakeholders as well as provide sufficient detail to the technical team to begin the design of the software solution.

Key Activities
•    Translation of functional requirements to application features & flow
•    User Interface Specification (Wireframes)
•    Review of Wireframes with project management and stakeholders for consensus
•    Business logic specification (System Requirements Specifications)
•    Review of SRS documents with project management and stakeholders for consensus

Phase Deliverables
•    Application Flow Diagram
•    Wireframes
•    System Requirements Specifications 

The design phase is focused on the technical implementation of the system and is based on the detailed specifications document and related clarifications delivered as part of the discovery and definition phases. 

In this phase, decisions around technology frameworks, infrastructure and software architecture are made that are pre-requisites to developing the application. As an added confirmation step prior to developing code, this phase also translates the user interface prototypes captured in the existing detailed specifications document into re-usable user interface prototypes. Without business logic, the user interface screens provide an opportunity for additional review with the project stakeholders to flush out any remaining questions or changes.

Key Activities
•    Technology recommendations and selection
•    Software architecture definition
•    Data modeling
•    Implementation of user interface screens without business logic
•    Review of user interface screens with IT project management and stakeholders for consensus
•    Weekly status reporting to project management

Phase Deliverables
•    Software Architecture Document
•    Data Model
•    User Interface Screen Prototypes
•    Weekly Status Reports

The development phase consists of implementation of business logic and code assets to ultimately deliver a fully functioning application.  This phase begins with the approved user interface screens, data model and software architecture documents as the foundation of the solution. 

SolTech develops based on an AGILE, iterative development model.  As key functions or modules of the system are completed, they are built to a demo server which is often made available allowing information technology management or stakeholders to view regular progress throughout the Development phase. 

Once initial development of the application is complete, it will be tested in accordance with SolTech’s Quality Assurance process and a project specific test plan. The final deliverable of the development process is the complete, functioning application for User Acceptance testing.

Key Activities
•    Database implementation
•    Software framework implementation
•    Business logic implementation
•    Unit testing
•    Iterative builds to demo environment
•    Quality Assurance test planning
•    Quality Assurance testing & issue resolution
•    Document deployment instructions
•    Delivery of application for User Acceptance testing
•    Project setup in the SolTech Issue Tracking System to support UA Testing
•    Weekly status reporting to project management

Phase Deliverables
•    Database
•    Iterative Builds of Completed Modules to Test Environment
•    Quality Assurance Test Plan
•    Final QA Build for User Acceptance Testing
•    Logins for the SolTech Project Issue Tracking System
•    Deployment Document
•    Weekly Status Report

SolTech focuses on being a long-term business partner to our clients and we look forward to supporting projects even after completion of the project.  In the short term, SolTech will work with clients to resolve any items identified during User Acceptance testing leading to the delivery of the final production ready application and source code.
 

SolTech will remain available and ready to support the project on an as-needed basis for any future enhancements.  For mission critical applications where support ticket turn-around is critical, SolTech can offer Service Level Agreement (SLA) support with guaranteed response times.

Key Activities
•    Resolution of any items identified during the User Acceptance timeframe
•    As needed support for on-going enhancements
•    SLA support if applicable

Phase Deliverables
•    Final Build of Software for Production Roll-out
•    Completed Source Code
•    On-going Enhancements as Requested

During the project life cycle, SolTech adheres to a formal change management process.  The primary purpose is to prevent scope creep so that project milestones and deliverable dates are met according to the project plan. 

The change management process supports potential changes identified by the customer and those identified by the development team.  Our consultants not only build what is specified in the requirements document, they also identify areas where improvements can be made.

When a potential change is identified, it is communicated to the project manager, who will discuss the details of the change with the client.  SolTech will then assess the magnitude of the change, the project impact, and identify any additional costs the change implementation may incur.  In some cases, the change enhances the overall system, but does not impact the cost or timeframe of the project.  If both parties agree to the change, a change request form is filled out and signed, and the project schedule is adjusted accordingly.