INTRODUCTION
This Software is very useful for managing the daily cases diary for Lawyers/
Advocates. This is of software, which store information about an advocate's clients,
opponents, cases no., Previous Date, Current Date, Next Date, court name. You can
filter the data according to case no, Parties, next date etc. You can also maintain the
files stored on the locations of your hard disk for individual client. The software is very
easy to operate and light on system tool to maintain information about Clients, Cases,
Hearings, Rulings, Accounts, books, periodicals etc. Software manages day-to-day
activity and builds a comprehensive client/case/matter database and history that can
help improve every aspect of your practice. You will have immediate access to tools for
case status and information, document management and assembly, calendaring and
docketing and contact management. The system also comes with a number of standard
reports that can be accessed easily by users. Track time, manage receivables etc. For
quick reference provision of many reports is also made. It also provides information
about daily schedule tasks. Software is dedicated to advocates/ lawyers to help them in
maintaining their offices.
This software is very easy to use. The main goal is reducing paper work. It helps us
to recollect the information about the previous and future case information.
1.1 PROJECT DESCRIPTION
Information need only be entered once and is available wherever and whenever you
need it. More importantly, it all works together in the way you would expect, so there's
a natural workflow to everything you do.
Daily reports, overviews and practice reminders
Create separate files on each client matter
A Notepad for centralized note taking
Provide information about daily schedule tasks.
Maintain their Diary of Cases & Clients
Case Entry
Information need only be entered once. You have to just fill up required information
of your Client/Case, Further you have to only make entries of Next Date and Stage and
remaining will be take care by this software. When case is decided, you can select
option of decide cases so that further it will be not shown in the system.
Personal Information
You have to make entries relating to your personal information can also add your
photograph.
Diary
You can see cases of a Specific date or between any dates and many more
information as detailed below. Next date of Hearing and Case Stage can be entered
directly from Diary.
In the existing system the maintenance of all the case details will take place
manually.
Since it is not computerized the details were not stored in the database.
The details were maintained in the records. So there may have a chance of
missing the data.
This system is designed in such a way to meet the requirements with the
maximum flexibility.
In this system the details of all the cases will be recorded in the database.
Searching for particular person’s details will be easy through this system.
2.3 FEASIBLITY ANALYSIS
The feasibility of the project is analyzed in this phase and business proposal
is put forth with a very general plan for the project and some cost estimates. During
system analysis the feasibility study of the proposed system is to be carried out. This is
to ensure that the proposed system is not a burden to the company. For feasibility
analysis, some understanding of the major requirements for the system is essential.
Economical Feasibility
Technical Feasibility
Social Feasibility
This study is carried out to check the economic impact that the system will
have on the organization. The amount of fund that the company can pour into the
research and development of the system is limited. The expenditures must be justified.
Thus the developed system as well within the budget and this was achieved because
most of the technologies used are freely available. Only the customized products had to
be purchased.
This study is carried out to check the technical feasibility, that is, the technical
requirements of the system. Any system developed must not have a high demand on the
available technical resources. This will lead to high demands on the available technical
resources. This will lead to high demands being placed on the client. The developed
system must have a modest requirement, as only minimal or null changes are required
for implementing this system.
2.3.3 SOCIAL FEASIBILITY
The aspect of study is to check the level of acceptance of the system by the
user. This includes the process of training the user to use the system efficiently. The
user must not feel threatened by the system, instead must accept it as a necessity. The
level of acceptance by the users solely depends on the methods that are employed to
educate the user about the system and to make him familiar with it. Users’ level of
confidence must be raised so that the user is also able to make some constructive
criticism, which is welcomed, as end user is the final user of the system.
3. SYSTEM SPECIFICATION
RAM : 1 GB
An interface for users is build using ASP .Net. SQL server 2008 is used as a
backend tool. Additional technologies used is web services and ADO .Net. Then it
comes the turn of operating System. Any .Net framework Compatible software
platform can be used.
“.NET” is also the collective name given to various software components built
upon the .NET platform. These will be both products (Visual Studio.NET and
Windows.NET Server, for instance) and services (like Passport, .NET My Services, and
so on).
Managed Code
The code that targets .NET which contains certain extra Information -
“metadata” - to describe itself. While both managed and unmanaged code can run in the
runtime, only managed code contains the information that allows the CLR to guarantee,
for instance, safe execution and interoperability.
Managed Data
Managed Code comes Managed Data. CLR provides memory allocation and
Deal location facilities, and garbage collection. Some .NET languages use Managed
Data by default, such as C#, Visual Basic.NET and JScript.NET, whereas others,
namely C++, do not. Targeting CLR can, depending on the language the user’re using,
impose certain constraints on the features available. As with managed and unmanaged
code, one can have both managed and unmanaged data in .NET applications - data that
doesn’t get garbage collected but instead is looked after by unmanaged code.
The CLR uses something called the Common Type System (CTS) to strictly enforce
type-safety. This ensures that all classes are compatible with each other, by describing
types in a common way.
CTS define how types work within the runtime, which enables types in one
language to interoperate with types in another language, including cross-language
exception handling. As well as ensuring that types are only used in appropriate ways,
the runtime also ensures that code doesn’t attempt to access memory that hasn’t been
allocated to it.
Common Language Specification
The CLR provides built-in support for language interoperability. To ensure that
the user can develop managed code that can be fully used by developers using any
programming language, a set of language features and rules for using them called the
Common Language Specification (CLS) has been defined. Components that follow
these rules and expose only CLS features are considered CLS-compliant.
Constructors are used to initialize objects, whereas destructors are used to destroy
them. In other words, destructors are used to release the resources allocated to the
object. In C#.NET the sub finalize procedure is available. The sub finalize procedure is
used to complete the tasks that must be performed when an object is destroyed. The sub
finalize procedure is called automatically when an object is destroyed. In addition, the
sub finalize procedure can be called only from the class it belongs to or from derived
classes.
Garbage Collection
Overloading
Multithreading
C#.NET supports structured handling, which enables the user to detect and remove
errors at runtime. In C#.NET, the user need to use Try…Catch…Finally statements to
create exception handlers. Using Try…Catch…Finally statements, the user can create
robust and effective exception handlers to improve the performance of this application.
BACK END
FEATURES OF SQL-SERVER
The OLAP Services feature available in SQL Server. The term OLAP Services has
been replaced with the term Analysis Services. Analysis Services also includes a new
data mining component. The term repository is used only in reference to the repository
engine within Meta Data Services.
TABLE
QUERY
FORM
REPORT
TABLE
Design View
Datasheet View
DESIGN VIEW
To build or modify the structure of a table the user work in the table design
view. It can specify what kind of data will be hold.
DATASHEET VIEW
To add, edit or analyses the data itself the user work in tables datasheet view
mode.
QUERY
Queries are the real workhorses in a database, and can perform many different
functions. Their most common function is to retrieve specific data from the tables. The
data the user want to see is usually spread across several tables, and queries allow the
user to view it in a single datasheet. Also, since the user usually don't want to see all the
records at once, queries let the user add criteria to "filter" the data down to just the
records the user want. Queries often serve as the record source for forms and reports.
FORMS
Forms are sometimes referred to as "data entry screens." They are the interfaces
the user use to work with your data, and they often contain command buttons that
perform various commands. The user can create a database without using forms by
simply editing your data in the table datasheets. However, most database users prefer to
use forms for viewing, entering, and editing data in the tables.
REPORTS
Reports are what the user use to summarize and present data in the tables. Each
report can be formatted to present the information in the most readable way possible. A
report can be run at any time, and will always reflect the current data in the database.
Reports are generally formatted to be printed out, but they can also be viewed on the
screen, exported to another program, or sent as e-mail message.
4. SYSTEM DESIGN
In the system design phase, the diagram identifies logical data flow, data
stores and destination. Input data is collected and organised into groups of similar data.
The goal behind designing input data is to make the data entry easy and make it free
from logical errors. The input entry to all type of clients is the user name and password
only. If they are valid the client is allowed to enter into the software.
Objectives
Outputs are the most important and direct source of information to the user and
to management. Efficient and eligible output design should improve the system’s
relationship with the user and help in decision making. Output Design generally deals
with the results generated from stored or calculated values.
Reports are displayed either as screen preview or printed form. Most end users
will not actually operate the information systems or enter data through workstations,
but they will use the output from the system.
Form Design
The cost of collecting raw data and cost of distributing processed information are
major costs of a system. So careful forms design can affect the cost effectiveness of the
system. Well-designed forms can increase efficiency; improve workflow and lower
system costs.
Code Design
The general objective is to make information access easy, quick, expensive and
flexible for the user. In database design several specific objectives are consider:
Control Redundancy:
The accuracy and database ensures the data quality content remain constant.
Integrity controls detects data inaccuracy where occur.
Unit testing focuses efforts on the smallest unit of software design. This is
known as module testing. The modules are tested separately. The test is carried out
during programming stage itself. In this step, each module is found to be working
satisfactory as regards to the expected output from the module.
Data can be lost across an interface. One module can have an adverse effect on
another, sub functions, when combined, may not be linked in desired manner in major
functions. Integration testing is a systematic approach for constructing the program
structure, while at the same time conducting test to uncover errors associated within the
interface. The objective is to take unit tested modules and builds program structure. All
the modules are combined and tested as a whole.
Validation testing can be defined in many ways, but a simple definition is that
the validation succeeds when the software functions in a manner that is expected by the
customer. After validation test has been conducted, one of the three possible conditions
exists.
After performing the validation testing, the next step is output testing of the
proposed system, since no system could be useful if it does not produce the required
output in a specific format. The output format on the screen is found to be correct. The
format was designed in the system design time according to the user needs. For the hard
copy also; the output comes as per the specified requirements by the user. Hence output
testing did not result in any correction for the system.
User acceptance of a system is the key factor for the success of any system. The
system under consideration is tested for the user acceptance by constantly keeping in
touch with the prospective system users at the time of developing and making changes
whenever required.
Error messages and warning messages are “bad news” delivered to the user’s
iterative systems where something has gone away or wrong. Therefore in this developed
software there are some messages which will be displaying while using this developed
software if the user goes wrong. These messages are used to help the user for better use.
When the user enters wrong password the displayed message would be Invalid
Password! Please try again .While adding information for various modules no field
should be empty when saving the information in the database otherwise corresponding
error messages are given immediately. While updating the information if any field is
left empty then the messages are displayed accordingly Like select the task title, please
Enter Numeric values etc.
6. SYSTEM IMPLEMENTATION
The active user must be aware of the benefits of using the system
Implementation Plan
Implementation is the stage, which is crucial in the life cycle of the new system
designed. Implementation means converting a new or revised system design into an
operational one. The mechanism involved in dealing with the data structures are equally
important and have to be taken into consideration .This is the stage of the project where
the theoretical design is turned into a working system. In this project implementation
includes all those activities that take place to convert from the old system to the new
one. The important phase of implementation plan is changeover.
Careful planning
Investigation current system and its constraints on implementation
Changeover
The implementation is to be done step by step since testing with dummy data
will not always reveal the faults. The system will be subjected to the employees to
work. If such error or failure is found, the system can be corrected before it is
implemented in full stretch. The trail should be done as long as the system is made sure
to function without any failure or errors. Precautions should be taken so that any error if
occurred should not totally make the process to a halt. Such a care should be taken. The
system can be fully established if it does not create any error during the testing periods.
Implementation is the stage, which is crucial in the life cycle of the new system
designed. Implementation means converting a new or revised system design into an
operational one. The mechanism involved in dealing with the data structures are equally
important and have to be taken into consideration .This is the stage of the project where
the theoretical design is turned into a working system. In this project implementation
includes all those activities that take place to convert from the old system to the new
one. The important phase of implementation plan is changeover.
System Maintenance
A security vulnerability in the system has been found and needs patching.
The hardware or network is being improved and so the system should take
advantage of that.
Corrective Maintenance
Preventative Maintenance
Perfective Maintenance
Providing shortcuts commands that experts can use instead of the slower standard
menu system
Adaptive Maintenance