1.

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.

Next Hearing Date Entry

This entry can be made directly into This system or by using Special Feature which
shows all cases where Next Hearing date not entered.
Cases without next date of Hearing
A special feature in this system is which shows you all cases where no next date of
hearing entered. You can directly enter next date and case stage.

Case Stage Entry

Facility to know progress stage of case, this entry made while entering Hearing Date
in This system.
Individual Case Details
Facility to see All Hearing Dates and other details of an individual case provided.
All cases of a Client
Facility to see details of All Cases of a Client with hearing dates provided.
Court Wise Cases
This system will show you list of cases for a Specific Court.
Active Cases
You have option in case details to make a Case Active or Decided. New case is
automatically selected option of Active Case.
Decided Cases
When you select this option for a case in case details, then that Case is not shown in
This system. You can any time deselect this option and Case can become Active.
 2. SYSTEM ANALYSIS
2.1 EXISTING SYSTEM
In the existing system the user cannot able to view the case details on website .If
they want to know the details about their case they have to visit the court. They want to
go through various website to see the full details. It is very difficult because the user
want to spend much more time . At present all records are typed in typewriter and they
are filed. Because of thousands of records searching for the required data is time
consuming. Typing using the typewriter leads many problems. For each error they have
to make a note and get the signatures. Also system is not pool proof.
2.1.1 Disadvantages

 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.

 It is not time consuming process.

2.2 PROPOSED SYSTEM
The proposed system will overcome all the difficulties of the existing system. In this
the user can view the full details about their case through online. The user can get all
the detail about the Hiring, Trial, Degree and the case entry details. In the proposed
system all information will entered to system. All scheduling can be done in the
computer it self. So they can track each case easily.
2.2.1 Advantages

 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.

 This will save the time.

 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.

Three key considerations involved in the feasibility analysis are

 Economical Feasibility
 Technical Feasibility
 Social Feasibility

2.3.1 ECONOMICAL 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.

2.3.2 TECHNICAL FEASIBILITY

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

3.1 HARDWARE REQUIREMENTS

PROCESSOR : Pentium 4 (1.6 GHZ or above)

RAM : 1 GB

MONITOR : 15” Color

HARD DISK : 250 GB

MOUSE : Logical Mouse

KEYBOARD : Logical Multimedia Keyboard

3.2 SOFTWARE REQUIREMENTS

FRAMEWORK : .NET Framework SDK 3.5

OPERATING SYSTEM : Windows SP2, Vista, Windows 7

DATABASE : Microsoft SQL Server 2005

LANGUAGE : C#.NET,Microsoft Reporting Services

DOCUMENTATION : Microsoft Office 2007

3.3 ABOUT THE SOFTWARE

In this project software project monitoring system .Net Framework is used as

Frontend tool. .Net is one of the most beautiful and recently more popular front-end
tools. C# .Net and ASP.Net are used in this project.

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.

Introduction to Dot Net

Microsoft .NET is a set of Microsoft software technologies for rapidly building

and integrating XML Web services, Microsoft Windows-based applications, and Web
solutions. The .NET Framework is a language-neutral platform for writing programs
that can easily and securely interoperate. There’s no language barrier with .NET there
are numerous languages available to the developer including Managed C++, C#, Visual
Basic and Java Script. The .NET framework provides the foundation for components to
interact seamlessly, whether locally or remotely on different platforms. It standardizes
common data types and communications protocols so that components created in
different languages can easily interoperate.

“.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).

The .Net Framework

The .NET Framework has two main parts:

 The Common Language Runtime (CLR).

 A hierarchical set of class libraries.

The CLR is described as the “execution engine” of .NET. It provides the

environment within which programs run. The most important features are
 Conversion from a low-level assembler-style language, called Intermediate Language
(IL), into code native to the platform being executed on.
 Memory management, notably including garbage collection.
 Checking and enforcing security restrictions on the running code.
 Loading and executing programs, with version control and other such features.
 The following features of the .NET framework are also worth description.

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.

Common Type System

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.

The Class Library

.NET provides a single-rooted hierarchy of classes, containing over 7000 types.

The root of the namespace is called System; this contains basic types like Byte, Double,
Boolean, and String, as well as Object. All objects derive from System. Object. As well
as objects, there are value types. Value types can be allocated on the stack, which can
provide useful flexibility. There are also efficient means of converting value types to
object types if and when necessary.

