Loading…
Computer System Compliance and Quality Planning
Quality planning as specified in the quality plan is critical to the success of a project. Despite its importance, the sufficiency of the project plan and its impact on quality planning are often not well understood. It has been surprising over the years to find that some project managers balk at pr...
Saved in:
Published in: | Journal of GXP compliance 2011-01, Vol.15 (1), p.74 |
---|---|
Main Author: | |
Format: | Article |
Language: | English |
Subjects: | |
Online Access: | Get full text |
Tags: |
Add Tag
No Tags, Be the first to tag this record!
|
cited_by | |
---|---|
cites | |
container_end_page | |
container_issue | 1 |
container_start_page | 74 |
container_title | Journal of GXP compliance |
container_volume | 15 |
creator | O'Connor, Bernard T |
description | Quality planning as specified in the quality plan is critical to the success of a project. Despite its importance, the sufficiency of the project plan and its impact on quality planning are often not well understood. It has been surprising over the years to find that some project managers balk at preparing a project plan. There are multiple possible reasons for the absence of planning. Perhaps the project managers do not consider computer systems development as a process. For a software quality engineer or compliance professionals to be able to fully understand the development process of a computer system, they must first understand all of the elements of the system life cycle and the software development life cycle. The best start in achieving a computer system design that remains true to its original requirements is the preparation of solid and meaningful project and quality plans that unambiguously spell out a testable, compliant design. |
format | article |
fullrecord | <record><control><sourceid>proquest</sourceid><recordid>TN_cdi_proquest_journals_862155722</recordid><sourceformat>XML</sourceformat><sourcesystem>PC</sourcesystem><sourcerecordid>2321641481</sourcerecordid><originalsourceid>FETCH-proquest_journals_8621557223</originalsourceid><addsrcrecordid>eNpjYuA0MjQ10DUztTRgYeA0NDU10jU1tzTkYOAqLs4yMDA1MDI35WTQd87PLSgtSS1SCK4sLknNVQDxczIT85JTFRLzUhQCSxNzMksqFQJyEvPyMvPSeRhY0xJzilN5oTQ3g5Kba4izh25BUX5haWpxSXxWfmlRHlAq3sIM6ABTcyMjY6IUAQCw0jOi</addsrcrecordid><sourcetype>Aggregation Database</sourcetype><iscdi>true</iscdi><recordtype>article</recordtype><pqid>862155722</pqid></control><display><type>article</type><title>Computer System Compliance and Quality Planning</title><source>ABI/INFORM global</source><creator>O'Connor, Bernard T</creator><creatorcontrib>O'Connor, Bernard T</creatorcontrib><description>Quality planning as specified in the quality plan is critical to the success of a project. Despite its importance, the sufficiency of the project plan and its impact on quality planning are often not well understood. It has been surprising over the years to find that some project managers balk at preparing a project plan. There are multiple possible reasons for the absence of planning. Perhaps the project managers do not consider computer systems development as a process. For a software quality engineer or compliance professionals to be able to fully understand the development process of a computer system, they must first understand all of the elements of the system life cycle and the software development life cycle. The best start in achieving a computer system design that remains true to its original requirements is the preparation of solid and meaningful project and quality plans that unambiguously spell out a testable, compliant design.</description><identifier>ISSN: 1552-5791</identifier><identifier>EISSN: 2150-6590</identifier><language>eng</language><publisher>North Olmsted: Informa</publisher><subject>Compliance ; Computer peripherals ; FDA approval ; Federal regulation ; Managers ; Planning ; Project management ; Quality control ; Social support ; Software quality ; Success ; Support groups ; Systems design ; Systems development ; Total quality ; User interface</subject><ispartof>Journal of GXP compliance, 2011-01, Vol.15 (1), p.74</ispartof><rights>Copyright Advanstar Communications, Inc. Winter 2011</rights><lds50>peer_reviewed</lds50><woscitedreferencessubscribed>false</woscitedreferencessubscribed></display><links><openurl>$$Topenurl_article</openurl><openurlfulltext>$$Topenurlfull_article</openurlfulltext><thumbnail>$$Tsyndetics_thumb_exl</thumbnail><linktopdf>$$Uhttps://www.proquest.com/docview/862155722/fulltextPDF?pq-origsite=primo$$EPDF$$P50$$Gproquest$$H</linktopdf><linktohtml>$$Uhttps://www.proquest.com/docview/862155722?pq-origsite=primo$$EHTML$$P50$$Gproquest$$H</linktohtml><link.rule.ids>314,776,780,11667,36037,44339,74638</link.rule.ids></links><search><creatorcontrib>O'Connor, Bernard T</creatorcontrib><title>Computer System Compliance and Quality Planning</title><title>Journal of GXP compliance</title><description>Quality planning as specified in the quality plan is critical to the success of a project. Despite its importance, the sufficiency of the project plan and its impact on quality planning are often not well understood. It has been surprising over the years to find that some project managers balk at preparing a project plan. There are multiple possible reasons for the absence of planning. Perhaps the project managers do not consider computer systems development as a process. For a software quality engineer or compliance professionals to be able to fully understand the development process of a computer system, they must first understand all of the elements of the system life cycle and the software development life cycle. The best start in achieving a computer system design that remains true to its original requirements is the preparation of solid and meaningful project and quality plans that unambiguously spell out a testable, compliant design.</description><subject>Compliance</subject><subject>Computer peripherals</subject><subject>FDA approval</subject><subject>Federal regulation</subject><subject>Managers</subject><subject>Planning</subject><subject>Project management</subject><subject>Quality control</subject><subject>Social support</subject><subject>Software quality</subject><subject>Success</subject><subject>Support groups</subject><subject>Systems design</subject><subject>Systems development</subject><subject>Total quality</subject><subject>User interface</subject><issn>1552-5791</issn><issn>2150-6590</issn><fulltext>true</fulltext><rsrctype>article</rsrctype><creationdate>2011</creationdate><recordtype>article</recordtype><sourceid>M0C</sourceid><recordid>eNpjYuA0MjQ10DUztTRgYeA0NDU10jU1tzTkYOAqLs4yMDA1MDI35WTQd87PLSgtSS1SCK4sLknNVQDxczIT85JTFRLzUhQCSxNzMksqFQJyEvPyMvPSeRhY0xJzilN5oTQ3g5Kba4izh25BUX5haWpxSXxWfmlRHlAq3sIM6ABTcyMjY6IUAQCw0jOi</recordid><startdate>20110101</startdate><enddate>20110101</enddate><creator>O'Connor, Bernard T</creator><general>Informa</general><scope>0U~</scope><scope>1-H</scope><scope>3V.</scope><scope>7WY</scope><scope>7WZ</scope><scope>7X7</scope><scope>7XB</scope><scope>87Z</scope><scope>88C</scope><scope>8FI</scope><scope>8FJ</scope><scope>8FK</scope><scope>8FL</scope><scope>8G5</scope><scope>ABUWG</scope><scope>AFKRA</scope><scope>AZQEC</scope><scope>BENPR</scope><scope>BEZIV</scope><scope>CCPQU</scope><scope>DWQXO</scope><scope>FRNLG</scope><scope>FYUFA</scope><scope>F~G</scope><scope>GHDGH</scope><scope>GNUQQ</scope><scope>GUQSH</scope><scope>K60</scope><scope>K6~</scope><scope>K9.</scope><scope>L.-</scope><scope>L.0</scope><scope>M0C</scope><scope>M0S</scope><scope>M0T</scope><scope>M2O</scope><scope>MBDVC</scope><scope>PADUT</scope><scope>PQBIZ</scope><scope>PQBZA</scope><scope>PQEST</scope><scope>PQQKQ</scope><scope>PQUKI</scope><scope>PRINS</scope><scope>PYYUZ</scope><scope>Q9U</scope></search><sort><creationdate>20110101</creationdate><title>Computer System Compliance and Quality Planning</title><author>O'Connor, Bernard T</author></sort><facets><frbrtype>5</frbrtype><frbrgroupid>cdi_FETCH-proquest_journals_8621557223</frbrgroupid><rsrctype>articles</rsrctype><prefilter>articles</prefilter><language>eng</language><creationdate>2011</creationdate><topic>Compliance</topic><topic>Computer peripherals</topic><topic>FDA approval</topic><topic>Federal regulation</topic><topic>Managers</topic><topic>Planning</topic><topic>Project management</topic><topic>Quality control</topic><topic>Social support</topic><topic>Software quality</topic><topic>Success</topic><topic>Support groups</topic><topic>Systems design</topic><topic>Systems development</topic><topic>Total quality</topic><topic>User interface</topic><toplevel>peer_reviewed</toplevel><toplevel>online_resources</toplevel><creatorcontrib>O'Connor, Bernard T</creatorcontrib><collection>Global News & ABI/Inform Professional</collection><collection>Trade PRO</collection><collection>ProQuest Central (Corporate)</collection><collection>ABI-INFORM Complete</collection><collection>ABI/INFORM Global (PDF only)</collection><collection>ProQuest Health & Medical Collection</collection><collection>ProQuest Central (purchase pre-March 2016)</collection><collection>ABI/INFORM Collection</collection><collection>Healthcare Administration Database (Alumni)</collection><collection>Hospital Premium Collection</collection><collection>Hospital Premium Collection (Alumni Edition)</collection><collection>ProQuest Central (Alumni) (purchase pre-March 2016)</collection><collection>ABI/INFORM Collection (Alumni Edition)</collection><collection>Research Library (Alumni Edition)</collection><collection>ProQuest Central (Alumni)</collection><collection>ProQuest Central UK/Ireland</collection><collection>ProQuest Central Essentials</collection><collection>ProQuest Central</collection><collection>Business Premium Collection</collection><collection>ProQuest One Community College</collection><collection>ProQuest Central</collection><collection>Business Premium Collection (Alumni)</collection><collection>Health Research Premium Collection</collection><collection>ABI/INFORM Global (Corporate)</collection><collection>Health Research Premium Collection (Alumni)</collection><collection>ProQuest Central Student</collection><collection>Research Library Prep</collection><collection>ProQuest Business Collection (Alumni Edition)</collection><collection>ProQuest Business Collection</collection><collection>ProQuest Health & Medical Complete (Alumni)</collection><collection>ABI/INFORM Professional Advanced</collection><collection>ABI/INFORM Professional Standard</collection><collection>ABI/INFORM global</collection><collection>Health & Medical Collection (Alumni Edition)</collection><collection>ProQuest Healthcare Administration Database</collection><collection>ProQuest research library</collection><collection>Research Library (Corporate)</collection><collection>Research Library China</collection><collection>One Business (ProQuest)</collection><collection>ProQuest One Business (Alumni)</collection><collection>ProQuest One Academic Eastern Edition (DO NOT USE)</collection><collection>ProQuest One Academic</collection><collection>ProQuest One Academic UKI Edition</collection><collection>ProQuest Central China</collection><collection>ABI/INFORM Collection China</collection><collection>ProQuest Central Basic</collection><jtitle>Journal of GXP compliance</jtitle></facets><delivery><delcategory>Remote Search Resource</delcategory><fulltext>fulltext</fulltext></delivery><addata><au>O'Connor, Bernard T</au><format>journal</format><genre>article</genre><ristype>JOUR</ristype><atitle>Computer System Compliance and Quality Planning</atitle><jtitle>Journal of GXP compliance</jtitle><date>2011-01-01</date><risdate>2011</risdate><volume>15</volume><issue>1</issue><spage>74</spage><pages>74-</pages><issn>1552-5791</issn><eissn>2150-6590</eissn><abstract>Quality planning as specified in the quality plan is critical to the success of a project. Despite its importance, the sufficiency of the project plan and its impact on quality planning are often not well understood. It has been surprising over the years to find that some project managers balk at preparing a project plan. There are multiple possible reasons for the absence of planning. Perhaps the project managers do not consider computer systems development as a process. For a software quality engineer or compliance professionals to be able to fully understand the development process of a computer system, they must first understand all of the elements of the system life cycle and the software development life cycle. The best start in achieving a computer system design that remains true to its original requirements is the preparation of solid and meaningful project and quality plans that unambiguously spell out a testable, compliant design.</abstract><cop>North Olmsted</cop><pub>Informa</pub></addata></record> |
fulltext | fulltext |
identifier | ISSN: 1552-5791 |
ispartof | Journal of GXP compliance, 2011-01, Vol.15 (1), p.74 |
issn | 1552-5791 2150-6590 |
language | eng |
recordid | cdi_proquest_journals_862155722 |
source | ABI/INFORM global |
subjects | Compliance Computer peripherals FDA approval Federal regulation Managers Planning Project management Quality control Social support Software quality Success Support groups Systems design Systems development Total quality User interface |
title | Computer System Compliance and Quality Planning |
url | http://sfxeu10.hosted.exlibrisgroup.com/loughborough?ctx_ver=Z39.88-2004&ctx_enc=info:ofi/enc:UTF-8&ctx_tim=2025-02-01T01%3A14%3A07IST&url_ver=Z39.88-2004&url_ctx_fmt=infofi/fmt:kev:mtx:ctx&rfr_id=info:sid/primo.exlibrisgroup.com:primo3-Article-proquest&rft_val_fmt=info:ofi/fmt:kev:mtx:journal&rft.genre=article&rft.atitle=Computer%20System%20Compliance%20and%20Quality%20Planning&rft.jtitle=Journal%20of%20GXP%20compliance&rft.au=O'Connor,%20Bernard%20T&rft.date=2011-01-01&rft.volume=15&rft.issue=1&rft.spage=74&rft.pages=74-&rft.issn=1552-5791&rft.eissn=2150-6590&rft_id=info:doi/&rft_dat=%3Cproquest%3E2321641481%3C/proquest%3E%3Cgrp_id%3Ecdi_FETCH-proquest_journals_8621557223%3C/grp_id%3E%3Coa%3E%3C/oa%3E%3Curl%3E%3C/url%3E&rft_id=info:oai/&rft_pqid=862155722&rft_id=info:pmid/&rfr_iscdi=true |