one of the easiest ways to ensure your reputation, to uphold your fiduciary duty to shareholders, to...
TRANSCRIPT
One of the easiest ways to ensure your reputation, to uphold your fiduciary duty to shareholders, to exercise due skill and care and not leave things to chance, is to adhere to ‘best practice’ technology audit.
Using ISO 9126, the BetaWatch workshop will teach you how to achieve digital due diligence by verifying that technology product, process, or service delivers what has been promised.
AgendaAgendaWhat is the International Organization for Standardization (ISO) 9126? What are the key documents required to perform the audit? What are the contents of of SRD, FR, PRD, and MRD How is the auditor an independent beta site? What is a functionality test matrix Gift Draw
ISO Advantage Workshop: March 31, 2003
BetaWatch IncBetaWatch Inc
Founded in 1999 by British trained librarian, English Language and Literature major
BetaWatch Education teaches ISO compliant proprietary data-gathering and analysis techniques to audit technology
BetaWatch Inc. verifies that technology product, process and service delivers what has been promised and validates that users can use it.
BetaWatch has audited a wide range of technologies including, middleware, virtual private network, CRM, e-commerce,knowledge management, transaction switch, digital imaging, media convergence, information warehousing, security, encryption, and business tracking
ISO Advantage Workshop: March 31, 2003
Assets of Product Process Assets of Product Process ServiceService
ISO Advantage Workshop: March 31, 2003
Qualitative Qualitative AnalysisAnalysisISO Quality Terms and digital due diligence methodology™
Quality terms are a mark of a mature theory
Even novices know quality terms
Growing recognition and expectation amongst auditors, investors, software engineers, users -- all stakeholders that technology must provide the value that has been promised
Technology auditors can provide the much needed stimuli for corporate governance
ISO Advantage Workshop: March 31, 2003
QueryQueryHave you ever had the feeling that a technology process, product, or service has not been integrated as expected?
Have you ever felt that a senior manager influenced the IS team to purchase technology?
Do you need assurance that the technology fulfills its claimed features and that your users can use it?
ISO Advantage Workshop: March 31, 2003
ISO 9126ISO 9126
Documented standard for Information, Technology, Software Product Evaluation, Quality, Characteristics, and Guidelines for their Use
Testing technology conformance of technology to its initial specifications
ISO Advantage Workshop: March 31, 2003
ISO 9126ISO 9126
ISO Advantage Workshop: March31, 2003
Three ViewsInternal Quality - development and maintenanceExternal Quality - executionQuality in Use - users achieve goals
Two Models External and Internal Quality in Use
9126 External and Internal 9126 External and Internal ModelModel
ISO Advantage Workshop: March 31, 2003
9126 Quality In Use Model9126 Quality In Use Model
ISO Advantage Workshop: March 31, 2003
• Effectiveness
• Productivity
• Safety
• Satisfaction
ISO Advantage Workshop: March 31, 2003
Information TheoryInformation Theory
The value others place in your efforts and expertise comes down to the quality of your communication skills and your ability to scribe signal from noise
ISO Advantage Workshop: March 31, 2003
Essential QuestionsEssential Questions
• What precisely are we doing? • How are we planning to do it?• How long will we be doing it for?• What resources are required?• What are the risks?• What value is expected?
Technology LifeCycleTechnology LifeCycle
ISO Advantage Workshop: March 31, 2003
ITERATIVE SEQUENTIAL
WATERFALLPROGRESSIVE
System Requirements System Requirements DocumentDocument
ISO Advantage Workshop: March 31, 2003
1 Features
2 Deliverables
3 Constraints
4 Design Description
5 User Interface
6 Testing
What precisely are we doing?
Feature RequirementsFeature Requirements
ISO Advantage Workshop: March 31, 2003
1 Design, refine baseline requirements, key features andcore functionality
2 Revision controlled detailed design document
3 Support development of documentation & trainingmaterials
4 Identify alpha and beta objectives
8 Liaise between sales
What precisely are we doing? How long will we be doing it for? What resources are required?
Product Requirements Product Requirements DocumentDocument
ISO Advantage Workshop: March 31, 2003
1 Plan and schedule deliverables associated with miliestones2 Track progress to determine slippage3 Manage and oversee staffing resources4 Communicate issues so each team member is aware of their goal,
role, and responsibility5 Ensure training is informed and involved with the resolutions that
affect delivery, functionality, and useability6 Monitor, and comply with project quality and process objectives7 Lead project status meetings8 Communication portal
How long will we be doing it for? What are the risks?What value is expected? Does it work as described?
Marketing RequirementsMarketing Requirements1 Set user requirements for the technology within the constraints of field support
2 Manage the technology launch from the box or conception to release and then post-release activities
3 Recommend and justify the plans with projections of future expectations
4 Develop and monitor consistent visibility and awareness communiqué
ISO Advantage Workshop: March 31, 2003
What value is expected? Can users can use it?
Auditor is an Independent Auditor is an Independent BetaSiteBetaSite
ISO Advantage Workshop: March 31, 2003
Yield the greatest Yield the greatest return return
ISO Advantage Workshop: March 31, 2003
• Technology is used in critical business area
• Over-ride the technology commonplace that there are always problems and users always want more
• First class audit measures the capability of the technology to fulfill its promise
Value PropositionValue Proposition
Using ISO 9126 quality terms and digital due diligence™ methodology auditors make sure that technology does what it says it does and that users can use it.
ISO Advantage Workshop: March 31, 2003