|
[DoD 881A]
|
US Department of Defence (1975), Standard 881A, Work Breakdown Structures for Defence Material Items
Keywords: WBS, work breakdown structure
|
|
[DoDAF]
|
US Department of Defense (2010), The DoDAF Architecture Framework Version 2.02, [Online], Available: http://cio-nii.defense.gov/sites/dodaf20/ [14 Sep 2011]
See also: [MoDAF], [TRAK], [IEC 42010]
Keywords: architecture description, architecture views
|
|
[AGPS]
|
Australian Government Publishing Service, Style Manual for Authors, Editors and Printers, AGPS, Canberra
Keywords: style guide, document development
|
[AS 4817] |
Standards Australia (2006), AS 4817 Project performance measurement using Earned Value
Keywords: earned value management, cost variance, schedule variance
CA Video: Earned Value Management
See also: [PMI EVM], [EIA 748], [DoD 7000.2], [Fleming 05]
Abstract (from section 1.2 Application): This Standard can be applied to the measurement and reporting of the cost and schedule performance of projects and programs. It can be applied to any situation where a specified deliverable (product, service, output, result) is to be produced by a specified date and with finite resources.
|
|
[August 91]
|
August, Judy (1991), Joint Application Design - The Group Session Approach to System Design, Yourdon Press
|
|
[Barnes 97]
|
Barnes, John (1997), High Integrity Ada - The SPARK Approach, Addison-Wesley
|
[Boar 84] |
Boar, Bernard (1984), Application Prototyping, New Jersey: John Wiley and Sons, Inc
Keywords: prototyping, software requirements, mock-up, model
CA Resources: Prototype
|
[Boehm 81] |
Boehm, Barry (1981), Software Engineering Economics, New Jersey: Prentice Hall
Keywords: lines of code, LOC, KLOC, estimation, job costing, COCOMO
Abstract: This text is a classic in the field of software estimation. It provides a practical guide to determining software costs, applying the fundamental concepts of microeconomics to software engineering, and utilizing economic analysis in software engineering decision making.
|
[Buckle 87] |
Buckle Jk. (1987), Software Configuration Management, London: Macmillan Education Ltd
Keywords: Software Configuration Management, change control
CA Resources: Configuration Management
|
|
[Caliber]
|
Micro Focus, Caliber Software Requirements Definition and Management, [Online], Available: http://www.microfocus.com/products/caliber/ [15 Sep 2011]
Keywords: requirements management, traceability analysis
|
|
[Collins 96]
|
Collins, J. and Porras, J. (1996) Building Your Company's Vision, Harvard Business Review, vol. 74 no. 5, September-October 1996, pp. 65-77
Keywords: vision statement, goals and objectives, core ideology, envisioned future, strategic planning, mission and vision
CA Resources: Goal, Objective
|
|
[DO 178B]
|
Radio Technical Commission for Aeronautics (RTCA) (1992), DO 178B - Software Considerations in Airborne Systems and Equipment Certification
Keywords: functional safety, reliability, availability, maintainability, RAMS
See also: [IEC 61508], [DoD 882D], [EN 50126]
Abstract: The USA's Federal Aviation Administration (FAA) applies DO-178B as guidance to determine if software is safe for deployment in an airborne environment. FAA's Advisory Circular AC20-115B established DO-178B as the accepted means of certifying all new aviation software.
|
|
[DoD 7000.2]
|
US Department of Defence (1977), Instruction 7000.2. Performance Measurement for Selected Acquisitions
Keywords: earned value, cost schedule control, cost variance, schedule variance
CA Video: Earned Value Management
See also: [EIA 748], [AS 4817], [PMI EVM], [Fleming 05]
|
|
[DoD 882D]
|
US Department of Defense (2000), MIL-STD-882D Department of Defense Standard Practice For System Safety, [Online],
Available: http://www.everyspec.com/MIL-STD/MIL-STD+(0800+-+0899)/MIL_STD_882D_934/ [28 Sep 2011]
CA Resource: Functional Safety Management
See also: [EN 50126], [IEC 61508]
|
|
[Doors]
|
IBM Rational, Rational Doors: A requirements management tool for systems and advanced IT applications
, [Online], Available: http://www-01.ibm.com/software/awdtools/doors/ [15 Sep 2011]
Keywords: requirements management, traceability analysis
|
[EIA 748] |
Electronic Industries Alliance (EIA) (2007), ANSI/EIA-748-B Earned Value Management Systems
Keywords: earned value management, cost variance, schedule variance, cost schedule control
CA Video: Earned Value Management
See also: [PMI EVM], [AS 4817], [DoD 7000.2], [Fleming 05]
|
[EN 50126] |
European Committee for Electrotechnical Standardization (CENELEC) (1999), EN 50126 Railway applications - The specification and demonstration of Reliability, Availability, Maintainability and Safety (RAMS)
Keywords: functional safety, reliability, availability, maintainability, RAMS
See also: [IEC 61508], [DoD 882D]
|
[EN 50128] |
European Committee for Electrotechnical Standardization (CENELEC) (2001), EN 50128 Railway applications - Communications, signalling and processing systems - Software for railway control and protection systems
Keywords: functional safety, reliability, availability, maintainability, RAMS, software safety
See also: [IEC 61508], [DoD 882D]
|
[EN 50129] |
European Committee for Electrotechnical Standardization (CENELEC) (2003), EN 50129 Railway applications - Communications, signalling and processing systems - Safety related electronic systems for signalling
Keywords: functional safety, reliability, availability, maintainability, RAMS, software safety
See also: [IEC 61508], [DoD 882D]
|
[Fleming 05] |
Fleming Q.W. and Koppelman, J.M. (2005), Earned Value Project Management, Pennsylvania: Project Management Institute Inc
Keywords: earned value management, cost variance, schedule variance, cost schedule control
CA Video: Earned Value Management
See also: [PMI EVM], [AS 4817], [DoD 7000.2], [EIA 748]
|
[Garlan 96] |
Garlan D., Shaw, M (1996), Software Architecture: Perspectives on an Emerging Discipline, New Jersey: Prentice-Hall Inc
Keywords: Software Architecture, Computer Architecture
CA Resource: Standard for System Architecture Specifications
|
|
[IEC 9126]
|
ISO/IEC (2001), ISO/IEC 9126 Software engineering - Product quality, Geneva, Switzerland: International Standards Organisation
Abstract: This standard provides quantitative measures of software quality. It is divided into four parts:
1. Quality model
2. External metrics
3. Internal metrics
4. Quality in use metrics.
|
|
[IEC 61508]
|
IEC (2011), ISO/IEC 61508 Functional safety of electrical/electronic/programmable electronic safety-related systems, [Online], http://www.iec.ch/functionalsafety/ [22 Sep 2011]
See also: [DoD 882D], [EN 50126]
Keywords: functional safety, SIL, Safety Integrity Level, system safety
CA Resource: The 10 Minute Guide to IEC 61508
|
|
[IEC 42010]
|
ISO, IEC, IEEE (2011), ISO/IEC 42010 Systems and software engineering — Architecture description, [Online], Draft available: http://www.iso-architecture.org/ieee-1471/docs/ISO-IEC-IEEE-latest-draft-42010.pdf [14 Sep 2011]
See also: [DoDAF], [MoDAF], [TRAK]
Keywords: architecture description, architecture views
|
[IEEE 730] |
Software Engineering Standards Committee of the IEEE Computer Society (2002), IEEE 730 Standard for Software Quality Assurance Plans, Piscataway, NJ, USA: The Institute of Electrical and Electronics Engineers, Inc.
Abstract: IEEE 730 is an industry standard for software quality planning, used by thousands of projects all over the world.
CA Resources: Does Quality Matter?
Quality Management System Framework
Architecting a Quality Management System
|
[IEEE 828] |
Software Engineering Standards Committee of the IEEE Computer Society (2005), IEEE 828 - IEEE Standard for Software Configuration Management Plans, Piscataway, NJ, USA: The Institute of Electrical and Electronics Engineers, Inc.
CA Services: Configuration Management
Abstract: IEEE 828 describes the format and content of a Software Configuration Management (SCM) Plan.
It applies to the entire life cycle of critical software; e.g., where failure would
impact safety or cause large financial or social losses. It also applies to noncritical software and to software already
developed.
The Plan documents what SCM activities are to be done, how they are to be done, who is responsible for perfroming various
activities, when they are to happen, and what resources are required.
|
[IEEE 829] |
Software Engineering Standards Committee of the IEEE Computer Society (1998), IEEE 829 - IEEE Standard for Software Test Documentation, Piscataway, NJ, USA: The Institute of Electrical and Electronics Engineers, Inc.
CA Services: Testing
Abstract: IEEE 829 is the world's most used software testing standard. It describes eight document types that can form the basis of any test program. For test planning: the test plan; for test specification: the test design specification, test case specification, test procedure specification; for test reporting: the test item transmittal report, test log, test incident report, test summary report.
|
[IEEE 830] |
Software Engineering Standards Committee of the IEEE Computer Society (1998), IEEE 830 - IEEE Recommended Practice for Software Requirements Specifications, Piscataway, NJ, USA: The Institute of Electrical and Electronics Engineers, Inc.
Abstract: Widely applied across many industry sectors this standard provides several formats for software requirements specifications. It also covers the qualities of a good SRS.
|
[IEEE 1012] |
Software Engineering Standards Committee of the IEEE Computer Society (2004), IEEE 1012 - IEEE Standard for Software Verification and Validation, Piscataway, NJ, USA: The Institute of Electrical and Electronics Engineers, Inc.
Keywords: V&V, verification, validation
Abstract: This is an industry standard for software verification and validation. It provides a comprehensive coverage of V&V activities organised by development life cycle phase. The standard applies to software being developed, maintained, or reused. Software V&V processes covered include analysis, evaluation, review, inspection, assessment, and testing of software products.
CA Resources:
Quality Management System Framework
Architecting a Quality Management System
|
[IEEE 1028] |
Software Engineering Standards Committee of the IEEE Computer Society (2008), IEEE 1028 - IEEE Standard for Software Reviews and Audits, Piscataway, NJ, USA: The Institute of Electrical and Electronics Engineers, Inc.
Abstract: This standard decribes five types of software reviews and audits, together with procedures required for the execution of each type. Review processes covered are: management reviews, technical reviews, inspections, walkthroughs and audits.
Keywords: audit, review, inspection, walkthrough |
[ISO 9000] |
International Standards Organisation (2000), ISO 9000:2000 Quality management systems - Fundamentals and vocabular, Geneva, Switzerland: International Standards Organisation
CA Resources: Does Quality Matter?
Quality Management System Framework
Architecting a Quality Management System
|
[ISO 9001] |
International Standards Organisation (2008), ISO 9001:2008 Quality management systems — Requirements, Geneva, Switzerland: International Standards Organisation
CA Resources: Does Quality Matter?
Quality Management System Framework
Architecting a Quality Management System
|
[ISO 9241-11] |
International Standards Organisation (1998), ISO 9241-11 Ergonomic requirements for office work with visual display terminals (VDTs) - Part 11: Guidance on usability, Geneva, Switzerland: International Standards Organisation
Abstract (from the standard): ISO 9241-11 defines usability and explains how to identify the information which is necessary to take into account when specifying or evaluating usability of a visual display terminal in terms of measures of user performance and satisfaction. Guidance is given on how to describe the context of use of the product (hardware, software or service) and the relevant measures of usability in an explicit way. The guidance is given in the form of general principles and techniques, rather than in the form of requirements to use specific methods.
Keywords: usability, learnability
CA Resource: learnability, Software Requirements Specification
|
|
[Kruchten 95]
|
Kruchten P. (1995), Architectural Blueprints—The “4+1” View Model of Software Architecture, [Online], Available: http://www.cs.ubc.ca/~gregor/teaching/papers/4+1view-architecture.pdf [21 Sep 2011]
See also: [DoDAF], [MoDAF], [TRAK], [IEC 42010]
Keywords: architecture description, architecture views
|
[McConnell 93] |
McConnell, Steve (1993), Code Complete: A Practical Handbook of Software Construction, Redmond: Microsoft Press
Keywords: software development, coding, quality control
CA Video: An ISO 9001 Quality Management System Architecture
|
|
[Mills 90]
|
Mills, Harlan and Cobb, Richard (1990), Engineering Software Under Statistical Quality Control, IEEE Software, vol. 7 no. 6, November 1990, pp. 45-54
Keywords: cleanroom development, quality control
CA Video: An ISO 9001 Quality Management System Architecture
|
|
[MoD 00-56]
|
UK Ministry of Defence (2004), MoD (UK) Interim Defence Standard 00-56 Safety Management Requirements for Defence Systems, [Online], Available: http://segoldmine.ppi-int.com/content/standard-def-stan-00-56-safety-management-requirements-defence-systems [29 Sep 2011]
Keywords: functional safety, reliability, availability, maintainability, RAMS, software safety
See also: [IEC 61508], [DoD 882D], [EN 50126]
|
|
[MoDAF]
|
UK Ministry of Defence (2010), The MOD Architecture Framework, [Online], Available: http://www.modaf.org.uk/ [14 Sep 2011]
See also: [DoDAF], [TRAK], [IEC 42010]
Keywords: architecture description, architecture views
|
[Myers 79] |
Myers, Glenford (1979), The Art of Software Testing, New Jersey: John Wiley and Sons, Inc
Keywords: software testing
CA Resources: Software Testing |
[Pinault 00] |
Pinault L. (2000), Consulting Demons: Inside the Unscrupulous World of Global Corporate Consulting, New York: HarperCollins Publishers Inc
Keyword: consulting
|
[PMI EVM] |
Project Management Institute (2005), Practice Standard for Earned Value Management, Pennsylvania: Project Management Institute Inc
Keywords: earned value management, cost variance, schedule variance, cost schedule control
CA Video: Earned Value Management
See also: [EIA 748], [AS 4817], [DoD 7000.2], [Fleming 05]
Abstract from the Preface: The Practice Standard Earned Value Management (EVM) has been developed as a supplement to a Guide to the Project Management Body of Knowledge (PMBOK® Guide). The Practice Standard for EVM is designed to provide readers who are familiar with the PMBOK® Guide with a fundamental understanding of the principles
of EVM and its role in facilitating effective project management.
|
[PMI WBS] |
Project Management Institute (2001), Practice Standard for Work Breakdown Structures, Pennsylvania: Project Management Institute Inc
CA Video: The WBS Development Process
CA Service: Project Management
|
|
[ReqPro]
|
IBM Rational, Rational RequisitePro : A requirements management tool
, [Online], Available: http://www-01.ibm.com/software/awdtools/reqpro/ [15 Sep 2011]
Keywords: requirements management, traceability analysis
|
[Tiwana 99] |
Tiwana, Amrit (1999), The Knowledge Management Toolkit: Orchestrating IT, Strategy, and Knowledge Platforms , Pearson Education
Keywords: knowledge management
CA Resources: Knowledge Management
|
|
[TRAK]
|
UK Department of Transport (2010), TRAK Enterprise Architecture Framework, [Online], Available: http://trak.sourceforge.net/ [14 Sep 2011]
See also: [DoDAF], [MoDAF], [IEC 42010]
Keywords: architecture description, architecture views
|
|
[Wise 11]
|
Jeff Wise Blog (10 Nov, 2011), Forging a Soul of Iron, [Online], Available: http://jeffwise.net/2011/11/10/forging-a-soul-of-iron/ [23 Feb 2012]
Keyword: goal |
|
[Yellow Book]
|
UK Railtrack (2000), Engineering Safety Management, [Online], Available: http://www.yellowbook-rail.org.uk/ [29 Sep 2011], London: Railtrack PLC
Keywords: functional safety, reliability, availability, maintainability, RAMS, Yellow Book
CA Resource: Functional Safety Management, Hazard
See also: [IEC 61508], [DoD 882D], [EN 50126]
Abstract: Engineering Safety Management (or the Yellow Book as it is more commonly known) is a handbook designed to help people who are involved in changes to the railway (such as new trains and signalling). The objective of the Yellow Book is to improve the understanding of the safety management processes in railway projects.
|
| |
|
| |
|
|
|
