Home > Articles > Software Development & Management > UML

This chapter is from the book

3.5 The Quality Process

3.5.1 Quality Management Process-Component

The quality management process-component strives to bring together the social and methodological aspects of the project with a focus on quality. Some of the responsibilities of this process-component are planning for the project while keeping quality in mind, identifying the standards (including the UML standards for modeling), setting the expectations of the users, and, most importantly, getting the right people together for the quality work.

Figure 3.34Figure 3.34 Process-component for quality management


3.5.2 Roles in Quality Management

  • Quality manager organizes and manages the quality function including creation of the quality environment.

  • User highlights the quality expectations and provides feedback on the product/team's ability to meet those expectations.

  • Quality team/quality analysts carry out the quality functions.

3.5.3 Activities and Tasks in Quality Management

Figure 3.35 describes the activities and tasks of the process-component in quality management. Refer to the accompanying CD for a tabular form of these activities and tasks to enable you to create your own customized project plan.

Figure 3.35Figure 3.35 Activities and tasks in quality management

3.5.4 Deliverables in Quality Management

  • The quality plan handles the overall approach to quality within the project.

  • The test plan handles the management aspect of testing within the project.

  • The Quality Software Process describes the software process that can be customized and followed by the project members.

  • The standards (interim/input) exist at all levels within the project, including design, documentation, coding, and testing standards, to name but a few.

3.5.5 Quality Comments on Quality Management

Necessity

  1. The quality plan includes all documentation related to organizing the quality function. This includes all resources and schedules related to quality management, as well as to the project itself. This can be considered the main controlling deliverable for all quality-related activities in the project.

  2. The quality process is part of the overall QSP, but specifically deals with the process-components related to quality.

  3. The quality manager is responsible for overall planning, execution, and tracking of the quality functions—supported by the project manager.

  4. The user participates in explaining her quality needs and expectations, as well as providing input into quality activities.

  5. The quality expectations are created and continuously updated by the user with the quality manager.

  6. The quality planning activity undertakes planning and documentation of all quality functions.

  7. The quality environment creation deals with the creation of the physical and technical environment for quality activities.

  8. The quality team formation includes staffing, organizing, and motivating the people who perform quality roles in the projects.

  9. The process/model/other standardizations deal with creation and implementation of all relevant standards within the project.

Sufficiency

  1. The standards document provides a reference point for all standards within the project. In addition to the process and model standards, there are standards related to languages and data-bases, which are referred to in this iteratively produced standards document.

  2. The test plan deals with the quality control aspect of testing. It is created here especially from the resourcing point of view.

  3. The quality team and quality analyst are responsible for following the standards. At this stage, though, they provide input into the project and the organizational-level standards.

  4. The quality team formation is achieved by users who may decide to become part of the quality team, facilitating direct and continuous input in terms of quality expectations.

  5. The test planning activity creates and updates the test plan.

  6. The process/model/other standardizations are updated and followed by the quality team.

3.5.6 Quality Assurance Process-Component

Quality assurance follows the process-component of quality management and it undertakes the actual effort of assuring the quality of the models and processes in the project. As with most other process-components, the quality assurance process-component is not an independent process-component, but rather is intertwined with the process-components that produce the MOPS, MOSS, and MOBS. The project manager and the quality manager play key supporting roles in the execution of this process-component.

Figure 3.36Figure 3.36 Process-component for quality assurance


3.5.7 Roles in Quality Assurance

  1. Quality analyst

  2. Project team

  3. Project manager/quality manager

3.5.8 Activities and Tasks in Quality Assurance

Figure 3.37 describes the activities and tasks of the process-component in quality assurance. Refer to the accompanying CD for a tabular form of these activities and tasks to enable you to create your own customized project plan.

3.5.9 Deliverables in Quality Assurance

  • Quality Software Process in enactment. The QSP provides the basis for enacting the quality aspect of the project. This is made up of the templates, deliverables, activities, and tasks (including the ones mentioned here) that focus on quality.

  • MOPS. The Model Of Problem Space is subject to the rigors of quality assurance activities and tasks.

  • MOSS. The Model Of Solution Space is subject to the rigors of quality assurance activities and tasks.

  • MOBS. The Model Of Background Space is subject to the rigors of quality assurance activities and tasks.

