Concurrent Version Schema

S.No TITLE P.No

1. SYNOPSIS

2. INDRODUCTION & SYSTEM STUDY

2.1 Project overview

2.2 Problem definition

3. PROBLEM ANALYSIS

3.1 Solution strategies

3.2 H/W & S/W Requirements
3.3 S/w justification

4. DESIGN & DEVELOPMENT PROCESS

4.1 Module Design

4.2 Design Notations

A. Data flow Diagram

B. Structure Chart
C. E-R Diagram

4.3 Design process

A. Data base design

B. Input design
C. Output design
 5. TESTING & IMPLEMENTATIONS

5.1 System testing

5.2 System Implementation
5.3 System Maintenances

6. CONCLUSSION

6.1 Scope for future Enhancement

6.2 Bibliography

7. APPENDIX

 SCREEN LAYOUTS
 CODE LIST
 REPORTS
 Synopsis

CVS is a version control system, an important component of Source Code Configuration

Management. Using it, you can record the history of sources files.

CVS stores individual file history. It can run scripts which you can supply to log CVS
operations or enforce site-specific polices.

 CVS enables developers scattered by geography or slow modems to function as a

single team. The version history is stored on a single central database and the all
the system sharing the copy of all the files that the developers are working on.
Therefore, the network between the developers must be up to perform CVS
operations (such as checking or updates) but need not be up to edit or manipulate
the current versions of the files. Developers can perform all the same operations
which are available locally.
 In cases where several developers or teams want to each maintain their own
version of the files, because of geography and/or policy, CVS can import a
version from another module within a project, and then CVS can merge the
changes from the module with the latest files if that is what is desired.
 Unreserved checkouts, allowing more than one developer to work on the same
files at the same time.
 CVS provides a flexible modules database that provides a symbolic mapping of
names to components of a larger software distribution. It applies names to
collections of directories and files. A single command can manipulate the entire
collection.
Problem in Existing System

In information technology and telecommunications, the term configuration management

or configuration control has the problem of managing the source code and the project
documentation of the complete project. New release and updates of the project are not
completely updated and maintained. This becomes a major challenge in the current IT
Industry. May critical problems have been raised and still they have not be solved and it
becomes an huge risk for the IT firm to manage it.

Several Techniques and technology have been developed and many research and
development were still on the way to provide a better quality.

Proposed System:

The Problems in the IT industry regarding the configuration details can be solved by our
project. The management of features and assurances through control of changes made to
hardware, software, firmware, documentation, test, test fixtures and test documentation of
an automated information system, throughout the development and operational life of a
system. Source Code Management or revision control is part of this project.

The control of changes, including the recording thereof, that are made to the hardware,
software, firmware, and documentation throughout the system lifecycle. The control and
adaptation of the evolution of complex systems. It is the discipline of keeping evolving
software products under control, and thus contributes to satisfying quality and delay
constraints. .After establishing a configuration, such as that of an IT or computer system,
the evaluating and approving changes to the configuration and to the interrelationships
among system components.
This project contains following modules:

ADMINISTRATOR MODULE:
This module helps the administrator to get the source code from the user and
register it into the server database. Depending on the information given by the data
management group the data or code would be stored in the system. If the client wants to
know the status of their files then they can get it from the administrator. The
Administrator would get the requested data from quality analyst’s database.

Login (Cryptography)

This module is used for authentication purpose. Any registered employee who is
trying to enter his work area is checked for his id and password .If he is authorized then
he would be allowed to enter into his work area.

Token Rising

The main motivation of this module each employee should contain task and other
employee not allow doing same task... The project leader assigns each task by the tokens.

Each employee gets the task based on the token raised and the status of the token. Each
token will be allocated to the employee as per the previous work allocated and time
duration of the work and the work details of the employee.

Task Allocation

This module helps the employee to track the current status of the project on which
a employee operator is working on. Task will be allocated on a concurrent basis to the
employee as per the work completion criteria and work duration criteria. Any updates in
the new task will be updated as per the process and this will be updated before assigning
the work to the specific employee. This module also ensures that the same task should not
be shared with some other employee so as to reduce the communication gap between the
employee and to complete the work within the time frame and ensure error free
completion. Each task allocated to the employee will be monitored and updates in the
work will be notified and recorded for further tracking.
This module ensures that the work allocated should not be altered after assign of
work to the employee to re-assign to some other employee as it may cause critical errors
in the project. Only with the redundant situations the task may be re-assigned to some
other employee but make ensure that the work assigned to the new employee is in the
same technology and with having the knowledge of the given work so has to avoid
confusion and critical errors in the project.

