Thank you for sending your enquiry! One of our team members will contact you shortly.
Thank you for sending your booking! One of our team members will contact you shortly.
Course Outline
Block 1: Requirements without requirements engineering - good and bad practices
- Workshop 1 - where do the requirements really come from? Requirements engineering or business analysis? Requirements engineering hidden in project management Agile, i.e. really excellent requirements engineering (although hidden under exotic terminology) Requirements engineering as the responsibility of the development team
Block 2: How precise should the requirements be?
- Workshop 2 - what does the accuracy of a cookbook depend on? Requirements diligence as a function of failure consequences Requirements diligence as a function of product size and complexity Requirements diligence as a function of organization characteristics
Block 3: Good and bad requirements
- Features (properties) of good requirements Useful requirements parameters and their possible values Good requirements as elements of the product backlog in agile
Block 4: Ways of acquiring requirements
- Workshop 3 – searching for requirements Business vision and requirements for the IT system Stakeholders: us, them and others System boundary, system context and the rest of the world Requirements elicitation process Requirements elicitation techniques Requirements validation and negotiation
Block 5: describing requirements
- Exploratory requirements specification Description of requirements in natural language – benefits and risks, auxiliary methods Requirements modeling Light use of incomplete modeling User stories Control flow diagrams Swim lane diagrams Data flow diagrams (contextual) Entity relationship diagrams [ 2]: use case diagrams UML: activity diagrams UML: state transition diagrams UML: interaction diagrams UML: structural diagrams
Estimating effort based on requirements Linking requirements with the system vision, with each other, with the system architecture, components and tests How to deal with changes in requirements
14 Hours
Testimonials (4)
Poruszenie wszystkich punktów zawartych w programie szkolenia oraz elastyczność prowadzącego na formę prowadzenia zajęć i tematy, które w danym momencie uczestnik szkolenia chciał rozwinąć
Mateusz Gaweł
Course - Podstawy inżynierii wymagań i analizy
To, że w drugi dzień prowadząca bardzo rozsądnie zrezygnowała z przyjętego planu i bardziej nacisk został położony na rozmowy/dyskusje nad tematem wymagań i tego jakie mamy problemy w projekcie i jak można zastosować wymienione techniki praktycznie w życiu codziennym.
Beata Heba - Asseco Poland S.A.
Course - Podstawy inżynierii wymagań i analizy
Podejście do części praktycznej.
Anton Lytvynovskyi
Course - Podstawy inżynierii wymagań i analizy
Profesjonalizm, elokwencja, humor i duża wiedza.