Hi all,
I used a PRD template which includes this differentiation and was wondering what other teams are doing in regard to communicating functional/non Functional in PRD.
Thanks!
Functional Requirements. The Astronaut must be able to meet each of the following functional requirements:
i. Be within the following height and weight range: 5’0” 110 lbs. and 6’4” 223 lbs.;
ii. Dress themselves in a one-piece, zip-up flight suit;
iii. Climb the New Shepard Launch Tower (equivalent to 7 flights of stairs) in under ninety (90) seconds;
iv. Walk quickly across uneven surfaces, such as a ramp or a deck with occasional steps;
v. Be comfortable on the top deck of the launch tower and on the grated gangway to the CC. These are about seventy (70) feet above ground level and are surrounded by balcony-like railings. The view is equivalent to the view from a seventh floor balcony.
vi. Fasten and unfasten his/her own seat harness in under fifteen (15) seconds, which is about as difficult as fastening the seat-belt in an unfamiliar car in the dark;
vii. Sit strapped into the CC’s reclined seat for forty (40) minutes, but up to ninety (90) minutes if there is a long launch delay, without getting up, and without access to a bathroom;
viii. Spend forty (40) minutes, but up to ninety (90) minutes if there is a long hold, in the CC with up to five (5) other people with the CC hatch closed;
ix. Experience up to three times your normal weight (3gs) pushing you into your seat for up to two (2) minutes during powered ascent;
x. Hear and understand instructions in English from a ground crewmember nearby or from mission control over a radio speaker, in an environment where the noise level can reach one hundred (100) dB during the Flight;
xi. See and respond to alert lights in the CC. At each seat, there is a panel of six (6) lighted symbols to indicate, for example, when to fasten the harness or leave the CC (the lights are similar to the warning lights on a car’s dashboard; the use of corrective lenses is permitted because glasses and contact lenses both function normally in zero-g);
xii. Reliably follow instructions provided either over the radio speaker or via the alert lights;
xiii. Experience up to five-and-a-half times one’s normal weight (5.5gs) pushing the Astronaut into his/her seat for a few seconds during descent into the atmosphere; and
xiv. Lowering down from the CC’s hatch opening to the ground after landing, which is equivalent to lowering down to the floor from a dining-room table (note that Blue Origin expects to provide the option of using stairs within a few minutes of landing).
I have been seeking a wood furniture Dragunov SVD aeg for about a year and a half now.
Somebody help a battle brother out!!
Trying to understand where the details go. So I understand so much going into specific requirements, but what about some of the information that isn't in a specific requirement?? Such as overall process flows across many requirements, assumptions, out of scope details, etc
All that stuff I'm used to seeing in a large Word document along with 25 requirements. Forgive me - I'm SAP and may have 6-7 interdependent scrum teams going at once. There is stuff at each of the process levels that describes the process, rather than at the requirement level, but I feel like the Functional Specification is going away???
Hello everyone, hope you’re all having a wonderful and productive day!
I`m working on an article with main focus to finally differentiate the Functional and Non-Functional requirements in software engineering projects, why are they so important to begin with, and also seek some of the best practices out there to help others with writing them properly.
I believe these are easily forgotten and in my opinion, it's the stepping stone of every successful project when you have both requirements clearly defined from the beginning.
Do you think this topic is attractive and interesting, to begin with?
I would really appreciate your honest feedback on this. Thanks in advance
BTW, this is Filip from Macedonia :)
can someone give me some of these requirements I'm really stuck
Hello,
I'm writing a VCDX design, and I have a question regarding conceptual design requirements.
What is the point of differentiating functional vs non-functional requirements?
Does the functionality type of a requirement serve any purpose to the effects of a design?
Thanks
Nicolás
I have researched Functional and Non-Functional Requirements and they still continue to plague me. The examples I find are not consistent. Can someone explain this to me in a better way than "non-functional requirements describe how the system works, while functional requirements describe what the system should do." - Because those sound like the same thing to me.
Everyone who doesn't already have it is essentially not going to get it this wipe without cheesing which is not okay. It gates generator level 3 which gates the final stretch of finishing the hideout.
Skip the intro - https://slashproject.co/posts/2020/non-functional-requirements-are-my-favorite-and-i-will-make-them-yours-too/
--
Hey team,
It's roadmap season over here and I found myself diving deep into non-functional requirements. If you're not used to incorporate them in your PRDs or curious about how I work with NFRs in my day-to-day PMing, go check it out.
Cheers!
Hi Everyone! If you ignore non-functional requirements, you end up with a non-functional product. Read our detailed article on functional and non-functional requirements for SaaS applications. Ask any questions, we'd be glad to discuss.
https://ddi-dev.com/blog/programming/functional-vs-non-functional-requirements-what-is-the-difference-ultimate-guide-with-examples/
Cleaning companies in Riyadh, London, Dubai, and other big cities usually get orders through an app. Eliciting functional requirements are easy, but things start going to the south when the development team starts considering non-functional requirements. It seems like the list is never gonna end. How do you manage it?
Hello everyone, hope you’re all having a wonderful and productive day!
Me & my team were working on an article with the main focus to finally differentiate the Functional and Non-Functional requirements in software engineering projects, why are they so important to begin with, and also seek some of the best practices out there to help others with writing them properly.
Do you think this topic is attractive and interesting, to begin with?
I would really appreciate your honest feedback on this one. Thank you 🙏
https://adevait.com/software/functional-non-functional-requirements
