Scribd
Upload
692 views

Q1 What Is The of BA in Team Size and PR

A requirement is a characteristic that a system or component must have to satisfy a stakeholder's needs. There are two main types of requirements: 1. Functional requirements - Specify what a system should do. Examples include calculating loan interest, processing orders. 2. Non-functional requirements - Specify criteria that can be used to judge the operation of a system, rather than specific behaviors. Examples include usability, reliability, performance.

Uploaded by

Nikhil Kulkarni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
692 views

Q1 What Is The of BA in Team Size and PR

A requirement is a characteristic that a system or component must have to satisfy a stakeholder's needs. There are two main types of requirements: 1. Functional requirements - Specify what a system should do. Examples include calculating loan interest, processing orders. 2. Non-functional requirements - Specify criteria that can be used to judge the operation of a system, rather than specific behaviors. Examples include usability, reliability, performance.

Uploaded by

Nikhil Kulkarni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOC, PDF, TXT or read online on Scribd
You are on page 1/ 3

Q1)What is the % of BA in Team Size and Project Duration?

The BA s involvement in project is 12% to 16% in the team size i.e. 2 BA's in 12 to 13 team members
or 4 BA's in 24 to 25 team members.
The allocated time for BA for each project is 15% of the project i.e. 2 months time period in 1 year of
project.

Q2)What is the role of BA in a product development IT Company ?

In product development company BA's responsibilities are


a) first understand the product domain thrarolly
b) understand the product features
c) understand where product fits in to domain
d) understand clients requirements for the product
e) and study what all customizations are required for the product to fit into clients requirements

Q3. Explain Agile & Scrum Process?

Agile process
Agile means light so here agile means easy to model maintain and track. Agile process is used or
implemented when faster delivery is required. In agile no documentation is required since there is no
documentation customer retention is possible as there is no documentation code itself becomes the
documentation and SDLC life gets shorter by employing seasoned developers

Scrum process
Scrum process is used or implemented when project is falling behind the schedule. It is to get the
project on fastrack pace to reach the specified delivery time of the project. Here a scrum master
administrates the project with scrum team around 7 to 8 members team including developers technical
team and BA's scrum master resolves issues and gets the allocated work done in decided sprint, here
sprint is of 2 weeks but may get stretched to 4 weeks.

Q4) List all diagrams of UML and draw samples ?


Unified modeling language is used to specifying designing simplifying and understand the software
system. Thease are classified into

A) static diagrams
 use case diagrame

Q5)Explain Abstraction, encapsulation, polymorphism, Inheritance?

These steps are used to implement object oriented application

Abstraction:

abstraction means to filter out the properties and opportunities of the project until thr required one's are
remaining i.e. filtering out the required ones and ignoring the not required one's. It is most difficult task
to do for a modeler. The techniques used for this are

pareto principle-
80-20 or 20-80 technique where it is said that when 20% of the requriements are achived than 80% can
be achieved.

MVP-
Minimum value product

Gold plating-
It is the technique where making changes to the project outside the agreed scope. It takes time for
practice. It is used to enhance the product by adding extra features to it which were not asked by client
but to impress the client fot the same. It is vary rarely seen in practice.

Encapsulation

This is the information hiding technique, it is used to hide the complex internal structure or working of
the project.
In login system when we enter the submit button by entering userid & password it gets logeed in but in
background it follows commands to call the logged to in page only if the userid & password matched
this background hidden process is encapsulation.

Inheritance

whenever we have child class it inherits the parent class properties

Polymorphism

This means in simple language “one instruction-multiple operations”


sometimes single command can be used for multiple operations for ex. when we are shopping with
debit or credit cards we swipe at same swiping machine but the data will be sent to the concerned banks
.

Q6)what steps you follow to draw a use-case diagram from a Case study?

1) First we do not consider manual or physical action while drawing use-case.


2) No negative flow i.e. error or failure can be shown in use-case diagrams.
3) Information which we do not model in use case are
Names of the systems(laptops, desktops, workstations)
Databsase names( SQL server, DB2 etc.)
Networks(LAN WAN Internet)
Brand names(HP,INTEL,WIPRO,etc)
Technology names(Java,.net etc.)
4) different information against actions
5) Writing all the sequence of actions
6) find all the actors
7) finding out which action is performed by which actor
8) finding which is essential cases and supporting cases
9) identify the modules with respect to functionality or usage
10) draw the relationships between identified actors and use cases

Q7) Why MVC Architecture is used? What are MVC Rules in identifying classes? What guidelines
will you follow to place the classes on a three tier Architecture ? What are persistence and Transient
classes?

The Model-View-Controller (MVC) architectural pattern is used in software engineering to allow for
the separation of three common features of GUI applications

the data access (typically via a database)


the business logic (how the data will be used)
~ THE user interaction (how the data and actions will be visually presented)

MVC rules identifying the classes

1) combination of one actor and one use case result into one boundary class.
2) Combination of two actors and an use case result into two boundary class.
3) Combination of three actors and an use-case result into three boundary class.
4) Use case will result into controller class
5) each actor will result into entity class.

Guidelines to follow to place the classes on three tire architecture

1) Place entity classes on DB layer


2) Place primary actors associated boundray class in application layer
3) In governing body influence or re useability is there with any of remaining boundary classes,
place them on business logic layer, else place them on application layer.

Persistent class

Persistent classes in an application that implement the entities of the business problem.
It includes entity class.

Transient class

It includes boundary classes and controller classes

Q 8) What is a Requirement? How many types of requirements are there? Explain them with examples

You might also like