MediaWiki API resultaat.

{
    "batchcomplete": "",
    "continue": {
        "gapcontinue": "Risk_Analysis",
        "continue": "gapcontinue||"
    },
    "warnings": {
        "main": {
            "*": "Subscribe to the mediawiki-api-announce mailing list at <https://lists.wikimedia.org/mailman/listinfo/mediawiki-api-announce> for notice of API deprecations and breaking changes."
        },
        "revisions": {
            "*": "Because \"rvslots\" was not specified, a legacy format has been used for the output. This format is deprecated, and in the future the new format will always be used."
        }
    },
    "query": {
        "pages": {
            "49": {
                "pageid": 49,
                "ns": 0,
                "title": "Requirement List",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "[[Bestand:SS_RequirementList.jpg|200px|thumb|right|]]\n=Why= \n\nTo create a starting point for design choices during the project, and to measure whether the project succeeded. \n\n=How= \n\nCollect applicable regulations, norms, best practices. Draw up the requirements list with fixed requirements, flexible requirements, and nice-to-haves. Include methodologies to measure whether the requirement is met. Discuss with all stakeholders if your interpretation of their requirements is correct. \n\n=Ingredients= \n\n*Critical mind and an allergy for ambiguity. \n\n*Access to applicable knowledge. \n\n*Clear and concise writing skills. \n\n*Measurement tools. \n\n=Practice= \n\nThe requirements list is the start of the content of any business project. It is also the document that the project team will check during the wrap-up of each project phase as the project moves towards its conclusion. In each phase, the professional products present a more detailed level of requirement fulfilment. This iterative process makes it one of the most valued stepping stones of any engineering project."
                    }
                ]
            },
            "26": {
                "pageid": 26,
                "ns": 0,
                "title": "Requirements Engineering",
                "revisions": [
                    {
                        "contentformat": "text/x-wiki",
                        "contentmodel": "wikitext",
                        "*": "[[Bestand:Workshop_RequirementsEngineering.jpg|200px|thumb|right|]]\n=Why= \n\nTo define, refine, document and maintain requirements throughout a project.  \n\n=How= \n\nRequirements can be elicited through various methods. Developers typically progress from an initial, high-level overview of a system to a detailed description of its behavioural and performance requirements. At each iteration, requirements are refined. To ensure completeness, the set of requirements can be divided into the different viewpoints, for example functional, operational, safety, security, and privacy. \n\n=Ingredients= \n\n*An understanding of the levels of development: functional specification, high-level design, low-level design, detailed design or source code. \n\n*Differing viewpoints, \n\n*Grice\u2019s maxims: be brief, be relevant, be polite, and be informative. \n\n=Practice= \n\nAs requirements list are essential in the documentation and process, \u2018getting it right\u2019 warrants time and effort. Some companies hire dedicated requirement engineers for this."
                    }
                ]
            }
        }
    }
}