Udemy
    •  
    •  
    •  
    •  
    •  
    •  
    •  
    •  
Subscribe
Turn what you know into an opportunity and reach millions around the world.
Learn More
Your cart is empty.
Keep shopping
Software requirements specification: develop fast and clear
Rating: 3.9 out of 5(63 ratings)
335 students

Software requirements specification: develop fast and clear

Gather, prioritize requirements, develop software specification in close collaboration with a customer and users
Created byDanil Dintsis
Last updated 3/2023
English

What you'll learn

  • define project stakeholders;
  • gather stakeholder's demands, requirements, and expectations;
  • develop business and technical requirements traceability matrix;
  • create simple UML models
  • develop software specification;

Course content

1 section • 9 lectures • 1h 5m total length

  • Introduction7:58

    In this module You learn who are stakeholders, and why it is extremely important to identify stakeholders. You make an exercise and identify different types of stakeholders - internal vs external; groups/organizations/individuals - for your own project.

  • Develop a stakeholder register8:13

    In module 2 You learn how to collect requirements using Stakeholder register, and analyze requirements and expectations based on stakeholder's classification.

  • D.A.N.C.E. with major stakeholders3:55

    In this lecture you learn about the most important types of stakeholders, and the best ways of collaborating with them.

  • Assignment 1. Stakeholder register
  • Manage requirements. MoSCoW prioritizing5:24

    In module 3 students learn the M-S-C-W prioritization matrix, and test this tool themselves

  • Additional. KANO prioritizing model6:54

    In this additional lecture you learn about KANO model. It comes from Japan lean techniques. It's a good idea to implement M-S-C-W and KANO models together for better requirements management and customer satisfaction

  • Prioritize requirements (Optional)
  • Develop a matrix of business vs technical requirements4:55

    In module 4 students learn the tool named "business vs technical requirements traceability matrix". You learn how to align business and technical demands in the best way to reach business needs.

  • Develop business vs technical requirements matrix
  • Prototyping as a planning tool6:22

    In module 5 students learn different types of prototypes and develop a wireframe for their project.

  • Implementing UML diagrams for more detailed requirements9:34

    In module 6 students learn basic UML concepts and models: use cases, states and consequence diagrams.

  • Develop a Wireframe or/and a UML diagram
  • Create a software specification (SRS)12:40

    In module 7. students learn the structure of the Software Requirements Specification and try to develop their own SRS document. In this module we resume the results of the course in general.

Requirements

  • A student is an experienced software user
  • A student has an experience in software/App development or
  • A student has an experience in software/App testing

Description

In the course you learn the full cycle of collecting, prioritizing, balancing and agreeing on IT product/service requirements.

You learn the software specification document and UML models and you have an option to try working out software requirements, prioritize them and design a software requirements specification by yourself.

At the course you can consequently develop your own package of software requirements, share it with the expert trainer (PfMP, PgMP, PMP; ITIL Expert, Managing professional and Strategic Leader; DevOps Product Owner and accredited trainer) for a friendly feedback.

At the course completion you learn and will be able: 

  • How to engage stakeholders and develop a Stakeholder register

  • Identify the top priority stakeholders

  • Define the appropriate communications approach to the top-ranked stakeholders

  • How to create and agree on Business - technical requirements matrix

  • Solve conflicts in requirements between different stakeholder groups

  • Prioritize and balance requirements using MoSCoW priority matrix

  • Apply KANO prioritizing tool

  • Develop use cases, states diagrams, consequence diagrams

  • How to develop Software requirements specification.

The course contains four assignments which help you to learn the topics practically.

You are welcome to submit and receive and receive expert-level feedback.. Usually I try to deliver my feedback in 2 business days.

In the course materials you find templates and examples demo.

Who this course is for:

  • Software users,
  • Software customers,
  • software developers,
  • IT support teams,
  • system analytics

Report abuse