MS Project: Modeling Non-Functional Requirement

Hello..

I just completed working on my MS project. Here is a small overview of my MS project.. Humm.. I am graduating....... :)

 

The major problem big software organizations are facing is, documenting the non functional requirements in such a manner that they can communicate effectively. It is not possible for the organization to arrange a meeting for all the team members of the project from all different countries to explain the non functional requirements and to train them to think in a different mind set to capture those requirements.

 

The situation becomes more complex when the project is very large and geographically scattered. It is really required for the system analyst to explain exactly what they need in a specific module from the developers who might not have a good overall picture for the overall system.

The primary objective for this project is to develop a standardized methodology for the modeling of the non functional requirements. The developed process will help the project managers to manage their projects and train programmers and prepare them for the non functional requirements. It may not result immediate advantageous to the organization but at a longer span, it can definitely improve the Software Development approach for the organization. The solution is divided in two major parts. The first part discuss about understanding the project and identifying the quality attributes and second part deals with really implementing them using the use case scenario.

 

Thanks.

The Unleasher