Assuring the quality of software maintenance components. Magister LIKMI/SQA01

Transcription

1 Assuring the quality of software maintenance components Magister LIKMI/SQA01

2 Introduction 1. Menjamin, dengan tingkat kepercayaan yang diterima, bahwa kegiatan pemeliharaan perangkat lunak yang sesuai dengan persyaratan teknis fungsional. 2. Menjamin, dengan tingkat kepercayaan yang diterima, bahwa kegiatan pemeliharaan perangkat lunak sesuai dengan penjadwalan dan persyaratan anggaran pihak manajemen. 3. Memulai dan mengelola kegiatan untuk memperbaiki dan meningkatkan efisiensi pemeliharaan perangkat lunak dan kegiatan SQA.

3

4 Foundation 1: software package quality Product operation factors: (1) Correctness includes: Output correctness: The completeness of the outputs specified (in other words, no pre-specified output is missing), the accuracy of the outputs (all system s outputs are processed correctly), the up-to-datedness of the outputs (processed information is up to date as specified) and the availability of the outputs (reaction times do not exceed the specified maximum values, especially in online and real-time applications). Documentation correctness. The quality of documentation: its completeness, accuracy, documentation style and structure. Documentation formats include hard copy and computer files printed manuals as well as electronic help files whereas its scope encompasses installation manuals, user manuals and programmer manuals. Coding qualification. Compliance with coding instructions, especially those that limit and reduce code complexity and define standard coding style. (2) Reliability. The frequency of system failures as well as recovery times.

5 Product Revision Factors: 1. Maintainability. These requirements are fulfilled first and foremost by following the software structure and style requirements and by implementing programmer documentation requirements. 2. Flexibility. Achieved by appropriate planning and design, features that provide an application space much wider than necessary for the current user population. In practice, this means that room is left for future functional improvements. 3. Testability. Testability includes the availability of system diagnostics to be applied by the user as well as failure diagnostics to be applied by the support center or the maintenance staff at the user s site.

6 Products Transition Factors: 1. Portability. The software s potential application in different hardware and operating system environments, including the activities that enable those applications. 2. Interoperability. The package s capacity to interface with other packages and computerized equipment. High interoperability is achieved by providing capacity to meet known interfacing standards and matching the interfacing applied by leading manufacturers of equipment and software.

7

8 Foundation 2: maintenance policy Version development policy This policy relates mainly to the question of how many versions of the software should be operative simultaneously. Change policy Change policy refers to the method of examining each change request and the criteria used for its approval.

9 Pre-maintenance software quality components Maintenance contract review: (1) Customer requirements clarification Type of corrective maintenance services required: list of remote services and on-site services to be provided, hours of service, response time, etc. Size of the user population and the types of applications to be used. Location of users, especially of long-distance (or overseas) sites and the types of applications installed in each. Adaptive and functionality improvement maintenance to be provided and procedures for submission of requests for service as well as proposing and approving performance of these services.

10 Maintenance contract review: (2) Review of alternative approaches to maintenance provision Subcontracting for sites or type of service Performance of some services by the customer himself with support from supplier s maintenance team. (3) Review of estimates of required maintenance resources First, these estimates should be examined on the basis of the required maintenance services, clarified by the proposal team. Then, the company s capacity to meet its commitments with respect to professional competence as well as availability of maintenance teams should be analyzed.

11 Maintenance contract review: (4) Review of maintenance services to be provided by subcontractors and/or the customer This review refers to the definition of the services provided by each participant, payments to subcontractors, quality assurance and follow-up procedures to be applied. (5) Review of maintenance costs estimates These estimates should be reviewed on the basis of required resources.

12 Maintenance plan review: 1) A list of the contracted maintenance services The internal and external customers, the number of users, the locations of each customer site. The characteristics of corrective maintenance services (remote and on site). The obligations for adaptive and functional improving maintenance service provision for each customer.

13 Maintenance plan review: (2) A description of the maintenance team s organization The number of required team members. If services are to be provided from several facilities, the team requirement for each facility. The required qualifications for team members according to the maintenance tasks, including acquaintance with the software package(s) to be maintained. Organizational structure of the maintenance teams, including names of team leaders. Definition of tasks (responsibility for customers, types of applications, etc.) for each team. Training needs.

14 Maintenance plan review: (3) A list of maintenance facilities The maintenance support center with its installed hardware and communication equipment to provide user support and software correction services. A documentation center containing a complete set of documents (in printed or electronic format): The software documentation, including the development documentation The service contracts The software configurations for each customer and versions of the software packages installed at each site, provided by configuration management The maintenance history records for each user and customer.

15 Maintenance plan review: (4) A list of identified maintenance service risks Staff shortages, whether throughout the organization s maintenance services, in a specific maintenance support center or for a specific application. Inadequate qualifications or acquaintance with part of the relevant software packages for performing user support services and/or corrective maintenance tasks. Insufficient team members qualified to perform functional improvement as well as adaptive tasks, in cases where a customer places an order of a significant size.

16 Maintenance plan review: (5) A list of required software maintenance procedures and controls Most of the required procedures refer to the processes implemented by the corrective maintenance teams and by the user support center. These procedures typically deal with: Handling customers applications Handling a software failure report Periodic reporting and follow-up of user support services Periodic reporting and follow-up of corrective maintenance services Training and certification of maintenance team members.

17 Maintenance plan review: (6) The software maintenance budget The estimates used in the corrective maintenance budget are based on the manpower organization plan, required facilities and investments needed to establish these facilities, team training needs and other tasks.