CHAPTER 5 System Analysis

CHAPTER 5

5.1 Problem Identification

Problem identification is very first step of system analysis. The analyst meets with the candidate and the company’s placement. Here in our case both candidates and the company placement and end-user are the former and candidate . In this step, we are interested to understand the product’s objective and defined the goals required to meet the objective. After identifying overall goals, we moved towards evaluation of supplementary information during preliminary investigation. We also focused on “does the technology exit to build the system?” and “what bounds have been placed on costs and schedule”. To perform it we scanned followings:

Ø The performance of the system

Ø The information being supplied and its form

Ø The economy of processing

Ø The control of the information processing

Ø The efficiency of the existing system

Ø The security of the data & software

5.2 Preliminary Investigation

Once the request for the information system development is received, the first system activity “ preliminary investigation ” begins. This activity is independent of the software-engineering paradigm. That means whether a system will be developed by means of the system development life cycle (SDLC), a prototyping strategy, or the structured analysis method, or a combination of these methods, preliminary investigation must be performed first. This activity has three parts:

· Request Clarification

· Study and

· Approval

It may be possible that the request that has been received is not clearly defined and it is difficult to figure out what for the request is. So, in that case, the person who has made the request is contacted and asked to explain the request. If the request is appropriate enough then in that case feasibility study is carried out for that request. I.e. before the feasibility study, the request must be determined and defined precisely. After request clarification the feasibility study is performed. If the request for the information system is feasible in the request is approved and then starts the real analysis phase called “Requirement study”. The data that are collected from the organization as the part of preliminary investigation is follows three mechanisms also called “ Fact Finding Techniques “:

· Reviewing existing Documents material and existing systems (web sites)

· Conducting Interviews and

· On-Site Observation

To conduct preliminary investigation, we contacted with the perfect placement like noida , employment exchange, mrg placement etc. The very first impression validates the request for the automation (i.e. Information System development). I talked with head of the company and the subordinates about the current working system and about the tasks they were performing. We used all the three fact-finding techniques for data collection. We collected various papers & documents related to the activities like the objective and subjective exams. And conducted marketing surveys to know the interest among the people associated and attached with different organization .It was surprising to know that most of them were very interested in computers and has the better understanding of Computer & Information Systems. Both were very helpful in passing the exact information we were looking for. Reviewing the traditional one and having own experience in the field helped us immensely in the knowing the data items being processed by the system. It also helped in understanding the complexities of the working process of the web site.

Latter on, we examined the various kinds of reports and result the company were producing. The above said fact finding techniques not only helped in the understanding of the system but also proposed some solutions to the new information systems.

5.2.1 Information Content:

Information content represents the individual data and control objects that constitute some larger collection of information transformed by the software. In our case the object, which is composite of a number of important pieces of data as project, package and item with its category. So the contents is defined by the necessary attributes required to create it. During the analysis of the information domain the inter relationship between objects is also defined.

5.2.2 Information Flow:

Information flow represents the manner in which data and control changes as each moves through a system. Input objects are transformed into intermediate information, which is further transformed to output. Here, additional information is also supplied and transformations are some engineering functions/formulae.

5.2.3 Information Structure:

Information structure represents the internal organization of various data and control items. Some queries are answered like “how does information in one information structure relate to information in another structure?”, “is all information contained within a single structure or are distinct structure to be used?”.

5.2.4 Feasibility Study:

5.3.1 Introduction:

The feasibility study of any system is mainly intended to study and analyze the proposed system and to decide whether the system under consideration will be viable or not after implementation. That is it determines the usability of the project after deployment. To come to result a set of query is answered keeping the efficiency of the software and its impact on the domain for which it was developed. It main emphasis is on the following three questions elucidated below as:

What are the user’s requirements and how does a candidate system meet them?

What resources are available for the proposed systems? Is it worth solving the problem?

What is the likely impact of the proposed system on the organization? I.e. how does the proposed system fit with in the organization?

Thus since the feasibility study may lead to commitment of large resources, it becomes necessary that it should be conducted competently and no fundamental errors of judgment are made. Different types of feasibility study and the way we performed on our project “TRANS SERVICE NET”

5.2.5 Technical Feasibility:

In technical feasibility, we study all technical issues regarding the proposed system. It is mainly concerned with the specifications of the equipments and the software, which successfully satisfies the end-user’s requirement. The technical needs of the system may vary accordingly but include:

• The feasibility to produce outputs in a given time.

• Response time under certain conditions.

• Ability to process a certain volume of the transaction at a particular speed.

• Facility to communicate data.

