Software Qualification Testing Process - Assignment Example

Software quality management Name: Number: Course: Lecturer: Date: Software quality management ISO/IEC 15504 is a process assessment framework that is used to evaluate a process that is to be used in an organization. This model has various capability levels that show how the model meets a given standard. The goal of any organization is to have processes that will add value to the overall productivity of the organization. This framework therefore plays a pivotal role in evaluating processes that are to be introduced[Car09]. There are six capability levels that are defined in this framework. These six levels have attributes that evaluate and assess the process to see if they meet the requirements and the standards that are required of them. The first level is Level 0 which is the incomplete level. With this level, there is nothing which is achieved in the process. At this level, the process does not achieve the purpose in which it was defined to achieve. There is hardly any evidence indicating there is some activity that was taking place. The second level is level 1 which is the performed process. In this level, the process achieves the goal and the purpose in which it was intended to achieve. Level 2 is managed process. At this level, the process which was performed in level 1 is now managed in a systematic process with planning and monitoring[Gio06]. Level 3 is the established process where the process can now be implemented using a process that is well defined and is in a position to attain the outcomes that was designed to achieve. Level 4 is the predictable process where the process can now be in operation and works within the limits which have been set forth so that the outcomes are clear. Then there are level 5, optimizing processes, is where the predictable process which was previously defined can now be improved continuously so that it continues to be relevant and meet the outcomes that are expected as time proceeds. This paper will look at Level 2 Maturity Level and assess the attributes of a software product so that assessing the attributes of the process to see if they have been met. The rest of the paper will look at a software product and see if they meet requirements of this level[Gio06]. Software qualification testing process This is the process of ensuring that the software modules that have been integrated in the information system meet the required standards. There is no one such stipulated time when the software testing process is to be carried out on the contrary; such a process can be done at any stage of the software development process. This, however, must be done before implementation of the software and possibly its accreditation as being reliable. As it has been happening in the past, software testing as a process is done just after coding has been done and all requirements have been set I place. However, this is not the case in the agile approach to software development. From the above argument it can be stated that the stage at which testing is conducted almost or rather entirely depends on the approach used during the design and implementation of the software[Gio06]. Despite the advancement in technology refining reliability in software, it remains a fact that almost all software used at least contains risks. The smart thing is that most of such risks are not too complicated, and hence can be moderated, or rather eliminated. This is true especially as regards complexities related to the required specifications, which presents the most dangerous and hard to deal with risks, if not handled early in the development stages. Commonly made mistakes that subjects most projects to risks of failure or stagnation include having requirements that are not clear; failure to involve the customers and other stakeholders in the requirements specification process; having so many malfunctioning and unrealistic requirements that may never be realized and that are not in line with the goal and an utmost focus of the project (Hoboken, 2012). For instance, the project manager and other team members should ensure that the specified requirements are as clear as possible; to avoid mistakes that may arise from a failure to understand what is genuinely needed for the project to progress smoothly[Gio06]. All stakeholders should also be involved when defining the requirements, and more especially the potential customers who understand exactly what they require more deeply than the project manager and designers. It’s also pertinent to ensure that the set objectives and specified requirements are realistic and achievable, to avoid spending resources on unrealistic goals that only serve to stretch both the human and other resources and consume so much time, but still remain unachievable[Cle06]. Different models focus on different points of the software. This differs more especially between the waterfall model also referred to as the traditional model and the modern or agile model. With the modern model, the system testing process is vested with the developer before the system is surrendered to external quality testers for final verification. On the other hand, software testing is done after the requirements specification and coding is done and finished. Software products One of the software products in Level 2 capability maturity level is that of telemedicine information system. The software products that can be tested are described below: Laboratory information management system (LIMMS) This is one product that is part of the hospital management system that forms the telemedicine system. This product is required to have tests that are carried out in laboratories. It is used to ensure that the test results are transmitted to the physicians who will give the correct diagnosis and correct medication. Justification for choosing this work product The reason for choosing this work product is that there is a need to record what goes on in the laboratories. Work product outcomes The work processes that will be achieved and solved in the process include: i. Reporting laboratory results. The system is supposed to report the results of the laboratory test that is being carried out. ii. Giving the procedure that has been carried out. Correct reporting of the procedure that has been undertaken in the process is very important. Physicians make use of the procedure in order to get the right result and correct diagnosis. iii. Historical data will be obtained so that the procedures and the results that have been found with the same procedure are known. Pharmacy Information System Another work product that will be integrated into the hospital information system is a pharmacy information system. Interoperability in the pharmacy and laboratory is so crucial. This is mainly because they form the crucial departments in the health sector, if quality and efficiency is to be realized[Car09]. There has always been a need for e-pharmacy services and electronic control in the laboratory, for fast and effective service delivery to the patients. The more reason these departments should be accorded priority when implementing the electronic system. Imaging and radiology also could be considered for faster operations. Interoperability in this sector could also mean faster production and delivery of reports to the concerned physicians, saving on time and meeting the urgent requirements[She04]. The key features embedded in the hospital system include electronic prescriptions from a majority of pharmacies in the region, lab test orders and receipt of lab results and electronic immunization. Additionally, this system should support up to 30 specialties that can be effectively managed, these include cardiology, immunology, dermatology, family practice, endocrinology, internal medicine, Neurology, physical and occupational therapy among others[Lyo11]. Justification for choosing this work product I choose this work product because of the fact that drugs are part of the treatment process and it should be properly documented in the process. Work product outcomes The work processes that will be solved with this work product include: i. There will be a systematic process of dispensing drugs in the system ii. There will be a systematic billing system within the hospital iii. There will be a strict tracking drug stock within the system. iv. There will be a better way of disposing drugs that are no longer working in the system Electronic health record (EHR) This is another work product that many organizations with avenues in the health sector are pursuing new technologies in an attempt to improve the efficiency and effectiveness of health care services. Among these technologies is the electronic health records (EHR). This technology involves the systematic collection of information about patients and digitally or electronically storing, manipulating and sharing of this information between different healthcare facilities[Ken09]. The technology aims to ensure speedy storage and retrieval of information, about patients, diseases and treatment in the health care facilities, and enable the patients and doctors easily access this information. Electronic health record products range from quick-visit EHRs, electronic prescription where prescriptions are sent to the pharmacies for quick diagnosis. They also include EHR reporting and EHR specialty systems aimed at maintaining and providing updated information and records regarding general surgery, obstetrics, infectious disease, gynecology, cardiology among others[Gio06]. The adoption of these systems in the healthcare facilities by the administrators and physicians is bound to improve performance in operations, in these health care systems. The technology will ensure efficient service to patients and reduce the time lag in the facilities. It enhances communication, reduces chances of errors and omissions and ensures better and safer treatment to patients[Cou09]. Justification for choosing this work product I have chosen this work product because data management and health records are a crucial process in any hospital. Health records have to be managed well. Work products The process outcomes with the use of this work product include: i. Data records will be properly managed by this system ii. There will be accurate health records for patients iii. There will be accurate and systematic recording of historical data of the clients Capability Level 2 attributes The first Capability Level 2 attribute management attributes. One additional work product that can be added in regard to this capability level 2 attribute is CRM (Customer Relationship Management) which is a system that is used to manage the relationships with the clients and the staff. This way, the performance will be kept in check[Cle06]. The rationale for choosing this work product is that it helps check the performance of the staff because the clients will be in a position to rate the services they are getting. The CRM systems management application is used to manage customer interactions by integration of processes that are customer oriented like customer service and sales. The CRM systems are not only used in automation of these processes for cost reduction but also collection and analysis of customer information with the aim of better fulfilling customer needs and improve customer satisfaction. The system can be easily integrated into the hospital information system[Cou09]. The second Capability Level 2 attribute is work product management attribute. This attribute is used to measure the extent in which the work products that are used in the information system have been managed well. One work product that will work effectively is module management and maintenance. This work product is used to manage work products that have been installed in the system. There will be maintenance of the system and this module will also have a role. Module maintenance is a crucial role when it comes to module management and maintenance. This module takes a log of what is happening in the system and report any faults and bugs that the system encounter. It is a vital work product as it helps in solving the problems that the system and the entire information system that is used in the organization encounter. It plays a pivotal role when solving bugs and errors within the system. It has a log of what is going on the system. The rationale for choosing this work product is because it is a work product that reports the progress and the status of the work products that have been integrated in the system[Car09]. Additional characteristics The additional characteristics that are required to be identified in the work products initially identified include: i. The work products should be accurate and precise in handling the processes ii. The work products should be simple to use because most of the data entry tasks will be handled by junior staff in hospitals. Also, the hospital physicians have limited skills in information technology[Bar08]. iii. It should be easy to integrate other modules to the system. This way, it is easy to add other modules to the system. iv. It should have proper security features so that the system is free from attacks from the external users. With the advancement in technology and security vulnerability, it is easy to have attacks to information systems. It is therefore a requirement that the information systems that are in place should have enough measures to ensure that the various modules and work products do not have the loopholes that can be a route for attacks. v. It should handle integrity and privacy of information well. This way, it will be possible to have private information and data so that the data management is kept private as much as possible. Conclusion SQM Roles have its rules to ensure that the required level of quality is achieved in a software product, to encourage a company-wide "Quality Culture" where quality is viewed as everyone’s responsibility, to reduce the learning curve and help with continuity in case team members changes positions within the organization and to enable in-process fault avoidance and fault prevention through proper development. References Car09: , (Carey & Lloyd, 2009), Gio06: , (Gioe, 2006), Cle06: , (Cleland & Ireland, 2006), She04: , (Sheldon & Yoxon, 2004), Lyo11: , (Lyonnet, 2011), Ken09: , (Kendrick, 2009), Cou09: , (Council & Staff, 2009), Bar08: , (Barnes, 2008), Read More