Search for a command to run...
As a student, I combine the worlds of learning and blogging. With a thirst for knowledge and a will for writing, I share my notes through engaging blogs. These are the long boring lectures of my life I have survived through that I have summarized to you with a pinch of salt.
No comments yet. Be the first to comment.
Computer system failures are a common issue, with computers crashing or malfunctioning unexpectedly. This often leads to mistrust in personal computers. The dependability of a computer system refers to its trustworthiness, indicating the user's confi...
With the increasing integration of computer systems into various aspects of our lives, the repercussions of system and software failures are growing. Failures, such as server software malfunction in e-commerce or errors in embedded control systems in...
User or customer testing is a crucial stage in the testing process where users or customers provide input and feedback on the system being tested. It can involve formal testing of a system commissioned from an external supplier or an informal process...
Release testing is the process of testing a particular release of a system that is intended for use outside of the development team. Normally, the system release is for customers and users. In a complex project, however, the release could be for othe...
Test-driven development (TDD) is a programming methodology where testing and code development are interleaved. It involves incrementally developing code alongside corresponding tests, ensuring that each increment of code passes its respective test be...
Requirement engineering is a very complex and time-consuming process. This process is divided into four parts
Requirement specification
Requirement elicitation and analysis
Requirement validation
Requirement Management
Now let us understand each of these in detail
Requirement specification:- Requirement specification is the process of writing down the user and system requirements in a requirement document. In recruitment specification, the user requirements for a system should be described the functional and non-functional so that they can be understood by the system user who doesn’t have detailed technical knowledge. If you are writing user requirements, you should not use software jargon, structural notation, or formal notation. You should write user requirements in natural language with simple tables, forms and diagrams.
Ideally, user and system requirements should be :
Clear
Easy to understand
Unambiguous
Complete and consistent
Ways of writing a system requirement specification are:
Natural language sentences:-The requirements are written using numbered sentences in natural language. Each sentence should express one requirement.
Structural natural language:- the requirements are written in natural language on standard form or template. Each field provides information about a specific requirement.
Design description language:- This approach uses a language like programming language, but with more abstract features to specify requirements by defining an operational model of the system. This approach is now rarely used altogether. It can be useful for interface specification.
Graphical notations:- graphical notations supplemented by text annotations are used to define the functional requirement for the system; UML use and sequence diagrams are commonly used.
Mathematical specifications:- these notations are based on mathematical concepts such as finite state machines or sets. Although these unambiguous specifications can reduce ambiguity In a requirement document, most customers don’t understand formal specifications.
This is all about the requirement specification, we will learn about the further processes in our next blog.
