Chapter 1 Some Fundamental Truths
Truth 1 Requirements are not really about requirements
Requirements are what the software product, or hardware
product, or service, or whatever you intend to build, is meant to do and to be.
Requirements exist whether you discover them or not, and whether you write them
down or not. In essence, then, requirements are not about the written
requirements as such, but rather an uncovering of the problem to be solved.
Truth 2 If we must build software, then it must be optimally
valuable for its owner.
As the software becomes more capable and the cost of
construction increases, so does the benefit that the software brings. At some
point, however, the cost of construction starts to outstrip the benefit and the
project is no longer beneficial.
Truth 3 If your software does not have to satisfy a need,
then you can build anything. However, if it is meant to satisfy a need, then
you have to know what that need is to build the right software
It is worthwhile considering that the most useful products are those for which
the developers correctly understood what the product was intended to accomplish for its users, and in what manner it was to accomplish that purpose.
Truth 4 There is an important difference between building a
piece of software and solving a business problem. The former does not necessarily
accomplish the latter.
Truth 5 The requirements do not have to be written, but they
have to become known to the builders.
Naturally, there is a need to communicate the requirements
to the builders of the product.
Truth 6 Your customer won’t always give you the right
answer. Sometimes it is impossible for the customer to know what is right, and
sometimes he just doesn’t know what he needs.
Truth 7 Requirements do not come about by chance. There
needs to be some kind of orderly process for developing them.
Truth 8 You can be as iterative as you want, but you still
need to understand what the business needs.
Truth 9 There is no silver bullet. All our methods and tools
will not compensate for poor thought and poor workmanship.
Truth 10 Requirements, if they are to be implemented
successfully, must be measurable and testable.
Truth 11 You, the business analyst, will change the way the
user thinks about his problem, either now or later.
What are these Requirements?
- Functional Requirements: Functional requirements are things the product must do.
The product shall produce a schedule of all roads upon which ice is
predicted to form within the given time parameter.
- Non- Functional Requirements: Non-functional requirements are qualities the product must have.
The product shall provide a pleasing user experience.
The product shall be able to be used by travelers in the arrivals hall who do not speak the home language.
- Constraints: Constraints are global issues that shape the requirements. Constraints are simply another type of requirement.
The product must be available at the beginning of the new tax year.
The product shall operate as an iPad, iPhone, Android, and Blackberry
app.
Since we have come with a new CRM tool to implement at IG. Gathering Functional and non-functional requirements are really important. The following can be good examples for the same:
ReplyDeleteFunctional requirements : The system should ease out the process of data validation and data format conversion.
Non-functional requirements: User interface should be free of jargon and easy to use. All the users must be aware and consistent while entering the data.
So as we come up with idea apply a new CRM tool at IG, the requirements for the new CRM tool is very important for some reasons. Firstly, the requirement is the crucial part if we want to conduct a new CRM tool because in order to conduct a new CRM tool, we have to do everything based on the requirement. Secondly, if we have good requirements for the new tool, we will have more higher chances to succeed in this CRM tool. Last but not least, the requirements not only keeps us in track with our work, also can draw a big picture and build trust to the stakeholders.
ReplyDeleteThe requirements contain the new properties, behavior and attribute for the further future and it is one of the main task of the business that these requirements are understood by stakeholders. As we are implementing a new CRM tool to our company IG wealth management, for the success of the system it is essential to understand the requirement and implement them properly. Moreover, gathering the requirements are important for solving the problems which can occur during the process or to achieve the objective. while gathering the requirements, for our company constraints is also important. As these will help us to shape our system.
ReplyDelete