PROJECT SUPPORT FUNCTION

MAIN TOPICS COVERED

· Method Used For Implementation

5.1 Implementation Methods:

Implementation means the process of transforming present manual system into a new developed system. There are different options of conversion, which can be adoped in a way that the working of the organization should not be disturbed.

I. Completely Convert the System,

II. Convert the System Gradually,

III. Implement the new System Parallel with Existing System,

5.1.1. Direct Conversion:

According to this method, new system implemented completely without any reference with the existing system. In this method, the old system is totally left and the new system is placed. This method is suitable when the new system is very different from the existing one this method is not suitable for conversion. This method has some advantages and disadvantages.

Advantages

I. If no major problem occurs, cost saving can be fully exploited.

II. If it does not cost much, on keeping the temporary backup of the present system.

Disadvantages

I. Since our system is base on existing system, so this method is not suitable for Conversion.

II. It will shock the organization because there is no adjustment period. The risk of Failure of whole system or some of its parts is there.

5.1.2 Gradual Conversion:

This technique allows the change of the existing system. Gradually, the present system should be change with newly designed system on Small-scale to confirm that this change over will be successful. As one part of the new system is tested, that portion of the system should be converted into new system and this process continues until the new system is gets the place of existing system.

5.1.3 Parallel Conversion:

The old or existing system and the proposed system runs simultaneously in this technique. It is believed that the select approach to conversion is to turn both new and old system at the same time, until it is admitted that the new system is producing reliable result.

Advantages:

I. User has maximum flexibility because he does not have to start with new system until he is certain that the new system is providing acceptable outputs.

II. Even if the system flops due to any reason the old system is available as backup.

III. Efficiency of the new system can be compare with the old system. Use of the system has enough time to get familiar with the new system.

Disadvantages:

I. Cost to operate both systems is one of the disadvantages of this method.

II. User has to spend more time to make both systems operational.

5.2 Proposed Conversion Plan:

Since the main objectives of the proposed system were to increase efficiency and to simplify the procedures. It has the power to over come the existing system, and eliminating the use of existing system is will not effect the organization working, New automated student information system will work from now and satisfy the need of organization, and the old record will be entered in the new system gradually. Another advantage of this technique is that the burden of over working in the case of using parallel or gradual change in system. Although this implementation is a bit expensive. One of the benefits to the organization is that the organization is an institute of computer studies, so that will not be difficult to under stand and use the system

SYSTEM TESTING PLAN

MAIN TOPICS COVERD

· Testing Strategies Code Testing

· Project Testing Report

· User Training

· Conclusion

6.1 Introduction:

Software testing strategy a road maps for the software developer, the quality assurance organization and the user.

Testing is a set of activities that can be placed in advance and conducted systematically. Software testing is a hypercritical component of software quality assurance and represents a review of specification, design and coding. A series of test cases that are intended to demolish the software was created.

The basic testing objectives are.
Correct errors those are uncovered.

Quality Assurance consists of the auditing and reporting functions of management. The goal of quality assurance is to provide management with the data necessary to be informed about product quality, thereby gaining insight and confidence that product quality is meeting its goals.

Software quality is defined as “Conformance to explicitly stated functional and performance requirements, explicitly documented development standards, and implicit characteristics that are expected of all professionally developed software.” Software

quality assurance is composed of a variety of tasks associated with two different constitutes – the software engineers who do technical work and an SQA group that has responsibility for quality assurance planning, oversight, record keeping, analysis, and reporting.

Testing starts at the component level and works “outward” toward the integration of the entire computer based system.

Different testing techniques are appropriate at different points in time.

Testing is conducted by the developer of the software and (large projects) and independent testing group.

Testing and debugging are different activities, but debugging must be accommodated in any testing strategy.

6.2 Testing Strategies:

A strategy for software testing integrates software test case design methods into a well-planned series of steps that result in the successful construction of software. The strategy provides a road map that describes the steps to be conducted as part of testing, when these steps are planned and then undertaken, and how much effort, time, and resources will be required.

This project used incremental approach in the integration testing:

· Top Down: testing on the higher modules. If there was any error, continue to test the individual modules.

· Bottom Up: testing on the individual modules first, continue to test the higher modules if no error.

· Sandwich: mixed testing approach of top down and bottom up approach.

There are some modules tested by Top Down approach and some modules tested by Bottom Up approach.

The main technique used for testing was Black Box Testing and software was checked for following:

Interface incompatibility, unreachable code
Timing analysis to prove that a critical real-time system respond to its input data within specified time constraints .

System Testing

Validation testing

Integration Testing

Unit Testing

Code

Design

Requirements

6.3 Project Testing Reports:

6.3.1 Unit Testing

Initially test focus on each on module individually, assuring it functions properly as a unit. The advantage of unit testing is that error, if any, which are module, focused can be dealt at this level individually.

This type of testing has been conducted for multiple modules of the system in parallel.

Test Cases:

I. LOGIN PROCESS:

System was tested with invalid user id and password and provided the satisfactory results by not allowing login using the false parameters.

II. DATA OPERATIONS:

Each form is separately tested for performing the four necessary operations, which are data-entry, updation, and deletion of agent and all of the tests provided satisfactory results.

Unit testing started out adjacent to the coding step. It continued after source level code was developed, reviewed, and verified for correspondence to component level design. The module interface was tested to ensure that information properly flows into and out of the program unit under test. The local data structure was examined to ensure that data stored temporarily maintains its integrity during all steps in an algorithm’s execution. Boundary conditions were tested to ensure that the module operates properly at boundaries established to limit or restrict processing.

All independent paths (basis paths) through the control structure were exercised to ensure that all statements in a module have been executed at least once. Finally, all error-handling paths were tested.

6.3.2 Integration Testing:

