The Payroll Unit in Juba used two software systems namely the
‘SunSystem’ and the ‘Progen Payroll Unit‘ (“Payroll System Software”) to which
the Applicant had login access in his position as a Finance Assistant.
6. (...) Carol Joseph, prior to placing a
“W” in the Payroll System Software; and
b. that he only placed a “W” in the Payroll System Software
in April 2010, with the intention to recover the sums from
his May and June 2010 payroll.
93. (...) The Applicant admitted placing a “W” in the Payroll System Software to
delay recovery, but only in April 2010.
Language:English
Score: 872482.7
-
www.un.org/en/internalj...dt/judgments/undt-2014-052.pdf
Data Source: oaj
He asserts that because of cracked software, pop-ups occurred over which he had no
control. (...) Because of the lengthy waiting period for receiving legal software for the operational
needs, most OCHA field offices use cracked software to be able to perform their duties. (...) The reason for a website with cracked software is to direct a user to specific pages
because that is how income is derived from the use of cracked software.
Language:English
Score: 850652
-
www.un.org/en/internalj...dt/judgments/undt-2018-122.pdf
Data Source: oaj
ITU Software Copyright Guidelines
International Telecommunication Union
ITU Software Copyright Guidelines
(7/12/2011)
applicable as from 13 April 2012
i
ITU Software Copyright Guidelines
Summary
The ITU Software Copyright Guidelines provide guidance to a study group in its consideration of
the incorporation of material protected by copyright law in Recommendations of ITU-R and ITU-T.
(...) Different issues that arise when considering the incorporation of Software in a
Recommendation 3
2.1 General Rule 3
2.2 Copyright considerations for technically appropriate uses of Software in
ITU Recommendations 4
2.2.1 Use of Software to describe functionality, serve as an example of how
required functionality might be achieved, or to test an implementation for
conformance 4
2.2.2 Software that describes data structures, data streams, schemas, ASN.1, etc. 5
2.3 Software developed collaboratively by the Study Group 5
2.3.1 Software developed collaboratively by the Study Group without
contributed code 5
2.3.2 Software developed collaboratively by the Study Group with contributed
code 5
3 Study Group procedures for including software in Recommendations 6
3.1 Introduction 6
3.2 Overview of the process 6
3.3 The Software Copyright Statement and Licensing Declaration 7
3.4 Study Group responsibilities 7
3.4.1 Decision to incorporate Software 7
3.4.2 Selection process 7
3.4.3 On-going maintenance considerations 7
3.5 Actions and obligations of parties prior to approval 8
3.5.1 Actions and obligations of Software Copyright Holder 8
3.5.2 Actions and obligations of the ITU 8
3.5.3 Actions and obligations of Members reviewing the Software 8
3.6 Actions and obligations during and after Recommendation publication by
the ITU 8
3.6.1 Copyright Notices to accompany the Software 8
Annex A Software Copyright Statement and Licensing Declaration 9
Annex B License agreement of Software for evaluation of the ITU Recommendation and
the use of the Software to evaluate or test output 11
Annex C Copyright Notices 12
1
ITU Software Copyright Guidelines
1. (...) The Software is and will remain the sole property of the Software Copyright Holder.
Language:English
Score: 826153.3
-
https://www.itu.int/dms_pub/it.../04/04/T04040000040004PDFE.pdf
Data Source: un
ITU Software Copyright Guidelines
International Telecommunication Union
ITU Software Copyright Guidelines
(7/12/2011)
applicable as from 13 April 2012
8
ITU Software Copyright Guidelines
Summary
The ITU Software Copyright Guidelines provide guidance to a study group in its consideration of the incorporation of material protected by copyright law in Recommendations of ITU-R and ITU-T.
(...) Different issues that arise when considering the incorporation of Software in a Recommendation 3 2.1 General Rule 3 2.2 Copyright considerations for technically appropriate uses of Software in ITU Recommendations 4 2.2.1 Use of Software to describe functionality, serve as an example of how required functionality might be achieved, or to test an implementation for conformance 4 2.2.2 Software that describes data structures, data streams, schemas, ASN.1, etc. 5 2.3 Software developed collaboratively by the Study Group 5 2.3.1 Software developed collaboratively by the Study Group without contributed code 5 2.3.2 Software developed collaboratively by the Study Group with contributed code 5 3 Study Group procedures for including software in Recommendations 6 3.1 Introduction 6 3.2 Overview of the process 6 3.3 The Software Copyright Statement and Licensing Declaration 7 3.4 Study Group responsibilities 7 3.4.1 Decision to incorporate Software 7 3.4.2 Selection process 7 3.4.3 On-going maintenance considerations 7 3.5 Actions and obligations of parties prior to approval 8 3.5.1 Actions and obligations of Software Copyright Holder 8 3.5.2 Actions and obligations of the ITU 8 3.5.3 Actions and obligations of Members reviewing the Software 8 3.6 Actions and obligations during and after Recommendation publication by the ITU 8 3.6.1 Copyright Notices to accompany the Software 8 Annex A Software Copyright Statement and Licensing Declaration 9 Annex B License agreement of Software for evaluation of the ITU Recommendation and the use of the Software to evaluate or test output 11 Annex C Copyright Notices 12
ITU Software Copyright Guidelines
1. (...) The Software is and will remain the sole property of the Software Copyright Holder.
Language:English
Score: 826153.3
-
https://www.itu.int/dms_pub/it...04/04/T04040000040004MSWE.docx
Data Source: un
ITU Normal.dot
- 18 -
ITU-T SOFTWARE COPYRIGHT GUIDELINES
Issue 2.1.1 – March 2005
These Software Copyright Guidelines are dedicated to the memory of Mr. (...) For all software in this category, Section 3 of these Guidelines, and Annexes A, B, C, and D, do not apply.
2.3 Software that may raise IPR issues
A Recommendation may include software that is submitted to the Study Group with asserted restrictions. (...) Generally, if the software is essential, it is not possible to implement the Recommendation without infringing on the copyright associated with that software.
Language:English
Score: 822284
-
https://www.itu.int/dms_pub/it.../04/05/T04050000030002MSWE.doc
Data Source: un
ITU Normal.dot
- 18 -
ITU-T SOFTWARE COPYRIGHT GUIDELINES
Issue 2.1 – February 2003
These Software Copyright Guidelines are dedicated to the memory of Mr. (...) Generally, if the software is essential, it is not possible to implement the Recommendation without infringing on the copyright associated with that software. (...) Note: Users of the software, whether through the ITU-T Recommendation or via a transposed SDO standard, may be required to acquire licenses from the Software Copyright Holder for use of the software for implementation of the Recommendation.
Language:English
Score: 822284
-
https://www.itu.int/dms_pub/it.../04/05/T04050000030001MSWE.doc
Data Source: un
ITU Normal.dot
- 18 -
ITU-T SOFTWARE COPYRIGHT GUIDELINES
Issue 2.1.1 – March 2005
These Software Copyright Guidelines are dedicated to the memory of Mr. (...) For all software in this category, Section 3 of these Guidelines, and Annexes A, B, C, and D, do not apply.
2.3 Software that may raise IPR issues
A Recommendation may include software that is submitted to the Study Group with asserted restrictions. (...) Generally, if the software is essential, it is not possible to implement the Recommendation without infringing on the copyright associated with that software.
Language:English
Score: 822284
-
https://www.itu.int/ITU-T/dbase/copyright/softguidelines.doc
Data Source: un
Some pluggable equipment might not contain software. Others may contain software that is intrinsically bound to the NT's own software image. (...) In this case, the ME-R would support only the 'get software image' action. S.4.1.1 Software images attributes for fundamental usage The following manageable attributes are specified for each software image instance: Managed software image: This attribute distinguishes between the two software image instances (0, 1). (...) Get software image: Retrieve attributes of a software image instance.
Language:English
Score: 822144.5
-
https://www.itu.int/en/publica...files/basic-html/page1009.html
Data Source: un
Discussion: I would like to request help from the team regarding risk management.
1
DEL04: AI software lifecycle specification
Provides a summary of existing software development lifecycle standards and how they could be applied for healthcare AI.
(...) Lifecycle steps & references
ESTABLISH INTENDED USE ([82304-1])
PERFORM INITIAL RISK ASSESSMENT ([82304-1])
ESTABLISH USE REQUIREMENTS ([82304-1])
ESTABLISH SYSTEM REQUIREMENTS ([82304-1])
CREATE SOFTWARE PLAN(S) ([62304], [XAVIER])
SOFTWARE REQUIREMENTS ([62304], [XAVIER])
SOFTWARE ARCHITECTURE ([62304], [XAVIER])
SOFTWARE DETAILED DESIGN ([62304], [XAVIER])
SOFTWARE INTEGRATION, UNIT-LEVEL, INCLUDING TESTING ([62304], [XAVIER])
SOFTWARE INTEGRATION, INTEGRATION LEVEL, INCLUDING TESTING ([62304], [XAVIER])
SOFTWARE SYSTEM TESTING ([62304], [XAVIER])
SOFTWARE RELEASE ([62304], [XAVIER])
ESTABLISH VALIDATION PLAN ([82304-1])
VALIDATE THE PRODUCT ([82304-1])
CREATE VALIDATION REPORT ([82304-1])
MONITOR PRODUCT PERFORMANCE ([82304-1], [XAVIER])
MAINTAIN SOFTWARE AFTER LAUNCH ([82304-1])
RETIREMENT ([82304-1])
RISK MANAGEMENT (CONTINUOUS) ([82304-1], [XAVIER])
CHANGE CONTROL / PROBLEM RESOLUTION (CONTINUOUS) ([62304], [XAVIER])
CONFIGURATION MANAGEMENT (CONTINUOUS) ([62304], [XAVIER])
References:
IEC 62304:2006, Medical device software: software lifecycle process. https://webstore.iec.ch/publication/6792
Note that 62304 is in the process of being updated; I expect there to be a 2021 version released in the next few months.
(...) System development activities (including risk management)
System maintenance activities (including risk management)
Maintenance
request
Request
satisfied
7 Software risk management
8 Software configuration management
9 Software problem resolution
5.8 Software release
5.7 Software system testing
6.2 Problem and modification analysis
5.3 Software architectural design
5.4 Software
detailed design
5.6 Software integration and integration testing
5.5 Software unit implementation and verification
6.1 Establish software maintenance
plan
S
YSTEM
development
ACTIVITIES
(
including
RISK
MANAGEMENT
)
Customer
needs
Customer
needs
satisfied
7
Software
RISK
MANAGEMENT
8
Software configuration management
9
Software problem resolution
Activities outside the scope of IEC
62304
5
.
2
Software
requirements
analysis
5
.
1
Software
development
planning
5
.
8
Software
release
for
VALIDATION
5
.
7
Software
SYSTEM
testing
5
.
3
Software
architectural
design
5
.
6
Software
integration and
integration testing
5
.
5
Software
UNIT
implementation
5
.
4
Software
detailed
design
Language:English
Score: 821925.5
-
https://www.itu.int/en/ITU-T/f...ocuments/all/FGAI4H-K-034.pptx
Data Source: un
NB – Same presentation as K-034.
1
DEL04: AI software lifecycle specification
Provides a summary of existing software development lifecycle standards and how they could be applied for healthcare AI.
(...) Lifecycle steps & references
ESTABLISH INTENDED USE ([82304-1])
PERFORM INITIAL RISK ASSESSMENT ([82304-1])
ESTABLISH USE REQUIREMENTS ([82304-1])
ESTABLISH SYSTEM REQUIREMENTS ([82304-1])
CREATE SOFTWARE PLAN(S) ([62304], [XAVIER])
SOFTWARE REQUIREMENTS ([62304], [XAVIER])
SOFTWARE ARCHITECTURE ([62304], [XAVIER])
SOFTWARE DETAILED DESIGN ([62304], [XAVIER])
SOFTWARE INTEGRATION, UNIT-LEVEL, INCLUDING TESTING ([62304], [XAVIER])
SOFTWARE INTEGRATION, INTEGRATION LEVEL, INCLUDING TESTING ([62304], [XAVIER])
SOFTWARE SYSTEM TESTING ([62304], [XAVIER])
SOFTWARE RELEASE ([62304], [XAVIER])
ESTABLISH VALIDATION PLAN ([82304-1])
VALIDATE THE PRODUCT ([82304-1])
CREATE VALIDATION REPORT ([82304-1])
MONITOR PRODUCT PERFORMANCE ([82304-1], [XAVIER])
MAINTAIN SOFTWARE AFTER LAUNCH ([82304-1])
RETIREMENT ([82304-1])
RISK MANAGEMENT (CONTINUOUS) ([82304-1], [XAVIER])
CHANGE CONTROL / PROBLEM RESOLUTION (CONTINUOUS) ([62304], [XAVIER])
CONFIGURATION MANAGEMENT (CONTINUOUS) ([62304], [XAVIER])
References:
IEC 62304:2006, Medical device software: software lifecycle process. https://webstore.iec.ch/publication/6792
Note that 62304 is in the process of being updated; I expect there to be a 2021 version released in the next few months.
(...) System development activities (including risk management)
System maintenance activities (including risk management)
Maintenance
request
Request
satisfied
7 Software risk management
8 Software configuration management
9 Software problem resolution
5.8 Software release
5.7 Software system testing
6.2 Problem and modification analysis
5.3 Software architectural design
5.4 Software
detailed design
5.6 Software integration and integration testing
5.5 Software unit implementation and verification
6.1 Establish software maintenance
plan
S
YSTEM
development
ACTIVITIES
(
including
RISK
MANAGEMENT
)
Customer
needs
Customer
needs
satisfied
7
Software
RISK
MANAGEMENT
8
Software configuration management
9
Software problem resolution
Activities outside the scope of IEC
62304
5
.
2
Software
requirements
analysis
5
.
1
Software
development
planning
5
.
8
Software
release
for
VALIDATION
5
.
7
Software
SYSTEM
testing
5
.
3
Software
architectural
design
5
.
6
Software
integration and
integration testing
5
.
5
Software
UNIT
implementation
5
.
4
Software
detailed
design
Language:English
Score: 821925.5
-
https://www.itu.int/en/ITU-T/f...ocuments/all/FGAI4H-L-046.pptx
Data Source: un
