There are several ways to cover a cat so that differentiation between user needs and functional requirements can be done in different ways. We can say that user requirements – as defined – are used to determine most of the functional requirements. If you build a software or web site, you can define user needs as the tasks or "things" that users want to achieve, and functional requirements may have software or system features that allow users to
user needs are organizational strategic goals, government-imposed regulation (eg, compliance with section 508), external environment, etc. can be controlled. he does a lot of work in formulating the scope of the project. The steps taken to define the powers and ensure that all interested parties clarify it is complex. To this end, many techniques may be used, as described in this article.
Keep the system away for a minute and study this very simple example: Mr. and Mrs. Jones live in a one-bedroom house and she was very happy to find out that Mrs. Jones was expecting a baby. Mr and Mrs. Jones realize that their one-bedroom house no longer meets their future needs, so they decide they're looking for a bigger house. Do you see Mr and Mrs Jones's needs? In the corporate world, the need to create a project can be affected by a competitor who uses another type of technology to generate more profits. This factor you can not control may require a new project to update the system.
If the necessity of a new house has been identified, Mr and Mrs Jones's work comes to identify what kind of home would satisfy their needs. The following thought process / technique is used:
Determine what the new house wants to do to them; the new house must comply:
- They love their privacy and do not have to share a room with their children
- I want to protect antique furniture from pencils, paint, etc.
- They like to play with the child when they are older
- They want the child to have access to good school
- They want security for their children
- They want to live near a supermarket or a pharmacy
- They want to live near a hospital.
This is a big, but incomplete list of the above demands for Mr. and Mrs. Jones's requirements / needs. To bring this back to building a software system, you can use the same technique to identify the user's needs. After Mr. and Mrs. Jones have completed their needs, refine their lists by eliminating what they can from the list, creating restrictions, assumptions, etc. They can now think of the properties that the house needs to meet their needs. If you build software, some of the functional requirements; (characteristics that the system meets the needs of users) come from user requirements, just as the functional requirements of Mr and Mrs. Jones.
- Mr. and Mrs. Jones wants to keep their privacy, the new house has at least two bedrooms, one for them and one for the baby.
- They strive to preserve antique furniture; the new house must be a playground that is far from the habitats where antique furniture is kept.
- They want to play with their children; the new house has a yard.
- They want a good school, the house must be located in a room where a good school is located, etc … From the above example Mr. and Mrs. Jones were able to identify the requirements of the new house, as they have identified their needs. Then we can say that user needs can be the driving force of most to find and identify the functional requirements of the system. The remaining functional requirements may be guided by business rules / requirements (not discussed in this article). More complex techniques such as flowcharts, case use, galaxy analysis, requirements elicitation meetings, etc. should be added to the technique discussed to identify the scope.