As businesses look for software that meets the demands of a modern working environment, they are increasingly using cloud computing and mobile technology. Cloud computing really took off in 2011:

The ISEB/ISTQB Foundation Certificate in Software Testing is the industry standard certification for software testers. The qualification allows testers to demonstrate their skills to employers and for businesses to show the proficiency of their software testing team.

The qualification is recognised internationally and so opens up testers and businesses to a wealth of new opportunities world wide. It also allows for multi-national projects as everybody is working with a common understanding of software testing.

You will find more information on the course and how to book at our ISEB/ISTQB Foundation in Software Testing Training course page.

What you need to know before starting the ISEB/ISTQB Foundation course

Who is the course for? Read the rest of "ISEB/ISTQB Foundation in Software Testing – What You Need to Know"

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.

systems analysis in a changing world

Systems Analysis and Design in a Changing World by John W. Satzinger and Robert Jackson is a revised edition of one of the most popular texts on the subject. It’s been updated making it easier to navigate whiles keeping it’s real world case studies of the traditional (structured) and the object-orientated (OO). It includes a new “Best Practices” feature and is updated to UML 2.0. You’ll find advanced object-orientated topics throughout the book as well as extensive coverage of the latest concepts in project management.

• ISBN-10: 0760058792
• ISBN-13: 978-0760058794
• Publisher: Course Technology Inc; Revised edition edition (20 April 2000)

The book is huge and heavy!! However the aims of the book are stated as:

“providing the most comprehensive, balanced and up-to-date coverage of systems analysis and design available”

It covers:

• Project management
• System modelling
• Object technology with UML
• Client-server architecture
• The Internet
• Database design
• User interface design.

The book includes updates to  the object technology approach to UML 2.0

Systems Analysis and Design in a Changing World provides the flexibility to emphasise the traditional (structured) or the object-orientated (OO), or both, and includes integrated case studies  through every chapter to demonstrate and practice the skills learned. There’s lots of hands-on practice, including the original “Rocky Mountain Outfitters” case which  is now better integrated with the chapter texts and this addition includes a further running case study “Reliable Pharmaceuticals”.  The case studies take the reader through various stages of systems analysis including entity relationship diagrams and DFDs for the traditional approach as well as UML 2.0 and Object oriented techniques for newer approaches to the subject.

The book covers a lot of fairly involved topics but is well illustrated and visual. Various illustrations, pictures and diagrams aid the understanding of the topics discussed.

Systems Analysis & Design In A Changing World includes well crafted questions and exercises at the end of each chapter as well as case studies that can be used for practise and experience.

It is a  comprehensive and well written book covering  every aspect of Systems analysis both modern and traditional with sufficient practical material to ‘learn by doning’.