The ultimate aim of business/mission software is to help implement the business value or mission imperatives. For critical business/mission applications, high-level strategies need to play a crucial role in the development and validation of software requirement, so that the requirements and the produced software can closely align with the business/mission objectives and effectively contribute to the business/mission success. In this paper, we propose a strategy-guided method for the development and validation of requirements. We firstly articulate the dimensions of strategy and concept model for connecting strategies and requirements. We then present the approaches for the requirements development and validation, based on the relationship between the elements of strategies and requirements. This strategy-guided method addresses the paradigms for both the market-oriented and customer-specific software development. We also give an example illustrating the strategy perspectives and the resulting requirements.