IT Business Analyst Glossary - A
Analysis
Analysis
Analysis is detailed examination of components or structure of something.
So as a business analyst if you are given a problem to analyse : 1) Look up at the structure or the issue or problem 2) Breakup the issue or problem into components. For e.g components of a business process are the process steps. 3) Understand the requirement or objective of your analysis 4) Come up with a viable solution
So as a business analyst if you are given a problem to analyse : 1) Look up at the structure or the issue or problem 2) Breakup the issue or problem into components. For e.g components of a business process are the process steps. 3) Understand the requirement or objective of your analysis 4) Come up with a viable solution
Analytics
Analytics the systematic computational analysis of data or statistics. The objective of analytics is to arrive at information, insights , actionable insights from the data which is analysed.
analysis vs analytics
Analysis can have both qualitative and quantitative focus, where as analytics invariably deals with large data sets.
IT Business Analyst Skill Set : Requirements Process, Domain Skills, Skills in softwares like Visio, Balsamiq, Jira, Bizagi, Word, Excel, PPT, Axure
Business Analytics : Statistics and Quants. Skills in software like SAS, R, Matlab etc
IT Business Analyst Skill Set : Requirements Process, Domain Skills, Skills in softwares like Visio, Balsamiq, Jira, Bizagi, Word, Excel, PPT, Axure
Business Analytics : Statistics and Quants. Skills in software like SAS, R, Matlab etc
association relationship (UML)
An actor in a software system has got several goals. These goals are Use Cases of the system. If an actor A can carry out Use Cases say 2,3 and 6 in the system then there exists association relationship between Actor A and Use Cases 2,3 and 6. The notation for Use Case relationship is a straight line.
axure (Software)
Axure is an expert solution for software prototyping. Prototypes are software models which posses interactivity. Prototyping is a proven and popular Requirements development and Requirements validation technique.
activities (UML Activity diagram)
In UML or Unified modelling language the processes or workflows are captured or modelled through Activities or UML Activity Diagram. Activities are thus the visual of the entire process.
action (UML)
Individual step in an Activities model is called an Action. Beware between the difference between the word action and activities. Lets say we prepare an Activity model for a ticket booking process. Individual steps in the process are select train, provide passenger details, make payment etc. So an individual step of the process say provide passenger details isan Action and the whole process is called as an Activity
analyst
A person who conducts analysis or IT business analysis is called an analyst
actor (UML)
Actors interact with our system or subsystem in question. Actors can be human or non-human (other software, hardware or device which interact with our system.
Agile methodology
Agile is a popular software development methodology. It is governed by Agile Philosophy (4 points) and Agile Manifesto (12 points) . Agile is an iterative software development methodolgoy. Various variations of Agile software development methodology are SCRU, DSDM, Kaanbaan etc
agile philosophy
There are 4 points in Agile Philosophy they are
1) Individual and Interactions are important over Process and tools
2) Working Software over comprehensive documentation
3) Customer Collaboration over Contract Negotiation
4) Responding to change over following the plan
Would you like to feel and live the points of agile philosophy http://agilemanifesto.org/
1) Individual and Interactions are important over Process and tools
2) Working Software over comprehensive documentation
3) Customer Collaboration over Contract Negotiation
4) Responding to change over following the plan
Would you like to feel and live the points of agile philosophy http://agilemanifesto.org/
aris modeller (Business process modelling software)
Answer to question 11
acceptance and evaluation criteria
Answer to question 12
alfred chandlers strategy triology
artifacts (BPMN)
Artifacts are one of the five BPMN elements. Artifacts in BPMN or Business Process Model Notation are Group and Text Annotation. A Group allows us to group a portion of a BPMN model. The notation of a Group in BPMN is a rectangle with dashed lines. Group can cross boundaries of a lane and a pool. Text Annotations are used to provide additional details to a BPMN diagram. These are comments which are attached to other elements of the BPMN model via Association notation.
action point
A / B Test
automation
Software Automation aims at automating all the phases of Software Development Lifecycle ie Analysis, Design, Development, Testing and Implementation.
Automation in development : Examples of automation in software development are plug and play services or software available in the cloud which can be integrated with software being built or modified. Other example can be generation of source code and creation of underlying software schema by Business Process Modelling Software when we prepare a Business Process Model
Automation in testing : Software test automation has gained
Automation in development : Examples of automation in software development are plug and play services or software available in the cloud which can be integrated with software being built or modified. Other example can be generation of source code and creation of underlying software schema by Business Process Modelling Software when we prepare a Business Process Model
Automation in testing : Software test automation has gained
Question 18