Skip to main content
removed irrelevant tag
Link
gnat
  • 20.8k
  • 29
  • 115
  • 295
added 38 characters in body
Source Link
Arseni Mourzenko
  • 135.8k
  • 31
  • 350
  • 522

From what I've learned last term on SWE courses, a big part of it is writing documents, so it seems that a SRSsoftware requirements specification (SRS) should earn points for my end-of-course project.

However, I will be more comfortable if I use prototyping, i.e., I make a small thing that works for the most trivial of situations and gradually add up features and improvements. LVS 68:1996 doesn't seem to recommend mixing these two things together.

Is it possible to still maintain my preferred approach to development, and have some usable requirement specification document?

From what I've learned last term on SWE courses, a big part of it is writing documents, so it seems that a SRS should earn points for my end-of-course project.

However, I will be more comfortable if I use prototyping, i.e., I make a small thing that works for the most trivial of situations and gradually add up features and improvements. LVS 68:1996 doesn't seem to recommend mixing these two things together.

Is it possible to still maintain my preferred approach to development, and have some usable requirement specification document?

From what I've learned last term on SWE courses, a big part of it is writing documents, so it seems that a software requirements specification (SRS) should earn points for my end-of-course project.

However, I will be more comfortable if I use prototyping, i.e., I make a small thing that works for the most trivial of situations and gradually add up features and improvements. LVS 68:1996 doesn't seem to recommend mixing these two things together.

Is it possible to still maintain my preferred approach to development, and have some usable requirement specification document?

Source Link

Is rapid prototyping incompatible with software requirements specification?

From what I've learned last term on SWE courses, a big part of it is writing documents, so it seems that a SRS should earn points for my end-of-course project.

However, I will be more comfortable if I use prototyping, i.e., I make a small thing that works for the most trivial of situations and gradually add up features and improvements. LVS 68:1996 doesn't seem to recommend mixing these two things together.

Is it possible to still maintain my preferred approach to development, and have some usable requirement specification document?