1.

Usecase Diagram A Use-case corresponds to a sequence of transactions, in which each transaction is invoked from outside the system (actors) and engages i nternal objects to interact with another and with the system's surroundings. A Use-case diagram is a graph of actors, a set or use ca ses enclosed by a system boundary, communicate(participation) associates b etween the actors and the use cases, and generalization among the cases. A use case is shown as an ellipse containing the name of the use case. The name of the use case can be placed below or inside the ellipse. An actor is shown as a class rectangle with a label and a stick fi gure, or just he stick figure with the name of the actor below the figure Admin

Analyst

Developer Code Reviewer

QA

2. Scenario A Scenario specifies the behavior of use case by description, not modeling. It i ncludes informal structured text, formal structured text with conditions, and ps eudo code. It also specifies how and when the use case starts and ends and the i nteraction with the actors and the exchange of objects and the flow of events: m ain / typical (success), alternative (success), and exceptional (failure) flows. In the case of Admin At the starting the system checks whether the administrator is valid or not. If it is a valid user then login successfully preceded, otherwise login fails. Task The administrator can do the creation of new users after the login. The administrator can do the maintenance of existing users. The administrator can do the maintenance of the application In the case of Analyst

Analyst can login as user type Analyst with a user name and password, the system checks whether the user name is valid or not. If it is valid user of that parti cular user type can login successfully, otherwise login fails. Analyst can create what are all the requirements which have to be fulfilled. Based on the requirements to be fulfilled the analyst can create Task List. Analyst can make review on requirements which are in work and make necessary act ion or planning to meet the requirement. Analyst can review the test scenarios which are created by the Quality Analyst. Requirement fulfillment In the case of Developer Developer can login as user type Developer with a user name and password, the sy stem checks whether the user name is valid or not. If it is valid user of that p articular user type can login successfully, otherwise login fails. A Developer will get a list of Tasks to be fulfilled Requirement search. Based on the requirement to be fulfilled the Developer can create Rules. Developer can assign rules to the other developers or programmers for working on the rules. Developer can work on the Rules which are assigned to the developer for the fulf illment of the Rule Developer can make Reports on progress of the Rule and Rule fulfillment. In the case of Code Reviewer Code Reviewer can login as user type Code Reviewer with a user name and password , the system checks whether the user name is valid or not. If it is valid user o f that particular user type can login successfully, otherwise login fails. Tasks which are assigned to developers can accessed by Code Reviewer. The Code Reviewer can review the Rules which are created by Developers Rule can be assigned while the Code Reviewer notes any problem in Rule review. In the case of QA QA can login as user type QA with a user name and password, the system checks wh ether the user name is valid or not. If it is valid user of that particular user type can login successfully, otherwise login fails. Task list Requirement search QA can create Requirement Test scenarios for Requirements Requirement assignment for test case review Reports

3. Class diagram Class diagram of Requirement :

Class diagram for User Administration:

Class diagram for Custom Table Class Diagram 4. Sequence Diagram Form Design

1.

Add_Project

2. 3.

Add_CustomTable Add_CustomField