At this stage, there are basics that have to be addressed.

a. Usage model

This enables one to explore how end users will work with your system. This may be a compilation of indispensable use cases on a Rational Unified Process project or a set of facial appearance for a Feature Driven Development project.

b. Initial domain model

It is one of the agile requirements of modeling. It identifies essential business article types and the relations between them. These domain models contain sufficient information: the major attributes of the main domains, domain themselves, and the associations between the entities.

c. User interface model

It entails the development of screen sketches and sometimes the interface prototype.

2. Iteration Modeling

This is part of the Agile Requirement Modeling efforts performed at the commencement of the iteration. One often has to discover the necessities to a slightly more detailed level than the previous phase.

3. Model Storming

Comprehensive necessities also form part of agile requirements modeling. They are elicited in order to realize the Agile Requirements Modeling. A better way to realize it is to make sure the high- level requirements are analyzed in time. In case the developer has an innovative obligation to implement, they have to first ask themselves if they are familiar with what is being asked for.

4. Acceptance Test Driven Development (ATDD)

It is an evolutionary approach to the agile requirements modeling that requires substantial discipline and reliable tooling.

Levels of Acceptance Test Driven Development

1. Acceptance TDD

With ATDD, one ought to write a single acceptance test or behavioral measurement depending on the favored jargon. Then just check enough production functionality or code to accomplish the test.

2. Developer TDD.

It entails writing a solitary developer test known as a unit test.