Methodologies enable us to:

- Maintain an effective communication with the client
- Implement customer focused development
- Implement necessary changes and resolve conflicts in a professional manner.
- Develop and deliver high quality applications
- Deliver the project in scheduled time
- Identify and analyze current and future needs of our customers, and the priority levels of these needs. Implementing a systematic process makes future enhancement on the project easier.

Assessment

During the “Assess” phase we address the following factors:

i. Major goals of the project
ii. Clients' expectations and measures of the success of the project. Are these in alignment with the project goals and mission of the company?
iii. Analysis of the business processes and environment
iv. Identification/Analysis of the target users
v. Integration of the current project with the clients' existing systems
vi. Suresoft team organization in accordance of the specific project

The analysis should be done in a way so that the process does not overwhelm any of the parties involved. However, this phase should generate all the essential information for incorporating the Requirement Specification Document.

Input
a. Communication with the client and the Suresoft team members
b. Example sites/applications provided by the clients

Output
a. Requirement Specification Document (RSD): this document does not delineate the architectural or implementation details, but specifies information at a “high” level. Our clients are the primary readers of the document. So that is why the requirement document specifies “what” features are to be developed rather than how they are to be designed. The document includes:

1. A logical breakdown of the project into two or more modules
2. Further breakdown and functional analysis of the modules
3. Time and cost analysis
4. Team roles and responsibilities
5. Development tools to be used for the project

Architecture

We take the RSD as the prototype document in coming up with the detailed design document. The prime users of the design document are the project managers and the development team. The document describes “how” the project is to be developed as opposed to what is to be developed. The document specifies information at a “low” level. The complexity of the project determines the size and complexity of the document

The document may contain:
- Detailed description of the architecture
- Algorithms (detailed plan to implement the project/specific component of the project)
- Components, their interfaces and behaviors
- Data structures
- Information/guidelines on platforms, memory size, etc.

Development

During this phase we develop and test the product. The features and functionalities of the finished product should be compliant to the one delineated in the document developed during the asses and architect phase.

During this phase we accomplish the following things:

i. User interface design
ii. System design
iii. Analyze the quality and performance of the product
iv. Complete unit and system testing
v. User acceptance testing (UAT)

We make this process as feasibly interactive as possible. During the UAT phase, the client will see if the delivered product meets its criteria. In this phase, if any discrepancies arise, the client will communicate directly with the project manager, who will resolve such issues in a timely and professional manner.

Deployment

This phase signifies that the project is moving from a development and test phase to the launch phase. Deploy is usually triggered by a formal acceptance that all of the agreed upon deliverables have been completed to the required standard.

During this phase, we address the following issues:

i. User training
ii. Enhancement, maintenance and support