by Caston Corporate on Flickr

When you are testing software you need to identify risks in applications and prioritise them to test, this is called Risk Analysis.

There may be some risks which are unavoidable in software testing, for example –

• A change in requirements or requirements which are incomplete
• The amount of time allocated for testing
• Developers may delay delivering the build for testing
• Clients may be urgent for delivery
• There may be defect leakage due to the applications size or complexity.

The following must be done to overcome these problems –

• Conduct a risk assessment review with the devolvement team
• Profile for risk coverage is created by mentioning the importance of each area
• Use all available resources for work on high risk areas e.g. allocate more testers to high risk areas and use minimum resources for medium and low risk areas.
• Create a risk assessment database to refer back to for future risk management.

by Alpha Beta Gamma on Flickr

Alpha Testing Definition –

Alpha Testing is like performing usability testing, which is normally done by the in-house developers. On rare occasions Alpha Testing is done by the client or an outsider. Once the alpha testing version is released, it’s then called the Alpha Release.

Beta Testing Definition –

Beta Testing is done by a small number of end users before it is delivered; the change request is fixed if the user gives feedback or reports a defect. Once the beta testing version is released, it’s called the Beta Release.

Gamma Testing Definition –

Gamma testing is done once the software is ready for release with specified requirements. This testing is done directly by skipping all the in-house test activities.

by alisdair on Flickr

Dynamic Software Testing –

Dynamic Software Testing is done by executing the actual application with valid inputs to check the expected output. Unit Testing, Integration Testing, System Testing and Acceptance Testing are all examples of Dynamic Software Testing.

Static Software Testing –

Static Software Testing is a white box testing technique where the developers verify or test their code with the help of a checklist to find errors in it. This testing is done without actually running the application of program. At this stage of testing, code reviews, inspections and walk throughs are normally performed.

Here are some differences between Dynamic Software Testing and Static Software Testing –

• Static Software Testing is actually more cost effective than Dynamic Software Testing; this is because Static Software Testing is done in the initial stage.
• Static Software Testing covers more areas in a shorter space of time than Dynamic Software Testing.
• Dynamic Software Testing is done after the code deployment; Static Software Testing is done before.
• Dynamic Software Testing is done in the Validation stage, whereas Static Software Testing is done in the Verification stage.

In any project team you need someone with knowledge of business analysis, this is very important and it’s a great skill for any project manager to have.

Usually, the business analyst’s role entails –

• Consulting
• Requirements Management
• Requirements Analysis
• Systems Analysis
• Business Analysis

It is vital that the business analysis process doesn’t happen just once as it is a key concept within the structure of a project. It needs constant monitoring and should start at the beginning of the project and work right through to the end.

Read below to find out the main time-frames in the project lifecycle, where business analysis is key –

When producing a Business Case – Plans are drawn up for every project, it should include in-depth information and everyone involved should understand what is expected of them.

Requirements Planning – creating a schedule with various time-based requirements and documenting tasks.

Requirements Management – Managing the project as things develop and change is very important, it can be very complex and lots of things can change and evolve as the project progresses.

Obtaining Requirements – Building a relationship with stakeholders is key, you need to think about how you word and structure your questions and also consider where things could go wrong so you’re prepared.

Even though project management and business analysis do have common characteristics, they are still noticeably different. The whole project is presided over by the project manager, this includes being in charge of the projects progress, reducing the chance of risks and finishing the project on time and within budget. Whereas the business analysts’ job is to define the product in the project and make sure that it is of a sufficient standard. This job doesn’t end until the stakeholders confirm that the product is at a good enough standard and so it follows the whole project lifecycle.