SYSTEM STUDY: FEASIBILITY STUDY

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 !"#"$%!&' F &(%)%'%T* T !+#%!&' F &(%)%'%T* ("!%&' F &(%)%'%T*

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 e,penditures 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. "nly the customized products had to be purchased. TECHNICAL FEASIBILITY This study is carried out to check the technical feasibility, that is, the technical requirements of the system. &ny 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.

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. +is level of confidence must be raised so that he is also able to make some constructive criticism, which is welcomed, as he is the final user of the system. SYSTEM TESTING The purpose of testing is to discover errors. Testing is the process of trying to discover every conceivable fault or weakness in a work product. %t provides a way to check the functionality of components, sub assemblies, assemblies and-or a finished product %t is the process of e,ercising software with the intent of ensuring that the (oftware system meets its requirements and user e,pectations and does not fail in an unacceptable manner. There are various types of test. ach test type addresses a specific testing requirement.

TYPES OF TESTS

Unit testing .nit testing involves the design of test cases that validate that the internal program logic is functioning properly, and that program inputs produce valid outputs. &ll decision branches and internal code flow should be validated. %t is the testing of individual software units of the application .it is done after the completion of an individual unit before integration. This is a structural testing, that relies on knowledge of its construction and is invasive. .nit tests perform basic tests at component level and test a specific business process, application, and-or system configuration. .nit tests ensure that each unique path of a business process performs accurately to the documented specifications and contains clearly defined inputs and e,pected results.

Integration testing %ntegration tests are designed to test integrated software components to determine if they actually run as one program. Testing is event driven and is more concerned with the basic outcome of screens or fields. %ntegration tests demonstrate that although the components were individually satisfaction, as shown by successfully unit testing, the combination of components is correct and consistent. %ntegration testing is specifically aimed at arise from the combination of components. e,posing the problems that

Functiona test Functional tests provide systematic demonstrations that functions tested are available as specified by the business and technical requirements, system documentation, and user manuals. Functional testing is centered on the following items/ 0alid %nput %nvalid %nput Functions "utput / identified classes of valid input must be accepted. / identified classes of invalid input must be rejected. / identified functions must be e,ercised. / identified classes of application outputs must be e,ercised.

(ystems-1rocedures/ interfacing systems or procedures must be invoked.

"rganization and preparation of functional tests is focused on requirements, key functions, or special test cases. %n addition, systematic coverage pertaining to identify )usiness process flows2 data fields, predefined processes, and successive processes must be considered for testing. )efore functional testing is complete, additional tests are identified and the effective value of current tests is determined.

S!ste" Test (ystem testing ensures that the entire integrated software system meets requirements. %t tests a configuration to ensure known and predictable results. &n e,ample of system testing is the configuration oriented system integration test. (ystem testing is based on process descriptions and flows, emphasizing pre3driven process links and integration points.

#$ite Bo% Testing 4hite )o, Testing is a testing in which in which the software tester has knowledge of the inner workings, structure and language of the software, or at least its purpose. %t is purpose. %t is used to test areas that cannot be reached from a black bo, level.

B ac& Bo% Testing )lack )o, Testing is testing the software without any knowledge of the inner workings, structure or language of the module being tested. )lack bo, tests, as most other kinds of tests, must be written from a definitive source document, such as specification or requirements document, such as specification or requirements document. %t is a testing in which the software under test is treated, as a black bo, .you cannot 5see6 into it. The test provides inputs and responds to outputs without considering how the software works. Unit Testing:

.nit testing is usually conducted as part of a combined code and unit test phase of the software lifecycle, although it is not uncommon for coding and unit testing to be conducted as two distinct phases.

Test strategy and approach Field testing will be performed manually and functional tests will be written in detail.

Test o'(ecti)es &ll field entries must work properly. 1ages must be activated from the identified link. The entry screen, messages and responses must not be delayed.

Features to 'e teste* 0erify that the entries are of the correct format #o duplicate entries should be allowed &ll links should take the user to the correct page.

Integration Testing

(oftware integration testing is the incremental integration testing of two or more integrated software components on a single platform to produce failures caused by interface defects. The task of the integration test is to check that components or software applications, e.g. components in a software system or 7 one step up 7 software applications at the company level 7 interact without error.