Statement how you as Software Interface Engineer will collect/Elicit Requirements related to the Interaction design of different users? Research Different Collection Techniques for requirements only related to the Interface Design and development. Hints: In this assignment you will search related to the different techniques associated with software interface design for the users.
Eliciting Requirements:
In
this process we actually determine, the actual requirements of the customer.
Create a proposal what will be the system do. Create documents about the
system. It also describes the functions of the system, interface design like
UI/UX etc.
This usually includes 4 types of major requirements:
·
What users will
requires who related to this tool.
·
Based on the
business requirements for the specific company.
·
Demands about
the software including functional and non-functional requirements of the
system.
Why we need to Eliciting Requirements:
With
the help of a suitable example I will explain why its requires the most in
software development process:
If
you visit any institute and you used its system and its software, after that
you like all the functionality and the interface of the system, and you have
visited any website of any institute, you want same.
So how you achieve the
actual result. You can only achieve the actual result if you describe these:
Why we need to Eliciting Requirements:
With
the help of a suitable example I will explain why its requires the most in
software development process:
If
you visit any institute and you used its system and its software, after that
you like all the functionality and the interface of the system, and you have
visited any website of any institute, you want same.
So how you achieve the actual result. You can only achieve the actual result if you describe these:
Most common Eliciting Techniques:
These
are the most commonly used to gather data for any software, to complete the
effective tool as well. Explain in detail one by one.
Interview:
Conduct
interview before starting the project is always essential, this is how we
gather the background information, what system used before and what changes
requires the most.
Brainstorm:
Create a rough draft after conduct the interview,
like not down the major keywords and major functionality, or write down whatever
comes in mind after interview.
Focus group
After brainstorm short all these points, just
extract the most essential elements require for the software. focused group
only includes the stakeholders.
Requirements
workshop:
Conduct more and more workshops
for it, do little work and did practical for it as well, by doing practical
after short steps save time, fix error, because fixing error at the end is
better than fix it on each step by testing it.
Prototyping:
It includes the final version of the software which
is going to developed or design. It also includes ideation, evolution and user
feedback.
Interface analysis
Examine system components. Overall interface test is
it actually fulfills the requirements, the interface which shows to the end user.
User interface analysis
User interface analysis incudes the features
requires for the end user, easy to use, easy to understand easy to access, easy
to work on it, and is it actually guide the user by giving a hint
Survey and questionnaire:
Prepare few questions about the system, and conduct it from different users of different age, different areas, and different levels to better know the working of the software for the stakeholders.
Documentation analysis
In this process it’s the most essential technique in
which we examine at the end, what details we write on the documents while
gather the information from the stakeholders using different phases.
0 comments:
Post a Comment