Create a software project 1. Introduction 1 1.1 Objective 1 1.2 Standards document layout 1 1.3 groups of reader
Posted: Fri May 20, 2022 6:03 pm
Create a software project
1. Introduction 1
1.1 Objective 1
1.2 Standards document layout 1
1.3 groups of readers and reading Recommendations 1
1.4 scope of the project 1
1.5 References 1
2. General description 2
2.1 product positioning 2
2.2 Basic Functions 2
2.3 User groups and their characteristics
2.4 Operating environment 2
2.5 Restrictions in the design and implementation 2
2.6 User documentation 3
2.7 Assumptions and Dependencies 3
3. Functions 3
3.1 Function 1 3
3.2 Function 2 (and so on) 4
Interface requirements 4
4.1 User aspects of interfaces 4
4.2 Hardware aspects of interfaces 4
4.3 Software aspects of the interfaces 4
4.4 Communication aspects of interfaces 4
5. Non-functional requirements 5
5.1 For productivity 5
5.2 For safety 5
5.3 Security 5
5.4 For quality 5
6. Other requirements 6
Indicate any other requirements not specified elsewhere in the CL. These may be requirements related to the internationalization of PP, the ability to reuse its components and more. Please note in particular the requirements for the procedure for the adoption of the PP
Appendix A: Glossary
<Define all terms that you consider necessary for a good understanding of the CL, incl. acronyms and abbreviations. If your organization already has a common vocabulary developed, you could use a relevant subset of it.>
Annex B: Analytical models
<If you deem it necessary, include here analytical models such as block diagrams, class diagrams, E-R diagrams, etc.>
Appendix C: List of unresolved issues
<This is a dynamic list of open issues that need to be resolved - gathering missing information, pending solutions, unresolved conflicts, etc.>
1. Introduction 1
1.1 Objective 1
1.2 Standards document layout 1
1.3 groups of readers and reading Recommendations 1
1.4 scope of the project 1
1.5 References 1
2. General description 2
2.1 product positioning 2
2.2 Basic Functions 2
2.3 User groups and their characteristics
2.4 Operating environment 2
2.5 Restrictions in the design and implementation 2
2.6 User documentation 3
2.7 Assumptions and Dependencies 3
3. Functions 3
3.1 Function 1 3
3.2 Function 2 (and so on) 4
Interface requirements 4
4.1 User aspects of interfaces 4
4.2 Hardware aspects of interfaces 4
4.3 Software aspects of the interfaces 4
4.4 Communication aspects of interfaces 4
5. Non-functional requirements 5
5.1 For productivity 5
5.2 For safety 5
5.3 Security 5
5.4 For quality 5
6. Other requirements 6
Indicate any other requirements not specified elsewhere in the CL. These may be requirements related to the internationalization of PP, the ability to reuse its components and more. Please note in particular the requirements for the procedure for the adoption of the PP
Appendix A: Glossary
<Define all terms that you consider necessary for a good understanding of the CL, incl. acronyms and abbreviations. If your organization already has a common vocabulary developed, you could use a relevant subset of it.>
Annex B: Analytical models
<If you deem it necessary, include here analytical models such as block diagrams, class diagrams, E-R diagrams, etc.>
Appendix C: List of unresolved issues
<This is a dynamic list of open issues that need to be resolved - gathering missing information, pending solutions, unresolved conflicts, etc.>