How We Work


We believe transparency and trust is the key to a successful delivery


Custom Software Development is what we deal with everyday!

We work with clients here in the US and abroad and believe transparency and trust is the key to a successful delivery of any software projects. To establish this relationship we use the following tools and methodologies in our everyday work:

Project management software: Redmine, Asana, Trello and others
Time tracker: Scrum Toggle
Version control system: GIT - where the codes of the entire project is stored and records changes to a file or set of files over time so that you can recall specific versions later.

So here’s how we do it. Let’s walk through together:


1

Project Initiation Stage

Initial Project Analysis

This is the intro phase, where we will learn more about your business, your goals, your desired timeframe and define the project scope. Once we’re both comfortable and satisfied with the result of our discussion, our team will put together the finalized project concept and provide you with a brief functionality description, the suggested collaboration model and the preliminary project model.

Project Scope

When we both are in agreement of the project scope, we will articulate what the project entails, create a roadmap and divide it into milestones. Basically we divide large projects into stages and complete each stage one at a time and represent the results to customers upon completion of every stage or milestone. Here in each milestone, we monitor deadlines, make sure it’s easy to identify important dates, identify critical path and potential bottleneck within the project.

Project timeframe and Budget

Here we will confirm project delivery timeframe and budget with you.

Service Agreement

Upon agreement of all previously competed tasks we will proceed to signing a services agreement.

2

Development

Analytics

We call this stage the “What” phase. Basically we will determine in a clear and precise fashion what is to be built and deliver requirement specifications, domain ontology(things, action, states), typical and atypical scenarios.

Architectural Design

In this stage we will map the requirements delivered in the previous stage(Analytics) into an architecture, where we define the project’s components, interfaces and its behavior. Here we will partly or entirely build a prototype of the project, test it as thoroughly as possible to save our clients hundreds or even thousands of dollars in possible corrections.

Graphic Design

Now it’s time to determine the look and feel of your project’s user interface. As it is critically important, our designers will take target audience into consideration and communicate with you to make sure the final design matches your needs and tastes. If however, you choose to provide your own design, we recommend the following suggestions:

Make sure your design is unique.
Record invoices of purchased images and/or videos.
If free images are used, make sure they do not violate infringement rights.

Development / Implementation

At this stage our programmers start to write codes and build components either from scratch or by composition to build exactly what has been requested. This stage will be followed by implementation phase where we deal with issues of quality, performance, baselines, libraries, and debugging for possible critical errors.

Source Code

Customer’s access to source code depends on the collaboration model selected. If the collaboration model is based on hourly rate, then customer has immediate access to source codes. If customer goes for the fixed priced model, then the time to access the source code is determined in the service agreement signed by both client and Uniwebb Software.

QA Process

Quality is very important to us. We believe quality must be a distinguishing attribute to the systems we build which indicates the degree of excellence we provide.



Once the coding and implementation phase is done, a separate team of QA engineers will perform a series of tests like regression test, internal testing, unit testing, application testing and stress testing of the completed project and check for possible errors (if any) and conditions under which they arise. If errors are found, it will be sent back to programmers for correction and the process continues until the software is validated for final delivery.

Deployment

This is where all the documents and both the final product and its source code are delivered and installed on your server. Now you’re exclusively the proud owner of your product.

3

Support

Software Maintenance

Here we recommend to enter into a software maintenance agreement. The purpose is to prevent any possible defects and faults, timely software update to maintain smooth operation. Necessary software modification to maintain its function and increase its demand in the market.

Terms of Support

By now you have your software installed on your server(s), a software maintenance agreement is in place and you are enjoying your application :), but our work does not end here. Our team is always available 24/7 to support your product. We can enter into a separate support agreement upon your request and agree on details and options as it pertains to your project’s requirements.

Service Agreement

All the terms and conditions of the services agreement is included in either the maintenance or support agreement and is normally based on hourly basis for additional work needed.

Sofware Development Process

Software Development Process

4
At Uniwebb Software we know how to build sophisticated applications and employ methodology that is best suited for such projects.

In all of our project development processes we use both formal (Waterfall) and agile(Scrum and Kanban) methodologies to deliver fully functioning programs and exceed our customer’s expectations.