Business Analysis
Our Business Analysts will undertake the following activities:
- Understand your business, manage user expectations;
- Determine solution requirements. Create Functional Requirements document. New functionality specified where necessary. Functional Specifications will be prepared and signed off;
- Change Analysis. Impact of new functionality on other systems, processes and the wider business investigation;
- Business Liaison;
- Co-ordinate with users and development, user input and feedback, System Testing, UAT (User Acceptance Test), Implementation;
- Customer kept informed of progress at least weekly.
Business Case
The Project Business Case is a one-off, start-up document used by senior management to assess the justification of a proposed project, or to asses the options for a project that has already received funding. If approved, it confirms senior management support and/or resourcing for a recommended course of action (option). Business case is approval for resources, finance, duration and agreement on the score of the project. Project case can be used to prioritise the various initiatives.
Knowledge and understanding of a project business case is compulsory for P&P-Bridge Project Management.
Business Plan
Business Plan is a management document for the project and includes mainly information to ensure the delivery of project outputs and the realization of project outcomes. In case of small to medium size projects it is also a management document for the project. In P&P-Bridge we create a project plan to provide:
- Overview of all the project components - how we intend to produce the outputs and briefly describe the rules and responsibilities of each of the parties;
- Formalised agreement between the project manager and customer of what needs to be done and when. This is to ensure delivery and to effectively monitor the project from start to finish.
Design Specification
Creating design specification is a core activity of all P&P-Bridge IT projects. Every Design Specification includes the following steps:
- Project goals;
- Project justification;
- Project success criteria;
- Main modules;
- Security requirements;
- Data conversion;
- Performance and response time requirements;
- Main data model;
- Data archival backup and recovery requirements
Testing
We use mostly the following different levels of testing:
- Performance. This is to insure that the application responds in the time limit set by the user. We create our own standard: each query must perform no longer than 5 seconds independent of number of records;
- Windows/Internet GUI standard. This test is used to ensure that the application has a standardised look and feel;
- Stress Testing. This is testing to ensure that the application will respond appropriately with many users using the application simultaneously (multiuser environment);
- Gorilla Testing. This is a great technique when the potential customer not very computer literate. To accomplish this we ask someone to perform a function without telling them the steps for doing it;
- Security Testing. Testing to guarantee that only users with the appropriate authority are able to use the appropriate features of the system.
Implementation
Implementation starts after final user acceptance report has been signed. Implementation includes the following steps:
- Finalising of user training. Training is done on the user acceptance test system, accessing the test database or a special training database;
- Finalising of user documentation. System documentation corrected with all updates from the testing levels is handed over to production support;
- Installation. The production system is installed in the appropriate production environment or on the appropriate production server, and on any client workstations that require it.
