SYSTEM ANALYSIS

System analysis introduces the concept of software architecture and architectural design.
This makes the system architecture explicit at an early stage in the software development.
This has a profound effect on whether the system can meet critical requirements such as
performance, reliability and maintainability. During this phase, the system is organized
by decomposing it into various sub-systems that provide some related set of services. For
a large system, these sub-systems are further divided into various modules. In case of
small projects, the sub-systems can themselves act as the modules. Thus, system analysis
involves the following:
I) Module Specification
II) Feasibility studies
III) Requirement Elicitation & Analysis

I) Module Specification:

The overall organization of the system divides the system into various sub-systems that
behave as independent systems in their own rights. Sub-systems are composed of
modules and have defined interfaces, which are used for communication other sub-
systems.
A module is normally a system component that provides one or more services to other
modules. It makes use of services provided by other modules. It is not normally
considered to be an independent system. Modules are usually composed from a number
of other simpler system components.
The system after careful analysis has been identified to be presented with the following
modules:
I. Admin
II. User
i) Registered
ii) Non registered

Admin
Admin is the one who monitors all users and user transactions. Admin haves the
complete information related to user and all the information related to the services. All
the data is maintained at the Admin level. Admin is having the rights to restrict any user.
It maintains authentication in order to access the application. Administrator task is
verified and sanction all requests from Civilizer s like passport registration, birth
registration, electricity registration etc... And he can view the feedbacks of website and
send mails.
 Admin
A_id
U_id
Amt
monitors( u_id)
maintain( u_id)
Registration()
acceptRequest(U_id)
Issueprocess()
Reports()
Search()
Servicedetails()
Mail()
Query()

monitors(s_id or u_id): All user accounts and monitors .

maintain(s_id or u_id):Maintain information about user details.
Registration(): user will register and admin will add new register.
AcceptRequestCard(): user apply for the service and admin will accept the request.
Payment(u_id,amt):payment process
issueProcess():information regarding status of the process.
Search():retrieving of information from database.
Reports():reports generated by the admin.
User
Registered
Any person who wants to utilize the services of website application at any time from
any where they should get registered in this application. After getting registered user can
apply for the required service. For this user has to furnish the required information and
get registered. User can query to the admin of the system. user can check th status of the
applied service. He can have the complete information of all the services details which he
applied.

User
u_id
u_name
Register()
ApplyService()
Checkstatus()
Query()
Search()
Servicedetails()
Payment()

Register():user need to register by furnishing all the details.

ApplyService():User need to apply for the service he want from the system.
Checkstatus():User can check the status of the applied service.
Query():User can query to the admin
Payment():user need to pay amount to the system.
Servicedetails():user can get the complete information regarding the applied services.
Visitor/Non-Registered
Visitor is the one who visits the Registro civil application and want to have the complete
information related to the Services Provided by the website

II) Feasibility studies:

Feasibility Study is a high level capsule version of the entire process intended to answer a
number of questions like: What is the problem? Is there any feasible solution to the given
problem? Is the problem even worth solving? Feasibility study is conducted once the
problem clearly understood. Feasibility study is necessary to determine that the proposed
system is Feasible by considering the technical, Operational, and Economical factors. By
having a detailed feasibility study the management will have a clear-cut view of the
proposed system.
Feasibility study is conducted once the problem is clearly understood. The objective is to
determine quickly at a minimum expense how to solve a problem. The purpose of
feasibility is not to solve the problem but to determine if the problem is worth solving.
In this phase, we study the feasibility of all proposed systems, and pick the best feasible
solution for the problem. The feasibility is studied based on three main factors as follows.

i) Technical feasibility

ii) Economical feasibility

iii) Operational feasibility

Technical feasibility:
In this step, we verify whether the proposed systems are technically feasible or not. i.e.,
all the technologies required to develop the system are available readily or not.
Technical Feasibility determines whether the organization has the technology and skills
necessary to carryout the project and how this should be obtained. The system can be
feasible because of the following grounds.

i) All necessary technology exists to develop the system.

ii) This system is too flexible and it can be expanded further.
 iii) This system can give guarantees of accuracy, ease of use, reliability
and the data security.
iv) This system can give instant response to inquire.
v) Our project is technically feasible because, all the technology needed
for our project is readily available.
The proposed system can be developed using existing technology or not. It is
planned to implement the proposed system using ASP.NET with C# and
databases are SQL Server 2005and with web server IIS 6.0 with the operating
system Windows XP.

Economical Feasibility:
In this step, we verify which proposal is more economical. We compare the financial
benefits of the new system with the investment. The new system is economically feasible
only when the financial benefits are more than the investments and expenditure.
Economical Feasibility determines whether the project goal can be within the resource
limits allocated to it or not. It must determine whether it is worthwhile to process with the
entire project or whether the benefits obtained from the new system are not worth the
costs. Financial benefits must be equal or exceed the costs. In this issue, we should
consider:
i) The cost to conduct a full system investigation.
ii) The cost of h/w and s/w for the class of application being considered.
iii) The development tool.
iv) The cost of maintenance etc.,

Our project is economically feasible because the cost of development is very minimal
when compared to financial benefits of the application.
Operational feasibility:
In this step, we verify different operational factors of the proposed systems like
man-power, time etc., whichever solution uses less operational resources, is the
best operationally feasible solution. The solution should also be operationally
possible to implement. Operational Feasibility determines if the proposed system
satisfied user objectives could be fitted into the current system operation. The
present system Enterprise Resource Information System can be justified as
Operationally Feasible based on the following grounds.
i) The methods of processing and presentation are completely accepted by the
clients since they can meet all user requirements.
ii) The clients have been involved in the planning and development of the
system.
iii) The proposed system will not cause any problem under any circumstances.

Our project is operationally feasible because the time requirements and personnel
requirements are satisfied.

III) Requirement Elicitation & Analysis:

In this activity, s/w engineers work with customers and system end-users to find out
about the application domain, what services the system should provide, the requirement
performance of the system, h/w constraints and so on. The whole process activities are:

In the requirement elicitation the user requirements can be obtained from the following

Error avoidance
At 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 is always likely to occur, these types of errors can be discovered by
using validations to check the input data.
Data validation
Procedures are designed to detect errors 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 user and the
user has to again key in the data and the system will accept the data only if the data is
correct. Validations have been included where necessary.