 Software – Requirements Flow |
| Let’s get started Requirements Flow: Everyone is aware that the application is designed for end users based on the customer requirements. But, only few people are aware that there is lot of process that draw the customer requirements into different layers before converting / designing into an application. Here is the explanation. Just have a look at the diagram. More information with regards to the Requirements Flow could be added to the table at the later editions. |
| |
| Requirement: The basic customer needs are called as Requirements. The set of all customer needs put together is called requirements document or marketing requirements document. |
| |
| BRS (Business Requirement Specification): · At Business level, all the customer requirements are documented , designed and approved by customer. · All these bossiness requirements should exactly map to end user real-time scenarios FRS (Function Requirements Specification): The BRS are segregated into different Functions / Modules and are described in more detailed and such that more detailed information is provided with respect all the functions / modules of the application. |
| SRS (Software Requirement Specification): In depth of the requirements, such as the detailed information like windows / dialog boxes information, field level information and Just as clear-cut document for coding and prototypes are called as SRS |
| SRS (System Requirement Specification): The entire SRS (Software Requirement Specification) are merged together so as to make complete System approach is called System Requirement Specification |
| Use Cases: Use Case is a document that describes the User actions versus System / Application responses |
| |
QA – Introduction To Testing |
Let’s get started You would be able to learn the following, at the end of this chapter o What are the advantages of Testing? o How do we Test? o Who are needed Testing? o What is a Defect / Bug? o Explain in detail about Testing Process Introduction to Testing o Testing is the process of executing a program with the intention of finding errors o Testing is the process of verifying an application to check if the application is behaving as per the requirements / specifications. o Testing is the process of executing test cases on the application to differentiate between expected and actual results. o Testing is the process of V and V ( Verification and Validation) o Testing is obviously concerned with finding bugs, defects, errors, faults, failures and incidents with the applications. o Testing is the process of verifying customers’ needs with respect of the designed software/application o Testing is the combined process of Analyzing / Understanding the Reqs, Designing Test Cases, Executing Test Cases, Reporting Test Status, Supporting Application You can learn the following:
|
Let’s go on… |
What is Software : o Software is a set of programs o Software represents the process of transforming BRS into FRS , FRS into SRS and SRS into Application o Software is the designed application or program that resembles the customer requirements What is a Program : o Program is a set of instructions that performs some action |
Why do we need Testing : § For Customer Satisfaction § To give a QUALITY Project to Customer § > Bug Free § > On Time § > Process Followed § Dev team thinks in point of code, loops, conditions (Structural testing) § There should be someone else to Validate the App (Tester, QA) § Tester is a mediator between Dev and Customer § Tester thinks in point of Customer o External Focus o Functional Tests o No Code at all § Tester thinks in point of Functional approach o Benefits of Testing. o Consistent and Accurate Quality of Software / Project o Cost Effective and Efficient Process o Reduces Overall Development Cycle Time o Process Oriented o Gain Customer Satisfaction o Retains company’s name and fame |
Why does software have defects in it.. : o Poor Requirements (Unclear Reqs) o Programming errors o Software complexity o Changes in Requirements o Time pressure o Inefficient Dev (Poorly coded modules) o Poor Management o Poor Documentation o Poor Quality Assurance o Other reasons |
When do we start Testing : • Right from the beginning of the Requirements • Reqs / BRS / SRS / Use Cases / wire frames are clear / understandable / testable / transformable into application • When Test Plan, Test Cases , Test Environment is ready • When Application is ready , stable and is in our QA hands |
When do we stop Testing : • Reqs / BRS / SRS / Use Cases / wire frames are covered in the Application and are working fine • Application is bug free • When Quality Indicators, QA Metrics represent the 100% quality of the application • Application is handed over / delivered to Client/ Customer • Maintenance / Support is successful
| |||||||||||
Posts
All Comments
