INTRODUCTION
Design a system for automating the judicial services in India. Using this system, plaintiff can easily give complaints to the concerned authority and they can view status of their cases etc. This system will reduce the time and risk to the users compare with manual system. The project performs intended function with required precision. The registered user’s files can be stored in centralized database which can be maintained by the system. Authentication is provided for this application only registered users can access.
SYSTEM ANALYSIS
SYSTEM ANALYSIS
As in any other system development model, system analysis is the first phase of development in case of Object Modeling too. In this phase, the developer interacts with the user of the system to find out the user requirements and analyses the system to understand the functioning.
Save your time!
We can take care of your essay
- Proper editing and formatting
- Free revision, title page, and bibliography
- Flexible prices and money-back guarantee
Based on this system study, the analyst prepares a model of the desired system. This model is purely based on what the system is required to do. At this stage the implementation details are not taken care of. Only the model of the system is prepared based on the idea that the system is made up of a set of interacting objects. The important elements of the system are emphasized.
SYSTEM DESIGN
System Design is the next development stage where the overall architecture of the desired system is decided. The system is organized as a set of sub systems interacting with each other. While designing the system as a set of interacting subsystems, the analyst takes care of specifications as observed in system analysis as well as what is required out of the new system by the end user.
as the basic philosophy of object-oriented method of system analysis is to perceive the system as a set of interacting objects, a bigger system may also be seen as a set of interacting smaller subsystems that in turn are composed of a set of interacting objects. while designing the system, the stress lies on the objects comprising the system and not on the processes being carried out in the system as in the case of traditional waterfall model where the processes form the important part of the system.
EXISTING SYSTEM
Through the existing system process which is purely manual process and time taking process. There are chances of having incorrect status representation to the case information. In the existing system, the person has to go to the police station and lodge a complaint personally. After that the person has to go regularly whenever they call for hearings.
PROPOSED SYSTEM
In this system registered users can view the case details by opening the site. They can lodge a complaint from home itself. User Friendliness is provided in the application with various controls provided by system Rich User Interface. The system makes the overall project management much easier and flexible. It can be accessed over the Internet. The registered user’s files can be stored in centralized database which can be maintained by the system. Authentication is provided for this application only registered users can access.
Advantages
- Searching jobs from more companies.
- Common question format is available.
- Previous exam results can be viewed.
- No need of separate resume registration for two or more companies.
Modules
1. Administrator
Admin enters into the site with his credentials. Admin can register defendant, Plaintiff Lawyer and Judge. File cases from plaintiffs. Schedule hearings (initial and continuing). Send hearings through mails to corresponding case Persons and Lawyers. Give instructions to representing advocates. All formal instructions must be logged in the system. These instructions may be multi-lingual. Send proceedings case wise after each hearing. View date wise case Reports. View Judgment file and send it to corresponding case personals through mails.
2. Lawyers
Lawyer enters in to the site with his credentials. He can view his clients own proofs and opposite candidate proofs. He can view instructions and proceedings sent by admin. He can send his own proofs to admin. He can change his password. He can communicate with his clients and admin through mails.
3. Defendant
Defendant can enter in to the website with his credentials. Defendant can send his proof to lawyer. Defendant can view proceedings. He can communicate to lawyer through mails and receives judgment through mails.
4. Judge
Judge can enter in to the site with his credentials. Judge view proceedings and send proceedings. Judge declares his judgment. He Communicate to admin through mails.
5. Authentication
This module provides security to the application. Every user should enter correct user name and password to proceed. This request will goes to database and check the user existing. If you entered wrong user name and password then it prompts you “Incorrect Username or Password…”
VALIDATION TESTING
The final step involves Validation testing, which determines whether the software function as the user expected. The end-user rather than the system developer conduct this test most software developers as a process called “Alpha and Beta Testing” to uncover that only the end user seems able to find.
The compilation of the entire project is based on the full satisfaction of the end users. In the project, validation testing is made in various forms. In question entry form, the correct answer only will be accepted in the answer box. The answers other than the four given choices will not be accepted.
MAINTENANCE
The objectives of this maintenance work are to make sure that the system gets into work all time without any bug. Provision must be for environmental changes which may affect the computer or software system. This is called the maintenance of the system. Nowadays there is the rapid change in the software world. Due to this rapid change, the system should be capable of adapting these changes. In our project the process can be added without affecting other parts of the system.
Maintenance plays a vital role. The system liable to accept any modification after its implementation. This system has been designed to favour all new changes. Doing this will not affect the system’s performance or its accuracy.
In the project system testing is made as follows:
The procedure level testing is made first. By giving improper inputs, the errors occurred are noted and eliminated. Then the web form level testing is made. For example storage of data to the table in the correct manner.
In the form, the zero length username and password are given and checked. Also the duplicate username is given and checked. The client side validations are made.
The dates are entered in wrong manner and checked. Wrong email-id is given and checked.
This is the final step in system life cycle. Here we implement the tested error-free system into real-life environment and make necessary changes, which runs in an online fashion. Here system maintenance is done every months or year based on company policies, and is checked for errors like runtime errors, long run errors and other maintenances like table verification and reports.
Implementation is the stage of the project when the theoretical design is turned out into a working system. Thus it can be considered to be the most critical stage in achieving a successful new system and in giving the user, confidence that the new system will work and be effective.
The implementation stage involves careful planning, investigation of the existing system and it’s constraints on implementation, designing of methods to achieve changeover and evaluation of changeover methods.
Implementation is the process of converting a new system design into operation. It is the phase that focuses on user training, site preparation and file conversion for installing a candidate system. The important factor that should be considered here is that the conversion should not disrupt the functioning of the organization.
The application is implemented in the Internet Information Services 5.0 web server under the Windows 2000 Professional and accessed from various clients.
Software testing is an investigation conducted to provide stakeholders with information about the quality of the product or service under test.[1] Software testing also provides an objective, independent view of the software to allow the business to appreciate and understand the risks of software implementation. Test techniques include, but are not limited to, the process of executing a program or application with the intent of finding software bugs (errors or other defects).
Software testing can also be stated as the process of validating and verifying that a software program/application/product:
- meets the business and technical requirements that guided its design and development;
- works as expected; and
- can be implemented with the same characteristics.
Software testing, depending on the testing method employed, can be implemented at any time in the development process. However, most of the test effort occurs after the requirements have been defined and the coding process has been completed. As such, the methodology of the test is governed by the software development methodology adopted.
Different software development models will focus the test effort at different points in the development process. Newer development models, such as Agile, often employ test driven development and place an increased portion of the testing in the hands of the developer, before it reaches a formal team of testers. In a more traditional model, most of the test execution occurs after the requirements have been defined and the coding process has been completed.
White box testing is when the tester has access to the internal data structures and algorithms including the code that implement these.
Types of white box testing
The following types of white box testing exist:
- API testing (application programming interface) - testing of the application using public and private APIs
- Code coverage - creating tests to satisfy some criteria of code coverage (e.g., the test designer can create tests to cause all statements in the program to be executed at least once)
- Fault injection methods - improving the coverage of a test by introducing faults to test code paths
- Mutation testing methods
- Static testing - White box testing includes all static testing
Test coverage
White box testing methods can also be used to evaluate the completeness of a test suite that was created with black box testing methods. This allows the software team to examine parts of a system that are rarely tested and ensures that the most important function points have been tested.[21]
Two common forms of code coverage are:
- Function coverage, which reports on functions executed
- Statement coverage, which reports on the number of lines executed to complete the test
They both return a code coverage metric, measured as a percentage.
Specification-based testing: Specification-based testing aims to test the functionality of software according to the applicable requirements.[22] Thus, the tester inputs data into, and only sees the output from, the test object. This level of testing usually requires thorough test cases to be provided to the tester, who then can simply verify that for a given input, the output value (or behavior), either 'is' or 'is not' the same as the expected value specified in the test case.
Specification-based testing is necessary, but it is insufficient to guard against certain risks.[23]
Advantages and disadvantages: The black box tester has no 'bonds' with the code, and a tester's perception is very simple: a codemust have bugs. Using the principle, 'Ask and you shall receive,' black box testers find bugs where programmers do not. On the other hand, black box testing has been said to be 'like a walk in a dark labyrinth without a flashlight,' because the tester doesn't know how the software being tested was actually constructed. As a result, there are situations when (1) a tester writes many test cases to check something that could have been tested by only one test case, and/or (2) some parts of the back-end are not tested at all.
CODE EFFICIENCY
MEASURES OF CODE EFFICIENCY
The code is designed with the following characteristics in mind.
- Uniqueness: The code structure must ensure that only one value of the code with a single meaning is correctly applied to a give entity or attribute.
- Expandability: The code structure are designed for in a way that it must allow for growth of it’s set of entities or attributes, thus providing sufficient space for the entry of new items with in each classification.
- Conciseness: The code requires the fewest possible number of positions to include and define each item.
- Uniform size and format: Uniform size and format is highly desirable in mechanized data processing system. The addition of prefixes and suffixes to the root code should not be allowed especially as it is incompatible with the uniqueness requirement.
- Simplicity: The codes are designed in a simple manner to understand and simple to apply.
- Versatility: The code allows modifying easily to reflect necessary changes in conditions, characteristics and relationship of the encoded entities. Such changes must result in a corresponding change in the code or coding structure.
- Sortability: Reports are most valuable for user efficiency when sorted and presented in a predetermined format or order. Although data must be sorted and collaged, the representative code for the date does not need to be in a sortable form if it can be correlated with another code that is sortable.
- Stability: Codes that do not require to be frequently updated also promote use efficiency. Individual code assignments for a given entity should be made with a minimal likelihood of change either in the specific code or in the entire coding structure.
- Meaningfulness: Code is meaningful. Code value should reflect the characteristics of the coded entities, such as mnemonic features unless such a procedures results in inconsistency and inflexibility.
- Operatability: The code is adequate for present and anticipated data processing both for machine and human use. Care is taken to minimize the clerical effort and computer time required for continuing the operation.
CONCLUSION
The conclusion of the system ensures the complete freedom for court procedings, where user at his own system can logon to this website and can check the status of his case. Our proposed system allows only registered users to check case status, view Judge and Lawyer details.
BIBLIOGRAPHY
- Mastering Visual C#.Net
- Practical Database Programming With Visual C#.NET
- Programming In C#, 3E
- OOP with Microsoft Visual Basic.NET and Microsoft Visual C# .NET step by step
- Essential ASP. NET with Examples in C#
- Professional ASP.NET 3.5 SP1 Edition: In C# and VB
- Beginning ASP.NET 2.0 with C#
- ASP.NET development
- http://www.wikipedia.com
- http://www.asp.net
- http://www.c#.net
Stuck on your essay?
