i have a project which should consist of functional and non functional requirements of any job portal kindly help me completing it

functional requirements and nonfunctional requirements for online job portal

Functional requirements define what the product should do. They are actions that a product must fulfill in order to meet the basic reason for its existence. Think of the functional requirements of both business requirements. That is, if you talk to a person or a business, they will describe what the product should do in order to complete some of their work. Keep in mind that the specification requirements of the contract will be the product to be built. Thus, the functional requirements shall describe fully the steps that the desired product can perform. I also associate it with a product you can buy in the store - if you look at the list of features of the bullets on the back side of the box, he describes the functionality of the product.

Non-functional requirements are properties that your product must have. Think about these properties, as the characteristics or qualities that make a product attractive or useful, or fast or reliable. These properties are not required, as they are the main directions of activity of the product - activities such as computing, data manipulation, and so on - but there, because the customer wants to core activities to perform in a certain way. They are not part of the main reason for the existence of the product, but are necessary to make the product perform as desired.

Non-functional requirements do not change the functionality of the product. That is, the functional requirements remain the same, no matter what properties you attach to them. The non-functional requirements to add product functionality - it takes a certain amount of clicks to make a simple product to use, or safe, or interactive. However, the reason that this functionality is part of the product to give it the desired characteristics. Thus, you can think of functional requirements, such as those doing the work, and non-functional requirements, such as those that give the nature of work.

Non-functional requirements account for a large part of the specification. They are important, as a client, and the user can judge the good product in its non-functional properties. Provided that the product complies with the necessary amount of functionality, non-functional properties - how to use, comfortable, inviting and secure it - can be the difference between the received, well-liked product, and unused.

Let's look at another real-world example. Anyone who has bought a car, whether they were aware of it or not, has made its final decision, on the basis of which the vehicle met their functional and nonfunctional requirements. Functionally, the car had to be able to carry passengers from an initial position to a particular destination (ie, to get me from point A to point B). A variety of non-functional attributes or characteristics are likely to have been considered: safety and security, maintainability (simple repairs), reliability (probability of failure), scalability (ease of expansion), the efficiency and productivity (gas mileage, engine size, power - both in the number of passengers and cargo space), mobility (ease of transportation - it can be towed easily and can tow a trailer), flexibility (easy to change - it can adapt to changes in the weather / road conditions) and usability (ease of use - comfort, control, stereo sound quality).