Database sharing

A new separate database will be created and maintained to hold the

completed configuration of the project. The temporary database will be moved to the
Permanent database on the given criteria basis. Any updates in the temporary
database will be updated only with the given duration and the permanent database
will be updated after moving from the temporary database only.

Report Generation

Reports will be generated for the each stage of the project based on the
requirement. Reports for the permanent database will be created and generated on the
task and criteria basis.

Software Requirements:

Front End: ASP.NET

Back End: SQL

Operating System: Windows 2000/Xp

DATAFLOW DIAGRAM:

The data flow diagram (DFD) is one of the most important tools used by system analysts.
Data flow diagrams are made up of a number symbols, which represent system
components. Most data flow modeling methods use four kinds of symbols. These
symbols are used to represent four kinds of system components. Processes, data stores,
data flows and external entities. Processes are represented by circles in DFD. Data Flow
represented by a thin line in the DFD and each data store has a unique name and square
or rectangle represents external entities.

Unlike detailed flowchart, Data Flow Diagrams do not supply detailed description of the
modules but graphically describes a system’s data and how the data interact with the
system.

To construct a Data Flow Diagram, we use,

 Arrow
 Circles
 Open End Box
 Squares

An arrow identifies the data flow in motion. It is a pipeline through which information is
flown like the rectangle in the flowchart. A circle stands for process that converts data
into information. An open-ended box represents a data store, data at rest or a temporary
repository of data. A square defines a source or destination of system data.

Six rules for constructing a Data Flow Diagram

 Arrows should not cross each other.

 Squares, circles and files must bear names.
 Decomposed data flow squares and circles can have same names.
 Choose meaningful names for data flow
 Draw all data flows around the outside of the diagram.
Level – 0 DFD

Login Request
Concurrent Version
USER Schema Administrator
Authenticate Response

Token Primary Storing

Raising Database process

Permanent Database
 ADMINISTRATOR DFD

Level 1

Admin Login

Admin Client Data Client

Authenti
Detail
Store
cation

valid

Client
Client Report Store Requiremen
t

Invalid Project
Project Detail Store
Detail
Client
Requir

Emp Detail Store

Emp
Detail

Schedul
e Project scheduling
Project details
Manager save

view

Report
 Level 2

Project Manager
Detail
Detail

Authentic valid Allocate Emp

Team Leader Detail
Prj manager
Login

Report

Invalid
 Level 3

Team Leader

valid Allocate
Authenticat Task
Team Leader
Login ion Proj
Data

Developer
Allocation Emp
Invalid
Data

Task detail

View
 ENTITY RELEATIONSHIP DIAGRAM:

Pname Databas
Report e Language
ProjName
Tlid
Code

EmpNam
Project Pmid Employee
Duration e
Register Report Allocation

TokenN
Empid o
Task

Pid Result

Task
Allo Allocation Allo
cate cate
d d

Pid Tokeni
Empid d Task

Token Set
Token

TokenN
1 oO Task
Project
Get Name
Task

Result Source
Empid Code

1 1
Task
TokenN
oO

Task Store
Complete code
Table Design:
EmpAlloc

EmployeeMaster
NewEmployee

NewPm
NewTl

PMMster

project_registr
project_registrattion

Tlallocation

TLMster

TokenSet
Cost Estimation an Scheduling

Estimating Cost

There are many factors to consider when estimating the total cost of a
project. These include labor, hardware and software purchases or rentals, travel
for meeting or testing purposes, telecommunications (e.g., longdistance phone
calls, video-conferences, dedicated lines for testing, etc.), training courses, office
space, and so on.

Exactly how you estimate total project cost will depend on how your
organization allocates costs. Some costs may not be allocated to individual
projects and may be taken care of by adding an overhead value to labor rates ($
per hour).

Often, a software development project manager will only estimate the labor
cost and identify any additional project costs not considered “overhead” by the
organization. The simplest labor cost can be obtained by multiplying the project’s
effort estimate (in hours) by a general labor rate ($ per hour). A more accurate
labor cost would result from using a specific labor rate for each staff position
(e.g., Technical, QA, Project Management, Documentation, Support, etc.). You
would have to determine what percentage of total project effort should be
allocated to each position. Again, historical data or industry data models can help.

