I wonder this SRS documentation for a project I made years before can make the cut to get a job as a Software Requirement Analyst.
Farahin Musa’s Post
More Relevant Posts
-
Why Software Testing Matters for Quality Assurance In software development, testing is essential for delivering reliable and high-quality products. Here’s why testing is a critical part of the process: ✅ Defect Prevention: Fixes issues early to avoid costly errors ⚖️ Quality Assurance: Ensures software meets all standards 😊 User Satisfaction: A well-tested product means happier users 📉 Risk Mitigation: Reduces risks like financial or reputational loss Dive into our latest blog on Software Testing to learn more👉 https://lnkd.in/gNbYVtx3
To view or add a comment, sign in
-
-
🔍 Why Domain Experience Matters in Software Testing 🤔 Companies seek with domain knowledge for specific reasons. Here's why it's important: 1️. Understanding Industry: Domain expertise helps testers grasp unique industry challenges, making software testing more effective. 2️. Faster Testing: Testers with domain experience can quickly identify critical testing areas, leading to efficient bug detection. 3️. Higher Quality: Domain knowledge helps anticipate user needs and issues, resulting in better software quality. 4️. Client Satisfaction: Companies value domain expertise as it aligns testing with client expectations, boosting satisfaction. Let's boost our testing skills with domain knowledge!
To view or add a comment, sign in
-
All the different artifacts in software delivery 😮💨 I'm sure there's some I have missed. Each of these could introduce problems. This is why collaboration and peer review is important throughout the entire process. Requirements - product, business, technical, acceptance criteria Design documents - architecture, database, system, UI, API, data flow diagrams, integrations Developments - source code, build scripts, config files, logs Testing - strategies, plans,, test summary reports Deployment - release notes, rollback procedures Operation and maintenance - monitoring dashboards, logging, incident reports, operational runbooks, disaster recovery, support Documentation and knowledge - API documentation, User manuals, Risk management(process)
To view or add a comment, sign in
-
🚀 New Blog Post Alert! 🚀 Ever wondered how to ensure your software meets the real-world needs of users? Dive into my latest Medium article on User Acceptance Testing (UAT) and discover best practices, common challenges, and how to overcome them. Your insights and feedback are welcome! https://lnkd.in/dn6xd9p4
To view or add a comment, sign in
-
Testing talks about the presence of defects and don’t talk about the absence of defects. The testing process does not guarantee that software is 100% error-free. Even if testers cannot find defects after repeating testing, it does not mean the software is 100 % bug-free. 🐞
To view or add a comment, sign in
-
-
In order for a mistake to affect many customers, all of the following need to happen: The developer codes the bug. The code reviewer(s) miss it. The unit tests miss it. The integration tests miss it. The monitoring misses it in the canary rollout. The monitoring misses it in the production rollout, doesn't roll it back quickly or the roll back fails.
To view or add a comment, sign in
-
What is the difference between defect priority & severity, give examples? • Defect priority is the order in which a defect should be fixed. Higher the priority the sooner the defect should be resolved. • Defect severity is a degree of impact a bug or a Defect has on the software application under test. A higher effect of bug/defect on system functionality will lead to a higher severity level. • Order of priority: 1. High priority – High severity 2. High priority – Low severity 3. Low priority – High severity 4. Low priority – Low severity • High Priority & High Severity: Submit button is not working on a login page and customers are unable to login to the application • Low Priority & High Severity: Crash in some functionality which is going to deliver after couple of releases • High Priority & Low Severity: Spelling mistake of a company name on the homepage • Low Priority & Low Severity: FAQ page takes a long time to load
To view or add a comment, sign in
-
SA schools IT project runs $47m over budget! https://lnkd.in/gmvtcGqa The downloadable report makes for interesting reading... ⏺ Vendor oversold and underdelivered on both product & services? - ✅ ⏺ Poor scope capture leading to a blowout of change requests? - ✅ ⏺ Less than 50% of functionality working correctly in Prod? - ✅ ⏺ 80% of users experiencing issues with data migration? - ✅ ⏺ Less than 50% approval rating from users? - ✅ ⏺ Around 500 open defects now in Prod? - ✅ ⏺ Decreased Task efficiency? - ✅ ⏺ Inadequate staff training? - ✅ ⏺ Nearly $50m over budget? - ✅ Unfortunately this is an all too common story, if you've ever worked on large scale IT projects you only have to read the first page of this story to know how it ends. The best time to engage Testers is before choosing your product (static testing anyone?)....the second best time is now.
To view or add a comment, sign in
-
-
🔍 𝐖𝐡𝐚𝐭 𝐃𝐨𝐞𝐬 𝐚 𝐒𝐲𝐬𝐭𝐞𝐦 𝐀𝐧𝐚𝐥𝐲𝐬𝐭 𝐃𝐨? 🔍 As a System Analyst, I bridge the gap between IT and business ensuring technology solutions align with organizational goals. My role involves: ✔️ Analyzing Requirements: Understanding business needs and translating them into technical specifications. ✔️ Designing Solutions: Crafting system designs and recommending software and hardware improvements. ✔️ Testing and Evaluation: Ensuring systems function properly through rigorous testing and feedback loops. ✔️ Collaboration: Working with stakeholders, developers and users to optimize performance and efficiency.
To view or add a comment, sign in
-
Required data for Test Matrix : 1) Number of requirements 2) Average Number of test cases written per requirement 3) Total Number of test cases written for all the requirements 4) Total Number of test cases executed 5) Number of test cases passed 6) Number of test cases failed 7) Number of test cases blocked 8) Number of test cases un executed 9) Total Number of defects identified 10) Critical defects count 11) Higher defects count 12) Medium defects count 13) Low defects count 14) Customer defects 15) Number of defects found in UAT
To view or add a comment, sign in