Despite considerable time and resources spent on the initiation phase of software projects, discrepancies often exist between formal project documentation, customer requirements, and final project specifications. Such discrepancies in the requirements management process can have a very negative impact on final project outcomes. A Business Requirements Document (BRD) constitutes the formal software requirements documentation, which typically includes stakeholders’ needs and expectations and project scope while providing a clear project roadmap and project plan. According to IEEE standards, a BRD should be a structured document that includes specific elements such as functional and technical requirements while incorporating certain traits such as traceability and verifiability. Numerous studies indicate that most software companies do not ritually follow accepted standards, such as IEEE, while developing their BRDs and we know little about the relationship between requirements documentation project outcome. This thesis is a study the impact of requirements documentation quality on software project’s outcomes through a random sample of software projects from 12 different hospitals within a large healthcare provider. Requirements documentation quality was evaluated against IEEE standards. Projects’ cost and schedule metrics were used to assess project outcomes. Results outline the key elements of the requirements documentation process that are associated to project success.
","abstract_html":"<p>Despite considerable time and resources spent on the initiation phase of software projects, discrepancies often exist between formal project documentation, customer requirements, and final project specifications. Such discrepancies in the requirements management process can have a very negative impact on final project outcomes. A Business Requirements Document (BRD) constitutes the formal software requirements documentation, which typically includes stakeholders’ needs and expectations and project scope while providing a clear project roadmap and project plan. According to IEEE standards, a BRD should be a structured document that includes specific elements such as functional and technical requirements while incorporating certain traits such as traceability and verifiability. Numerous studies indicate that most software companies do not ritually follow accepted standards, such as IEEE, while developing their BRDs and we know little about the relationship between requirements documentation project outcome. This thesis is a study the impact of requirements documentation quality on software project’s outcomes through a random sample of software projects from 12 different hospitals within a large healthcare provider. Requirements documentation quality was evaluated against IEEE standards. Projects’ cost and schedule metrics were used to assess project outcomes. Results outline the key elements of the requirements documentation process that are associated to project success.</p>","abstract_has_math":false,"creators":["Alla, Sujatha"],"institution":null,"degree_name":"Master of Science (MS)","degree_level":"Thesis","degree_discipline":"Engineering Management & Systems Engineering","degree_department":null,"school":null,"contributors":["Pilar Pazos","Charles Daniels","Ariel Pinto"],"advisors":[],"committee_chairs":[],"committee_members":[],"year":2017,"date_issued":"2017-04-01T07:00:00Z","date_published":"2017-04-01T07:00:00Z","updated_at":"2026-07-24T03:34:02Z","subjects":["Business requirement documentation","IEEE standards","Project management","Requirements management","Scope creep","Software project performance","Business Administration, Management, and Operations","Computer Sciences","Operational Research","Software Engineering"],"languages":[],"rights":[],"rights_urls":[],"identifier_entries":[{"key":"dc:identifier","label":"Identifier","values":["9780355385991"],"render_values":[{"text":"9780355385991","href":null,"code":true}]}]},"links":{"outbound_url":"https://digitalcommons.odu.edu/emse_etds/20","outbound_label":"Repository record","outbound_source":"dc:identifier"},"metadata_groups":[{"id":"people","label":"People","entries":[{"key":"dc:contributor","label":"Contributor","values":["Pilar Pazos","Charles Daniels","Ariel Pinto"]},{"key":"dc:creator","label":"Author","values":["Alla, Sujatha"]}]},{"id":"academic_context","label":"Academic Context","entries":[{"key":"dc:date.available","label":"Dc Date Available","values":["2017-10-13T07:00:00Z"]},{"key":"thesis:degree_discipline","label":"Discipline","values":["Engineering Management & Systems Engineering"]},{"key":"thesis:degree_level","label":"Degree Level","values":["Thesis"]},{"key":"thesis:degree_name","label":"Degree Name","values":["Master of Science (MS)"]}]},{"id":"subjects_keywords","label":"Subjects and Keywords","entries":[{"key":"dc:subject","label":"Dc Subject","values":["Business requirement documentation","IEEE standards","Project management","Requirements management","Scope creep","Software project performance","Business Administration, Management, and Operations","Computer Sciences","Operational Research","Software Engineering"]}]},{"id":"identifiers","label":"Identifiers","entries":[{"key":"dc:identifier","label":"Identifier","values":["9780355385991","https://digitalcommons.odu.edu/emse_etds/20"]}]},{"id":"additional","label":"Additional Metadata","entries":[{"key":"dc:description.abstract","label":"Abstract","values":["Despite considerable time and resources spent on the initiation phase of software projects, discrepancies often exist between formal project documentation, customer requirements, and final project specifications. Such discrepancies in the requirements management process can have a very negative impact on final project outcomes. A Business Requirements Document (BRD) constitutes the formal software requirements documentation, which typically includes stakeholders’ needs and expectations and project scope while providing a clear project roadmap and project plan. According to IEEE standards, a BRD should be a structured document that includes specific elements such as functional and technical requirements while incorporating certain traits such as traceability and verifiability. Numerous studies indicate that most software companies do not ritually follow accepted standards, such as IEEE, while developing their BRDs and we know little about the relationship between requirements documentation project outcome. This thesis is a study the impact of requirements documentation quality on software project’s outcomes through a random sample of software projects from 12 different hospitals within a large healthcare provider. Requirements documentation quality was evaluated against IEEE standards. Projects’ cost and schedule metrics were used to assess project outcomes. Results outline the key elements of the requirements documentation process that are associated to project success.
"]},{"key":"dc:title","label":"Title","values":["Role of Requirements Engineering in Software Project’s Success"]}]}],"canonical_facts":{"dc:contributor":["Pilar Pazos","Charles Daniels","Ariel Pinto"],"dc:creator":["Alla, Sujatha"],"dc:date.available":["2017-10-13T07:00:00Z"],"dc:description.abstract":["Despite considerable time and resources spent on the initiation phase of software projects, discrepancies often exist between formal project documentation, customer requirements, and final project specifications. Such discrepancies in the requirements management process can have a very negative impact on final project outcomes. A Business Requirements Document (BRD) constitutes the formal software requirements documentation, which typically includes stakeholders’ needs and expectations and project scope while providing a clear project roadmap and project plan. According to IEEE standards, a BRD should be a structured document that includes specific elements such as functional and technical requirements while incorporating certain traits such as traceability and verifiability. Numerous studies indicate that most software companies do not ritually follow accepted standards, such as IEEE, while developing their BRDs and we know little about the relationship between requirements documentation project outcome. This thesis is a study the impact of requirements documentation quality on software project’s outcomes through a random sample of software projects from 12 different hospitals within a large healthcare provider. Requirements documentation quality was evaluated against IEEE standards. Projects’ cost and schedule metrics were used to assess project outcomes. Results outline the key elements of the requirements documentation process that are associated to project success.
"],"dc:identifier":["9780355385991","https://digitalcommons.odu.edu/emse_etds/20"],"dc:subject":["Business requirement documentation","IEEE standards","Project management","Requirements management","Scope creep","Software project performance","Business Administration, Management, and Operations","Computer Sciences","Operational Research","Software Engineering"],"dc:title":["Role of Requirements Engineering in Software Project’s Success"],"thesis:degree_discipline":["Engineering Management & Systems Engineering"],"thesis:degree_level":["Thesis"],"thesis:degree_name":["Master of Science (MS)"]},"updated_at":"2026-07-24T03:34:02Z"}