Requirements Analysis.

After our training in Requirements Analysis you can... - Deliver business value through requirements specifications based on the organisation's actual needs, both functional and quality-related - Use business models (goal, stakeholder, process and information models) to build a picture of needs - Capture requirements using interview and workshop techniques - Translate the organisation's needs into system requirements, described with use cases - Secure business value by using the use cases as a basis for review and testing, to quality-assure the requirements and eliminate risks Course content Introduction to requirements analysis The aim of this section is to reach a shared view of what requirements are and their role in development General introduction to requirements Different types of requirements (functional requirements and quality requirements) Conditions for effective requirements analysis (organisation, priorities, management support, etc.) Different problems that can arise Quality in information systems Sources of requirements Describing requirements: how are requirements documented? The aim of this section is to introduce use cases and actors and explain how their different uses support different project phases Techniques for gathering and specifying requirements Use cases Actors How do we find use cases and actors Describing the main flow and alternative flows Writing use case descriptions Quality requirements and how they are formulated and grouped Reviews and review techniques Use cases as a basis for testing: understanding the versatility of use cases The right requirements: how is business value secured? The aim of this section is a shared view of how to find the right requirements that match the organisation's actual needs Requirements specification and process efficiency Make sure the process is efficient before capturing requirements Systems built on requirements identified from needs in an inefficient process cement the inefficient process Conditions for value-creating requirements analysis. Requirements must be based on needs Techniques for identifying possible use cases Workshop techniques for identifying and defining use cases Prioritising requirements: how is time used most effectively? Only do what is necessary, and the most important things first The aim of this section is to show how to use time as effectively as possible by prioritising correctly. Prioritising functional requirements Prioritising quality requirements Prioritisation techniques Sharper requirements analysis with business models The aim of this section is to show how business models can be used as tools for collaboration between the business and IT. Brief overview: business architecture à la Astrakan The process model explained Business models as a basis for... - identifying use cases in the process model - checking that the use cases are based on the right needs in an efficient process - finding actors in the process model and the stakeholder model - avoiding misunderstandings through a shared terminology: the concept model - reviewing use cases: the information model - a joint workshop to identify improvement needs Using requirements The aim of this section is to show the value that use cases can provide through all their different uses. What characterises effective requirements work with use cases? Creating test cases from use cases Choosing technology with the help of quality requirements Use cases as a basis for acceptance testing Testing and quality requirements Conclusion Summary Review of the course objectives How do I move forward