WebSpec

WebSpec

1. Introducción

   • Furthermore the rapid development of Web apps presents additional Restrictions to allow continuous and timely implementation Testing against the specification of the requirement.

2. a DSL to capture interactive Web requirements

   • Web applications tend to change quickly, and it's hard for them to change. Developing teams to adapt easily to these changes. In the following subsections, we're going to introduce the These concepts are based on an example of an e-commerce application. The language will be described as a Simple user story: "As a customer, I'd like to search. Products by name and see their details.'
     • WebSpec diagrams
     • Interactions
       • An interaction represents a point where the user can interact with the application by using its interface objects (widgets).
     • Specifying the application’s behavior
       • Usually, the behavior of Web applications is exercised either by navigating from one page to another or by local (interface) changes that may not involve navigation to a new page.
         • On the other hand, there are behaviors that are not directly perceived by the user and are triggered as a consequence of navigating from one page to the other
     • Specifying properties with generators
       • With WebSpec, it is possible to specify general and concrete application properties. A concrete property is specified with one or more scenarios that use constant values in Actions
     • Diagrams’ composition
       • When the application grows, new requirements may refer to previous described (and perhaps finer grained) requirements. Let us assume that we have the following requirements expressed as user stories: ‘‘As an administrator, I would like to search for users by email in order to ban them’’ and ‘‘As an administrator, I would like to check the user’s activity searching them by email’’.
     • WebSpec guidelines
       • When using WebSpec for Web requirements specification, diagrams tend to grow with the time, thus hindering comprehension; as a consequence, we have written several simple guidelines to be taken into account during the development process:
         • Similar interactions
         • Explicit specification

3. In Use

   • How Webspec is used in the development cycle. As an introduction, we detail how a diagram that has cycles and specifies infinite scenarios is used in practice
     • Bounding infinite scenarios
     • Improving team understanding with WebSpec and Mockups
     • Requirements validation
     • Requirement changes
       • Capturing requirement changes
       • Using requirement changes to ease application evolution

Images and files in the map