Practice of developing software requirements - course RUB 40,490. from Specialist, training 32 ac. h., Date: June 24, 2023.

An experienced specialist in system analysis and software testing, a brilliant teacher. In his classes, he constantly provides specific practical examples (including from his own rich experience) to facilitate understanding of the material.
Graduated from the Faculty of Mechanics and Mathematics of Moscow State University named after M.V. Lomonosov. Has been working in the IT field since 1998. In 2013, she completed training at the Russian Academy of National Economy and Public Administration under the President of the Russian Federation in the IT manager program. Continuously develops in the areas of test design, software quality assurance, system analytics and management.

Has extensive practical experience in testing and quality control of large information systems. Currently, Elena Sergeevna is a leading analyst, developing test design for information systems. Participates in the development and implementation of internal corporate quality assurance regulations. Conducts corporate training on testing, system analysis and quality assurance.
The educational material is presented clearly and intelligibly, drawing the attention of students to all the features of practical work. Examples from practice, additional information, detailed answers to any questions - all this constantly maintains high interest and attention among Elena Sergeevna’s listeners. Grateful graduates leave the most enthusiastic reviews and strive to sign up for further studies with Elena Sergeevna.

Module 1. Definition of requirements (4 ac. h.)

• What are the requirements? Definition of requirements.
• Classification of requirements. Requirements attributes.
• Quality attributes of requirements.

Practical work: problem statement. Description of the business process for which requirements will be developed in the next lessons.

Module 2. Requirements development process (4 ac. h.)

• General requirements development process.
• Business requirements. Statement of the problem, stakeholders, definition of the system boundary.
• User requirements. Defining users, identifying needs.

Practical work: identifying stakeholders, system boundaries for automation. Definition of users.

Module 3. Requirements development process. Practical aspects (4 ac. h.)

• Practical aspects of requirements development. Planning the requirements elicitation process.
• Sources of requirements. People. Systems. Documentation
• Methods for identifying requirements. Psychological problems of identifying requirements. Features of preparing and conducting interviews, working group seminars, surveys, etc.

Practical work: drawing up a plan. Preparing and conducting interviews with interested parties

Module 4. Requirements analysis (4 ac. h.)

• Requirements development. Requirements analysis stage.
• Modeling is part of the overall process.
• Pros and cons of modeling.
• Model types

Module 5. User requirements. Use cases (3 ac. h.)

• Definition. Structure. Rules for describing Use cases.
• Main flow, alternatives, exceptions.
• Preconditions and postconditions
• Use case diagram. Notation.
• Types of relationships

Practical work: drawing up a Use case diagram for an educational project.

Module 6. User requirements. User story (3 ac. h.)

• Requirements in Agile. Concepts of Topic, Epic, User story, Backlog
• Rules for writing a User story. INVEST
• Actor, actions, value.

Practical work: creating a user story for an educational project.

Module 7. Domain models. Entity-relationship diagram ERD (3 ac. h.)

• Purpose of the diagram, basic concepts.
• Chen's Notation, Crow's Foot
• Degrees of connection. Unraveling uncertainties.

Practical work: creating an entity relationship diagram for an educational project

Module 8. Domain models. DFD Data Flow Diagram (3 ac. h.)

• Purpose of the diagram. Basic elements of a diagram.
• Jordan, Gein-Sarson notations
• Levels of detail.

Practical work: creating a data flow diagram for a school project.

Module 9. Creating a document (4 ac. h.)

• Functional requirements.
• Non-functional requirements. Types of non-functional requirements. Software quality attributes.
• Requirements Specification. Document structure. Criteria for writing requirements text.

Training project: developing a requirements specification structure. Writing requirements using a template.