Call : (+91) 968636 4243
Mail : info@EncartaLabs.com
EncartaLabs

Decoding Requirements Engineering

( Duration: 3 Days )

The Decoding Requirements Engineering training course is aimed to address some very critical and unique points related to requirements engineering which are usually not understood well and hence contribute to the complexity associated with this multifaceted problem.

By attending Decoding Requirements Engineering workshop, delegates will learn:

  • Human limitations faced by software professionals when dealing with complexities inherent to software systems
  • Problem of Single Frame of Vision and its repercussion on software systems
  • Importance of Non Functional Requirements and its ignorance by the software development industry
  • Requirements Engineering – "A Monster with multiple heads" making it one of the toughest problems to address
  • Abuse and Misconceptions associated to the usage of Agile and Scrum as a magic bullet to address most of the problems associated with requirements engineering and software systems
  • Unstructured way of capturing, representing and managing the information representing the requirements thereby limiting the scope of automation

The Decoding Requirements Engineering class is recommended for:

  • Requirements Gatherer’s
  • Architects
  • Analyst
  • Project / Technical Managers

COURSE AGENDA

1

Importance of Requirements Engineering to the success of software systems

2

Understanding the technical line items involved in defining the Functional Requirements of a system

3

Understanding the importance of Non Functional Requirements to the success of software systems

4

Multiple Facets related to "Requirements Engineering" making it one of the toughest problems to solve

5

Difference between "Functional Requirements" and "Business Requirements" – A term which is mostly used interchangeably

6

Different types of "Human Limitations" faced by Software Professionals while analyzing complexities associated to software system

7

Understanding the human limitation of "Single Frame of Vision" and its repercussion on Software systems

8

Understanding the human limitation of "Inability of a human brain to comprehend hundreds of scenarios in a use case" and its repercussion on Software systems

9

Strategic issues related to requirements engineering and its repercussion on Software systems

10

Behavioral issues related to requirements engineering and its repercussion on Software systems

11

Time Bases issues related to requirements engineering and its repercussion on Software systems

12

Accountability related issues related to requirements engineering and its repercussion on Software systems

13

Understanding possible solutions to address this multifaceted problem of requirements engineering

14

Difference between "Requirements Gatherer", "Analyst" and "Domain Expert" and their responsibilities – One of the root causes behind the problems associated to requirements engineering

15

The scientific reasoning behind "estimates in software industry going off by a factor of 400 or more" and ways to address the same

16

Best practices for designing and representing "Structural Models" of systems to address the problem of "Single Frame of Vision"

17

Best practices for designing and representing "Behavioral Models" of systems to address the problem of "Single Frame of Vision"

18

Best practices for using Design or Data Structure Matrix as a tool to understanding structural complexity of software system without missing out on any information

19

Understanding generic characteristics of a system to validate the completeness of functional requirements of a system irrespective of the business domain

20

Understanding the "Source – Sin" characteristic of a system to represent the information representing the requirements to be processed by decision support systems [computer systems]

21

Best practices for designing and representing "Behavioral Models" of systems to address the problem of "Single Frame of Vision"

22

Usage of State Models as a tool to capture missing behaviors of a particular system

23

Automated way of finding out all the possible scenarios of a use case using software programs [or algorithms]

24

Requirements Engineering needs solid engineering best practices rather than individual human brilliance

25

Best practices for capturing and managing different types of "Non Functional Requirements" and its interrelations in a quantifiable manner

26

Understanding and interpreting the Non Functional Requirements Matrix

27

Misconceptions associated to usage of "Agile / Scrum" as a Magic Bullet to solve most of the problems associated to requirements engineering

28

Best practices wrt usage of "Agile / Scrum" in the appropriate context

Encarta Labs Advantage

  • One Stop Corporate Training Solution Providers for over 6,000 various courses on a variety of subjects
  • All courses are delivered by Industry Veterans
  • Get jumpstarted from newbie to production ready in a matter of few days
  • Trained more than 50,000 Corporate executives across the Globe
  • All our trainings are conducted in workshop mode with more focus on hands-on sessions

View our other course offerings by visiting https://www.encartalabs.com/course-catalogue-all.php

Contact us for delivering this course as a public/open-house workshop/online training for a group of 10+ candidates.

Top
Notice
X