Values of Agile Modeling

The five values of Agile Modeling (AM) are:
1.Communication : Models promote communication between your team and your project stakeholders as well as between developers on your team.
2.Simplicity : It’s important that developers understand that models are critical for simplifying both software and the software process—it’s much easier to explore an idea, and improve upon it as your understanding increases, by drawing a diagram or two instead of writing tens or even hundreds of lines of code.
3.Feedback : Kent Beck says it best in Extreme Programming Explained: “Optimism is an occupational hazard of programming, feedback is the treatment.” By communicating your ideas through diagrams, you quickly gain feedback, enabling you to act on that advice.
4.Courage : Courage is important because you need to make important decisions and be able to change direction by either discarding or refactoring your work when some of your decisions prove inadequate.
5.Humility : The best developers have the humility to recognize that they don't know everything, that their fellow developers, their customers, and in fact all project stakeholders also have their own areas of expertise and have value to add to a project. An effective approach is to assume that everyone involved with your project has equal value and therefore should be treated with respect. Huet Landry suggests the concept of "Other Esteem", instead of "Self Esteem", where you treat the opinions of others as if they have more value than yours. With this approach your first reaction to another's idea will be most positive.

Difference Between Authorization And Authentication

Authentication is the process to test whether the specific user is allowed to use or login to the application.

And

Authorization we test whether the specific user allowed to access some controls or features of the system/application/software.

Eg: In an office automation tool, every employee can login to the application, but only accounts manager can access accounts related features, only HR manager or executive can access company information

Severity And Priority

Severity
1. The Severity status is used to explain how badly the deviation is affecting the build.
2. The Severity type is defined by the tester on the written test cases and functionality.

Ex : If an aaplication or a web page crashes when a remote link is clicked,in this case clicking the remote link by an user is rare but the impact of application crashing is severe,so the severity is high and priority is low.

Priority
1. The Priority status is set by the tester to the developer mentioning the time frame to fix a defect.If High priority is mentioned then the developer has to fix it at the earliest.
2. The priority status is set based on the customer requirements.

Ex : If the company name is misspelled in the home page of a website, then the priority is high and the severity is low to fix it