Nominal Project Plan For 4 Months

Management Metric Planning Value

Direct Resources Costing 25 %
Indirect Resource Costing 5%
No of Employees 18.2%
Hosting Plan 5%
Development Plan 30.8%
Testing Plan 14%
Maintenance 2%

Project Scheduling

Requirement Analysis Starting Date Ending Date

System Study and Requirements Dec13, 2006 Dec27, 2006

Analysis
System Requirement Specification Dec28, 2006 Dec30, 2006

High Level Design Starting Date Ending Date

Breaking into Sub-Systems Jan02, 2007 Jan05, 2007

(Modules)
Prototype Development Jan06, 2007 Jan15, 2007

Logical Database Design Jan16, 2007 Jan23, 2007

Low Level Design Starting Date Ending Date

Physical Database Design Feb04, 2004 Feb07, 2004

User Interface Design (form Design) Feb08, 2004 Feb13, 2004

Coding Feb15, 2004 Feb28, 2004

Test Case Design and Starting Date Ending Date

Debugging
Recovery Testing Mar01, 2007 Mar04, 2007
Debugging of errors Mar05, 2007 Mar06, 2007

Stress Testing Mar07, 2007 Mar11, 2007

Debugging of errors Mar12, 2007 Mar13, 2007

Performance Testing Mar14, 2007 Mar16, 2007

Debugging of errors Mar13, 2007 Mar15, 2007

User Acceptance Testing Mar17, 2007 Mar20, 2007

INPUT DESIGN
Input design is a part of overall system design. The main objective during the
input designs the input designs is given bellow:
 To produce a cost-effective method of input.
 To achieve the highest possible level of accuracy
 To ensure that the input is acceptable and understood by the user.
INPUT STAGES
The main input stages can be listed bellow:
 Administrator
 Token Rising
 Task Allocation
 Database Sharing

INPUT TYPES
It is necessary to determine the various types of inputs can be categorized as
follows:
 External inputs, which are prime inputs for the system
 Internal inputs, which are user communication with the system.
 Operational, which are computer department’s communication to the
system
 Interactive, which are inputs entered during a dialogue
INPUT MEDIA
At this stage choice has to be made the input media. To conclusion about the input
media consideration has to be given to:
 Type of output
 Flexibility of format
 Speed
 Accuracy
 Verification methods
 Rejection rates
  Ease of correction
 Storage and handling requirements
 Security
 Easy to use
 Portability
Keeping in view the above description of the input types and input media, it can
be said that most of the inputs are of the form of internal and interactive. As input data is
to be the directly keyed in by the user, the keyboard can be considered to be the most
suitable input device.

ERROR AVOIDANCE
As this stage care is to be taken to ensure that input data remains accurate form
the stage at which it is recorded up to the stage in which the data is accepted by the
system. This can be achieved only by means of careful control each time the data is
handled

ERROR DETECTION
Even though every effort is make to avoid the occurrence of errors, still a small
proportion of errors are always likely to occur, these types of errors can be discovered by
using validation to check the input data.

DATA VALIDATION
Procedures are designed to detect error in data at a lower level of detail. Data
validations have been included in the system in almost every area where there is a
possibility for the user to commit errors. The system will not accept invalid data.
Whenever an invalid data is keyed in, the system immediately prompts the system will
accept the data only if the data is correct. Validations have been included where
necessary.
 The system is designed to be a user friendly one. In other words the system has
been designed to communicate effectively with the user. The system has been designed
with pop up menus.

USER INTERFACE DESIGN

It is essential to consult the system users and discuss their needs while designing
the user interface. The user interface system can be broadly classified as:
 User initiated interface the user is in charge. Controlling the computer-
initiated interface, the computer selects the next stage in the interaction.
 Computer initiated interfaces
In the computer initiated interfaces the computer guides the progress of the
user/computer dialogue. Information is displayed and tJhe user response of the computer
takes action or display further information.

USER INITIATED INTERFACE

User initiated interface fall into two approximate classes:
 Command driven interfaces: in this type of interface the user inputs
commands or queries which are interpreted by the computer.
 Forms oriented interface: the user calls up an image of the form to his/her
screen and fills in the form. The forms oriented is chosen because it is the
best choice.

COMPUTER-INITIATED INTERFACE
The following computer-initiated were used:
 The menu system for the user is presented with a list of alternatives and
the user chooses on: of alternatives.
 Question –answer type dialog where the computer asks question and takes
action based on the basis of users reply.
Right form the start the system is going to be menu driven; the opening menu
displays the available options. Choosing one option gives another popup menu with more
option. In this way every option leads the users to data entry where the user can key in
the data

ERROR MESSAGE DESIGN

The design of the error massages is a important part of the user interface design.
As user is bound to commit some error or other will design a system should be design to
be helpful by providing the user information regarding the error he/she has committed.
This application is able to produce the output at different modules of different inputs.

PERFORMANCE REQUIREMENT
Performance is measured in terms of report generation weekly and monthly.
Requirement specification is play important parts in the analysis of the system. Once the
requirement specifications are properly given, it is possible to design the system, which
will fit into the required environment. It rests largely in the par of the user of existing
system to give the requirement specification because they are the people who finally use
the system. This is because the requirements have to be known during the initial stages
so that the system can be designed according to those requirements. It is very difficult to
change the system once it has been designed and on the other hand designing a system,
which does not cater to the requirements of the user, is of no use. Stage as given bellow:
 The system to able to interface with the existing system
 The system is to be accurate
 The system to be better than the existing system
The existing system is completely dependent on the staff to perform all duties.

OUTPUT DEFINITION
The output should be defined in terms of the following points:
 Type of the output
 Content of the output
 Format of the output
 Location of the output
 Frequency of the output
  Volume of the output
 Sequence of the output
It is not always desirable to print to display data as it is held on a computer. It
should be decided as which form of the output is the most suitable.
OUTPUT MEDIA
In the next stage it is to be decided that which medium is the most appropriate for
the output. The main consideration when deciding about the output media are:

The suitability or the device to the particular application.

 The need for hard copy
 The response time required
 The location of the users
 The software and hardware available
 The cost
Keeping in view the above description the project is to have outputs mainly coming under
the category of internal outputs. The main outputs desired according to the requirement
specification are:
 The outputs were needed to be generated as a hot copy and as well as
queries to be viewed on the screen.
 Keeping in view these outputs
 The format for the output is taken form the outputs
 Which are currently being obtained after manual processing
 The standard printer is to be used as output media for hard copies

PROJECT TESTING

Testing is the most important phases in the software development activity. In software
development life cycle (SDLC), the main aim of the testing process in the quality, the
developed software is tested against attaining the required functionality and performance.
 During the testing process the software is worked with some particular test case and
the output of the test cases are analyzed whether the software is working according to the
expectations or not.

The success of the testing process in determining the error is mostly depends upon the
test case criteria, for testing any software we need to have a description of the expected
behavior of the system and method of determining whether the observed behavior confirmed
to the expected behavior.

LEVEL OF TESTING

Since the error in the software can be injured at any stage. so, we have carry out the testing
process at different levels during the development. The basic levels of testing are
 Unit Testing
 Integration Testing
 System Testing
 Acceptance Testing.
The Unit Testing is carried out on coding.here different modules are tested against the
specification produced during design for the modules .In case of integration testing different
tested are combined into sub system and tested in case of the System testing the full software
is tested and in the next level of testing the system is tested with user requirement document
prepared.

UNIT TESTING
Unit testing mainly focused first in the smallest and low level modules, proceeding one at a
time. Bottom-up testing was performed on each module. As developing a driver program, the test
modules by developed or used. But for the purpose of testing modules themselves were used as
stubs, to print verification of the actions performed. After the lower level modules were tested, the
modules that the next higher level those make use of the lower modules were tested

Each module was tested against required functionality and test cases were developed to test
boundary values.

The unit testing has been tested with sample data and adequate corrections were made as per
the user requirement, such that login module was tested with user id and code and appropriate error
messages are provided for errors like data entry error, id error,etc.

INTEGRATION TESTING
Integration testing is a systematic technique for constructing the program structure, while at
the same time conducting tests to uncover error associated with interfacing. As the system consists
of the number the edges of the two modules. The software tested under this incremental bottom-up
approach.

Bottom-up approach integration strategy was implemented with the following steps.

 Low modules were combined into clusters that perform specific software sub function
 The clusters were tested

TESTING PROCESS
A number of activities must be performed for testing software. Testing start with test
plan. Test plan identifies all testing related activities that need to be performed along with the
schedule and guide lines for testing. The plan also specified the levels of testing that need to be
done, by identifying the different testing units. For each unit specified in the plan first the test
cases and reports are produced. These report are analyzed.
TEST PLAN
Test plan is a general document for entire project, which defines the scope, approach to be
taken and the personal responsible for different activities of testing. The inputs for forming test
plan are
  Project Plan
 Requirements Document System Design

There are two basic approaches for testing. They are

 Functional Testing
 Structural Testing
SYSTEM TESTING
Series of different tests whose primary purpose is to fully exercise the computer-based
system. It also tested to find discrepancies between the system and its original objective,
current specifications.10011

EXECUTION TESTING
This program was successfully loaded and executed. Due to programming there were no
execution errors as fall as possible

QUALITY ASSURANCE
Quality assurance defines the objectives of a project and reviews
the overall activities so that error are corrected early in the development process.

LEVELS OF QUALITY ASSURANCE

Quality Assurance comes in three main levels namely
 Testing
 Validation
 Certification

TESTING
In system testing a common view is to eliminate program errors. This is
extremely difficult and time consuming. Since designers cannot prove 100% accuracy. A
successful test, then, is one that find errors.
VALIDATION
It checks the quality of the software in both simulated and live
environments. In the Simulated approach the developers test the product on their
workplace to make the products meet its requirements. In the Live Environment phase
the product is given to the customer to evaluate the product’s functionality.

Validation refers to the different set of activities that ensure that software
correctly implements a specific function and the software that been built is
traceable to customer requirements. Verification and validation can be defined in a
way like:
 Verification
 Validation
Software validation is achieved through a series of black-box test that demonstrate
conformity with requirement. After each validation check a test has been conducted, one
of the two possible condition exists

 The function or performance characteristics conform to specification and are

expected
 A deviation from specification is uncovered and a deficiency list is created

ALPHA AND BETA TESTING

The alpha testing is conducted at the developer’s site by the customer. the
software is used in the natural setting with the developer”looking over the developer” and
recording errors and usages problems. Alpha test is conducted in controlled environment

The beta testing is conducted at one or more customer site by the end user of the
software. Unlike software testing the developer is generally not present. Therefore beta
test is live application of the software in an environment that cannot be controlled by the
developer
 VALIDATION CHECK APPLIED IN THE PROJECT
 The files entered in the project must only have the doc extension
 The data entered must have only one format
 One should not make a enter into without checking the password
 The qc must enter into the status column only accepted or not accepted
 File which are already be registered should not be registered once again or
other time
 Qc can’t enter the file which are not entered by the dc
 Qc should enter the file into corresponding filenames registered by the dc
 Files which are registered and not accepted for the first time should not be
registered again but the reentry of date and status should be done only

CERTIFICATION
Certification is to certify that the program or software package is correct
and confirms to standards. With growing trend towards purchasing ready to use software,
certification has become more important.

System Security

Software integrity has become increasingly important in the age of hackers and
firewalls. This attributes measures a system ability to withstand attacks (both accidental
and intentional) to its security. Attacks can be made on all three components of software
program, data, and documents
To measure integrity, two additional attributes must be defined
o Thread
o Security

THREAD
Threat is the probability (which can be derived or estimated from empirical
evidence) that an attack of specific type occur with in a specific time.
SECURITY
Security is the probability (which can be estimated or derived from empirical
evidence) that attack on the specific type will be repelled.

SECURITY TESTING
Any computer based system that manages sensitive information or causes action
that can improperly harm(or benefit) individuals is the target for improper or illegal
penetration. Penetration spans a board range of activities; hackers who penetrate system
for sport; disgruntled employee who attempt to penetrate for revenge; dishonest
individual who penetrate for illicit personnel gains
Security testing to verify that protection mechanism built into a system will
in fact provide proper protection form improper penetration. During system testing, the
tester plays the role of the individual who desires to penetrate the system. Anything goes!
The tester may attempt to acquire password through external clerical means; may attack
the system with custom software designed to break down any defenses that have been
constructed may overwhelm the system thereby denying the service to other; may
purposely cause system errors.

IMPLEMENTATION

Implementation is used here to mean the process of converting a new or revised

system design into operational one; conversion is one aspect of implementation. the other
aspect is post implementation review and software and maintenance
There are three type of implementation:

 Implementation of a computer system

 Implementation of new computer system
 Implementation of a modified application

IMPLEMENTATION OF THE COMPUTER SYSTEM

 It’s should be replace a manual system the problems encountered are converting
files, training users creating accurate files, and verifying printouts for integrity

IMPLEMENTATION OF NEW COMPUTER SYSTEM

It’s should be replace an existing one this is usually a difficult conversion. if not
properly planned there can be many problems. Some large computer system have taken
even years to convert

IMPLEMENTATION OF A MODIFIED APPLICATION

It’s should be replace an existing one using the same computer. This type of
conversion is relativity easy to handle, provided there are no major changes to the file

MAINTENANCE

After the system has successfully implemented maintenance activity may require
continuous involvement of the developers. Provision must be made for environmental
changes, which may affect either the computer, or other parts of computer based system:
such activity is normally called maintenance. It includes both the improvement of system
functions and the correction of faults that arise during the operation of a system.

Maintenance activity may require the continuing involvement of a large

proportion of computer department resources. Maintenance works may arise due to two
reasons.
 Error that creep up during normal running.
 Request for changes by the service providers. As part of the normal
running of the system when errors are found.

This maintenance work will help to ensure that the system works smoothly as
predicted in the open environment. Whenever a maintenance work arises, the work has to
be properly carried out with proper documentation. This is to avoid any form of changes
in the structure of the system.
For every maintenance work an amendment notification is to be issued. This notification
will have the required changes and also authenticated. On receipt of the amendment
notification the amendment log is prepared which records these courses of action that has
been planned to be taken. It also records the estimated and the actual completion of each
of the activities.

Generic Risks

A risk is an unwanted event that has negative consequences. Project managers will
engage in risk management to understand and control the risks on their projects. We can
distinguish risks from other project events by looking for three things:

 A loss associated with the event.

 The likelihood that the event will occur.

The degree to which we can change the outcome.

The generic risks such as the Product size risk, business impact risks, Customer–Related
risks, Process risks, Technology risks, Development environment risks, Security risks etc.
for this project are analyzed and documented by the senior staffs in the organization. This
project is developed by considering these issues and with the constant support from
senior staffs in the organization.

Security Technologies and Policies

The software quality assurance is comprised of a variety of tasks associated with

seven major activities.
1. Application of technical methods.
2. Conduct of formal technical reviews
3. Software testing
4. Enforcement of standards
5. Control of change
6. Measurement
 7. Record keeping and reporting
The quality begins with a set of technical methods and tools that help the analyst
to achieve high quality specification and the designer to develop high-quality design.
The next activity involves assessment for quality for the design that is created
which is the formal technical review.
Software testing combines a multi step strategy with a series of test case design
methods that help ensure effective error detection.
It is assumed that testing will uncover most of the errors. In most cases the
standards are dictated by customers, in other situations, by self-imposed.
Every change to software has the potential for introducing errors or creating side
effects that propagate errors. The change control process contributes directly t software
quality by formalizing request for change, evaluating the nature of change and controlling
the impact of change.
An important objective of quality assurance is to track the software quality and
assess the impact of methodological and procedural changes on improved software
quality.
Record keeping and recording for software quality assurance provide procedures
for the evaluation and separation of Software quality assurance information

System Implementation

Implementation is the stage of the project where the theoretical design is

turned into a working system. At this stage the main work load, the greatest upheaval and
the major impact on the existing system shifts to the user department. If the
implementation is not planned and controlled it can cause chaos and confusion.
Implementation includes all those activities that take place to convert from the old
system to the new one. The new system may be totally new, replacing an existing manual
or automated system or it may be a major modification to an existing system. Proper
implementation is essential to provide a reliable system to meet the organization
requirements.Successful implementation may not guarantee improvement in the
organization using the new system, but improper installation will prevent it.
 The process of putting the developed system in actual use is called system
implementation. This includes all those activities that take place to convert from the old
system to the new system. The system can be implemented only after thorough testing is
done and if it is found to be working according to the specifications. The system
personnel check the feasibility of the system.
The most crucial stage is achieving a new successful system and giving
confidence on the new system for the user that it will work efficiently and effectively. It
involves careful planning, investigation of the current system and its constraints on
implementation, design of methods to achieve the changeover. The more complex the
system being implemented, the more involved will be the system analysis and the design
effort required just for implementation. The system implementation has three main
aspects. They are education and training, system testing and changeover.
The implementation stage involves following tasks.
Careful planning.
Investigation of system and constraints.
Design of methods to achieve the changeover.
Training of the staff in the changeover phase.
Evaluation of the changeover method.

The method of implementation and the time scale to be adopted are found out
initially. Next the system is tested properly and the same time users are trained in the
new procedures.

Implementation Procedures

Implementation of software refers to the final installation of the package in its real
environment, to the satisfaction of the intended users and the operation of the system. In
many organizations some one who will not be operating it, will commission the software
development project. The people unaware that the software is meant to make their job
easier. In the initial stage, they doubt about the software but we have to ensure that the
resistance does not build up as one has to make sure that
 - The active user must be aware of the benefits of using the system
- Their confidence in the software is built up
- Proper guidance is imparted to the user so that he is comfortable in using the
application.
Before going ahead and viewing the system, the user must know that for viewing the
result, the server program should be running in the server. If the server object is not up
running on the server, the actual processes won’t take place.

User Training
To achieve the objectives and benefits expected from computer based system, it is
essential for the people who will be involved to be confident of their role in the new
system. As systems become more complex, the need for education an training is more
and more important.
Education is complementary to training. It brings life to formal training by
explaining the background to the resources for them. Education involves creating the
right atmosphere an motivating user staff. Education sections should encourage
participation from all staff with protection for individuals for group criticism. Education
should start will before any development work to enable users to maintain or to regain the
ability to participate in the development of their system.
Education information can make training more interesting and more
understandable. The aim should always be to make individual feel that they can still make
all important contributions, to explain how they participate in making system changes,
and to show that the computer and computer staff do not operate in isolation, but are of
the same organization.

Training on the Application Software

After providing the necessary basic training on the computer awareness

the users will have to be trained on the new application software. This will give the
underlying philosophy of the use of the new system such as the screen flow, screen
design, type of help on the screen, type of errors while entering the data the
corresponding validation check at each entry and the ways to correct the data entered. It
should then cover information needed by the specific user/groups to use the system or
part of the system while imparting the training of the program on the application. This
training may be different across different user groups and across different levels of
hierarchy.

Operational Documentation

Once the implementation plan is decided, it is essential that the user of the system
is made familiar and comfortable with the environment. Education involves right
atmosphere & motivating the user. A documentation providing the whole operations of
the system is being developed. The system is developed in such a way that the user can
work with it in a well consistent way. The system is developed user friendly so that the
user can work the system from the tips given in the application itself. Useful tips and
guidance is given inside the application itself to help the user. Users have to be made
aware that what can be achieved with the new system and how it increases the
performance of the system. The user of the system should be given a general idea of the
system before he uses the system.

System Maintenance

The maintenance phase of the software cycle is the time in which a Software
product performs useful work.
After a system is successfully implemented, it should be maintained in a proper
manner. System maintenance is an important aspect in the software development life
cycle. The need for system maintenance is for it to make adaptable to the changes in the
system environment. There may be social, technical and other environmental changes,
which affects a system, which is being implemented. Software product enhancements
may involve providing new functional capabilities, improving user displays and mode of
interaction, upgrading the performance characteristics of the system. So only through
proper system maintenance procedures, the system can be adapted to cope up with these
changes.
Software maintenance is of course, far more than “finding mistakes”. We may
define maintenance by describing four activities that are undertaken to after a program is
released for use.
The first maintenance activity occurs because it is unreasonable to assume that
software testing will uncover all latent errors in a large software system. During the use
of any large program, errors will occur and be reported to the developer.
The process that includes the diagnosis and correction of one or more errors is
called corrective maintenance.
The second activity that contributes to a definition of maintenance occurs because
of the rapid change that is encountered in every aspect of computing. Therefore, adaptive
maintenance- an activity that modifies software to properly interfere with a changing
environment is both necessary and commonplace.
The third activity that may be applied to a definition of maintenance occurs when
a software package is successful. As the software is used, recommendations for new
capabilities, modifications to existing functions, and general enhancements are received
from users. To satisfy requests in this category, perfective maintenance is performed.
This activity accounts for the majority of all effort extended on software maintenance.
The fourth maintenance activity occurs when software is changed to improve
future maintainability or reliability, or to provide a better basis for future enhancements.
Often called preventive maintenance, this activity is characterized by reverse engineering
and techniques.
Screen Shots: