After software requirements is identified or requirement engineering is done next step is to do requirement gathering is done from different stakeholders of the system to wirte different requirement documents of the ssytem.

Business requirements are documented in the business requirement document, it is very precise and small define two things.

Vision

Context diagram

Vision

Vision or scope of the ssytem is written , it is short and define overall scope of business is waht is achieve by the ssytem ,what are economic goal,what is done and provided by the ssytem,it is generally of tow or three paragraph.

Context diagram

Conyexy diagram in business requirement document defines the boundary of the system and external user of the ssytem. Scope is the center of the context diagram.

User requirement define requirement definition document or user requirement document m this document contains all diagran of the system that defines how user is interact with systemm what action are performed by the user and how action is is flow in the in system to reach to final action or function.









User requiremnt document uses use CASE (computer Aided Software Engineering) tool to represent user ineration to the system in pictorial form,Use CASE tool is part Of UML(Unified Modeling Language), it is globally accepted standard to ro represent user requirement in diagram

In use CASE tool hase following element

Actor

Use case

Flowline

Context

Actor

Actirs are all the user or stakehikder that interact with system, it is repsented by human icon or human dummy.

Context

Use case

use case or case reoresent a complete function in the system that user interact in the system, it is represented by oval or eclipse.









Flowline

Flow line line show connection between actor and use case.

Context

Context in Use CASE represented by big square defines boundary of the system all use case is surrounded by the context.

Related posts: