Recent Posts

Pages: 1 ... 3 4 [5] 6 7 ... 10
41
Business Analyst Concepts Discussion / Re: Relationships in Use Case diagram
« Last post by 12125148309 on January 19, 2022, 12:51:55 pm »
1.   Association
(i)   Unary-Has one way relationship
(ii)   Binary- has two way relationship
(iii)   Multiplicity-It tells the number of objects in one class that relate to a single object of the associated class.
(iv)   Reflexive-Reflexive association happens when a class has objects that play a variety of roles

2.   Generalization-
A relationship that exists between generalized class and specialized class. Eg-humans and animals both living beings.

3.   Aggregation- It is the ?parts? and its ?whole? relationship. Even if the whole dies the part remains. We can take an example of the assembled computer system at our home.
4.   Composition- It is the parts and its whole relationship. The part also dies along with whole.
It is a strong type of aggregation.  Each component of aggregation can belong to just one whole.
The tabletop and the legs  are the component of the coffee table which make up the composite.
42
  Elicitation Techniques in Business analysis

1.   Brainstroming
2.   Document analysis
3.   Reverse Engineering
4.   Focus Groups
5.   Observation
6.   Workshop
7.   JAD (Joint Application Development) ? Requirement Workshop
8.   Interview
9.   Prototyping
10.   Questionnaire
43
Business Analyst Concepts Discussion / Different documents used in a Project?
« Last post by 12125148309 on January 19, 2022, 12:43:58 pm »
1.   Project vision Document
2.   Business Analysis Plan
3.   Business Requirements Document
4.   Functional requirement specification (FRS)/ Functional Specification Document (FSD)
5.   System requirement specification (SRS)/ System Requirement Document (SRD)
6.   Requirement traceability matrix (RTM)
7.   Use Case Diagrams
8.   Change Request Document
44
Business Analyst Concepts Discussion / Re: use case actors
« Last post by 12125148309 on January 19, 2022, 12:41:28 pm »
ypes of actors used in use case diagram:








1)Primary/principle Actor: People who use the main system functions are refereed as primary or principle actors. Example: in ATM system primary actor is customer

2)Secondary Actor: People who perform administrative or maintenance task are referred as secondary actors. It provides a service to the system under design. Example: in ATM system a person in charge of loading money into the system is a secondary actor.

3)External actor: The hardware devices which are required as apart of application domain and must be used are referred as external actors. Example: in ATM system printer is an external actor.

4)Other system actor: The other system with which the system must interact referred as other system actors.Example: in ATM system bank network system is another system actor.
45

   How we draw a usecase diagram from a case study?

1.   Information which should not model are name of the system. Architectures, data base names, Network, Brand Names, Technology
       Names
2.   Differentiate information against actions
3.   should write all sequence of actions
4.     should find out which actor is performing which action
5.   should identify Essential Use Cases and Supporting Use Cases
6.   should find out some modules with respect to functionality
7.   should draw the relationships appropriately between the identified actors and Use Cases
46
Business Analyst Concepts Discussion / Re: Scrum
« Last post by 12125148309 on January 19, 2022, 12:39:17 pm »
Scrum is an agile development methodology used in the development of Software. Scrum is adaptable, fast, flexible and effective agile framework that is designed to deliver value to the customer throughout the development of the project. The primary objective of Scrum is to satisfy the customer?s need through an environment of transparency in communication, collective responsibility and continuous progress. The development starts from a general idea of ​​what needs to be built, elaborating a list of characteristics ordered by priority that the owner of the product wants to obtain.
47
Business Analyst Concepts Discussion / Re: use case actors
« Last post by 12111163010 on January 19, 2022, 12:28:04 pm »
 Use case actors

1.   Actors is a living or non-living thing.
2.   Actor is represented by a noun.
3.   Actor always stay away from the system boundary
4.   Primary actor imitates the system to work 
5.   System depends on secondary actor for information.
6.   All reusable actors should be placed towards the right side of the system boundary.

48
Business Analyst Concepts Discussion / Re: Business Analysis???
« Last post by 12111163010 on January 19, 2022, 12:16:15 pm »
   
   Business Analysis is a disciplined approach for introducing and managing change to organizations, whether they are for-profit businesses, governments, or non-profits. business analysts, identify and define the solutions that will maximize the value delivered by an organization to its stakeholders.
49
Business Analyst Concepts Discussion / Re: Agile methodology
« Last post by 12111163010 on January 19, 2022, 12:12:26 pm »
          Agile methodology is a type of project management process, mainly used for software development, where demands and solutions
   evolve through the collaborative effort of self-organizing and cross-functional teams and their customers.

            Four values of Agile

           individuals and interactions over processes and tools
           working software over comprehensive documentation
           customer collaboration over contract negotiation
           responding to change over following a plan.
50
Business Analyst Concepts Discussion / Re: Qualities of Good requirement
« Last post by 12111163010 on January 19, 2022, 12:06:54 pm »
   Qualities of Good requirement

        A good requirement can be functions, constraints or other elements that must be present to meet the needs of the intended stakeholders. A good requirement described as a condition or capability a customer needs to solve a problem or achieve an objective. For clarification purposes, a descriptor should always precede requirements for example business requirements, user requirement and functional requirements .
Pages: 1 ... 3 4 [5] 6 7 ... 10