Java Tutorial - Java Script :
Needs Analysis
It might seem obvious that you should know what you need before you startlooking for a solution that properly addresses those needs. In reality, though, you often have only a general understanding of your needs before the project begins; other needs don’t rear their ugly heads until the project is already underway.
The initial goal of the feature analysis is to gain a better understanding of the types of features that are available in a group of related products. These features often exist because others trying to solve similar problems have encountered the same needs. Often, understanding the features offered by a set of products provides new insights into how those features can be appliedto your application. Also, you don’t want to limit yourself by a lack of foresight.If a feature is very common across products, it is likely that it will be desirable to have it available for your project at some point in the future. In other words, we can use the features analysis to aid us in our needs analysis by
highlighting what others have needed.
A good way to track the project’s needs is to add a needs column to your earlier table and check any feature that you must have to support your project. It is also useful to provide a weight or score for each need to serve as a measure of how important the need is for our project. Many ways to rank these exist; we prefer a simple scheme of “required,” “nice to have,” and “not needed.” An example based on our earlier feature summary example is shown in Table 3.2.
