What is agility method? What types of problems with our requirement practice? How is Actor? Explain with diagrams.

Definition of agility method:

Agility method is define as: The rapid and adaptive or effective response of changing and effective communication between all stockholder is called agility method.


Explanation of agility: 

Agility method is most use able method when describing the software method.            Agility method increase the delivery time of software to buyers.       Because it is iterative model.                                                               Main point of this method is that it organizing the team so that is control the workflow. Agility is applied to any software, however its essential that work of software must be in manner so its enable the team to adapt the task and control or modify it.


Principle of agility process: 

First thing is to satisfy the the customers and continuous delivery of valuable software.

Requirements can be change according to customers.  

Developers must work together through out the whole project. 

It promote sustainable development 

Attention and good design enhance the agility 


Example of Agility method :

Scrum 

Extreme programming 

Adaptive software development 

Lean software development


What types of problems with our requirement practice?

Requirement engineering:

It is systematic way of developing requirements through iterative process of analyzing a problem documenting the resulting observations. There are many problems with requirement practice which are given below: 


Trouble understanding:

Sometime we have trouble understanding of requirement which are given by customers. May be we do not properly understand problem due to leak of knowledge or may be customers does not explain in proper manner.


 Disorganized manner:

We often record requirements of customers in disorganized manner. That’s why we feel problems when we start to begin our customers project. we have to note down all requirements in organized manner.


Mechanism of control change: 

Control change is important for requirements . we allow to change to us we have not to change in requirements by establishing the mechanism of control change. 


Solid foundation:

Solid foundation is important for requirements engineering ,we have to follow the solid foundation. Sometimes we fail to establish solid function so we face problem in requirements practice. 


Attention of worker:

Bottom line worker producing working program is important and else are secondary. If they do not pay heed on this then they will face problems in requirements practice. 


Argue of software developer:

Sometimes software developer make a different argue during software production. With passage of times or day software grows and become complex and then all argue of software developer break down and then software project lead to failed.


Low understanding project stockholder: 

When project stockholder has less understanding what they need. Stockholder has able to better understand after early iteration of software.


How is Actor? Explain with Diagram Definition of Actor: 

Actor is the component the of use case diagram The person or user that interact with system or project by using use case is called actor.

Actor may be:

Person                                                                                                   Organization                                                                                        An outside system                                                                                External hardware Who interact with application or software


Explanation of actor: 

Actor do not represent any physical entities but particular facts such as role. Actor must be associated with one use case diagram and actor also associated with multiple use case diagram. And actors are not part of the system, i.e., they are outside of the system boundaries. Actor interact with system by use case using solid line. 


Types of Actor: 

Human                                                                                                                            Database systems                                                                                Client and Server                                                                                    Cloud platforms                                                                                    Sensors


Example: 

Let we take example of website and now we can define a actor in it by diagram. Here is new blog website where one side of website is admin side and other side of website is user side. Both admin and user behave like a actor.


Another example of actor we can take here Hera is the user of bank how can add fund withdraw fund open account and close account. So customer is behave like a actor.