1 / 13

Chapter 8 Technology of information system

Chapter 8 Technology of information system. TQM of information systems Presented By: Praveen.G.Acharya. What does TQM means ?.

arlene
Télécharger la présentation

Chapter 8 Technology of information system

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript


  1. Chapter8Technology of information system TQM of information systems Presented By: Praveen.G.Acharya

  2. What does TQM means ? In general, Total Quality Management means that the organization’s culture is defined by and supports the constant attainment of customer satisfaction through an integrated system of tools, techniques and training. This involves the continous improvement of organizational processes, resulting in high quality products and services. IN TQM TOTAL – Made up of whole. QUALITY – Degree of excellence a product/service provides. MANAGEMENT- Act/art. (manner of handling, controlling, directing, etc…) So, TQM is an art of managing the whole to achieve excellence.

  3. TQM of Information System • The objective of the TQM in the information system design is to assure the quality of information. This is done by ensuring, verifying and maintaining software integrity through an appropriate methodology choice among the technology, design and architecture. • It institutes appropriate procedures with checks and controls in all the processes of information systems development. • It ensures that the scope and the objective of the system, choice of the design architecture and development methodology and further quality ensuring the processes and planned implementaion methodologies. • The quality of information is governed by the quality of the information processing system design.

  4. Contd… • The perception of good quality is that of a customer or a user of the information system and not that of the conceiver, the planner or the designer of the information system. • The quality of the information and the systems which generate that information will be rated high provided it assures : • A precise and an accurate information, • A high level response in an interactive processing, • User friendly operations, • Reliability of information, and • An ease of maintenance.

  5. About Quality Assurance in TQM • The important measure of quality assurance is the level of user satisfaction it attains. • In the process of achieving user satisfaction, the information system must be conceived with business focus and orientation • It must address the total scope of the business with specific attention in the areas of core competence and mission critical applications. • It ensures that the information system design is flexible, bug free and easy to maintain with the changing needs. • Therefore the quality assuring ability of the system, is judged by its ability to sustain design and its ability to handle the changes with minimum cost.

  6. Types of Technologies in TQM • Current Technologies, are database management, distributed data processing, object orientation, parallel processing, data warehousing and replication, networks and communication. • Emerging Technologies, are Internet/Intranet, EDI and E-Mail, Groupware for term based application, client/server for application processing, multi-media for voice, video, image processing, imaging systems for image creation, storage mixing knowledge-based (KBS) for expert, artificial intelligence system and Computer Aided Software Engineering (CASE) for a systematic application development including I-CASE.

  7. Software Quality Assurance in TQM • The software quality assurance is nothing but what is required which would ensure conformance to the standards set by the management. • The software quality assurance is an essential activity to ensure the attainment of quality goals. • The activity comprises : • Application of the proven methods and tools - requirement analysis, - defining the scope and the problems, - modelling and prototyping, - finalising the software requirement specifications, - configuring the hardware software platforms.

  8. Contd… • Technical review to - detect errors in the functionality and its logic, - confirm that the software meets the basic system objectives, - confirm that it meets the predefined standard in all the areas, - confirm that uniform application of methods and technologies. • Testing to - detect errors at the data level, - ensure the execution of known functionality, - ensure internal working of the software, - ensure the execution on conditions and subsequent actions, - confirm the integration process.

  9. Contd… • Version changes control to - ensure that the change does not alter the original assured quality, - confirm that no bugs are introduced in the software, - ensure that proper documentation is made as changes introduced. • Record keeping to - establish knowledge and know how on reviews, audits, changes, testing for future reference and use in bug fixing.

  10. Software testing strategies in TQM • The software quality assurance largely depends on testing and quality of testing. • The different kinds of testing are, Unit testing, Integration testing, Validation testing and System testing. • In Unit testing, the smallest portion of the system is checked. It is essentially a code level testing. In this testing the quality of data in terms of the design and structure is confirmed. • In Integration testing, modular structure of the system when it works together is checked to see whether it produces the desired information and quality. This testing is the top-down or either for the bottom-up integration. If the system design initiates a trigger at the highest level and then it flows down, then the integration testing would be from the top-down. If the design is bottom-up then the integration testing will be bottom-up.

  11. Contd… • Validation testing is taken up when the integration phase is confirmed. Validation is necessary even though the checks and controls are satisfied and the outputs are correct and reliable. The validation tests confirm the conformance to the requirement specifications of the user, the scope and the objectives and the interface requirements. • System testing is at the end after the three tests are confirmed satisfactory and the software is acceptable. In the system testing the global issues are tested. They are recovery from the faults and restarting the next process, security from the unauthorised interventions, stress capability to handle the extreme conditions and performance of the system in the live mode. • The Performance testing is the last of the system testing where the operational performance of the system is tested.

  12. Contd… • The software quality is assured through a well planned series of testing starting from the code level to the system level. • The performance test is the last one on the quality assurance programme. • These tests ensure confirmation and conformance against the internal standards and user expectations.

  13. THANK YOU……………….:-)

More Related