You are here: Home > Key Processes
 
 
Business Opportunities | About Jordan | Contact Us
 
 
Search:  
 
About Us
About Us
  Profile
  Vision & Mission
  International Markets
  Partners & Memberships
  Services
  Products
  Our Clients
  Technologies Used
  Key Processes
 
  News
  Job Opportunities
   
  Primus Consulting
   
  Home
 
 

 

 
 
 



 


Project Management

For the successful ongoing management and conclusion of our projects, some procedures must be carried out and maintained throughout the life of a project. These procedures are intended for keeping the project on track, in terms of its schedule, and its functionality. Namely we carry out policies for Change Control, Risk Management, and User Acceptance Testing.

Change Control is the formal process through which change is carried out in the course of this project. And Risk Management is the procedure to be followed in addressing issues, before such issues materialize into problems.

When it comes to managing static websites more variables are concerned, not necessarily in the project requirements only. We deal with a wide range of clients, from government organizations to small business owners. It is rather difficult to have a unified system that can control all types of projects in the same manner.

Planning & coordination, communicating regularly with the whole team, using time wisely, documenting what is done, managing risks and managing expectations are requirements we aim at completing to manage our projects.

We at Primus believe that every project is a challenge, whether it is a simple website or a large critical project. We maintain systemized procedures throughout every project in order to ensure that the work is done perfectly. In addition, we are constantly updated with new ideas and skills and hence, chances of updating and changing control remain unlocked all the time.

Top
 

 

Software Development

For the proper implementation of software applications, our software projects go through a cycle of Requirements Gathering and Analysis, Detailed System Design and Proof of Concepts, Software Development, Testing, and finally Close Out and Deployment.

Detailed requirements gathering sessions are held to specify all the required features of the system, down to the smallest possible detail.

Having specified the requirements, our senior developers design the system to meet the requirement specifications in the most optimal way, ensuring data integrity, ease of use, and proper overall information system. Additionally, during this phase, small tests to determine suitability of a particular plan to satisfy requirements are conducted. These tests are called proof of concept tests.

Once the design of the system is completed, this design is then passed on to the development team, were the system is built. Additionally, the system design is passed on to the testing team, so that they start preparing their testing activities.

As the system is developed, each part of the system is put under numerous tests, while it is still in the development phase. This is called developer unit testing. However, this does not eliminate the need for a separate testing phase for the completed system to be done by the testing team. Very often the testing team can detect a different type of issues and problems that are in turn resolved by the development team. This cycle of testing, resolving problems, and re-testing is repeated until the system becomes free of problems.

Having completed the testing phase, the system is then prepared for deployment, either by packaging or by preparing installation scripts, and then deployed to its final home: the production environment.


Quality Assurance

The Quality Assurance Process works in parallel with the software development and production processes. Nevertheless, Quality Assurance at Primus means a whole lot more than testing and Quality Control. In fact Quality Control is only a part of the Quality Assurance process.

The Quality Assurance Process is involved with establishing and continuously revising all the processes and standards for software development and production. It starts with ensuring the quality of produced software through the preparation of testing plans, executing these testing plans, and reporting back the problems. It is also involved in the overall quality of the projects that we execute by ensuring that all products (code and documentation) meet the standards we adhere to. And furthermore, QA is involved with the establishment and review of the standards we adhere to, stemming from the international industry standards and making sure the development teams are well aware of these standards.

Top