1. CONCEPTS OF BA
1.1. **1📍 Activities**
1.1.1. Understanding enterprise problems and goals
1.1.2. Analyzing needs and solutions
1.1.3. Devising strategies
1.1.4. Driving changes
1.1.5. Facilitating stakeholder collaboration
1.2. **2📍 Responsibilities**
1.2.1. Turn customer's ideas into documented requirements -> used by: designer, tester, project manager...
1.2.2. Know product better than the customers
1.2.3. Understand customer's busines -> figure out the best solution for customer
1.2.4. Provide support in review activities
1.3. **3📍 Skills**
1.3.1. 🗣 Soft skills
1.3.1.1. Eliminating distractions
1.3.1.2. Attentive posture and eye contact
1.3.1.3. Restating key points to confirm your understanding
1.3.1.4. Verify new information against existing information
1.3.1.5. Detect contradictions, uncertainty, vagueness, and assumptions...
1.3.1.6. Interviewing and questioning
1.3.2. 🧠 In-depth skills
1.3.2.1. Analytical Skills
1.3.2.2. Systematic thinking
1.3.2.3. Observation skills
1.3.2.4. Creativity
1.3.2.5. Modelling skills: Flowchart, data flow diagram, entity-relationship diagram, UML
1.4. **4📍 Customer's Perspective**
1.4.1. 🔟 Rights
1.4.1.1. 1️⃣ Expect BAs to speak your language
1.4.1.2. 2️⃣ Expect BAs to learn about your business and your objectives
1.4.1.3. 3️⃣ Expect BAs to record requirements in an appropriate form
1.4.1.4. 4️⃣ Receive explanations of requirements practices and deliverables
1.4.1.5. 5️⃣ Change your requirements
1.4.1.6. 6️⃣ Expect an environment of mutual respect
1.4.1.7. 7️⃣ Hear ideas and alternatives for your requirements and for their solution
1.4.1.8. 8️⃣ Describe characteristics that will make the product easy to use
1.4.1.9. 9️⃣ Hear about ways to adjust requirements to accelerate development through reuse
1.4.1.10. 🔟 Receive a system that meets your functional needs and quality expectations
1.4.2. 🔟 Responsibilities
1.4.2.1. 1️⃣ Educate BAs and developers about your business
1.4.2.2. 2️⃣ Dedicate the time that it takes to provide and clarify requirements
1.4.2.3. 3️⃣ Be specific and precise when providing input about requirements
1.4.2.4. 4️⃣ Make timely decisions about requirements when asked
1.4.2.5. 5️⃣ Respect a developer's assessment of the cost and feasibility of equirements
1.4.2.6. 6️⃣ Set realistic requirement priorities in collaboration with developers
1.4.2.7. 7️⃣ Review requirements and evaluate prototypes
1.4.2.8. 8️⃣ Establish acceptance criteria
1.4.2.9. 9️⃣ Promptly communicate changes to the requirements
1.4.2.10. 🔟 Respect the requirements development process
2. **SOFTWARE DEVELOPMENT TASKS: CONCEPTS**
2.1. **1📍 Requirements Specification**
2.1.1. Enables businesses and their software development teams to better understand exactly what features customers are looking for
2.1.2. Conduct extensive customer research and analysis
2.1.3. Deliver that information into a list of exact software features that performs exactly what customer needs
2.2. **2📍 Data Modelling**
2.2.1. Represents data with diagrams, symbols, or text to visualize the interrelation
2.2.2. Process of simplifying the diagram or data model of a software system
2.2.3. Expressing data and information through text and symbols
2.3. **3📍 UI Design**
2.3.1. Process designers use to build interfaces in software, focusing on looks or style
2.3.2. Designers aim to create interfaces which users find easy to use and pleasurable
2.4. **4📍 Implementation**
2.4.1. Where software design is translated into the source code
2.4.2. 📱UI Implementation
2.4.2.1. the process of programming UI design
2.4.2.2. writing code for images, animations, sliders, text fields, buttons, etc
2.4.3. ⚙️ Backend Implementation
2.4.3.1. Server-side web application logic and integration and activities, like writing APIs, creating libraries, and working with system components
2.4.3.2. Building code that allows a database and an application/module to communicate with one another
2.5. **5📍 Testing**
2.5.1. Source code will go through a number of tests, including functional and non-functional ones, such as system, integration, unit, acceptance, etc
2.5.2. If a test reveals an error, bug, or any other issue, that needs to be fixed
2.6. **6📍 Management**
2.6.1. Project management
2.6.2. Technical management
2.6.3. Quality management
2.6.4. Budgeting management
2.7. **7📍 DevOps**
2.7.1. Development and operations: a collaborative or shared approach to the tasks performed by a company's application development and IT operations teams
2.8. **8📍 Documenting**
2.8.1. Written text or illustration that provides information about an application or other software product
2.8.2. Including user manuals, technical manuals, online help files, and API documentation
2.8.3. Created by technical writers and developers; designed to be clear, concise, and accurate
2.9. **9📍 Deployments**
2.9.1. Stages of installing, configuring, and testing a software application to prepare it for operating in a specific environment
3. **REQUIREMENTS ENGINEERING: 5W1H**
3.1. ❓ **What**
3.1.1. To develop explicit requirements specification that is agreed on by all stakeholders
3.2. ⁉️ **Why**
3.2.1. Without an accurate description of the system under development, no system can be developed
3.2.2. If you handle them in a systematic way, you understand the customer's problem and can then develop the best solution
3.3. 🧭 **Where**
3.3.1. Work with customer
3.3.2. Work with developers
3.4. ⏰ **When**
3.4.1. First phase of software development
3.5. 🔎 **How**
3.5.1. Elicitation
3.5.2. Analysis
3.5.3. Specification
3.5.4. Validation and Varification