class 14 02 19 requirements engineering - RequirementEngineering/helloworld-arysna182 GitHub Wiki

Stakeholder.-

  •    direct.- impact directly.(Academic Services)

  •  indirect/need to know what is going on with the system or project(not directly affected).()

Systematic.- done or acting according to a fixed plan or system methodical.

Verification.-am i building the product right?

Validation.- am i building the right product?

Types of requirements

#User(Bussness Analyst)Validation

High abstract requirements, from the user perspective they don't know what they wants exactly

#System(Developer team)Verification

more precise detailed of what they system should do, it's have to be more clean in the moment to solve the customers problem.

  • Functional.- Describe the system should do.
  • Non-functional.-it's the part when the customers doesn't see what the system do. example

Requirements imprecision

Problems arise when there are a ambiguous requirements and we dont know what exactly we want. make us the big problem of the software, doesn't have quality or the product it's not complete.

#NON-functional requirements implementation

usability requirements

Requirements engineering processes its like the activities, what the customers wants. (is an iterative activity in which these processes are interleaved.)

Spiral Model check step by step

User requirements specification.- have so much high abstract requirements User requirements Elicitation.- its the interview with the customer to gather information of the requirements of that product he/she wants.

System requirements specification and modeling.- we use tools to help us to build right the product.

Requirements Elicitation

  • Requirements discovery,
  • Requirements classification and organization,
  • Requirements prioritization and negotiation,
  • Requirements specification.

CRUD

  • Create
  • Read
  • Update
  • Delete

Interviewing

Types of interview

  • closed interviews are based on pre-determined list of questions
  • Open in this step you speak with the stakeholder and ask more than the usual

interviewing problems the main problems of here are not good for understanding domain requirements Domain requirements -Glossary

Ethnography

you analysing how the people actually work in the environment. doesn't work with new ideas.

Focused ethnography

combines ethnography with prototyping

Stories and Scenarios

Requirements specification the process of writing down the user and system requirements in a requirements document.

  • User.- requirements have to be understandable by end-users and customers who do not have a technical background
  • System.- requirements are more detailed requirements and may include more technical information.

ways of writing a system requirements specification

  • Natural language
  • Structured natural languages
  • Design description languages
  • Graphical notations
  • Mathematical specifications (Automatas)

Requirements and design

first the requirements and design are inseparable. should state what the system should do and the design should describe how it does this.

##Guidelines for writing requirements use text highlighting to identify key parts of the requirement (Jargon) technical way of talk.

##Problems with natural language

Lack of clarity

  • precision is difficult without making the document difficult to read.

Requirements confusion

  • functional and non-functional requirements tend to be mixed-up.

Requirements amalgamation

  • several different requirements may be expressed together.

User Cases

-Waterfall -Spiral take more longer project! SRS

USER Stories

-Agile Requirements constantly changes!#