1
Евгений
no recommendations
no complaints
Project title: Develop a course for TK formation
Type of cooperation: One-time project
Section: Education and consulting
Prepayment: without prepayment
Payment methods: Bank transfer
Acceptance of requests: from 2023-06-24 until 2023-07-01
Type of cooperation: One-time project
Section: Education and consulting
Prepayment: without prepayment
Payment methods: Bank transfer
Acceptance of requests: from 2023-06-24 until 2023-07-01
Project description:
Offering remote work. Develop a course on collecting requirements and developing TK for IT projects.
Need: presentation (PowerPoint), text for the speaker, preferably homework, but not necessarily
It is possible to cooperate on a permanent basis
Content:
Module 1. Introduction. Study of the feasibility of the IT project. Formation of stakeholder groups. Types of requirements
Requirements and feasibility study as a project phase
Definition of the concept of a requirement
Functional, non-functional and emergency requirements
Requirements for the product and development process
Limitations and assumptions
Module 2. Collection, execution and balancing of requirements and restrictions. Role of Users Supporting the Product
Model of the requirements collection process
Sources of claims
Requirement collection techniques
The role of users – supporters of the product
Getting support
Hierarchy of claims
Resolution of contradictions
Practice/Demo. Formation of a registry of claims
Module 3. Analysis and prioritization of requirements. Formation of business and technical specifications
Iterative nature of claims collection
The Matrix of Compromise
Conceptual and formal analysis of requirements
Epics – Properties – User Stories in Adaptive Models
Methods of prioritizing requirements. MoSCoW matrix (optional)
Matrix of Comparison of Business and Technical Requirements
Enforcement/acceptance criteria
Demo. Development of a matrix of business and technical requirements
Module 4. Details of requirements. Prototyping. Use case analysis tools
Prototyping
Explicit and implicit requirements
Define the context and boundaries of a software system
Identification of Use Cases (Use Cases)
System modeling using UML analysis diagrams (class diagrams, states)
Demo. Use case/UML diagrams
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Maybe just a specification?
Module 5. Registration and approval of the technical specification (technical specification)
Specification of IEEE SWEBOK Requirements
GOST 19 and 34 series.
Hierarchy of TK according to GOST 34: ACS, component, PP
Demo - Design of technical assignment
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Module 6. Quantitative indicators and limitations. Review of instruments
Quantitative indicators of the product
Quantitative indicators of the development project
Quantitative indicators and limitations.
Review of instruments
Offering remote work. Develop a course on collecting requirements and developing TK for IT projects.
Need: presentation (PowerPoint), text for the speaker, preferably homework, but not necessarily
It is possible to cooperate on a permanent basis
Content:
Module 1. Introduction. Study of the feasibility of the IT project. Formation of stakeholder groups. Types of requirements
Requirements and feasibility study as a project phase
Definition of the concept of a requirement
Functional, non-functional and emergency requirements
Requirements for the product and development process
Limitations and assumptions
Module 2. Collection, execution and balancing of requirements and restrictions. Role of Users Supporting the Product
Model of the requirements collection process
Sources of claims
Requirement collection techniques
The role of users – supporters of the product
Getting support
Hierarchy of claims
Resolution of contradictions
Practice/Demo. Formation of a registry of claims
Module 3. Analysis and prioritization of requirements. Formation of business and technical specifications
Iterative nature of claims collection
The Matrix of Compromise
Conceptual and formal analysis of requirements
Epics – Properties – User Stories in Adaptive Models
Methods of prioritizing requirements. MoSCoW matrix (optional)
Matrix of Comparison of Business and Technical Requirements
Enforcement/acceptance criteria
Demo. Development of a matrix of business and technical requirements
Module 4. Details of requirements. Prototyping. Use case analysis tools
Prototyping
Explicit and implicit requirements
Define the context and boundaries of a software system
Identification of Use Cases (Use Cases)
System modeling using UML analysis diagrams (class diagrams, states)
Demo. Use case/UML diagrams
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Maybe just a specification?
Module 5. Registration and approval of the technical specification (technical specification)
Specification of IEEE SWEBOK Requirements
GOST 19 and 34 series.
Hierarchy of TK according to GOST 34: ACS, component, PP
Demo - Design of technical assignment
--------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Module 6. Quantitative indicators and limitations. Review of instruments
Quantitative indicators of the product
Quantitative indicators of the development project
Quantitative indicators and limitations.
Review of instruments
