HOME - NEWS EVENTS - MAILING LISTS - OPST/OPSA TRAINING & EXAMS - ABOUT US - CORE TEAM - MEDIA KIT - CONTACT - OPEN LICENSES 




 


 

  TEAM ACCESS
     Beta Releases
     Gold Team Updates

  PROJECTS & RESEARCH

     Business Integrity Testing
     Compromise Detection
     Jack of All Trades
     Hacker Highschool
     Hacker's Profiling Project
     Protocol Database
     Security Incident Policy Enforcement
     Security Metrics
     Security Maturity Model
     Secure Programming
     Security Testing Methodology
     Software Quality Testing
     Security Tools
     Trusted Computing
     XML
     Graduate Projects

  ACCREDITED TRAINING

     ISESTORM Event 
     OPSA - Security Analyst 
     OPST - Security Tester 
     OPSE - OSSTMM Expert 
     OWSE - OSSTMM Wireless Expert 
     Hacker Highschool Teacher
     Training Material Accreditation 
     Trainer & Training Certification
     Training & Exam Schedule

  ASSOCIATIONS 

     ISECOM Associates
     ISECOM Affiliates
     ISECOM Partners
     ISECOM Auditors
     Sponsors

  SERVICES 

     Security Test Review
     Gold/Silver Subscriptions 
ISECOM - Institute for Security and Open Methodologies

www.isecom.org - SECURITY TESTING - STICK

Software Testing Checklist (STICK) by Claudia Kottmann and Pete Herzog

STICK is a tool to guide software developers, test designers and project managers through the troubled waters of how to guarantee that software is shipped in high quality. STICK is both a methodology on quality assurance in IT projects to compliment the STICK-checklist as a methodological basis.

The purpose of the project is to assure software quality, which as a project integrates with other ISECOM projects, where quality means durability, scalability, performance, security, usability, and readability. From this definition, it should be possible to test and
measure software quality using similar parameters and methods found in the OSSTMM and the BIT.

The stages and routines are collected in a checklist to represent test planning, design and execution and include a part to review which kind of tool might be helpful to perform these. Also included is a preliminary phase called Quality Assessment which gives the framework on whatever software development and test has to be done.

Testing has to have proper management attention to have a chance to survive budget and project time cutting. This is an existing problem because the erroneous idea that testing is just cost intensive without adding value to the software project is still in many heads. Project leaders therefore have to thoroughly plan tests and time frames within which these can be performed – the responsibility of which is to be seen
here. STICK, does have the aim of assuring quality through efficient and practical testing, however, any test will have some cost associated with it in both time and overhead.

A checklist such as STICK will help to on one hand to follow a guide through the complexity of testing possibilities and on the other hand it gives a documentation, which may save those who plan test, from time cuts just because things begin getting more transparent.

If you are interested in helping with this project please contact us at
stick<at>isecom.org.

Download STICK v. 0.5.: 
 
 Size     Date   Time   Name                     Spain USA
 23722    Dec 1  2002   stick.en.0.5.sxc.....................
 181760   Dec 1  2002   stick.en.0.5.xls.....................

 

 

 

 

 

 

 

Formerly the Ideahamster Organization - www.isecom.org - www.osstmm.orgwww.hackerhighschool.org - www.isestorm.org
 If you have any comments, questions, or to note broken links on this website send e-mail to the
Webmaster
. 
 All contents copyright © 2000 - 2006 - ISECOM - Institute for Security and Open Methodologies. All rights reserved.