: Re: Documenting software requirements As a self-taught developer the only requirement documents I've ever been privileged to read are those of hackerrank and the sort. However the more and more I

Requirements can be broadly categorised as follows (using FURPS):

Functionality: functional requirements (see also this stack overflow question)
Usability: Human factors, aesthetics and style, consistency, documentation
Reliability: reliability requirements
Performance: quantifiable requirements such as response time
Supportability: requirements to ensure it is testable, configurable, able to be installed and serviced

If you are attempting to develop formal requirements, try ISO/IEC/IEEE 29148:2018 Systems and software engineering -- Life cycle processes - Requirements engineering.

For large systems, you could also look at approaches such as SYSMOD that you can use to model the requirements and the system architecture. Using this approach, you would:

Describe the context of the project, supplemented with a case study
Identify stakeholders (users, domain experts, management, standards, customers, systems engineers and maintainers, marketing and sales, etc.) and then collect and develop requirements.
Model the proposed system, identify system actors (external forces) and information flow in and out of the system (as well as interaction points)
Identify use cases (stories) that involve the actors from the previous steps. Model these interactions, derive system interfaces, look at internal structures, etc.

For your average project, you will likely want to do something in-between. An important aspect of requirements engineering that should be mentioned is the back-and-forth between the engineering team and the stakeholders. Requirements are used by developers, testers, business analysts, technical writers, marketing and sales, and the customer as a method of communication. It describes the system that you are building - a shared vision. It can take many iterations for requirements to be agreed upon and without that communication it wont matter what you write!

Load Full (0)

: Just say black man. You're only describing his skin color, and black is a good, quick way to do it. What you have to ask yourself is, do you absolutely need to mention his ethnicity?

@Ogunnowo420

Load Full 0 Comments

: How much does translating a novel cost? I've read that writers and editors are often paid on a per-word basis. Then I did a search about the cost of translating a literary work into a different

@Ogunnowo420

Load Full 1 Comments

: What should tie a collection of short-stories together? Short-stories are a nice format to write. If you have been an aspiring writer for at least one year, it's quite probabile that you've

@Ogunnowo420

Load Full 5 Comments

: How to include external references when writing internal documentation? In the IT industry, we often write a lot of technical documentation meant for internal use only. Those documents are often

: Re: Documenting software requirements As a self-taught developer the only requirement documents I've ever been privileged to read are those of hackerrank and the sort. However the more and more I

More posts by @Ogunnowo420

: Just say black man. You're only describing his skin color, and black is a good, quick way to do it. What you have to ask yourself is, do you absolutely need to mention his ethnicity?

: How much does translating a novel cost? I've read that writers and editors are often paid on a per-word basis. Then I did a search about the cost of translating a literary work into a different

: What should tie a collection of short-stories together? Short-stories are a nice format to write. If you have been an aspiring writer for at least one year, it's quite probabile that you've

: How to include external references when writing internal documentation? In the IT industry, we often write a lot of technical documentation meant for internal use only. Those documents are often

Login to post a comment!

0 Comments

Back to top