Requirements Modeling for WebApps

Requirements Modeling for WebApps

•             Introduction : Web developers are often skeptical (doubtful) when the idea of requirements analysis for WebApps is suggested.

•             “After all,” they argue, “the Web development process must be agile, and analysis is time-consuming. It’ll slow us down just when we need to be designing and building the WebApp.”.

•             Requirements analysis does take time, but solving the wrong problem takes even more time.

•             How Much Analysis Is Enough?

•             WebApps is emphasized depends on the following factors:

•             Size and complexity of WebApp increment.

•             Number of stakeholders (analysis can help to identify conflicting requirements coming from different sources).

•             Size of the WebApp team.

•             Analysis can help develop a common understanding of the project.

 

Introduction:

•             It is a good idea to analyze the problem before beginning design.

•             It is not true that all analysis must precede all design.

•             In fact, the design of a specific part of the WebApp only demands an analysis of those requirements that affect only that part of the WebApp.

•             For example from SafeHome, you could validly design the overall website structure (layouts, color schemes, etc.) without having analyzed the functional requirements.

•             You only need to analyze that part of the problem that is relevant to the design work for the increment to be delivered.

Requirements Modeling Input for Web App

•             An agile version of the generic software process can be applied when WebApps are engineered.

•             The process incorporates a communication activity that identifies

•             Stakeholders and user categories,

•             The business context,

•             Defined informational and applicative goals,

•             General WebApp requirements,

•             Usage scenarios—

•             All above information that becomes input to requirements modeling.

•             This information is represented in the form of natural language descriptions, rough outlines, sketches, and other informal representations.

•             Analysis takes this information and then produces more rigorous models as an output.

•             The requirements model provides a detailed indication of the true structure of the problem and provides insight into the shape of the solution