Functional testing is the testing of the features of the software which are necessary for software to work. It is conducted against business requirement.
Non-functional testing is the testing related to the behavior of the system. It includes load test, performance test, security test, usability test, reliability test and etc.
Functional testing content usually is pre-defined by user as the user knows what he/she wants the software to do. However, non-functional testing is difficult to summarized as user themselves are not aware of the non-functional requirements.
Non-functional test is normally conducted after functional test.
Showing posts with label Functional. Show all posts
Showing posts with label Functional. Show all posts
2017-04-17
Functional Document and Business Document
Asking the question about difference of fictional document and business document is similar with difference with function requirement and business requirement.
1. Both documents come into play at different stage.
Business requirement is developed by business analysis at early stage of project initiation.
Functional document is developed when business document is approved by client/stakeholders before software design phase.
2. Both documents contain different information for different audiences.
Business document contains business requirement at the standpoint of end user, such as client and customers.
Functional document, on the other hand, contains technical requirement for architects and developers. These requirements are the baseline that developers design, implement software based on.
3. Both documents serves same purpose
Both business and functional documents are created to ensure the quality of delivery software/programme/products.
Business analyst create business document so that client's requirements are fully covered.
Business analyst create functional document so that team members such as development team and testing team understand the requirement in technical term, so that the final product will not be deviated from original design.
1. Both documents come into play at different stage.
Business requirement is developed by business analysis at early stage of project initiation.
Functional document is developed when business document is approved by client/stakeholders before software design phase.
2. Both documents contain different information for different audiences.
Business document contains business requirement at the standpoint of end user, such as client and customers.
Functional document, on the other hand, contains technical requirement for architects and developers. These requirements are the baseline that developers design, implement software based on.
3. Both documents serves same purpose
Both business and functional documents are created to ensure the quality of delivery software/programme/products.
Business analyst create business document so that client's requirements are fully covered.
Business analyst create functional document so that team members such as development team and testing team understand the requirement in technical term, so that the final product will not be deviated from original design.
2017-04-05
Key Benefits of Agile Methodology
Agile Methodology refers to set of principles of software development under which requirements and solutions evolved through small iterations.
Key benefit of using Agile methodology is:
Ability to change
In agile model, list of requirements are created as to-do list for the project, and during each iteration/sprint, several requirement will be implemented. Normally one iteration would be 2-4 week time. Therefore if customer/client asks for requirement change, it could be quickly implemented or revised during next sprint/iteration.
Fast delivery
Each iteration/delivery will come up with a demo to demonstrate what has been implemented to customer/client instead of waiting for few month as in waterfall model.
Tight team collaboration
In agile model, there is only one scrum master in charge of requirement management and the team members work closely with each other. The role of each member is not fixed as in waterfall model. One can be a tester if the other tester is not available.
Low risk
Because of small iterations to implemented certain requirements. Feedback from customer/client is constant therefore the team is pretty sure that they were working at the right direction.
Key benefit of using Agile methodology is:
Ability to change
In agile model, list of requirements are created as to-do list for the project, and during each iteration/sprint, several requirement will be implemented. Normally one iteration would be 2-4 week time. Therefore if customer/client asks for requirement change, it could be quickly implemented or revised during next sprint/iteration.
Fast delivery
Each iteration/delivery will come up with a demo to demonstrate what has been implemented to customer/client instead of waiting for few month as in waterfall model.
Tight team collaboration
In agile model, there is only one scrum master in charge of requirement management and the team members work closely with each other. The role of each member is not fixed as in waterfall model. One can be a tester if the other tester is not available.
Low risk
Because of small iterations to implemented certain requirements. Feedback from customer/client is constant therefore the team is pretty sure that they were working at the right direction.
How and why do we tag the complexity and severity to a defect?
Prioritizing defects by assigning complexity and severity is good for defect management.
Not all defects need to be rectified immediately and not all defects affect the proper function of software, there might be walk around to avoid certain defect before it is rectified.
Prioritized defect will help developers to focus on the urgent defect which hinder the quality of software within schedule timeline, and also for proper planning.
2017-04-02
Defect Management
The life cycle of a defect can be summarized as follow:
When a defect is reported during software development process, it is usually logged by tester into bug tracking system or defect management system. The earlier the defect is rectified, the less cost it could bring to project.
Defect management is the practice of managing defect throughout its life cycle with collaboration of multiple teams aiming at improving software quality by defect detection and defect prevention.
Subscribe to:
Posts (Atom)
Setup VNC on Ubuntu 20.04
sudo apt update sudo apt install xfce4 xfce4-goodies sudo apt install tigervnc-standalone-server sudo apt install tightvncserver vncserver...
-
Java学习路线排列 第一部分:JavaSE-筑基、结丹Java零基础教程视频(适合Java 0基础,Java初学入门) https://www.bilibili.com/video/BV1Rx411876f 数据结构与算法_适合零基础学习数据结构与算法 https://www...
-
sleep 10 && xset dpms force off ps -aux sudo lsof -i:3389 ssh -L 3389:localhost:5900 -C -N -l rocky localhost sudo iptables -t nat -...
-
sudo apt update Chrome https://www.google.com/chrome/ DoubleCommand sudo apt install doublecmd-gtk qbittorrent sudo apt-get update &...

