• Like
Rangkuman part 4
Upcoming SlideShare
Loading in...5
×
Uploaded on

 

More in: Technology , Business
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
    Be the first to like this
No Downloads

Views

Total Views
368
On Slideshare
0
From Embeds
0
Number of Embeds
3

Actions

Shares
Downloads
3
Comments
0
Likes
0

Embeds 0

No embeds

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
    No notes for slide
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Transcript

  • 1. Rangkuman Part 4
  • 2. By : Indah Mayang Sari 5209 100 087
  • 3. Chapter 14 - Procedures and WorkInstructionsChapter 15 - Supporting Quality DevicesChapter 16 - Staff Training andCertificationChapter 17 - Corrective and PreventiveActionsChapter 18 - Configuration ManagementChapter 19 - Documentation Control
  • 4. Chapter 14Procedures and Work Instructions
  • 5. Procedure• is “a particular way of accomplishing something or of acting”• In other words, procedures, as transmitted in documents, are the detailed activities or processes to be performed according to a given method for the purpose of accomplishing a task.
  • 6. Work Instructions• are used mainly in cases where a uniform method of performing the task throughout the organization is either impossible or undesirable.• As a result, work instructions are specific to a team or depart- ment; they supplement procedures by providing explicit details that are suitable solely to the needs of one team, department, or unit.
  • 7. The Conceptual Hierarcy for Development Procedures & WI
  • 8. 5 Issues of Procedures
  • 9. Content of Procedures
  • 10. SQA WI Example
  • 11. Chapter 15Supporting Quality Devices
  • 12. Templates• is “a gauge, pattern or mold (as a thin plate or board) used as a guide to the form of a piece being made” (Webster’s New College Dictionary).• When applied to software engineering, the term template refers to a format (especially tables of contents) created by units or organizations, to be applied when compiling a report or some other type of document.
  • 13. Contribution of Template • Facilitates the process of preparing documents • Ensures that documents prepared by the developer are more complete • Provides for easier integration of new team members • Facilitates review of documents
  • 14. Checklists• used by software developers refers to the list of items specially constructed for each type of document, or a menu of preparations to be completed prior to performing an activity (e.g., installing a software package at the customer site).• Checklists are planned to be comprehensive if not complete.• Usually, checklist use tends to be considered an optional infrastructure tool, depending mainly on the list’s professional attributes, user acquain- tance with the list and availability.
  • 15. Contribution of Checklists • Helps developers carrying out self- checks of documents / software code • Assists developers in their preparations for tasks • Assures completeness of document reviews by review team members
  • 16. Chapter 16 Staff Training and Certification
  • 17. Objective of Training & Certification
  • 18. Training & Certification Process Determine the professional knowledge requirements for each position■ Determine the professional training and updating needs■ Plan the professional training program■ Plan the professional updating program■ Define positions requiring certification■ Plan certification processes■ Deliver training, updating and certification programs■ Perform follow-up of trained and certified staff.
  • 19. Determining Training & Updating Needs • Training: for new employees, according to their designated assignment • Retraining: for employees assigned to new positions or receiving new assignments • Updating: for staff members as demanded by their position.
  • 20. Typical Certification Requirements Professional education: academic or technical degrees and in some cases certification by a professional organization or by a leading commercial software producer■ Internal training courses■ Professional experience in the organization (may be partially or completely replaced by experience in other organizations)■ Assessment of achievements and ability as noted in periodic performance appraisals■ Evaluation by the candidate’s direct superior (often by completion of a special questionnaire)
  • 21. Chapter 17Corrective and Preventive Actions (CAPA)
  • 22. CAPA Definitions
  • 23. CAPA Process
  • 24. Information Collection
  • 25. Chapter 18Configuration Management
  • 26. Definitions
  • 27. Common Type of Items
  • 28. Common Type of Items
  • 29. SCM Definition
  • 30. Software Change Request
  • 31. Type of Software Configuration Releases • Baseline versions • Intermediate versions • Revisions • Numeration conventions for identification of SCI & Software versions
  • 32. SCI version document
  • 33. Software Configuration Release Documentation
  • 34. Chapter 19Documentation Control
  • 35. Definitions
  • 36. Typical Documents
  • 37. Documentation Control Procedures