IS development: Quality Standards Documentation
|
|
- Loreen Richard
- 5 years ago
- Views:
Transcription
1 Lecture Objectives IS development: Quality Standards Documentation IMS9300 IS/IM FUNDAMENTALS At the completion of this topic, you should : understand the need for, and the role of, quality in systems development be able to define the terms quality and standards ; be aware of the quality attributes which may be applied to system development products and process; be aware of standards and reviews and their relationship to quality be familiar with major documents produced in the course of IS development understand some major considerations in planning documention 2 Some definitions of Quality Determining Quality.. Degree of excellence (Oxford) Fitness for purpose (AS1057) includes quality of design, the degree of conformance to design, it may include such factors as economic or perceived values Ability to satisfy stated/implied needs (ISO8402) Conformance to requirements (Crosby, Horch) when having a meal in a restaurant when purchasing a car when buying a computer The requirements vary immensely, and some of the success measures are very hard to quantify Quality means different things to different people.. and it varies in different situations 3 4 Why should it concern us? Error Detection Customers expectations and demands are increasing Competitors provide it Substantial savings demonstrated PRODUCTIVITY QUALITY EFFICIENCY COMPETITIVE POSITION COST SAVINGS 5 Effort spent on software maintenance is greater than that spent on software development. An error is typically 100 times more expensive to correct in the maintenance phase on large projects, than in the requirements phase. Boehm, B. (1981) Software Engineering Economics 6
2 Error Detection Quality Costs The cost of detecting and correcting errors rises greatly during the systems development cycle. $ Initiation Analysis Design Implementation In addition to this is the cost to the organisation of having an incorrect system 7 Obvious upfront costs to the organisation The hidden costs of not having quality The tip of the Iceberg Review, Inspection, Re-do, User complaints, Downtime, Loss of sales, Re-testing, Re-documenting, Re-training, Overtime, Customer complaints, Financial losses, Employee turnover 8 Quality Requirements Quality Requirements Correctness - Does it accurately do what is intended? Reliability - Does it do it right every time? Efficiency- Does it run as well as it could? Integrity - Is it precise and unambiguous? Usability - Is it easy to use? Maintainability - Is it easy to fix? Testability - Is correctness easy to check and verify? Flexibility - Is it easy to adapt and extend? Portability - Can it be easily converted? Reusability - Does it consist of general purpose modules? Interoperability - Will it integrate easily with other systems? 9 10 The Quality Process Implementing a Quality System The quality process involves the functions of: Quality control - monitoring a process and eliminating causes of unsatisfactory performance Quality assurance - planning and controlling functions required to ensure a quality product or process Quality must start at the top - Executive sponsorship is vital. Everyone must be involved and motivated to realise that they have a responsibility towards the final product, its use, and its quality. Improve job processes by using standards, and preparing better documentation (using project control methodologies). Use a QA group. Use reviews
3 Standards Standards applied King s standard (flag) as a point of reunion in battle (Oxford English Dictionary) agreed point of reference exemplar of a unit of measure eg. a measuring rod authoritative exemplar of correctness, or quality Documents/ publications - form, technology Communication channels - meetings, records (minutes), information distribution Security confidences, privacy, ethics Behaviour dress code, punctuality, follow up Testing/ rigor - analysis, design, software, hardware agreement to impose standards Standards (formal) Other standards in IS Development projects Two levels of standards Industry / National / International Organisational Industry (IT procurement) Capability Maturity Model (Humphrey 1989) National / International Standards Australia (AS 3563) International Standards Organisation (ISO 9000) Organisational The organisation may adopt or tailor industry, national or international standards. deliverable requires some previous task to have been completed in order for the deliverable to be created milestone indicator (finite document/ finite action) of how far you ve come, how far to go Reviews Reviews are used in the quality control and quality assurance functions. There are two main forms of review: management reviews technical reviews The review is part of quality control and must produce a report so that the quality assurance function can be satisfied. Management or Project Review deliverable checked to baseline to see it meets the quality assurance requirements. This may involve simply noting that a technical review (meeting quality assurance requirements) has passed a particular deliverable
4 Technical Reviews What is documentation? Structured meeting where a piece of work, which has previously been distributed to participants, is checked for errors, omissions, and conformance to standards. All deliverables need review. The report may be a checklist which indicates that the deliverable passes/fails the quality requirements for that type of deliverable. Not necessarily a piece of paper. Any permanent medium used to communicate to other people can be classed as documentation Documentation Typical IS documentation to inform user manual to communicate system specifications to convey knowledge DFD, ER Diagram to authorise credentials, ID to control or regulate relationships between people contracts, task specification to represent an action or deed meeting minutes to provide evidence system manual Data dictionary System specifications Feasibility report System manual Users manual Data dictionary Process models DFD Data models database schema Documents as deliverables Bad documentation Specified document, formal outline, eg. proposal Formal detailed requirements within document which must be presented Dependent upon underlying tasks being completed in order to create document Project management tool Confusing, inconsistent layout Important points buried, not highlighted Insufficient reference aids Insufficient consideration of the intended audience, purpose Use of jargon, without definitions or explanation Inappropriate layout for the material being discussed Verbose, or too brief Difficult to update Bulky overwhelming physical format 23 24
5 Developing the concept of an audience Developing the concept of a purpose the tone, style, language and emphasis you should use the relative level of technological experience general background, training, education possible attitudes towards your message muticultural backgrounds To correctly understand the purpose of a document you need to answer 2 questions: What are the specific problems you are addressing? What questions will the audience want answered? Information Systems Documentation Good Documentation User Manual Systems Manual Data Manual Program Specification Manual Operations Manual Good documentation: reduces the need to refer problems to system developers overcomes users fears of equipment and software ensures successful first encounters with a system enables users to find what they want and understand it when they find it is accurate and complete is written for the intended audience and purpose has good reference aids (table of contents, thorough index, cross-referencing) Document organisation - principles Make the organisation of material apparent to readers Tell them what you are going to tell them before you tell them Organise the document in ways expected by readers: chronological order most important to least important order of need order of difficulty question / answer order alphabetical order Planning a Cost-time Schedule for documentation Why? - Often documentation is forgotten, ignored or dismissed as not being important. Aim - to develop an estimate of the time required for documentation DURING development.. not a trivial task. Time vs Cost - be realistic about your estimates.. Time saved in the documentation task will be wasted many times over explaining things not included or not clearly described in the documentation provided
6 Reference References (2) WHITTEN, J.L., BENTLEY, L.D. and DITTMAN, K.C. (2001) 5th ed., Systems Analysis and Design Methods, Irwin/McGraw-HilI, New York, NY. Chapters 5, 8 HOFFER, J.A., GEORGE, J.F. and VALACICH (1999) 2nd ed., Modern Systems Analysis and Design, Benjamin/Cummings, Massachusetts. Chapter 9 ANDERSON, P.V. (1995). Technical writing: A reader-centred approach, 3rd ed. Harcourt, Brace & Co., Fort Worth. BROCKMAN, J. R. (1990). Writing better computer user documentation - From paper to hypertext. John Wiley and Sons, Inc., New York. Standards Association of Australia (1991). Australian Standard : Software Quality Management System. Part 1 Requirements Standards Association of Australia (1991). Australian Standard : Software Quality Management System. Part 2 Implementation Guide User manual ADDITIONAL NOTES Document planning Purpose: a contractual obligation a marketing tool a training tool a reference for non-technical people a memory in case key staff leave Contents: what the system is about (narrative); how to use the hardware how to carry out tasks - details of manual procedures involved; how to enter data, produce output, interpret output; how to correct mistakes how to solve typical problems; how to ensure security; how to perform backup and recovery Systems manual Data Manual Purpose: to enable technical staff to understand the system so that they can: modify the system evaluate the system s behaviour fix errors in the system Contents: overview of the system descriptions of all components system specifications controls, errors, audit trails. 35 enables (technically-oriented) developers and maintainers to: understand what data is used and where. identify the effects of changes relating to data. Contents: Files - schemas, sub-schemas, file layouts. Inputs/Outputs - reports; inputs Data Elements Data Analysis - logical and physical data model 36
7 Program specification manual Operations manual Purpose: to support communication between analyst/designer and programmer; to describe in detail what the program does > for initial development; > for maintenance. Contents: design specification (narrative describing the purpose and general functions of the program), listing of each program (for maintenance purposes), layouts of files or database area used, layouts of screens and reports, test plan, test data, test conditions, test results Purpose: Large scale systems may need operations support. If so, a separate operations manual is needed to instruct operations staff in operating and controlling the new system. Contents: system overview (purpose/functions of the system) processing flow system start-up/shut-down restart and recovery procedures security/backup procedures tape/disk library instructions user contacts and procedures priority of jobs report distribution information Planning your documentation Audience Audience - sets the tone, style, language and emphasis level of computer sophistication background, training, or education attitude towards your message cultural background Purpose - why is the documentation necessary? identifies the content indicates the level of detail required Medium paper-based manuals and reference cards on-line documentation aural and visual training materials 39 Type of documentation Audience User Manual users - new, intermediate, experienced System Manual client, maintenance team Data Manual (Data Dictionary) developers, maintenance team Program Manual developers, maintenance team Operations Manual operators, technical staff 40 Documentation organisation Chunking - the rule of seven Titles - briefly describe upcoming information Relevance - put related information together Consistency style, voice, emotion Hierarchy of structure - Chapters, Sections, Topics Integrated graphics appropriate, support text Accessible detail - access routes to different levels of detail (overall/general, specific, fine detail) 41 Choose appropriate media Manuals Most common... not good for trivial problems. Brochures Main capabilities are highlighted... emphasises simplicity and elegance, not the detail of manuals. 4-8 pages fully describing the system. Quick reference guides 90% of the time 90% of the needs of 90% of the readers can be met by a simple summary card. On-line help Ideal reminders... useful as an aid for experienced user BUT are not a replacement for manuals 42
8 Online vs paper-based documentation Online easier to distribute and maintain Printing costs reduced Online enables different search paths to the same information Easier for user to become disoriented Online documentation must be written differently Online documentation must be consistent with paper-based documentation 43 Reference Aids Information contained in a large, complex document is often inaccessible Use: Glossaries Indexes (very important) Contents page Others Numbering systems Page, Sections, paragraphs, items Section dividers - tabbed card, coloured pages, Section/chapter summaries 44 Colour and graphics Layout and Pagination Use a minimum number of colours Be consistent and familiar (eg. red for hot) in your use of colour codes Don't rely on colour alone to discriminate between items Graphics can make a document more effective: points in a text can be emphasised can increase reader's interest can replace, clarify or simplify the text Layout: Be consistent in your layout Use type size (at least 4 points different) or bolding to indicate relative importance or weight Page: Use a page size suited to the environment that the document is going to be used in Make sure page numbering is clear The Documentation Process Effective documentation check list Specify the document Draft and edit the document Review the document OK Publish the document Not OK Maintain the document Objective clearly stated Target audience identified Consistent approach used (wording, structure, layout) - templates help The principles of documentation organisation and development have been followed Maintenance process in place Put yourself in the users position - can you easily find what you re looking for? 47 48
Lecture Objectives. Documentation What is it? User Documentation Purpose. User Documentation Report Format (an example) User Documentation Purpose
Lecture Objectives IMS 2501 2 nd Year Studio Seminar 7 and Testing Semester 1, 2005 > What is it? > User, Report Format > Programming, Report Format > General Principles for Good Testing > What is testing?
More informationModelling as a Communication Tool: Introduction to Process Modelling. Modelling. Simplification in modelling. Representation in modelling
CSE104 - Information Systems 1 Modelling as a Communication Tool: Introduction to Process Modelling The requirements specification document Must be communicated to key stakeholders Should contain: Functions
More informationModelling: Review. Modelling Information Systems. Models in analysis and design. Process Modelling. Modelling perspectives
Modelling: Review IMS100 Systems Analysis and Design Topic Review of Process Modelling Why do we do it? Communication and understanding Simplification all models are simplifications of the real world:
More informationinformation process modelling DFDs Process description
Process modelling IMS9300 IS/IM FUNDAMENTALS information process modelling DFDs Process description processes are the action part of businesses process modelling graphically represents the processes which
More informationProcess Modelling. Data flow Diagrams. Process Modelling Data Flow Diagrams. CSE Information Systems 1
CSE104 - Information s 1 Process Modelling Data Flow Diagrams Process Modelling Process modelling aims to graphically represent the processes which capture, manipulate, store and distribute data. data
More informationIMS1002/CSE1205 Lectures 1
IMS1002/CSE1205 Systems Analysis and Design Lecture 2 & 3 Introduction to Data Modelling Entity Relationship Modelling Data Modelling Focus on the information aspects of the organisation In a database
More informationRequirement Analysis
Requirement Analysis Requirements Analysis & Specification Objective: determine what the system must do to solve the problem (without describing how) Done by Analyst (also called Requirements Analyst)
More informationCIS 890: Safety Critical Systems
CIS 890: Safety Critical Systems Lecture: Requirements Introduction Copyright 2011, John Hatcliff. The syllabus and all lectures for this course are copyrighted materials and may not be used in other course
More informationTopic 5c: Designing Interfaces and Dialogues Part 1. Lecture Objectives. Why bother with Interface Design? Human Computer Interface Design
IMS1002 Systems Analysis and Design Lecture Objectives Topic 5c Designing Interfaces and At the completion of this lecture you should be able to: Understand the importance of interface deisgn Understand
More informationContents. Before you begin. Topic 1: Plan documents 1. Topic 2: Draft text 41. Topic 3: Prepare final text 63. Topic 4: Produce a document 79
Contents Before you begin vii Topic 1: Plan documents 1 1A Determine the document purpose 2 1B Choose appropriate document format 6 1C Establish the means of communication 14 1D Determine document requirements
More informationCREATING A STYLE GUIDE FOR YOUR ORGANISATION
CIPR SKILLS GUIDE CREATING A STYLE GUIDE FOR YOUR ORGANISATION #CIPR @CIPR_UK WHY HAVE A STYLE GUIDE? Sloppy writing, jargon, long sentences and incomprehensible waffle ironically communicates one thing
More informationSystems Analysis and Design
Systems Analysis and Design Alan Dennis, Barbara Haley Wixom, and Roberta Roth John Wiley & Sons, Inc. Slides by Candace S. Garrod Red Rocks Community College 9-1 User Interfaces Chapter 9 9-2 Key Definitions
More informationEXAM PREPARATION GUIDE
When Recognition Matters EXAM PREPARATION GUIDE PECB Certified ISO 22000 Lead Auditor www.pecb.com The objective of the Certified ISO 22000 Lead Auditor examination is to ensure that the candidate has
More informationLecture 5: Requirements Specifications
Lecture 5: Requirements Specifications Why we need to write specifications Purpose and audience Choosing an appropriate size and formality Desiderata for Specifications Properties of good specifications
More informationInformation Mapping. Designing course notes that students learn from. Jackie Hoffman NMIT 2009
Information Mapping Designing course notes that students learn from Jackie Hoffman NMIT 2009 Think about the purpose of the document What is the document s purpose? What is the medium (paper/web/powerpoint)
More informationChapter 4 Requirements Elicitation
Object-Oriented Software Engineering Using UML, Patterns, and Java Chapter 4 Requirements Elicitation Outline Today: Motivation: Software Lifecycle Requirements elicitation challenges Problem statement
More informationLevel 5 Diploma in Computing
Level 5 Diploma in Computing 1 www.lsib.co.uk Objective of the qualification: It should available to everyone who is capable of reaching the required standards It should be free from any barriers that
More informationRequirements Elicitation
Requirements Elicitation Introduction into Software Engineering Lecture 4 25. April 2007 Bernd Bruegge Applied Software Engineering Technische Universitaet Muenchen 1 Outline Motivation: Software Lifecycle
More informationIt is written in plain language: no jargon, nor formality. Information gets across faster when it s written in words that our users actually use.
Web Style Guide A style guide for use for writing on Tufts Library Websites and LibGuides. Contents: 1. Web style guides for online content 2. LibGuides 2-specific style guide 3. Tisch s website-specific
More informationUniversal Design Principles Checklist
Universal Design Principles Checklist February 2012 The concept of Universal Design was developed by people who worked on designing equipment and environments for people with a disability. They saw that
More informationKM COLUMN. How to evaluate a content management system. Ask yourself: what are your business goals and needs? JANUARY What this article isn t
KM COLUMN JANUARY 2002 How to evaluate a content management system Selecting and implementing a content management system (CMS) will be one of the largest IT projects tackled by many organisations. With
More informationSoftware Requirements Specification (SRS) Software Requirements Specification for <Name of Project>
Software Requirements Specification (SRS) Software Requirements Specification for Version Release Responsible Party Major Changes Date 0.1 Initial Document Release for
More informationUsability Evaluation as a Component of the OPEN Development Framework
Usability Evaluation as a Component of the OPEN Development Framework John Eklund Access Testing Centre and The University of Sydney 112 Alexander Street, Crows Nest NSW 2065 Australia johne@testingcentre.com
More informationPROJ 302. Project Report, Poster and Digest Guidelines. for Industrial Engineering Students. Summer 2017
PROJ 302 Project Report, Poster and Digest Guidelines for Industrial Engineering Students Summer 2017 General Notes - Read this document carefully before writing your internship report, poster, and digest.
More informationEXAM PREPARATION GUIDE
When Recognition Matters EXAM PREPARATION GUIDE PECB Certified ISO/IEC 20000 Lead Auditor www.pecb.com The objective of the Certified ISO/IEC 20000 Lead Auditor examination is to ensure that the candidate
More informationTable of contents. TOOLKIT for Making Written Material Clear and Effective
TOOLKIT for Making Written Material Clear and Effective Table of contents U.S. Department of Health & Human Services Centers for Medicare & Medicaid Services Table of contents Overview of the Toolkit The
More informationConcepts of Usability. Usability Testing. Usability concept ISO/IS What is context? What is context? What is usability? How to measure it?
Concepts of Usability Usability Testing What is usability? How to measure it? Fang Chen ISO/IS 9241 Usability concept The extent to which a product can be used by specified users to achieve specified goals
More informationCourse 319 Supplementary Materials. Effective User Manuals
Course 319 Course 319 Supplementary Materials www.learningtree.com 1 Course 319 Originally published in the April, 2000 issue of the Smart Access newsletter from Pinnacle Publishing (www.pinpub.com). Peter
More informationThe ITIL v.3. Foundation Examination
The ITIL v.3. Foundation Examination ITIL v. 3 Foundation Examination: Sample Paper 4, version 3.0 Multiple Choice Instructions 1. All 40 questions should be attempted. 2. There are no trick questions.
More informationICAEW REPRESENTATION 68/16
ICAEW REPRESENTATION 68/16 Improving the Structure of the Code of Ethics for Professional Accountants - Phase 1 ICAEW welcomes the opportunity to comment on the Improving the Structure of the Code of Ethics
More informationModern Systems Analysis and Design Seventh Edition
Modern Systems Analysis and Design Seventh Edition Jeffrey A. Hoffer Joey F. George Joseph S. Valacich Designing Interfaces and Dialogues Learning Objectives ü Explain the process of designing interfaces
More informationEXAM PREPARATION GUIDE
EXAM PREPARATION GUIDE PECB Certified ISO 21500 Lead Project Manager The objective of the PECB Certified ISO 21500 Lead Project Manager examination is to ensure that the candidate has the knowledge and
More informationQuality Assurance & Standards
Quality Assurance & Standards PSD3 Nov 2013 1 Overview Quality Assurance (QA)» checking what we are producing QA standards» checking the checking 2 Further Reading Sommerville» 9 th Edition, Chap. 24»
More informationSoftware Requirements Specification. <Project> for. Version 1.0 approved. Prepared by <author(s)> <Organization> <Date created>
Software Requirements Specification for Version 1.0 approved Prepared by Software Requirements Specification for Page 2 Table of Contents Revision
More informationOUTLINE. Advanced Technical Communication & Writing Skills. What is technical communication? Technical communication skills
Advanced Technical Communication & Writing Skills What is technical communication? Technical communication skills Principles of technical writing Technical writing is interpreting Planning is crucial Technical
More informationThe Business Case for Web Accessibility. Facilitator s Notes for this Module
The Business Case for Web Accessibility About this Module: Goal: In this module we will review how an accessible website can benefit your business or organization Format: PowerPoint presentation Time:
More informationPOSITION DETAILS. Content Analyst/Developer
HR191 JOB DESCRIPTION NOTES Forms must be downloaded from the UCT website: http://www.uct.ac.za/depts/sapweb/forms/forms.htm This form serves as a template for the writing of job descriptions. A copy of
More informationComments submitted by IGTF-J (Internet Governance Task Force of Japan) *
submitted by IGTF-J (Internet Governance Task Force of Japan) * http:www.igtf.jp Do you have any comments on the process of determining the issues and their presentation by the WGIG? Yes. The purpose of
More informationTechnical Writing. Professional Communications
Technical Writing Professional Communications Overview Plan the document Write a draft Have someone review the draft Improve the document based on the review Plan, conduct, and evaluate a usability test
More informationRequirements Engineering. Establishing what the customer requires from a software system. Requirements Engineering. What is a Requirement?
Engineering Establishing what the customer requires from a software system Ian Sommerville 1995/2000 (Modified by Spiros Mancoridis 1999) Software Engineering, 6th edition. Chapters 5 and 6 Slide 1 Engineering
More informationOverview of the course. User-Centred Design. Group. Practical issue. Writting the report. Project work. Fang Chen
Overview of the course User-Centred Design Fang Chen 6 lectures, 3 hr each. L 1: April 6, 9-12, user-centered design concept L2: April 14, 9-12, usability concept L3. user-centered requirement study L4.
More informationEXAM PREPARATION GUIDE
When Recognition Matters EXAM PREPARATION GUIDE PECB Certified ISO 9001 Lead Auditor www.pecb.com The objective of the PECB Certified ISO 9001 Lead Auditor examination is to ensure that the candidate possesses
More informationSE351a: Software Project & Process Management. 11 Oct., 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa
SE351a: Software Project & Process Management W4.1: Requirements Engineering 11 Oct., 2005 SE351a, ECE UWO, (c) Hamada Ghenniwa SE351 Roadmap Introduction to Software Project Management Project Management
More informationADMIN 3.4. V e r s i o n 4. Paul Daly CEO RISSB
ADMIN 3.4 V e r s i o n 4 Paul Daly CEO RISSB 01 November 2017 DOCUMENT CONTROL Identification Document Title Number Version Date Document ADMIN 3.4 1 23/11/2007 Document ADMIN 3.4 2 04/02/2010 Document
More informationBMIT Capstone Course Business Plan Rubric. Name of Social Enterprise: Type of Business: Owners Name: Evaluator(s):
BMIT Capstone Course Business Plan Rubric Name of Social Enterprise: Type of Business: Owners Name: Evaluator(s): Business Plan Rubric 0 = no evidence 1 = little evidence or major flaws 2 = adequate minimum
More informationStandard Glossary of Terms used in Software Testing. Version 3.2. Foundation Extension - Usability Terms
Standard Glossary of Terms used in Software Testing Version 3.2 Foundation Extension - Usability Terms International Software Testing Qualifications Board Copyright Notice This document may be copied in
More informationAccessibility Tips for Teams
is everyone s responsibility Great products are clever concepts, realised for all. We all have a role to play Designer QA Testers 20% of users have a disability. Include simple tests for broad access.
More informationConformity Assessment Schemes and Interoperability Testing (1) Keith Mainwaring ITU Telecommunication Standardization Bureau (TSB) Consultant
Conformity Assessment Schemes and Interoperability Testing (1) Keith Mainwaring ITU Standardization Bureau (TSB) Consultant Moscow, 9-11 november 2011 Contents The benefits of conformity assessment Conformity
More informationPowerPoint. presentation
PowerPoint presentation Unit 301 (B&A 40): Communicate in a business environment Handout 3: Written communications 2014 City and Guilds of London Institute. All rights reserved. 1 of 11 Uses of different
More informationEXAM PREPARATION GUIDE
When Recognition Matters EXAM PREPARATION GUIDE PECB Certified ISO 14001 Lead Implementer www.pecb.com The objective of the PECB Certified ISO 14001 Lead Implementer examination is to ensure that the candidate
More informationQuality Software Requirements By J. Chris Gibson
Quality Software Requirements By J. Chris Gibson The information contained within this document has been gathered from a variety of sources and practices observed by the development team at Protera Software
More informationUsing the Common Industry Format to Document the Context of Use
Human-Computer Interaction. Human-Centred Design Approaches, Methods, Tools, and Environments - 15th International Conference, HCI International 2013, Las Vegas, NV, USA, July 21-26, 2013, Proceedings,
More informationThe Danger of Invalid Database Objects
The Danger of Invalid Database Objects Why they are dangerous. An awareness Paper for IT-Managers. http://www.it-checklists.com Copyright 2005-2006 Mercury Consulting Ltd. http://www.mercury-consulting-ltd.com
More informationUser Interface Design
Objective User Interface Design MIT, Walailak University by Dr.Wichian Chutimaskul Understand the principles of user interface (UI) design Understand the process of user interface design To design the
More informationRequirements. Requirements. Types of Requirement. What Is a Requirement?
Beatrice Åkerblom beatrice@dsv.su.se Everything else in software development depends on the requirements. If you cannot get stable requirements you cannot get a predictable plan... What Is a Requirement?!
More informationRecommended Practice for Software Requirements Specifications (IEEE)
Recommended Practice for Software Requirements Specifications (IEEE) Author: John Doe Revision: 29/Dec/11 Abstract: The content and qualities of a good software requirements specification (SRS) are described
More informationRequirements Validation and Negotiation
REQUIREMENTS ENGINEERING LECTURE 2015/2016 Eddy Groen Requirements Validation and Negotiation AGENDA Fundamentals of Requirements Validation Fundamentals of Requirements Negotiation Quality Aspects of
More informationStyle guide for Department for Education research reports and briefs
Style guide for Department for Education research reports and briefs November 2013 Contents Introduction 3 Why accessibility matters 3 What are the standards? 3 Guidance on writing research reports and
More informationSection 6 HCI & the Web 02/01/2013 1
Section 6 HCI & the Web 02/01/2013 1 Web Site Planning Main questions to address when planning a web site: What do I want the site to accomplish, sell, or promote? Who are my users and what do they want
More informationTEL2813/IS2820 Security Management
TEL2813/IS2820 Security Management Security Management Models And Practices Lecture 6 Jan 27, 2005 Introduction To create or maintain a secure environment 1. Design working security plan 2. Implement management
More information<PROJECT NAME> IMPLEMENTATION PLAN
IMPLEMENTATION PLAN Version VERSION HISTORY [Provide information on how the development and distribution of the Project Implementation Plan was controlled and tracked.
More informationThe GDPR Are you ready?
The GDPR Are you ready? kpmg.ie The GDPR - Overview The General Data Protection Regulation (GDPR) (Regulation (EU) 2016/679) will come into force from 25th May 2018, replacing the existing data protection
More informationEXAM PREPARATION GUIDE
EXAM PREPARATION GUIDE PECB Certified ISO 50001 Lead Auditor The objective of the PECB Certified ISO 50001 Lead Auditor examination is to ensure that the candidate has the knowledge and skills to plan
More informationDetailed Data Modelling. Detailed Data Modelling. Detailed Data Modelling. Identifying Attributes. Attributes
IMS1002 /CSE1205 Systems Analysis and Design Detailed Data Modelling The objective of detailed data modelling is to develop a detailed data structure that: Detailed Data Modelling: Attribute Collection
More informationAustralian/New Zealand Standard
AS/NZS ISO/IEC 15910:2004 ISO/IEC 15910:1999 AS/NZS ISO/IEC 15910 Australian/New Zealand Standard Information technology Software user documentation process AS/NZS ISO/IEC 15910:2004 This Joint Australian/New
More informationImplementation of INFCIRC 901: Promoting Certification, Quality Management and Sustainability of Nuclear Security Training
Implementation of INFCIRC 901: Promoting Certification, Quality Management and Sustainability of Nuclear Security Training Rhonda Evans Head, WINS Academy Presentation to the IAEA International Conference
More informationFederated authentication for e-infrastructures
Federated authentication for e-infrastructures 5 September 2014 Federated Authentication for E-Infrastructures Jisc Published under the CC BY 4.0 licence creativecommons.org/licenses/by/4.0/ Contents Introduction
More information[Product] MTM Program Product Software Requirements Specification
[Product] Software Requirements Specification [Version Number] [Version Date] [Product] MTM Program Product Software Requirements Specification [SRS Version Number] [SRS Version Date] [Applying MTM SRS
More informationAuditing Bring Your Own Devices (BYOD) Risks. Shannon Buckley
Auditing Bring Your Own Devices (BYOD) Risks Shannon Buckley Agenda 1. Understanding the trend towards BYOD. 2. Weighing up the cost benefit vs. the risks. 3. Identifying and mitigating the risks. 4. Tips
More informationMathematics and Computing: Level 2 M253 Team working in distributed environments
Mathematics and Computing: Level 2 M253 Team working in distributed environments SR M253 Resource Sheet Specifying requirements 1 Overview Having spent some time identifying the context and scope of our
More informationGT48232/ME4182 First Progress Report & Presentation (Fall 2016)
GT48232/ME4182 First Progress Report & Presentation (Fall 2016) The report clearly, concisely, and logically documents work to date including the process as well as the results. It is not a chronology
More informationIMS1501: Unit framework
IMS 1501 Studio 1: Information Systems Foundations 1 Seminar 12: Implementation, Review, Maintenance Introduction to HTML Authoring Semester 1, 2005 Seminar 12.1 - Sem1, 2005 Lecturer: Sue Foster/Suellen
More informationLesson Guides PRE-INTERMEDIATE
Lesson Guides PRE-INTERMEDIATE British Council 2018 The British Council is the United Kingdom s international organisation for cultural relations and educational opportunities. PRE-INTERMEDIATE LESSON
More informationHuman Computer Interaction Lecture 16. User Support
Human Computer Interaction Lecture 16 User Support User Support Main Types of user support quick reference, task specific help, full explanation, tutorial Issues different types of support at different
More informationCreating Accessible Documents
Creating Accessible Documents How-To Guide for MS Office 2016 This guide is intended users of Microsoft Office 2016 (PC and Mac) to help them make Word documents, PowerPoint presentations, and PDF files
More information3Lesson 3: Web Project Management Fundamentals Objectives
3Lesson 3: Web Project Management Fundamentals Objectives By the end of this lesson, you will be able to: 1.1.11: Determine site project implementation factors (includes stakeholder input, time frame,
More informationEXAM PREPARATION GUIDE
When Recognition Matters EXAM PREPARATION GUIDE PECB Certified ISO 37001 Lead Auditor www.pecb.com The objective of the Certified ISO 37001 Lead Auditor examination is to ensure that the candidate possesses
More informationNatural Language Specification
REQUIREMENTS ENGINEERING LECTURE 2017/2018 Dr. Jörg Dörr Natural Language Specification Most Requirements are Described in Natural Language Free Text (Prose) In Word In Excel (Tabular) In RM-Tools In Sys-ML
More informationTelecommunications Equipment Certification Scheme FEBRUARY 2017
Telecommunications Equipment Certification Scheme FEBRUARY 2017 Canberra Red Building Benjamin Offices Chan Street Belconnen ACT PO Box 78 Belconnen ACT 2616 T +61 2 6219 5555 F +61 2 6219 5353 Melbourne
More informationFocus. Writing for the Web. Topics. Types of Web page. Print vs Web? Some Key Differences
#pelc11 Focus Writing for the Web Words & Writing Page Layout Emphasis & Links Design Site Structure Matt Lingard, LSE Centre for Learning Technology Topics General Web Writing Guidelines Writing for Blogs
More informationATTACHMENT 2, EXHIBIT 3 Deliverable Expectation Document Template For [Deliverable Title]
ATTACHMENT 2, EXHIBIT 3 Expectation Document Template For [ Title] [This template provides a sample of the required contents of a Expectation Document (DED). Work plans that support the activity summary
More informationS1000D International Specification for Technical Publications
S1000D International Specification for Technical Publications What is S1000D? S1000D is an international specification for the production of technical publications for any civil or military project. While
More informationGROUP FINAL REPORT GUIDELINES
GROUP FINAL REPORT GUIDELINES Overview The final report summarizes and documents your group's work and final results. Reuse as much of your past reports as possible. As shown in Table 1, much of the final
More informationNOT PROTECTIVELY MARKED JOB DESCRIPTION
JOB DESCRIPTION APPENDIX C Before completing this form, please read the BTP Guide to writing job descriptions for Police Staff roles Appendix B to the SOP. A. POST DETAILS: Job Title: Database Administrator
More informationSymantec Data Center Transformation
Symantec Data Center Transformation A holistic framework for IT evolution As enterprises become increasingly dependent on information technology, the complexity, cost, and performance of IT environments
More informationProposition 89 Using Plain English
Proposition 89 Using Plain English In a Word Many people write too much, bureaucratically, and obscurely. Using plain English will save time in writing, make writing far easier, and improve understanding.
More informationFree ITIL Foundation Exam Paper 40 Questions 60 Minutes Allowed. Minimum of 26/40 to Pass. With the Compliments of www.itservicesuccess.com Good Luck!! GIVE YOURSELF THE UNFAIR ADVANTAGE! MULTIPLE CHOICE
More informationISO/IEC/ IEEE Systems and software engineering Content of life-cycle information items (documentation)
This is a preview - click here to buy the full publication INTERNATIONAL STANDARD ISO/IEC/ IEEE 15289 Second edition 2015-05-15 Systems and software engineering Content of life-cycle information items
More informationDealer Reviews Best Practice Guide
Dealer Reviews Best Practice Guide What do I do if I get a negative review? Well, the first thing is, don t panic. Negative reviews aren t the end of the world, they actually help build trust and credibility
More informationSoftware Requirements Specification. <Project> for. Version 1.0 approved. Prepared by <author> <organization> <date created>
Software Requirements Specification for Version 1.0 approved Prepared by Copyright 2002 by Karl E. Wiegers. Permission is granted to use, modify, and distribute
More informationGuide for Researchers: Online Human Ethics Application Form
Ethics & Integrity Research Office HUMAN RESEARCH ETHICS ONLINE APPLICATION October 2016/V1.03 Guide for Researchers: Online Human Ethics Application Form ENQUIRIES Senior Human Ethics Officer University
More informationAccessible Word Documents
Accessible Word Documents Using MS Word for Windows Why make documents accessible? Making accessible documents ensures that they usable by the widest range of users, but also ensures your document is easier
More informationSIMPLIFi Compliance Software User Manual
SIMPLIFi Compliance Software User Manual Version 1.7 2013 Simplifi-Solutions Ltd, Environmental Center, Unit B5, The Gordon Manley Building, Lancaster University, LA1 4WA Telephone: 01524 510431 Email:
More informationSecurity Management Models And Practices Feb 5, 2008
TEL2813/IS2820 Security Management Security Management Models And Practices Feb 5, 2008 Objectives Overview basic standards and best practices Overview of ISO 17799 Overview of NIST SP documents related
More informationFederal Plain Language Guidelines
Federal Plain Language Guidelines March 2011 Revision 1, May 2011 Table of Contents Introduction... i Revision 1 Changes... ii Table of Contents... iii I. Think about your audience... 1 a. Identify and
More informationDetailed Data Modelling: Attribute Collection and Normalisation of Data
Detailed Data Modelling IMS1002 /CSE1205 Systems Analysis and Design Detailed Data Modelling: Attribute Collection and Normalisation of Data The objective of detailed data modelling is to develop a detailed
More informationAdditional Support and Disability Advice Centre
Additional Support and Disability Advice Centre GUIDELINES TO PRODUCING ACCESSIBLE WORD DOCUMENTS 1 INTRODUCTION As well as allowing adaptation of font, background colour and layout to suit personal preferences,
More informationAccreditation Process. Trusted Digital Identity Framework February 2018, version 1.0
Accreditation Process Trusted Digital Identity Framework February 2018, version 1.0 Digital Transformation Agency This work is copyright. Apart from any use as permitted under the Copyright Act 1968 and
More informationCase 1:13-cv TSC Document Filed 02/05/16 Page 1 of 8 EXHIBIT 14
Case 1:13-cv-01215-TSC Document 164-22 Filed 02/05/16 Page 1 of 8 EXHIBIT 14 Case 1:13-cv-01215-TSC Document 164-22 Filed 02/05/16 Page 2 of 8 U.S. Department of Justice Civil Rights Division Disability
More informationGuidance to support the DWP 2 Tier Complaints Resolution Process
Guidance to support the DWP 2 Tier Complaints Resolution Process Purpose This guidance is for all DWP staff that are following the 2 tier complaints resolution process, except those working in a Contact
More information