Another compelling reason for documenting the business rationale behind the system is that the customer may change personnel during the project. The rationale for the new system is important as it will guide the decisions made by the business analysts, system architects and developers. This section describes the reasons why the customer is looking to build the system. Each of these is described in more detail below: Main ElementsÄepending on the methodology employed (agile vs waterfall) the level of formality and detail in the SRS will vary, but in general an SRS should include a description of the functional requirements, system requirements, technical requirements, constraints, assumptions and acceptance criteria. In addition to specifying how the system should behave, the specification also defines at a high-level the main business processes that will be supported, what simplifying assumptions have been made and what key performance parameters will need to be met by the system.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |