UNIT - III
SOFTWARE QUALITY
INFRASTRUCTURE
COMPONENTS
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Guidelines and tips
Prepare for your exams
Study with the several resources on Docsity
Earn points to download
Earn points by helping other students or get them with a premium plan
Community
Ask the community
Ask the community for help and clear up your study doubts
University Rankings
Discover the best universities in your country according to Docsity users
Free resources
Our save-the-student-ebooks!
Download our free guides on studying techniques, anxiety management strategies, and thesis advice from Docsity tutors
Effective Communication and Checklists in Software Development and Maintenance, Study notes of Information Technology
The importance of effective communication between staff involved in software development and maintenance. It discusses the role of work instructions and checklists in facilitating the process, providing examples of templates and checklists. The document also covers the advantages of checklists for development and maintenance teams, as well as the objectives and process of training and certification. Topics include software engineering, sqa & management skills, and software maintenance.
Typology: Study notes
2016/2017
1 / 59
This page cannot be seen from the preview
Don't miss anything!
Related documents
Partial preview of the text
Download Effective Communication and Checklists in Software Development and Maintenance and more Study notes Information Technology in PDF only on Docsity!
UNIT - III
SOFTWARE QUALITY
INFRASTRUCTURE
COMPONENTS
PROCEDURES AND WORK INSTRUCTIONS Procedures and Work Instructions are both parts of a Quality Management System Defines what someone needs to do (^) how to do it But both of them are really different.
WORK INSTRUCTIONS
(^) work instruction describes how to perform a specific task. work instructions are specific to a team or department They supplement procedures by providing explicit details, to the department or unit.
The Need For Procedures And Work Instructions SQA procedures and work instructions aim at: Performance of tasks, processes or activities in the most effective without deviating from quality requirements. Effective and efficient communication between the separate staffs involved in the development and maintenance of software systems. Simplified coordination between tasks and activities performed by the various bodies of the organization. Better coordination means fewer errors.
The Procedures Manual The collection of all SQA procedures is usually referred to as the SQA procedures manual. The contents of any one organization’s procedures manual varies according to:. [1] The types of software development and maintenance activities carried out by the organization [2] The range of activities belonging to each activity type [3] The range of customers (e.g., internal, customers of custom-made software, COTS software customers) and suppliers (e.g., self-development and maintenance, subcontractors, suppliers of COTS software and reused software modules)
Work Instructions And Work Instruction Manuals
- (^) Work instructions deal with the application of procedures, adapted to the requirements of a specific project team, customer, or other relevant party. Departmental work instructions
- Audit process for new software development subcontractors (supplier candidates)
- Priorities for handling corrective maintenance tasks
- Annual evaluation of software development subcontractors
- On-the-job instructions and follow-up for new team members
- Design documentation templates and their application
- C++ (or other language) programming instructions
Project management work instructions
- Coordination and cooperation with the customer
- Weekly progress reporting by team leaders
- Special design report templates and their application in the project
- Follow-up of beta site reporting
- Monthly progress reporting to the customer
- Coordination of installation and customer’s team instructions
- (^) Templates
- (^) The contribution of templates to software quality
- (^) The organizational framework for preparing, implementing and updating templates
- (^) Checklists
- (^) The contribution of checklists to software quality
- (^) The organizational framework for preparing, implementing and updating checklists
Examples of Templates
- (^) Software test plan
- (^) Software test description
- (^) Software test report
- (^) Software change request
- (^) Version description document
- (^) Software requirement specification
- (^) System design description
- (^) Computer operator manual
- (^) Interface design description
- (^) ……
Information sources in preparing a template
- (^) Informal templates already in use
- (^) Template examples found in professional publications
- (^) Templates used by similar organizations
* User proposals and suggestions.
* Changes in the organization's
areas of
activity.
* Proposals initiated by design
review and inspection teams.
* Analysis of failures as well as
successes.
* Other organizations' experience.
* SQA team initiatives
The advantages of checklists
To development teams:
(^) * Helps developers carrying out self- checks of documents or software code prior completion. (^) * Assists developers in their preparations for tasks.
To review teams:
(^) * Assures completeness of document reviews by review team members. (^) * Facilitates improves efficiency of review sessions.
Information sources in preparing a checklist
- (^) Informal checklists already in use
- (^) Checklist examples found in professional publications or books
- (^) Checklist s used by similar organizations