The modules must be assembled or integrated to form the complete software package. Integration testing addresses the issue associated with the dual problem of verification and program construction.

Integration testing is a systematic technique for constructing the program structure while conducting tests to uncover errors associated with interfacing. The objective was to take unit tested modules and build a program structure that has been dictated by design. Integration testing was accomplished using a Top-Down Integration Testing Strategy. Using this integration testing strategy modules were integrated by moving downward

through the control hierarchy, beginning with the main module. Top-Down integration as its name implies, begins testing with the top most levels in the program structure.

It also encompasses the testing of the software design. It is then that the integration testing took place.

Validation Testing

Software validation was achieved through a series of black-box tests that demonstrate conformity with the requirements. Both the plan and procedure were designed to ensure that all functional requirements have been satisfied; all performance requirements have been achieved; documentation is correct and human-engineered; and other requirements are met (e.g. transportability, compatibility, error recovery, maintainability).

Since this software is developed as a product to be used by many users, it was impractical to perform formal acceptance tests with each one. Alpha and beta tests were conducted to uncover errors that only the end-user seems able to find.

Validation testing is performed to ensure the software met the requirements of the user, so Web based purchasing agent was found to be providing the maximum functionalities required by the customer, it properly manages the product database and manipulates it and provide accurate and efficient reports to the management.

Test Cases

System is capable of storing the student information.
System is capable of providing proper updates facilities
System is capable of providing view of all records.
It is definitely a secure system.

6.3.3 System Testing:

System testing verifies that all elements interact properly and that the overall system function and performance is achieved.

Software is the only one element of a larger computer-based system. It is incorporated with other system elements (e.g. new hardware, information) and a series of system integration and validation tests are conducted. These tests fall outside the scope of the software engineering process and are not conducted solely by the software developer. However, steps taken during the software design and testing greatly improved the probability of successful software integration in the larger system. System testing is actually a series of different tests whose primary purpose is to fully exercise the computer-based system. Although each test has a different purpose, all work to verify that all system elements have been properly integrated and performing allocated functions.

For real-time, software that provides required function but does not conform to performance requirements is unacceptable. Performance testing is designed to test the run-time performance of software within the context of an integrated system. Student Information System was passed from a number of performance tests. Performance testing occurred throughout all steps in the testing process. Even at the unit level, the performance of an individual module may be assessed as white box tested are conducted.

At this stage, the interfacing errors has been uncovered and correct and this testing proved to be the final series of software tests and thus regarded as validation tests.

6.4 User Training:

The developed software is quite user friendly, so that any person can obtain the required information effectively out of the database, after few weeks training and practice. Furthermore, Self Explanatory Menus will keep guiding the user. However, a comprehensive lecture to familiarize the staff software will also help in better understanding of the system, but in our case user training is not a big case to work upon because all the staff in Institute of Computer Languages (ICL) is already computer literate so it is not difficult to understand and use the system.

6.5 Conclusion:

Different conclusions can be drawn after system testing and evaluation of the proposed system. These conclusions are based on the testing results. The major conclusions are as under:

I. The proposed system provides effective input data entry in order to facilitate the user.

II. Output is generated randomly and the user can easily operate and get the required data quickly.

III. Interface provides easy operation of the proposed system such that a user-friendly environment is established.

IV. It keeps the data accurate and long lasting, and keep it ready to access any time in any mode.

SYSTEM EVALUATION AND FUTURE ENHANCEMENT

MAIN TOPICS COVERD

· Future Enhancements

7.1 Future Extension:

The system evaluation phase is the final phase for the designer after implementing the system. The designer reviews the system and determines whether the objectives are achieved or not. A major factor during system evaluation is to evaluate the system with the perspective of the user for his ultimate use. This is termed as evaluation of the user interface.

The major goals of a designer is to succeed in all aspects though some tradeoffs are worth considering, for instance, if the rate of errors is to be kept extremely low, then the speed of performance may have to be sacrificed.

Thus, in software development there is no guarantee of a perfect system or unique interface, for there is always a room for improvement. All these mentioned earlier, one has to do away with some factors, so that the merits of a system are accompanied with some demerits too.

Future Enhancements:

The environment and needs of an organization are always dynamic in nature. In today’s global arena no organization can survive if cannot get pace with time the changing needs. With the changes in the environment, the organization may reorganize itself. Thus the system organization is using require changes and maintenance. The system is developed to cater the current requirements of the organization but has the

capacity to fulfill the growing needs of organization. So that in future if any changes arte to be made or integrated, one might just build on the existing system instead of building a new application.

During the design and development phase every possible effort is made to overcome the deficiencies of the system but in spite of this, there may be more room for improvement. The system is prone to corruption of files if at all the system maintenance and management is not done. Thus training of new user before handover is recommended.

User Guide

Main Topics Covered

User Guide

References

Appendices

User Guide:

8.1 User Guide:

Our developed software, Student information System, provides a lot of facilities to the user which user can easily understand, it’s not difficult at all, but a brief introduction to the system and its functionality is as under:

First as you start the system, it will start loading and a loading bar will appear.

After that a form will appear in which you have to enter the user name and password to get in the system.

As you will get in a main menu will appear on which you will find different labeled buttons for the working, e.g. entry form for student biodata, forms to enter educational records of student and search forms etc.

8.2 References:

Reference books:

· Soft ware engineering (Fifth Edition by Roger s. Pressman)

· Beginning C sharp by Wrox

· Modern DBMS (4^th Edition) written by Fred Roger

· Sql server (7.0)

· Mastering C sharp Database Programming

· Sams teach your self Visual Stodio.Net in 21 days

· Sams teach yourself crystal reports in 24 hours.

Reference Websites:

http://www.databases.about.com/library/weekly/aa100700a.htm

http://www.csharpfriends.com