The set of classes is pretty comprehensive, providing collections, file, screen,

and network I/O, threading, and so on, as well as XML and database connectivity.

Constructors and Destructors

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

Garbage Collection is another new feature in C#.NET. The .NET Framework

monitors allocated resources, such as objects and variables. In addition, the .NET
Framework automatically releases memory for reuse by destroying objects that are no
longer in use.
 In C#.NET, the garbage collector checks for the objects that are not currently in use
by applications. When the garbage collector comes across an object that is marked for
garbage collection, it releases the memory occupied by the object.

Overloading

Overloading is another feature in C#. Overloading enables the user to define

multiple procedures with the same name, where each procedure has a different set of
arguments. Besides using overloading for procedures, the user can use it for
constructors and properties in a class.

Multithreading

C#.NET also supports multithreading. An application that supports multithreading

can handle multiple tasks simultaneously, the user can use multithreading to decrease
the time taken by an application to respond to user interaction.

Structured Exception Handling

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.

Features of C#. Net

C#.NET is also compliant with CLS (Common Language Specification) and

supports structured exception handling. CLS is set of rules and constructs that are
supported by the CLR (Common Language Runtime). CLR is the runtime environment
provided by the .NET Framework; it manages the execution of the code and also makes
the development process easier by providing services.

C#.NET is a CLS-compliant language. Any objects, classes, or components that

created in C#.NET can be used in any other CLS-compliant language. In addition, the
user can use objects, classes, and components created in other CLS-compliant
languages in C#.NET .The use of CLS ensures complete interoperability among
applications, regardless of the languages used to create the application.
Conclusion of .NET

The .NET Framework is a new computing platform that simplifies application

development in the highly distributed environment of the Internet. To provide a
consistent object-oriented programming environment whether object codes is stored
and executed locally on Internet-distributed, or executed remotely. To provide a code-
execution environment to minimizes software deployment and guarantees safe
execution of code and eliminates the performance problems. There are different types
of application, such as Windows-based applications and Web-based applications.

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.

SQL-SERVER database consist of six type of objects they are

TABLE

QUERY

FORM

REPORT

TABLE

A database table is similar in appearance to a spreadsheet, in that data is stored

in rows and columns. As a result, it is usually quite easy to import a spreadsheet into a
database table. The main difference between storing your data in a spreadsheet and
storing it in a database is in how the data is organized. Data about products will be
stored in its own table, and data about branch offices will be stored in another table.
This process is called normalization.
VIEWS OF TABLE

Table in two types,

 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

4.1 INPUT DESIGN

Input design is the process of converting user inputs into computer-based

format. The project requires a set of information from the user to prepare a report. In
order to prepare a report, when organized input data are needed.

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

 To produce a cost-effective method of input.

 To achieve the highest possible level of accuracy.
 To ensure that the input is acceptable and understandable.
 The input design is actually designing of screens. Some of the major
screens involved in project.
 Registration form for new client.
 Form for login file.
 Form for displaying connected clients.
 Form for displaying result.

4.2 OUTPUT DESIGN

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

When a large volume of data is being handled, it is important that items be

identified, sorted or selected easily. To accomplish this, each data item must have a
unique identification and must be relates to other items of data of the same type. Thus
codes are used to identify item uniquely.

A Code is group of characters or numbers used to identify an item or data.

While identification is the main function of a code, it may also show relationships
between items of data. A good coding scheme should be expandable, precise, concise,
convenient and meaningful. Based on above idea, codes are used which contain
alphanumeric characters.

4.3 DATABASE DESIGN

A general theme begin a database is to handle information as an integrated

whole. A database is a collection of inter-related data stored with minimum redundancy
to server many users quickly and efficiently.

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:

Redundant data occupies space and therefore, is wasteful. If versions of the

same data are in different phase of updating, a system often gives conflicting
information. A unique aspect of database design is storing data only once, which
controls redundancy and improves system performance.
Data Independence:

An important database objective is changing hardware and storage procedures

for adding raw new data without having to rewrite application programs.

Accuracy and Integrity:

The accuracy and database ensures the data quality content remain constant.
Integrity controls detects data inaccuracy where occur.

Privacy and Security:

For the data to remain private, security measures must be taken to an

unauthorized access. Database security means that data are protected from various
forms of destructions. Uses must be positively identifies and actions
monitored.Managing the database require a DataBase Administrator (DBA) whose key
functions are to be managing data activities, The database structure and the DBMS. In
addition a managerial background the DBA needs a technical knowledge to deal with
database designer.

