# Foreword Documenting the business requirements and application design is a critical step in establishing sound communication between the business and the development. While business and development teams vary greatly in terms of conception and methodology, documentation helps both teams to build a common understanding on the key concepts and procedures in the specific business domain (i.e. domain-driven design), and facilitates direct communication and prompt feedback. A final document enables management to add or change developers to the project without adversely encroaching on the business requirements. This project adopts a combination of Rational Unified Process (RUP) and agile approach. Emphasis on centralized analysis and design avoid parochial view of the application which might cause signification rework in the later development. With the design in mind, the project is divided into multiple development phase. Each phase is driven by specific user stories and embrace common agile practice, such as emphasis on testing and control over project complexities. --- # Agent Instructions: Querying This Documentation If you need additional information that is not directly available in this page, you can query the documentation dynamically by asking a question. Perform an HTTP GET request on the current page URL with the `ask` query parameter: ``` GET https://docs.nuts.finance/nuts-docs-v1/foreword.md?ask= ``` The question should be specific, self-contained, and written in natural language. The response will contain a direct answer to the question and relevant excerpts and sources from the documentation. Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.