FORENSIC MANAGER


SYSTEM REQUIREMENT SPECIFICATIONS
  FORENSIC MANAGER
PURPOSE OF THE SYSTEM
The Forensic Manager is a web application which systematizes functions of large law firms, which have large number of clients.

The proposed forensic manager will enable the operations of the law firms to be conducted more effectively. The need will be felt more in the coming days when the profession of act will be opened up for foreign competition.

Proposed system provides information on the multiple facts of  laws such as the Constitution of India, which is a basic legislature dealing with fundamental rights, duties of the citizens of India, laws relating to the establishment of family courts and the rules of procedure of the courts, case, sections , and cause lists etc..,
EXISTING SYSTEM
·       It does not provide complete information about law, courts and sections related to constitutions of India.
·       Ineffectiveness of generating case history details.
·       This system is not providing secure registration and profile management of all the users properly.
·       Existing system does not provide case hearing alerts.
·       Information is not provided to general users.
PROPOSED SYSTEM
The development of this new system contains the following activities, which try to automate the entire process keeping in the view of database integration approach.
  • It provides complete information about law, courts and sections related to constitutions of India.
  • Providing previous case hearing details.
  • Manages case evidence type and witness details.
  • Providing proper managing of client profile details.
  • User friendliness is provided in the application with various controls provided by system rich user interface.
  • Authentication is provided to only registered users.
  • The user’s information can be stored in centralized database which can be maintained by the system.
  • Searching facility provided.

STUDY OF THE SYSTEM

In the flexibility of uses the interface has been developed a graphics concepts in mind, associated through a browser interface. The GUI’s at the top level has been categorized as follows
1.     Administrative User Interface Design.
2.     User Interface.

The administrative user interface will maintain Advertising Agency details in efficient way.
The user will interact with blazon agency to advertise about his company in particular location.
NUMBER OF MODULES
1.     User Registration.
2.     Law, Court and Section Management.
3.     Case Management.
4.     Security.
5.     Reports.


MODULES DESCRIPTION
1. USERS REGISTRATION        
The general users who registered as a one of member in organization to get the details of legal advises in previous cases, court verdict details and   sections are applied under those cases. 
In democratic and social countries it is common requirement to everybody to know about law and each client involve in his own domain like business, income tax, family issues etc,..  these are common to everybody. So he may willing to approach  law ,its details and sections to avoid illegal thing, to get all these details client has to register with his personal details like name, father name, address, contact details, etc,..
2.     LAW ,COURT AND SECTION  MANAGMENT
LAW
              In this part different type of sections ,clauses are included in different type of laws that is there is different categories in laws like civil law, criminal law, income tax, cyber law, family law, business laws, labour laws etc,..The lawyers well known about their domains and they give suggestions to register clients. Ex... The payment of a dowry was prohibited in 1961 under Indian criminal law and subsequently by Sections 304B and 498a of the Indian Penal court.
COURT
             In this country several types of courts are introduced by government  like supreme court, high court, special tribunals, district sessions and these court contain categories family courts, cyber courts, criminal courts runs different type of cases under different section like Type of case, Civil Appeal, Criminal Appeal, Special Leave Petition (Civil), Special Leave Petition (Criminal), Writ Petition (Civil) ...
SECTION
            Here we will get the information about the sections under which type of law types.

     

3. CASE MANAGEMENT
    CASE AND LAWYER MANAGEMENT
      According to these cases like Civil Appeal, Criminal Appeal, Special Leave Petition (Civil), Special Leave Petition (Criminal), Writ Petition (Civil) ... are deals correspondent lawyers belongs civil lawyer ,criminal lawyer ,family lawyer, income tax etc,…those are export in their domain to deal cases and make justice to their client or members with help of evidences and witness, in addtion to this lawyer details are maintain that is lawyer name, bar registration date, lawyer qualification details, address, contact numbers
     CASE EVIDENCE AND MEMBERS
      A lawyer deals his client cases in particular court with respective to client case, lower collects information about evidence. Evidence can be the most important part of a trial. It can either convict the accused, or set them free. There are specific types of evidence, and ways this evidence may be used during a trial. What evidence is and how it may be used will be explained here.
 
4.  SECURITY
This System provides good security with different kind of accessing levels.
5.  REPORTS
A.     User Profiles.
B.     Law, Court and Sections Reports
C.    Case hearing report.
.

FUNCTIONAL REQUIREMENTS
The main functionalities of this system is,
  1. User Registrations.
  2. Client Registration.
  3. Client Profile.
  4. Section details.
  5. Court, Court Type details.
  6. Case, Case Registration details.
  7. Lawyer, Law Type details.
  8. Case members/evidence details.
  9. Case hearing details.
     10. Case Witness details.



NON-FUNCTIONAL REQUIREMENTS
i.                  Secure access of confidential data (user’s details).
ii.                 24 X 7 availability.
iii.             Better component design to get better performance at peak time
iv.              Flexible service based architecture will be highly desirable for future extension.












SDLC METHDOLOGIES
             This document play a vital role in the development of life cycle (SDLC) as it describes the complete requirement of the system.  It means for use by developers and will be the basic during testing phase.  Any changes made to the requirements in the future will have to go through formal change approval process.
     SPIRAL MODEL was defined by Barry Boehm in his 1988 article, “A spiral Model of Software Development and Enhancement.  This model was not the first model to discuss iterative development, but it was the first model to explain why the iteration models.
     As originally envisioned, the iterations were typically 6 months to 2 years long.  Each phase starts with a design goal and ends with a client reviewing the progress thus far.   Analysis and engineering efforts are applied at each phase of the project, with an eye toward the end goal of the project.
The steps for Spiral Model can be generalized as follows:
·       The new system requirements are defined in as much details as possible.  This usually involves interviewing a number of users representing all the external or internal users and other aspects of the existing system.
·       A preliminary design is created for the new system.
·       A first prototype of the new system is constructed from the preliminary design.  This is usually a scaled-down system, and represents an approximation of the characteristics of the final product.
·       A second prototype is evolved by a fourfold procedure:
1.     Evaluating the first prototype in terms of its strengths, weakness, and risks.
2.     Defining the requirements of the second prototype.
3.     Planning an designing the second prototype.
4.     Constructing and testing the second prototype.
·       At the customer option, the entire project can be aborted if the risk is deemed too great.  Risk factors might involved development cost overruns, operating-cost miscalculation, or any other factor that could, in the customer’s judgment, result in a less-than-satisfactory final product.
·       The existing prototype is evaluated in the same manner as was the previous prototype, and if necessary, another prototype is developed from it according to the fourfold procedure outlined above.
·       The preceding steps are iterated until the customer is satisfied that the refined prototype represents the final product desired.
·       The final system is constructed, based on the refined prototype.
·       The final system is thoroughly evaluated and tested.   Routine maintenance is carried on a continuing basis to prevent large scale failures and to minimize down time.