4.4 DATA FLOW DIAGRAM

A data flow diagram (DFD) is a graphical system model that shows all of the
main requirements for an information system in one diagram: inputs and outputs,
processes, and data storage. A DFD describes what data flows rather than how it is
processed. Everyone working on a development project can see all aspects of the
system working together at once with DFD. That is one reason for its popularity. The
DFD is also easy to read because it is graphical model. The DFD is mainly used during
problem analysis. End Users, management, and all information systems workers
typically can read and interpret the DFD with minimal training.
 5. SYSTEM TESTING

Testing is the process of running a system with the intention of finding

errors. Testing enhances the integrity of a system by detecting deviations in design and
errors in the system. Testing aims at detecting error-prone areas. This helps in the
prevention of errors in a system. Testing also adds value to the product by conforming
to the user requirements.

The main purpose of testing is to detect errors and error-prone areas in a

system. Testing must be thorough and well-planned. A partially tested system is as bad
as an untested system. And the price of an untested and under-tested system is high.

The implementation is the final and important phase. It involves user-

training, system testing in order to ensure successful running of the proposed system.
The user tests the system and changes are made according to their needs. The testing
involves the testing of the developed system using various kinds of data. While testing,
errors are noted and correctness is the mode.

5.1 OBJECTIVES OF TESTING

The objectives of testing are:

● Testing is a process of executing a program with the intent of finding errors.

● A Successful test case is one that uncovers an as- yet-undiscovered error.

System testing is a stage of implementation, which is aimed at ensuring that the

system works accurately and efficiently as per the user need, before the live operation
commences. As stated before, testing is vital to the success of a system. System testing
makes a logical assumption that if all parts of the as system are correct, the goal will be
successfully achieved. A series of tests are performed before the system is ready for the
user acceptance test.

5.2 TESTING METHODS

System testing is the stage of implementation. This is to check whether the

system works accurately and efficiently before live operation commences. Testing is
vital to the success of the system. The candidate system is subject to a variety of tests:
on line response, volume, stress, recovery, security and usability tests. A series of tests
are performed for the proposed system is ready for user acceptance testing.

5.3 THE TESTING STEPS

5.3.1 Unit Testing

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.

5.3.2 Integration Testing

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.

5.3.3 Validation Testing

At the culmination of the integration testing, Software is completely

assembled as a package. Interfacing errors have been uncovered and corrected and a
final series of software test begin in validation testing.

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.

 The function or performance characteristics confirm to specification and are

accepted.

 A deviation from specification is uncovered and a deficiency lists is created.

  Proposed system under consideration has been tested by using validation test
and found to be working satisfactory.

5.3.4 Output Testing

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.

5.3.5 User Acceptance Testing

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.

This is done in regard to the following point:

 Input Screen Design

 Output Screen Design

 Format of reports and other outputs.

5.4 Error Messages

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

System Implementation is the creation and the installation of the method to

follow the engineering principles to remove part of the human element in the equation.
Implementation is the process of realizing the design as a program. The data footprint
results presented is might unveil relative performance of different classification
techniques(given the memory system is generally deemed as the
bottleneck),computation steps are the mechanism involved in dealing with the data
structures are equally important and have to be taken into consideration.

To arrive at more accurate evaluation, here executed al classification and

throughput performance is measured. System Implementation is a practice of creating
or modifying a system to create a new business process or replace an existing business
process. Implementation of software refers to the final installation of the packages in its
real environment, to the satisfaction of the intended users and the operation of the
systems. The people are not sure that the software is meant to make their job easier.

 The active user must be aware of the benefits of using the system

 Their confidence in the software buildup

 Proper guidance is impaired to the user so that it is comfortable in using
the application
The system implementation phase consists of the following steps :

 Testing the developed software with sample data

 Correction of any errors if identified

 Creating the files of the system with actual data
 Making necessary changes to the system to find out errors
 Training of users personnel
The system has been tested with sample data, changes are made to the user
requirements and run in parallel with the existing system to find out the discrepancies.
When the number of threads are rises with respect to the number of cores. The user has
also been appraised how to run the system during the training period.

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.

The implementation phase’s construction, installation and operations lie on the

new system .The most crucial and very important stage in achieving a new successful
system and in giving confidence on the new system for the user that it will work
efficiently and effectively.