Figure 3.37Figure 3.37 Activities and tasks in quality assurance

3.5.10 Quality Comments on Quality Assurance

Necessity

  1. The MOPS contains the relevant UML diagrams, descriptions, and specifications that are subjected to the quality checks. It is essential that this model is at a suitable level of completion (ideally at the end of an iteration) before quality checks are applied to it. As a result of the quality activities, the MOPS is updated.

  2. The MOSS contains the solution-level UML diagrams. This model is iteratively produced; therefore, its quality checks also iterate with the other two models.

  3. The MOBS is also subject to quality checks (a list of suggested quality checks appears in the accompanying CD for all three models including MOBS).

  4. The project team plays the supporting role to the quality analyst in his attempts to ensure quality of the models.

  5. The quality analyst is the primary role in this process-component. This role ensures that all the quality-related activities and tasks are carried out at the correct time and by the right people. In large practical projects, more than one person plays this role.

  6. Quality Software Process compliance ensures the compliance of the process as it is enacted. The necessary, sufficient, and malleable aspects of the process itself are assured here. This activity is carried out by the quality analyst.

  7. Quality Assuring MOPS undertakes the quality checks for MOPS as suggested on the accompanying CD.

  8. Quality Assuring MOSS undertakes the quality checks for MOSS as suggested on the accompanying CD.

  9. Quality Assuring MOBS undertakes the quality checks for MOBS as suggested on the accompanying CD.

Sufficiency

  1. The Quality Software Process in enactment is not a document-based deliverable but rather represents the entire QSP in enactment.

  2. In addition to the necessary roles played by the quality analyst, project manager, and quality manager, these managerial roles provide the organizational support for the quality effort.

  3. Quality Software Process compliance is supported by the project team.

  4. Deliverable correction is a reminder activity. It reminds the project team that they will continue to make corrections to the models, executables, and other deliverables in the project.

  5. In the quality process enactment, the project manager and the quality manager enact the process configured earlier in the process-configuration process-component.

  6. The standards compliance is also organized by the quality manager, but may be enforced by the quality analyst.

3.5.11 Quality Control Process-Component

While the process-component for quality control is mentioned here as a part of the overall quality process, it is discussed in great detail in Chapter 6.

3.5.12 Roles in Quality Control

  • Tester

  • Modeler/programmer/user

  • Quality manager

3.5.13 Activities and Tasks in Quality Control

Figure 3.39 describes the activities and tasks of the process-component in quality control. Refer to the accompanying CD for a tabular form of these activities and tasks to enable you to create your own customized project plan.

Figure 3.38Figure 3.38 Process-component for quality control


Figure 3.39Figure 3.39 Activities and tasks in quality control

3.5.14 Deliverables in Quality Control

  • The test plan contains the organizational aspect of testing. This includes details of the people and the schedules of testing, as well as what is expected of the testing process.

  • The test design provides a more tactical view of testing. Test designs can be organized around subsystems or packages.

  • The test environment is the physical environment that needs to be created before testing can begin. It is also the software environment (like the test databases and machines) that needs to be created for testing.

  • Test cases are the basic units of tests. They can be technical or business test cases. They contain, in addition to the steps to be executed in testing, inputs and expected results.

  • Test data is created, based on the sampling mechanisms (discussed in detail in Chapter 6), to ensure correct execution of tests—especially the ones with dependencies on another.

  • Test results are documented, collated, and used for reporting purposes. They can also be used to anticipate areas of the system that need more corrections, or even rewrites.

3.5.15 Quality Comments on Quality Control

Necessity

  1. The test plan is necessary for proper testing organization.

  2. Test cases are the basic units of tests and have to be created by users, testers, and programmers.

  3. Test data is the data on which tests are carried out. This is either the input in a test case or the test database.

  4. Test results should be carefully documented and analyzed.

  5. The tester is the primary actor in this process-component. The tester is played by more than one person, and depending on whether it is a technical or business testing, this role is played by a programmer, a business analyst, or a user.

  6. The quality manager supports the quality control activities.

  7. The model/program finalization is necessary before proper testing commences.

  8. The test case documentation must be carried out before testing can proceed.

  9. The model/program submission is made to the test manager, who then proceeds with the testing.

  10. The test execution is the testing of the model, executable, or whatever artifact is submitted for testing.

  11. The result collation is achieved preferably by using a tool to analyze the result, collate, and report.

Sufficiency

  1. The test design provides the sufficiency criteria, as good test designs based around the system design ensure that the testing is modular.

  2. The test environment focuses on creating a good test environment. It ensures that testing progresses in an orderly manner and takes less time than testing without the proper environment.

  3. The modelers, programmer, and user provide all necessary support to the programmer or, at times, play the tester role, as well.

  4. Testing the architecture establishment provides the additional impetus to testing by providing a well-organized basis for conducting the tests. This means organizing the databases, software, and operating systems for testing to commence.

  5. Testing the approach establishment ensures that all participants in the test teams are aware of the testing approach. This can be, at a high level, a decision to intensely test data, but not functionality, and vice versa.

  6. Test environment creation supports the physical creation of the environment.

  7. Reporting results is further analysis and reporting of the results from tests carried out.

  8. Model/program correction is correcting whatever has been found in error.

  9. Regression testing/planning is redoing tests after the corrections have been made by the developers/modelers.

InformIT Promotional Mailings & Special Offers

I would like to receive exclusive offers and hear about products from InformIT and its family of brands. I can unsubscribe at any time.

Overview


Pearson Education, Inc., 221 River Street, Hoboken, New Jersey 07030, (Pearson) presents this site to provide information about products and services that can be purchased through this site.

This privacy notice provides an overview of our commitment to privacy and describes how we collect, protect, use and share personal information collected through this site. Please note that other Pearson websites and online products and services have their own separate privacy policies.

Collection and Use of Information


To conduct business and deliver products and services, Pearson collects and uses personal information in several ways in connection with this site, including:

Questions and Inquiries

For inquiries and questions, we collect the inquiry or question, together with name, contact details (email address, phone number and mailing address) and any other additional information voluntarily submitted to us through a Contact Us form or an email. We use this information to address the inquiry and respond to the question.

Online Store

For orders and purchases placed through our online store on this site, we collect order details, name, institution name and address (if applicable), email address, phone number, shipping and billing addresses, credit/debit card information, shipping options and any instructions. We use this information to complete transactions, fulfill orders, communicate with individuals placing orders or visiting the online store, and for related purposes.

Surveys

Pearson may offer opportunities to provide feedback or participate in surveys, including surveys evaluating Pearson products, services or sites. Participation is voluntary. Pearson collects information requested in the survey questions and uses the information to evaluate, support, maintain and improve products, services or sites, develop new products and services, conduct educational research and for other purposes specified in the survey.

Contests and Drawings

Occasionally, we may sponsor a contest or drawing. Participation is optional. Pearson collects name, contact information and other information specified on the entry form for the contest or drawing to conduct the contest or drawing. Pearson may collect additional personal information from the winners of a contest or drawing in order to award the prize and for tax reporting purposes, as required by law.

Newsletters

If you have elected to receive email newsletters or promotional mailings and special offers but want to unsubscribe, simply email information@informit.com.

Service Announcements

On rare occasions it is necessary to send out a strictly service related announcement. For instance, if our service is temporarily suspended for maintenance we might send users an email. Generally, users may not opt-out of these communications, though they can deactivate their account information. However, these communications are not promotional in nature.

Customer Service

We communicate with users on a regular basis to provide requested services and in regard to issues relating to their account we reply via email or phone in accordance with the users' wishes when a user submits their information through our Contact Us form.

Other Collection and Use of Information


Application and System Logs

Pearson automatically collects log data to help ensure the delivery, availability and security of this site. Log data may include technical information about how a user or visitor connected to this site, such as browser type, type of computer/device, operating system, internet service provider and IP address. We use this information for support purposes and to monitor the health of the site, identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents and appropriately scale computing resources.

Web Analytics

