requirements engineering requirements engineering re in the engineering design process it is a common role in systems engineering and software engineering the first use of the term requirements engineering was probably in 1979 in trw technical report and the establishment of a conference series on requirements engineering that has evolved into the current international requirements engineering conference in the waterfall model requirements engineering is presented as the first phase of the development process later development methods including the rational unified process rup for software assume that requirements engineering continues through the lifetime of a system requirement management which is a subfunction of systems engineering practices is also indexed in the incose international council on systems engineering manuals activities the activities involved in requirements engineering vary widely depending on the type of system being developed and the specific practices of the organizations involved these may include requirements inception or requirements elicitation developers and stakeholders meet the latter are inquired concerning their needs and wants regarding the software product requirements analysis and negotiation requirements are identified including new ones if the development is iterative and conflicts with stakeholders are solved both written and graphical tools the latter commonly used in the design phase but some find them helpful at this stage too are successfully used as aids examples of written analysis tools use cases and user stories examples of graphical tools uml and lml system modeling some engineering fields or specific situations require the product to be completely designed and modeled before its construction or fabrication starts and therefore the design phase must be performed in advance for instance blueprints for a building must be elaborated before any contract can be approved and signed many fields might derive models of the system with the lifecycle modeling language whereas others might use uml note in many fields such as software engineering most modeling activities are classified as design activities and not as requirement engineering activities requirements specification requirements are documented in a formal artifact called requirements specification rs nevertheless it will become official only after validation a rs can contain both written and graphical models information if necessary example software requirements specification srs requirements validation checking that the documented requirements and models are consistent and meet the needs of the stakeholder only if the final draft passes the validation process the rs becomes official requirements management managing all the activities related to the requirements since inception supervising as the system is developed and even until after it is put into use e g changes extensions etc these are sometimes presented as chronological stages although in practice there is considerable interleaving of these activities problems one limited study in germany presented possible problems in implementing requirements engineering and asked respondents whether they agreed that they were actual problems the results were not presented as being generalizable but suggested that the principal perceived problems were incomplete requirements moving targets and time boxing with lesser problems being communications flaws lack of traceability terminological problems and unclear responsibilities criticism there is no evidence that requirements engineering contributes to the success of software projects or systems problem structuring a key aspect of requirements engineering decreases design performance requirements analysis requirements engineering focused in software engineering requirements engineering specialist group resg international requirements engineering board ireb ieee 12207 systems and software engineering software life cycle processes togaf chapter 17 concept of operations conops operations management software requirements software requirements specification software engineering body of knowledge swebok design specification specification technical standard formal specification 291482011 systems and software engineering life cycle processes requirements engineering 2011 pp194 doi101109ieeestd20116146379 isbn9780738165912this standard replaces ieee 8301998 ieee 12331998 ieee 13621998 httpstandardsieeeorgfindstdsstandard291482011html systems engineering body of knowledge requirements engineering management handbook by faa vtesystems engineeringsubfields aerospace engineering biological systems engineering configuration management earth systems engineering and management electrical engineering enterprise systems engineering performance engineering reliability engineering safety engineering processes requirements engineering functional specification system integration verification and validation design review concepts business process system system lifecycle vmodel systems development life cycle tools decisionmaking function modelling idef optimization quality function deployment system dynamics systems modeling language systems analysis systems modeling work breakdown structure people james s albus ruzena bajcsy benjamin s blanchard wernher von braun kathleen carley harold chestnut wolt fabrycky barbara grosz arthur david hall iii derek hitchins robert e machol radhika nagpal simon ramo joseph francis shea katia sycara manuela m veloso john n warfield related fields control engineering computer engineering industrial engineering operations research project management quality management risk management software engineering category vtesoftware engineeringfields computer programming requirements engineering software deployment software design software maintenance software testing systems analysis formal methods concepts data modeling enterprise architecture functional specification modeling language orthogonality programming paradigm software software archaeology software architecture software configuration management software development methodology software development process software quality software quality assurance software verification and validation structured analysis orientations agile aspectoriented object orientation ontology service orientation sdlc modelsdevelopmental agile eup executable uml incremental model iterative model prototype model rad up scrum spiral model vmodel waterfall model xp other spice cmmi data model er model function model information model metamodeling object model systems model view model languages idef uml usl sysml softwareengineers victor basili kent beck grady booch fred brooks barry boehm peter chen danese cooper ward cunningham tom demarco edsger w dijkstra delores m etter martin fowler adele goldstine margaret hamilton c a r hoare lois haibt mary jean harrold grace hopper watts humphrey michael a jackson ivar jacobson alan kay nancy leveson stephen j mellor bertrand meyer david parnas trygve reenskaug winston w royce james rumbaugh mary shaw peri tarr elaine weyuker niklaus wirth edward yourdon related fields computer science computer engineering project management risk management systems engineering category commons vteieee standardscurrent 488 730 754 revision 854 828 829 896 1003 1014 1016 1076 11491 1154 1164 1275 1278 1284 1355 1394 1451 1497 1516 1541 1547 1584 1588 1596 1603 1613 1666 1667 1675 1685 1722 1733 1800 1801 1815 1850 1900 1901 1902 1904 1905 2030 11073 12207 14764 16085 16326 29148 42010 802 series8021 d p q qat qay w x ab ad ae ag ah ak aq as ax az ba 80211 a b c d e f g h i j k n p r s u v w y ac ad af ah ai ax ay 2 3 4 5 6 7 8 9 10 12 14 15 1 4 4a 16 d e 17 18 20 21 22proposed p1363 p1619 p1699 p1823 p19061 superseded 7541985 830 1219 1233 1362 1364 1471 see also ieee standards association categoryieee standards vteiso standards by standard numberlist of iso standards iso romanizations iec standards19999 1 2 3 4 5 6 7 9 16 17 31 0 1 2 3 4 5 6 7 8 9 10 11 12 13 128 216 217 226 228 233 259 269 302 306 361 428 500 518 519 639 1 2 3 5 6 646 657 668 690 704 732 764 838 843 860 898 965 999 1000 1004 1007 10731 1155 1413 1538 1629 1745 1989 2014 2015 2022 2033 2047 2108 2145 2146 2240 2281 2533 2709 2711 2720 2788 2848 2852 3029 3103 3166 1 2 3 3297 3307 3601 3602 3864 3901 3950 3977 4031 4157 4165 4217 4909 5218 5426 5427 5428 5725 5775 5776 5800 5964 6166 6344 6346 6385 6425 6429 6438 6523 6709 6943 7001 7002 7010 7027 7064 7098 7185 7200 7498 1 7637 7736 7810 7811 7812 7813 7816 7942 8000 8093 8178 8217 8373 85011 8571 8583 8601 8613 8632 8651 8652 8691 88058806 8807 88205 8859 1 2 3 4 5 6 7 8 8i 9 10 11 12 13 14 15 16 8879 90009001 9036 9075 9126 9141 9227 9241 9293 9314 9362 9407 9506 9529 9564 95929593 9594 9660 97971 9897 9899 9945 9984 9985 9995 1000019999 10005 10006 10007 10116 101183 10160 10161 10165 10179 10206 10218 10303 11 21 22 28 238 10383 10487 10585 10589 10646 10664 10746 10861 10957 10962 10967 11073 11170 11179 11404 11544 11783 11784 11785 11801 11898 11940 2 11941 11941 tr 11992 12006 12182 12207 122342 13211 1 2 13216 13250 13399 134062 13450 13485 13490 13567 13568 13584 13616 14000 14031 14224 14289 14396 14443 14496 2 3 6 10 11 12 14 17 20 14644 14649 14651 14698 14750 14764 14882 14971 15022 15189 15288 15291 15292 15398 15408 15444 3 15445 15438 15504 15511 15686 15693 15706 2 15707 15897 15919 15924 15926 15926 wip 15930 16023 16262 166122 16750 16949 ts 17024 17025 17100 17203 17369 17442 17799 18000 18004 18014 18245 18629 18916 19005 19011 19092 1 2 19114 19115 19125 19136 19407 19439 19500 19501 19502 19503 19505 19506 19507 19508 19509 19510 19600 19752 19757 19770 197751 197945 19831 20000 20000 20022 20121 20400 21000 21047 21500 218272002 22000 23270 23271 23360 24517 24613 24617 24707 25178 25964 26000 26300 26324 27000 series 27000 27001 27002 27006 27729 28000 29110 29148 291992 29500 30170 31000 32000 38500 40500 42010 55000 80000 1 2 3 category authority control gnd 42139971 lccn sh2007004792 