There are several activities involved while implementing project:

 Careful planning
 Investigation current system and its constraints on implementation

 Design of methods to achieve the change over

 Training of the staff in the changeover procedure and evaluation of change
over method
The implementation is the final stage and it is an important phase. It involves
the individual programming system testing, user training and the operational running of
developed proposed system that constitutes the application subsystems .On major task
of preparing for implementation is education of users, which would really have taken
place much earlier in the project when were being involved in the investigation and
design work. The implementation phase of software development is concerned with
translating design specifications into source code. The user tests the developed system
and changes are made according to their needs.

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.

Education and User Training

Well-designed and technically elegant systems can succeed or fail because of

the way they are operated and used. Therefore the quality of the training received by the
personnel involved with the systems help or hinder, and may even prevent, the
successful completion of the system. An analysis of user training focuses on user
capabilities and the nature of the system being installed. Those users are verifying type
and nature. Some of them may not have any knowledge about the computers and the
others may be intelligent. The requirements of the system also range from simple to
complex tasks. So the training has to be generated to the specific user based on his/her
capabilities and system’s complexity. The user tests the develop system and changes
are made according to their needs.

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.

User training must instruct individuals in trouble shooting the system,

determining whether a problem that arises is caused by hardware or software. The
implementation phase of the software development is concerned with translating design
specifications into source code. The user tests the developed system and changes are
made according to their needs. A good or bad perfect documentation which instructs the
user on how to start the system and the various functions and meanings of the various
codes must be prepared and that will help the user to understand the system in a better
manner.

System Maintenance

The process of modifying a software system or component after delivery to

correct faults, improves Performance or other attributes, or adapt to a changed
environment. Systems must be maintained and improved to meet changing business
demands or to correct processing errors. Systems maintenance phase begins when a
system becomes operational and ends when it is replaced. At some point, a new system
will reach the end of its useful life, and the analyst must be able to recognize the signs
of system obsolescence. There are many reasons for maintaining a system that fall into
the categories given above

 An error / bug is serious enough to need fixing.

 A new business process needs to be incorporated.

 A security vulnerability in the system has been found and needs patching.

 An user has identified how the system could be improved.

 The hardware or network is being improved and so the system should take
advantage of that.

There are four major activities that occur to perform maintenance.

Corrective Maintenance

Corrective maintenance can be defined as the maintenance which is required

when an item has failed or worn out, to bring it back to working order. Corrective
maintenance is carried out on all items where the consequences of failure or wearing
out are not significant and the cost of this maintenance is not greater than preventative
maintenance.

Corrective Maintenance activity may consist of repair, restoration or

replacement of equipment. This activity will be the result of a regular inspection, which
identifies the failure in time for corrective maintenance to be planned and scheduled,
then performed during a routine maintenance shutdown.

Corrective maintenance can be subdivided into

"Immediate Corrective Maintenance" - in which work starts immediately

after a failure

"Deferred Corrective Maintenance" - in which work is delayed in

conformance to a given set of maintenance rules. In this project the end user can easily
correct the faults.

Preventative Maintenance

Preventative maintenance is maintenance which is carried out to prevent an item

failing or wearing out by providing systematic inspection, detection and prevention of
incipient failure. The preventative maintenance efforts are aimed at preserving the
useful life of equipment and avoiding premature equipment failures, minimising any
impact on operational requirements. Preventative maintenance is carried out only on
those items where a failure would have expensive or unacceptable consequences e.g.
lifts, fire alarms, electricity supply and gas supply. Many of these items are also subject
to a statutory requirement for inspection and preventive maintenance.

Perfective Maintenance

Perfective maintenance is a system of making data input screen a better one to

deal with. It has a more advance system to work with, correcting error in a more unique
and perfect way. This is maintenance that will improve the performance of the ICT
system. Usually this will involve adding features not originally present to the software
to make it produce the information from a database faster or to improve the speed of a
network.

Examples of making the system 'more perfect' include

 A better data input screen or form

 A more advanced help system

 Tweaks to the code so it is more responsive

 Providing shortcuts commands that experts can use instead of the slower standard
menu system

Adaptive Maintenance

Adaptive maintenance is modifying the system to cope with changes in the

software environment. This type of maintenance often occurs as a result of external
influences or strategic changes within the company. The system is being adapted to
remain up to date. This system is developed as run in all types of environments.