Pearson may use third party web trend analytical services, including Google Analytics, to collect visitor information, such as IP addresses, browser types, referring pages, pages visited and time spent on a particular site. While these analytical services collect and report information on an anonymous basis, they may use cookies to gather web trend information. The information gathered may enable Pearson (but not the third party web trend services) to link information with application and system log data. Pearson uses this information for system administration and to identify problems, improve service, detect unauthorized access and fraudulent activity, prevent and respond to security incidents, appropriately scale computing resources and otherwise support and deliver this site and its services.

Cookies and Related Technologies

This site uses cookies and similar technologies to personalize content, measure traffic patterns, control security, track use and access of information on this site, and provide interest-based messages and advertising. Users can manage and block the use of cookies through their browser. Disabling or blocking certain cookies may limit the functionality of this site.

Do Not Track

This site currently does not respond to Do Not Track signals.

Security


Pearson uses appropriate physical, administrative and technical security measures to protect personal information from unauthorized access, use and disclosure.

Children


This site is not directed to children under the age of 13.

Marketing


Pearson may send or direct marketing communications to users, provided that

  • Pearson will not use personal information collected or processed as a K-12 school service provider for the purpose of directed or targeted advertising.
  • Such marketing is consistent with applicable law and Pearson's legal obligations.
  • Pearson will not knowingly direct or send marketing communications to an individual who has expressed a preference not to receive marketing.
  • Where required by applicable law, express or implied consent to marketing exists and has not been withdrawn.

Pearson may provide personal information to a third party service provider on a restricted basis to provide marketing solely on behalf of Pearson or an affiliate or customer for whom Pearson is a service provider. Marketing preferences may be changed at any time.

Correcting/Updating Personal Information


If a user's personally identifiable information changes (such as your postal address or email address), we provide a way to correct or update that user's personal data provided to us. This can be done on the Account page. If a user no longer desires our service and desires to delete his or her account, please contact us at customer-service@informit.com and we will process the deletion of a user's account.

Choice/Opt-out


Users can always make an informed choice as to whether they should proceed with certain services offered by InformIT. If you choose to remove yourself from our mailing list(s) simply visit the following page and uncheck any communication you no longer want to receive: www.informit.com/u.aspx.

Sale of Personal Information


Pearson does not rent or sell personal information in exchange for any payment of money.

While Pearson does not sell personal information, as defined in Nevada law, Nevada residents may email a request for no sale of their personal information to NevadaDesignatedRequest@pearson.com.

Supplemental Privacy Statement for California Residents


California residents should read our Supplemental privacy statement for California residents in conjunction with this Privacy Notice. The Supplemental privacy statement for California residents explains Pearson's commitment to comply with California law and applies to personal information of California residents collected in connection with this site and the Services.

Sharing and Disclosure


Pearson may disclose personal information, as follows:

  • As required by law.
  • With the consent of the individual (or their parent, if the individual is a minor)
  • In response to a subpoena, court order or legal process, to the extent permitted or required by law
  • To protect the security and safety of individuals, data, assets and systems, consistent with applicable law
  • In connection the sale, joint venture or other transfer of some or all of its company or assets, subject to the provisions of this Privacy Notice
  • To investigate or address actual or suspected fraud or other illegal activities
  • To exercise its legal rights, including enforcement of the Terms of Use for this site or another contract
  • To affiliated Pearson companies and other companies and organizations who perform work for Pearson and are obligated to protect the privacy of personal information consistent with this Privacy Notice
  • To a school, organization, company or government agency, where Pearson collects or processes the personal information in a school setting or on behalf of such organization, company or government agency.

Links


This web site contains links to other sites. Please be aware that we are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of each and every web site that collects Personal Information. This privacy statement applies solely to information collected by this web site.

Requests and Contact


Please contact us about this Privacy Notice or if you have any requests or questions relating to the privacy of your personal information.

Changes to this Privacy Notice


We may revise this Privacy Notice through an updated posting. We will identify the effective date of the revision in the posting. Often, updates are made to provide greater clarity or to comply with changes in regulatory requirements. If the updates involve material changes to the collection, protection, use or disclosure of Personal Information, Pearson will provide notice of the change through a conspicuous notice on this site or other appropriate way. Continued use of the site after the effective date of a posted revision evidences acceptance. Please contact us if you have questions or concerns about the Privacy Notice or any objection to any revisions.

Last Update: November 17, 2020