Surveys of the project

Add caphttp://www.google.com.eg/imgres?imgurl=http://blogs.princeton.edu/itsacademic/avkat.jpg&imgrefurl=http://blogs.princeton.edu/

            In the first we will give you briefly introduction about the system analyst job because it’s the objective of our project to known what the analyst work.

System analyst:

-         System analyst’s job is to analyze the particular problem domain at abstract levels and provide a solution.

-         It includes risk management, hardware and SW's feasibility, costing (may include), and more depends on the domain in the particular system falls into.

-         He is supposed to know everything internal entities and external entities which are interacting with the system including customers.

-         This means the analyst must understand the general objectives of the business, as well as what each individual user's job requires. Once the system analyst has determined the general and specific needs of the business, he can choose appropriate systems that will help accomplish the goals of the business.

-         Analyst knows the specific needs of each user.

-         He must also be willing to listen to the constant needs and complaints of the users he builds systems for.

This programs made in our field of our project:

  1- An Automatic Tool for Improving the Quality of Software Requirements (QuARS):

Introduction:    

               QuARS performs a lexical and syntactical parsing of software requirements expressed in NL, and provides the following functionality. 

•         It’s an innovative tool that enables the user to analyze requirements expressed in NL automatically.

•         It provides a systematic and disciplined NL requirements analysis process.

•         It performs a lexical and syntactical parsing of software requirements expressed in NL, and provides the following functionality.

•         It performs a lexical and syntactic analysis of the input file in order to identify those sentences containing defects according to the quality model.

Using QuARS:

QuARS provides a systematic and disciplined L-requirements analysis process (see Figure 1). Input to the tool is composed of the requirements document which is to be analyzed. The permitted format of this input file is plain text. This file is given to the syntax parser component, which produces a new file containing the parsed version of its sentences. The tool relies on a set of indicator-related dictionaries; these may contain either terms indicating a defect type according to the quality model, or the domain dictionaries used for the view derivation. The dictionaries are in simple text format. Once the user selects the type of analysis to be performed, the corresponding dictionary is made available and can be tailored, if desired, according to the application domain