Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Shalagin Egor Comparative analysis of methods for requirements engineering #7

Open
wants to merge 1 commit into
base: main
Choose a base branch
from

Conversation

Wild-Queue
Copy link

No description provided.

@@ -0,0 +1,488 @@
\documentclass[conference]{IEEEtran}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Should be Markdown, but OK.

Eventually, the essentials of requirements engineering include studying the project's particular needs, character of the stakeholders, and tasks to be resolved. By utilizing a combination of the identified methods, requirements engineers can incorporate a more comprehensive approach, thus compensating for the weaknesses of single methods and ensuring the accuracy and dependability of the acquired requirements. Quick and a mixed-method approach of an organization provided it with knowledge of the stakeholder needs at a deeper level thus it helped design the final system that will be close to the expectation and the business goals as defined by the users.


\begin{thebibliography}{00}
Copy link
Collaborator

@deemp deemp Dec 18, 2024

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

References should be in a .bib file so that they're not hardcoded in a particular style in .tex but can be rendered in an arbitrary style.

The objective is to aim at a comprehensive wits of the techniques which are proper for particular projects, several of these will however reflect the needs of the practice people, offering the action-oriented stakeholders a firm foundation for choosing and applying these techniques. This research aims to improve the existing requirements elicitation practices and make them more effective, standardized, and participatory by ensuring that projects are aligned closely with stakeholder needs and expectations from start to finish.


\section{Related Work}
Copy link
Collaborator

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This section lacks references to similar comparisons.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants