Scribd
Upload
91 views4 pages

Problem Definition: 2.1 Existing System

The document discusses the development of a project using distributed client-server computing technologies. The database was normalized up to 3NF to eliminate anomalies. User interfaces are browser-specific to provide distributed accessibility. The database uses MS-SQL Server 2000. Security, data consistency, and authentication/authorization were prioritized. A feasibility study found the project technically, operationally, and economically feasible.

Uploaded by

sushil soni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
91 views4 pages

Problem Definition: 2.1 Existing System

The document discusses the development of a project using distributed client-server computing technologies. The database was normalized up to 3NF to eliminate anomalies. User interfaces are browser-specific to provide distributed accessibility. The database uses MS-SQL Server 2000. Security, data consistency, and authentication/authorization were prioritized. A feasibility study found the project technically, operationally, and economically feasible.

Uploaded by

sushil soni
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as DOCX, PDF, TXT or read online on Scribd
You are on page 1/ 4

The entire projects has been developed keeping in view of the distributed client

server computing technology, in mind. The specification has been normalized up to 3NF to
eliminate all the anomalies that may arise due to the database transaction that are executed by
the general users and the organizational administration. The user interfaces are browser
specific to give distributed accessibility for the overall system. The internal database has been
selected as MS-SQL server 2000.

The basic constructs of table spaces, clusters and indexes have been exploited to
provide higher consistency and reliability for the data storage. The MS-SQL server 2000 was
a choice as it provides the constructs of high-level reliability and security. The total front end
was dominated using the ASP.Net technologies. At all proper levels high care was taken to
check that the system manages the data consistency with proper business rules or validations.

The database connectivity was planned using the latest “SQL Connection”
technology provided by Microsoft Corporation. The authentication and authorization was
crosschecked at all the relevant stages. The user level accessibility has been restricted into
two zones namely.

Problem Definition
2.1 Existing System
 Cannot Upload and Download the latest updates.
 No use of Web Services and Remoting.
 Risk of mismanagement and of data when the project is under development.
 Less Security.
 No proper coordination between different Applications and Users.
 Fewer Users – Friendly
Disadvantages
1. User friendliness is provided in the application with various controls.
2. The system makes the overall project management much easier and flexible.
3. Readily upload the latest updates, allows user to download the alerts by clicking the
URL.
4. There is no risk of data mismanagement at any level while the project development is
under process.
5. It provides high level of security with different level of authentication.
2.2. Proposed System
To debug the existing system, remove procedures those cause data redundancy, make
navigational sequence proper. To provide information about audits on different level and also
to reflect the current work status depending on organization/auditor or date. To build strong
password mechanism.

Advantages:
 User friendliness I provided in the application with various controls.
 The system makes the overall project management much easier and flexible.
 Readily upload the latest updates ,allows user to download the alerts by
clicking the url.
 It provides high level of security with different level of authentication.

Feasibility Study

Preliminary investigation examine project feasibility, the likelihood the system will be
useful to the organization. The main objective of the feasibility study is to test the Technical,
Operational and Economical feasibility for adding new modules and debugging old running
system. All system is feasible if they are unlimited resources and infinite time. There are
aspects in the feasibility study portion of the preliminary investigation:

 Technical Feasibility
 Operation Feasibility
 Economical Feasibility

3.1. Technical Feasibility

The technical issue usually raised during the feasibility stage of the investigation
includes the following:

 Does the necessary technology exist to do what is suggested?


 Do the proposed equipments have the technical capacity to hold the data required to use
the new system?
 Will the proposed system provide adequate response to inquiries, regardless of the
number or location of users?
 Can the system be upgraded if developed?
 Are there technical guarantees of accuracy, reliability, ease of access and data security?

Earlier no system existed to cater to the needs of ‘Secure Infrastructure


Implementation System’. The current system developed is technically feasible. It is a web
based user interface for audit workflow at NIC-CSD. Thus it provides an easy access to the
users.

The database’s purpose is to create, establish and maintain a workflow among various
entities in order to facilitate all concerned users in their various capacities or roles.
Permission to the users would be granted based on the roles specified. Therefore, it provides
the technical guarantee of accuracy, reliability and security.

The software and hard requirements for the development of this project are not many
and are already available in-house at NIC or are available as free as open source. The work
for the project is done with the current equipment and existing software technology.
Necessary bandwidth exists for providing a fast feedback to the users irrespective of the
number of users using the system.

3.2. Operational Feasibility

Proposed projects are beneficial only if they can be turned out into information
system. That will meet the organization’s operating requirements. Operational feasibility
aspects of the project are to be taken as an important part of the project implementation.
Some of the important issues raised are to test the operational feasibility of a project includes
the following: -

 Is there sufficient support for the management from the users?


 Will the system be used and work properly if it is being developed and implemented?
 Will there be any resistance from the user that will undermine the possible application
benefits?

This system is targeted to be in accordance with the above-mentioned issues.


Beforehand, the management issues and user requirements have been taken into
consideration. So there is no question of resistance from the users that can undermine the
possible application benefits.

The well-planned design would ensure the optimal utilization of the computer resources and
would help in the improvement of performance status.

3.3. Economic Feasibility


A system can be developed technically and that will be used if installed must still be a good
investment for the organization. In the economical feasibility, the development cost in
creating the system is evaluated against the ultimate benefit derived from the new systems.
Financial benefits must equal or exceed the costs.

The system is economically feasible. It does not require any addition hardware or
software. Since the interface for this system is developed using the existing resources and
technologies available at NIC, There is nominal expenditure and economical feasibility for
certain.

System Analysis

4.1. Software Requirement Specification (SRS)


The software, Site Explorer is designed for management of web sites from a remote locatio

You might also like