Note: We will devote a set of questions to Functional Requirements
We will have another set of questions related to non-functional requirements later.
[1]
The functional requirements (First) describe the functionalities required from the system, such as business rules, transaction corrections, adjustments and cancellations, administrative functions, Authentication, and Authorization levels (Second).
First:
The functional and non-functional requirements present the Problem Space, and no one knows how to define and understand the Problem Space.
Why?
Because if we know how to understand the Problem Space, we will be able to:
1. Stop the nightmare of Maintenance, and we can implement preventive Maintenance.
2. Stop reinventing the wheels.
3. Develop self-manageable, self-adaptable, self, extendable, and self-configurable systems with unlimited applicability, reuse, and other quality properties of the system development.
Second:
(1) The functionalities described above do not tell the software and system requirements and only represent the business properties, which is very easy to do. It has been business as usual. Where are we now?
(2) Limited to business software and has nothing to do with critical life & time software systems, Aerospace, defense, and others,
(3) Limited to developing an instance-oriented software system which would lead to within and out reinventing the wheels.
(4) How to guarantee the business rules, transaction corrections, and others
Who's "we" here? And "any software system" is rather broad. Do you include military and aerospace embedded systems? Do you include commercial systems that must satisfy financial, auditability, and regulatory requirements? Now of course there are also smart appliances that have software and Internet connections. The domain of application and environment of use matters.
Hi. any system has functional and non functional needs. non functional needs such as: safety, efficiency, speed and ...
functional needs depend on type of system. such as: Telerehabilitation system, Virtual reality exergame and ...
To Dennis Hamilton,
You said: Who's "we" here?
My Reply: Every member in RG, including you.
Your reply to a straightforward question with more questions, and you don't know anything about the problem space and the nature of existing software development.
You said: And "any software system" is rather broad
My Reply: Software is the center of all systems.
Several reasons why we don't know how to work on the problem space:
1) Humans are trained and educated as solution-oriented, including yourself.
2) Most existing publications and books ignore talking about the problem space.
3) Software developers and system manufacturers ignore the problem space because of wealth by reinventing the wheel and creating new versions of the same product every year. Look at the iPhone, for example:
Of massive systems: a few upgrades to the iPhone version, the consumer pays the same amount or more yearly. If you are a fan of the iPhone and you buy an iPhone every year, you have spent more than 20K to 25K on the iPhone alone in the last 14 years.
Hello Fatemeh Sarpourian,
You said: Any system has functional and nonfunctional needs.
My Reply: Yes, I agree.
You said: Nonfunctional needs such as safety, efficiency, speed, and ...
My reply:
(1) Nonfunctional requirements are enduring. Therefore speed is not a nonfunctional requirement.
(2) Generic nonfunctional requirements, and it is not executable.
(3) Some generic nonfunctional requirements are impossible in current software developments.
(4) We must tie nonfunctional requirements to the system we build because we develop the system's requirements, not the software.
You said: Functional needs depend on the type of system. Such as Telerehabilitation systems, Virtual reality exergame, and ...
My Reply:
Excellent. Functional and nonfunctional needs (represent the problem space) depend on the type of system.
The reality is shown in my answer to Mr. Dennis Hamilton
And let me repeat them here.
Several reasons why we don't know how to work on the problem space:
1) Humans are trained and educated as solution-oriented, including yourself.
2) Most existing publications and books ignore talking about the problem space.
3) Software developers and system manufacturers ignore the problem space because of wealth by reinventing the wheel and creating new versions of the same product every year. Look at the iPhone, for example:
Of massive systems: a few upgrades to the iPhone version, the consumer pays the same amount or more yearly. If you are a fan of the iPhone and you buy an iPhone every year, you have spent more than 20K to 25K on the iPhone alone in the last 14 years.
- Badges
- Science method
- Similar topics
- Methodology