Under this analysis process questions like (i) does the compatible platform exist within our domain or can we procure it? (ii) Does the proposed equipment have the technical capacity to hold the data required using the new system? Both at the development site and at server where we will be hiring the space for the website, and also the database (iii) would it be possible to upgrade the system after it is developed and implemented, if necessary? And (iv) would the recommended technology guarantee the reliability, accuracy and data security? This analysis process requires more emphasis on system configuration given more importance rather than the actual hardware specifications.

The configuration of the existing systems is:

• Processor : Intel Pentium-IV

• Memory : 256 MB,

• Network adapter : Ethernet adaptor

• Modem : 56kbps voice fax data

• Secondary storage : Samsung/Seagate hard disk (40 GB)

• Printers: 2 Inkjet and one HP Laser Printer

• Internet: 128 kbps cable internet

The data will reside at server root directory installed with ORACLE server 7 and IIS. For Software there are following alternatives:

• Front End: VB.net

• Back End: ORACLE

• Editor: Micro media dreamweaver

• Documentation tool: MS-Word

Features of ORACLE

ORACLE provides one of the best security features among all RDBMS. With low cost and common availability in spite of having oracle as an option it was better to use ORACLE. As we know that the database is a repository for stored, operational data in a database environment and common data are available and used by several users. Instead of each program (or user) to manage its own data, the data across applications are shared by all authorized users with the help of database software managing the data as an entity.

The general concept behind a database is to handle information as an integrated whole. A database is a collection of interrelated data stored with minimum redundancy to serve many users quickly and effectively. The general objective is to make information easy, quick, expressive, and flexible for the user. In database design specific objectives are considered: -

· Ease of learning and use.

· More information at low cost.

· Accuracy and integrity.

· Recovery from failure.

· Performance.

In this way, ORACLE is one of the leading R.D.B.M.S. software in the world. It is characterized by the quick retrieval of information from huge tables. This quality allows it to cater to the ever-changing business needs of the present age. It supports fourth generation language, ORACLE, thereby making it easier for the customers to grasp it, a development language where complicated procedures, functions etc. can be used.

The S.Q.L server 2000 include following features:

· Queries

· Constraints

· Procedures

· Triggers

· batch implementation

• • • • functions

      • bulk copy utility

      • cursores

      • stored procedures

5.3.3 Economical Feasibility:

Economic feasibility is the most frequently used technique for evaluating the effectiveness of the proposed system. More commonly known as cost/benefit analysis, the procedure is to determine the benefits and savings that are expected from the proposed system and compare them with the costs. If the benefits outweigh costs, a decision is taken to design and implement the system otherwise further justification or the alternative in the proposed system will have to be made if it is to have a chance of being approved. This outgoing effort improves in accuracy at each phase of the system development life cycle.

Classification of Costs & Benefits: The various cost expected to incur & benefit expected to realize are given below.

Tangible or Intangible Costs & Benefits: Tangibility refers to the ease with which costs or benefits can be measured. An outlay of cash for a specific item or activity is referred to as a tangible cost. They are shown as disbursements on the books. The purchases of hardware or software, personnel training are examples of tangible costs. They are readily identified and measured.

Costs that are known to exist but whose financial value cannot be accurately measured are referred to as an intangible costs. Benefits are also classified as tangible or intangible. Like costs, they are often difficult to specify accurately. Tangible benefits such as saving of material cost are quantifiable. Intangible benefits such as improved institution image is also taken into account in the system evaluation process.

Direct or Indirect Costs & Benefits: Direct costs are those with which a monetary figure can be directly associated in a project. They are applied directly to the operation. Direct benefits can also be specified to the given project. Indirect costs are the results of operation that are not directly associated with the given system or activity. They are often referred to as overhead. Light, air conditioning, maintenance, protection of the computer center is all tangible costs, but it is difficult to determine the proportion of each attribute to a specific activity. Indirect benefits are realized as a by-product of another activity or system.

Fixed and Variable Costs and Benefits: Some costs and benefits are constant, regardless of how well a system is used. They are constant and do not change. Once encountered they will not reappear. In contrast, variable costs are incurred on a regular basis. They are proportion to work volume and continue as long as is in operation. For example, the cost of printer paper and cartridge. Fixed benefits are also constant and do not change. The variable benefits, on the other hand, are realized on a regular basis. For example, the system will save several hours of employees in preparing each report, which otherwise was prepared manually. Another examples are error free data entry, help about different topics and ease of use.

5.3.4 Operational Feasibility:

Proposed projects are beneficial only if they can be turned into information system that will meet the operating requirements for which they are designed and developed. It is mainly related to human organizational and political aspects. People are resistant to change, and computers have been known to facilitate change. Findings of operational feasibility analysis can be summarized as given below:

• Since the audiences are million of netigen who use it for information retrieval. So their will be many who will be benefited with this project

• End users are always welcome to have the technical support on the site.