The purpose of this project is to aid a chess coach in instructing a scholastic chess team. Included in the project is a guide to starting a scholastic chess club or team and recommended procedures for developing it. The reader is expected to know basic chess terminology and have at least a beginner's understanding of the game of chess (though a chess coach should probably be a competitive chess player). The portion of the introduction on starting a chess club is largely understandable to a person without a background in chess. A tactic is a combination of moves that clarify a chess position in favor of the executor. Chess problems are the demonstration of tactics in a chess game, and their purpose is to increase the player's tactical eye and his or her enjoyment of the game. The chess tactics in this project are geared toward an intermediate to advanced level chess player.

Gathering and managing software requirements, known as Requirement Engineering (RE), is a significant and basic step during the Software Development Life Cycle (SDLC). Any error or defect during the RE step will propagate to further steps of SDLC and resolving it will be more costly than any defect in other steps. In order to produce better quality software, the requirements have to be free of any defects. Verification and Validation (V&V;) of requirements are performed to improve their quality, by performing the V&V; process on the Software Requirement Specification (SRS) document. V&V; of the software requirements focused to a specific domain helps in improving quality. A large database of software requirements from software projects of different domains is created. Software requirements from commercial applications are focus of this project; other domains embedded, mobile, E-commerce, etc. can be the focus of future efforts. The V&V; is done to inspect the requirements and improve the quality. Inspections are done to detect defects in the requirements and three approaches for inspection of software requirements are discussed; ad-hoc techniques, checklists, and scenario-based techniques. A more systematic domain-specific technique is presented for performing V&V; of requirements.