Edit print and main programs Edit reference

variable
in
main py

Add print py

Modify main py
Delete colon from
reference variable

Add new examples of references

.gitignore

@@ -165,3 +165,4 @@ cython_debug/
 .venv2
 ~$sample.xlsx
 files/*
+.vscode/*

BibTex.bib

@@ -1,17 +1,10 @@
-@article{KnieselGünter2001Jrbe,
-journal = {Software, practice & experience},
-keywords = {access rights ; aliasing ; Computer Science ; Computer Science, Software Engineering ; encapsulation ; Java ; Science & Technology ; security ; Technology},
-language = {eng},
-number = {6},
-pages = {555-576},
-publisher = {John Wiley & Sons, Ltd},
-title = {JAC-Access right based encapsulation for Java},
-volume = {31},
-year = {2001},
-abstract = {Unwanted effects of aliasing cause encapsulation problems in object‐oriented programming. Nevertheless, aliasing is part of common and efficient programming techniques for expressing sharing of objects and as such its general restriction is not an option in practice. This paper proposes an approach that allows full referential object sharing but adds transitive access control to object references to limit the effects of aliasing. The approach relies on well‐known properties of object‐oriented type systems but exploits them in a novel way to support an access‐right‐based model of encapsulation. It is presented as an extension of Java, called JAC (Java with Access Control). Copyright © 2001 John Wiley & Sons, Ltd.},
-author = {Kniesel, Günter and Theisen, Dirk},
-address = {Chichester, UK},
-copyright = {Copyright © 2001 John Wiley & Sons, Ltd.},
-issn = {0038-0644},
-}
-
+@ARTICLE{8288807,
+author={},
+journal={ISO/IEC/IEEE 26512:2017(E)}, 
+title={ISO/IEC/IEEE International Standard - Systems and software engineering - Requirements for acquirers and suppliers of information for users}, 
+year={2017},
+volume={},
+number={},
+pages={1-47},
+keywords={IEEE Standards;IEC Standards;ISO Standards;Software engineering;Systems engineering and theory;Requirements engineering},
+doi={10.1109/IEEESTD.2017.8288807}}

BibTex2.bib

@@ -0,0 +1,13 @@
+@article{DBLP:journals/corr/abs-2107-03374,
+author={Mark Chen and Jerry Tworek and Heewoo Jun and Qiming Yuan and Henrique Ponde de Oliveira Pinto and Jared Kaplan and Harri Edwards and Yuri Burda and Nicholas Joseph and Greg Brockman and Alex Ray and Raul Puri and Gretchen Krueger and Michael Petrov and Heidy Khlaaf and Girish Sastry and Pamela Mishkin and Brooke Chan and Scott Gray and Nick Ryder and Mikhail Pavlov and Alethea Power and Lukasz Kaiser and Mohammad Bavarian and Clemens Winter and Philippe Tillet and Felipe Petroski Such and Dave Cummings and Matthias Plappert and Fotios Chantzis and Elizabeth Barnes and Ariel Herbert-Voss and William Hebgen Guss and Alex Nichol and Alex Paino and Nikolas Tezak and Jie Tang and Igor Babuschkin and Suchir Balaji and Shantanu Jain and William Saunders and Christopher Hesse and Andrew N. Carr and Jan Leike and Josh Achiam and Vedant Misra and Evan Morikawa and Alec Radford and Matthew Knight and Miles Brundage and Mira Murati and Katie Mayer and Peter Welinder and Bob McGrew and Dario Amodei and Sam McCandlish and Ilya Sutskever and Wojciech Zaremba},
+title        = {Evaluating Large Language Models Trained on Code},
+journal      = {CoRR},
+volume       = {abs/2107.03374},
+year         = {2021},
+url          = {https://arxiv.org/abs/2107.03374},
+eprinttype    = {arXiv},
+eprint       = {2107.03374},
+timestamp    = {Thu, 25 May 2023 10:38:31 +0200},
+biburl       = {https://dblp.org/rec/journals/corr/abs-2107-03374.bib},
+bibsource    = {dblp computer science bibliography, https://dblp.org}
+}

BibTex3.bib

@@ -0,0 +1,14 @@
+@book{RN1,
+   author = {Laplante, Phillip A. and Kassab, Mohamad H.},
+   title = {Requirements Engineering for Software and Systems},
+   publisher = {Auerbach Publishers, Incorporated},
+   address = {Milton, UNITED KINGDOM},
+   keywords = {Requirements engineering.
+Software engineering.
+Systems engineering.},
+   ISBN = {9781000593815},
+   url = {http://ebookcentral.proquest.com/lib/univlime-ebooks/detail.action?docID=6927367},
+   year = {2022},
+   type = {Book}
+}
+

BibTex4.bib

@@ -0,0 +1,14 @@
+@book{RN1,
+author = {Laplante, Phillip A. and Kassab, Mohamad H.},
+title = {Requirements Engineering for Software and Systems},
+publisher = {Auerbach Publishers, Incorporated},
+address = {Milton, UNITED KINGDOM},
+keywords = {Requirements engineering.
+Software engineering.
+Systems engineering.},
+ISBN = {9781000593815},
+url = {http://ebookcentral.proquest.com/lib/univlime-ebooks/detail.action?docID=6927367},
+year = {2022},
+type = {Book}
+}
+

BibTex5.bib

@@ -0,0 +1,12 @@
+@book{RN2,
+author = {Bron, Jean-Yves},
+title = {System Requirements Engineering : A SysML Supported Requirements Engineering Method},
+publisher = {John Wiley & Sons, Incorporated},
+address = {Newark, UNITED STATES},
+keywords = {Requirements engineering.},
+ISBN = {9781119751533},
+url = {http://ebookcentral.proquest.com/lib/univlime-ebooks/detail.action?docID=6268185},
+year = {2020},
+type = {Book}
+}
+

BibTex6.bib

@@ -0,0 +1,15 @@
+@article{https://doi.org/10.1002/smr.1780,
+author = {Holtmann, Jörg and Bernijazov, Ruslan and Meyer, Matthias and Schmelter, David and Tschirner, Christian},
+title = {Integrated and iterative systems engineering and software requirements engineering for technical systems},
+journal = {Journal of Software: Evolution and Process},
+volume = {28},
+number = {9},
+pages = {722-743},
+keywords = {systems engineering, requirements engineering, development process, model transformations, technical systems},
+doi = {https://doi.org/10.1002/smr.1780},
+url = {https://onlinelibrary.wiley.com/doi/abs/10.1002/smr.1780},
+eprint = {https://onlinelibrary.wiley.com/doi/pdf/10.1002/smr.1780},
+abstract = {Abstract The development of software-intensive technical systems involves several engineering disciplines like mechanical, electrical, control, and particularly software engineering. Model-based Systems Engineering (MBSE) coordinates these disciplines throughout the development by means of discipline-spanning processes and a system model. Such a system model provides a common understanding of the system under development and serves as a starting point for the discipline-specific development. An integral part of MBSE is the requirements engineering on the system level. However, these requirements need to be refined for the discipline-specific development to start, for example, into specific requirements for the embedded software. Because existing MBSE approaches lack support for this refinement step, we conceived in previous work a systematic transition from MBSE to model-based software requirements engineering. We automated the steps of the transition where possible, in order to avoid error-prone and time-consuming manual tasks. In this paper, we extend this approach with support for subsequent process iterations and provide an algorithm for the automated steps. We illustrate the approach and perform a case study with an example of an automotive embedded system. Copyright © 2016 John Wiley \& Sons, Ltd.},
+year = {2016}
+}
+

BibTex7.bib

@@ -0,0 +1,14 @@
+@book{alma991004068000403496,
+abstract = {This document contains provisions for the processes and products related to the engineering of requirements for systems and software products and services throughout the life cycle. It defines the construct of a good requirement, provides attributes and characteristics of requirements, and discusses the iterative and recursive application of requirements processes throughout the life cycle. This document provides additional guidance in the application of requirements engineering and management processes for requirements-related activities in ISO/IEC/IEEE 12207 and ISO/IEC/IEEE 15288. Information items applicable to the engineering of requirements and their content are defined. The content of this document can be added to the existing set of requirements-related life cycle processes defined by ISO/IEC/IEEE 12207 or ISO/IEC/IEEE 15288, or can be used independently.},
+address = {New York},
+booktitle = {ISO/IEC/IEEE 29148:2018(E): ISO/IEC/IEEE International Standard - Systems and software engineering : Life cycle processes : Requirements engineering},
+isbn = {1-5044-5302-6},
+keywords = {Computer software -- Standards},
+language = {eng},
+organization = {IEEE Computer Society. Software & Systems Engineering Standards Committee, author.},
+publisher = {IEEE},
+series = {ISO/IEC/IEEE ; 29148},
+title = {ISO/IEC/IEEE 29148:2018(E): ISO/IEC/IEEE International Standard - Systems and software engineering : Life cycle processes : Requirements engineering },
+year = {2018},
+}
+

BibTex8.bib

@@ -0,0 +1,14 @@
+@book{alma991004066978503496,
+abstract = {ISO/IEC/IEEE 26512:2011 was developed to assist users of ISO/IEC 15288:2008 (IEEE Std 15288-2008) or ISO/IEC 12207:2008 (IEEE Std 12207-2008) to acquire or supply software user documentation as part of the software life cycle processes. It defines the documentation process from the acquirer's standpoint and the supplier's standpoint. ISO/IEC/IEEE 26512:2011 covers the requirements for information items used in the acquisition of user documentation products: the Acquisition Plan, Document Specification, Statement of Work, Request for Proposals, and the proposal. It provides an overview of the software user documentation and information management processes which may require acquisition and supply of software user documentation products and services. It addresses the preparation of requirements for software user documentation. These requirements are central to the user documentation specification and Statement of Work. It includes requirements for primary document outputs of the acquisition and supply process: the Request for Proposal and the Proposal for user documentation products and services. It also discusses the use of a Documentation Management Plan and a Document Plan as they arise in the acquisition and supply processes. ISO/IEC/IEEE 26512:2011 is independent of the software tools that may be used to produce documentation, and applies to both printed documentation and on-screen documentation. Much of its guidance is applicable to user documentation for systems including hardware as well as software. Keywords: acquisition, information management, proposal, software user documentation, statement of work, supply.},
+address = {New York, NY, USA},
+booktitle = {ISO/IEC/IEEE 26512 First Edition, 2011-06-01 : ISO/IEC/IEEE Systems and software engineering -- Requirements for acquirers and suppliers of user documentation},
+edition = {First edition.},
+isbn = {0-7381-6583-2},
+keywords = {Software engineering},
+language = {eng},
+organization = {Institute of Electrical and Electronics Engineers, author, issuing body.},
+publisher = {IEEE},
+title = {ISO/IEC/IEEE 26512 First Edition, 2011-06-01 : ISO/IEC/IEEE Systems and software engineering -- Requirements for acquirers and suppliers of user documentation },
+year = {2011},
+}
+

BibTexOriginal.bib

@@ -0,0 +1,10 @@
+@INPROCEEDINGS{4530352,
+author={Omran, Ahmed},
+booktitle={2008 3rd International Conference on Information and Communication Technologies: From Theory to Applications}, 
+title={AGILE CMMI from SMEs perspective}, 
+year={2008},
+volume={},
+number={},
+pages={1-8},
+doi={10.1109/ICTTA.2008.4530352}
+}

holder/BibTexa.bib

@@ -0,0 +1,9 @@
+@book{abc,
+Title	={Software Engineering Aspects of Continuous Development and New Paradigms of Software Production and Deployment: Second International Workshop, DEVOPS 2019, Château de Villebrumier,},
+Title2  ={France, May 6-8, 2019, Revised Selected Papers},
+Volume  ={12055 of Lecture Notes in Computer Science Programming and Software Engineering},
+Editors	={Jean-Michel Bruel, Manuel Mazzara, Bertrand Meyer},
+Publisher	={Springer Nature, 2020},
+ISBN	={3030393062, 9783030393069},
+Length	={211 pages},
+}

main.py

@@ -97,6 +97,6 @@
 
 # __________________________________
 
-reference = author + ' (' + year + ') ' + '\'' + title + '\'' + ',' + ' ' + journal + ',' + ' ' + volume + '(' + number + ')' + ' ' + 'pp. ' + pages + ', ' + 'available: ' + doi + ' / ' + url + ' [accessed: ' + date + '].'
+reference = author + ' (' + year + ') ' + '\'' + title + '\'' + ',' + ' ' + journal + ',' + ' ' + volume + '(' + number + ')' + ' ' + 'pp. ' + pages + ', ' + 'available: ' + doi + ' / ' + url + ' [accessed ' + date + '].'
 
 print(reference)

print.py

@@ -0,0 +1,3 @@
+print('hi')
+import sys
+print(sys.exec_prefix)