Rangkuman part 3
Upcoming SlideShare
Loading in...5
×

Like this? Share it with your network

Share
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Be the first to comment
No Downloads

Views

Total Views
1,062
On Slideshare
953
From Embeds
109
Number of Embeds
2

Actions

Shares
Downloads
24
Comments
0
Likes
1

Embeds 109

http://indahmayangsari.blogspot.com 108
http://indahmayangsari.blogspot.tw 1

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
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n
  • \n

Transcript

  • 1. Rangkuman Part 3
  • 2. By : Indah Mayang Sari 5209 100 087
  • 3. Chapter 7 - Integrating Quality Activities in theProject Life CycleChapter 8 - ReviewsChapter 9 - Software Testing (Strategies)Chapter 10 - Software Testing (Implementation)Chapter 11 - Assuring the Quality of SoftwareMaintenance ComponentsChapter 12 - Assuring the Quality of ExternalParticipant’s ContributionChapter 13 - CASE Tools and Their Effect onSoftware Quality
  • 4. Chapter 7 Integrating QualityActivities in the Project Life Cycle
  • 5. • Most quality assurance activities take place in conjunction with the completion or examination of activity milestones, which require review of the product development activities previously completed.• Therefore, SQA professionals should be acquainted with the var- ious software engineering models in order to be able to prepare a quality plan that is properly integrated into the project plan.
  • 6. Software Development Methodologies• SDLC Model • the model display the major building blocks for the entire development process, described as a linear sequence• Prototyping Model • based on replacement of one or more SDLC phases by an evolutionary process• Spiral Model • provides a methodology for ensuring effective performance at each of the SDLC model phases• Object-oriented Model • incorporated large-scale reuse of software by integrating reusables modules into new software system
  • 7. SDLC Model
  • 8. Prototyping Model
  • 9. The main advantages & deficiencies of prototyping over the completed SDLC methodologies
  • 10. Spiral Model
  • 11. The Object-oriented model
  • 12. Verification, Validation, Qualification• “Verification – The process of evaluating a system or component to deter- mine whether the products of a given development phase satisfy the conditions imposed at the start of that phase.”• “Validation – The process of evaluating a system or component during or at the end of the development process to determine whether it satisfies specified requirements.”• “Qualification – The process used to determine whether a system or com- ponent is suitable for operational use.”
  • 13. Chapter 8 Reviews
  • 14. Review Objectives
  • 15. Formal Design Reviews
  • 16. Preparation for a DR• Review leader preparations• Review team preparations• Development team preparations
  • 17. Pressman Golden Guidelines
  • 18. Peer Reviews
  • 19. Participants of Peer Review • The review leader • The author • a designer • a coder implementer • a tester • Team assignments • the presenter • the scribe
  • 20. Post-peer review Activities
  • 21. Chapter 9Software Testing - Strategies
  • 22. Software Test Definition
  • 23. Software Testing Objective
  • 24. Software Testing Strategies
  • 25. Incremental testing
  • 26. Software Test Classification• Black box (functionally) testing• White box (structural) testing
  • 27. Classification according to requirements
  • 28. White box VS Black box
  • 29. Other Operation Factor Testing Classes
  • 30. Component of Documentation Tests• Functional descriptions of the software system• Installation manual• User manual• programmer manual• Document completeness check• Document correctness tests• Document style & editing inspection
  • 31. Revision factor Testing Classes • Maintainability tests • Flexibility tests • Testability tests
  • 32. Transition Factor Testing Classes • Portability Tests • Reusability Tests • Tests for interoperability requirements : • Software interfacing tests • Equipment interfacing tests
  • 33. Chapter 10 Software Testing - Implementation
  • 34. 1. The Testing process• Determining the test methodology phase
  • 35. Planning the tests• the test to be planned• What to test?• Rating unit, integrations, applications
  • 36. Test design
  • 37. Test Implementation
  • 38. 2. Test Case Design• Test case data component• Test case sources
  • 39. 3. Automated testing
  • 40. Types of automated tests
  • 41. The main advantages of automated tests :• Accuracy and completeness of performance• Accuracy of results log and summary reports• Comprehensiveness of information• Few manpower resources required to perform tests• Shorter duration of testing• Performance of complete regression tests• Performance of test classes beyon the scope of manual testing
  • 42. The main disadvantages of automated tests :• High investments required in package purchasing and training• High package development investment costs• High manpower requirements for test preparation• Considerable testing area left uncovered
  • 43. Chapter 11Assuring the Quality ofSoftware Maintenance Componenets
  • 44. Introduction Corrective maintenance – user support services and software corrections.■ Adaptive maintenance – adapts the software package to differences in new customer requirements, changing environmental conditions and the like.■ Functionality improvement maintenance – combines (1) perfective maintenance of new functions added to the software so as to enhance performance, with (2) preventive maintenance activities that improve reliability and system infrastructure for easier and more efficient future maintainability.
  • 45. The Foundation of High Quality• Foundation 1 : software package quality• Foundation 2 : maintenance policy
  • 46. Pre-maintenance Software Quality Components•Maintenance contract review•Maintenance plan construction
  • 47. Maintenance contract review• Customer requirements clarification• Review of alternative approaches to maintenance provision• Review of estimates of required maintenance resources• Review of maintenance services to be provided by subcontractors/customer• Review of maintenance costs estimates
  • 48. Maintenance plan• A list of the contracted maintenance services• A description of the maintenance team’s organization• A list of maintenance facilities• A list of identified maintenance service risks• A list of required software maintenance procedures & controls• The software maintenance budget
  • 49. Maintenance Software Quality Assurance Tools• SQA tools for corrective • maintenance documentation & maintenance quality records• SQA tools for functionality • Managerial control SQA tools for improvement maintenance software maintenance• SQA infrastructure components for • performance controls for software software maintenance maintenance service • maintenance procedures & WI • quality metrics for software maintenance • supporting quality devices • costs of software maintenance quality • training & certification of maintenance teams • cost of external failure of software corrective maintenance activities • preventive & corrective action • configuration management
  • 50. Chapter 12Assuring the Quality of External Participant’s Contribution
  • 51. Types of External Participants • Subcontractors • Supplier of COTS software & reused software modules • The customer themselves as participant in performing the project