Scribd
Upload
91 views1 page

GUI Requirement Gathering

The document outlines the typical sections and contents of a thesis, including an abstract, introduction, literature review, objectives, tasks completed in the project, testing results, analysis, conclusion, and references. It provides examples of tasks that could be included such as requirements gathering, user analysis, task analysis, UI design and implementation including tools used and code fragments, and testing including usability and acceptance testing. The analysis section may cover consistency, shortcuts for frequent users, feedback, dialog closure, and error handling.

Uploaded by

Jyotsna Suraydevara
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
91 views1 page

GUI Requirement Gathering

The document outlines the typical sections and contents of a thesis, including an abstract, introduction, literature review, objectives, tasks completed in the project, testing results, analysis, conclusion, and references. It provides examples of tasks that could be included such as requirements gathering, user analysis, task analysis, UI design and implementation including tools used and code fragments, and testing including usability and acceptance testing. The analysis section may cover consistency, shortcuts for frequent users, feedback, dialog closure, and error handling.

Uploaded by

Jyotsna Suraydevara
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

I have read both the drafts and the following are my observations:

The sub-tasks of your assigned work seem to be independent except the


communication with the backend. See that there is no overlap between your tasks:
In general, the Thesis contents shall be:
 Abstract
 Introduction
 Literature Review
 Gaps in the existing works
 Objectives you are addressing and
 Mainly the tasks you have done in your project:
Ex:
 UI Requirement Gathering - To have list of all functional and non-functional
requirements of UI. This can be taken from user and their existing software solution.
 User Analysis - Studies who is going to use the software UI. The target audience
matters as the design details change according to the knowledge and competency level
of the user. If user is technical savvy, advanced and complex UI can be incorporated.
For a novice user, more information is included on how-to of software.
 Task Analysis - To analyze what task is to be done by the software solution. Here in UI,
it does not matter how it will be done. Tasks can be represented in hierarchical manner
taking one major task and dividing it further into smaller sub-tasks. Tasks provide goals
for UI presentation. Flow of information among sub-tasks determines the flow of UI
contents in the software.
 UI Design & implementation - After having information about requirements, tasks and
user environment, design the UI and implements into code and embed the UI with
working system. It is then self-tested by the developers.
Tools used and the fragments of the code/algo can be given.
 Testing - Organization can have in-house inspection, direct involvement of users and
release of beta version are few of them. Testing may include usability, compatibility,
user acceptance etc
The results for various test cases can be given
The analysis shall include the points such as:
 Strive for consistency ,Enable frequent users to use short-cuts -,Offer informative
feedback ,Design dialog to yield closure , Offer simple error handling
 Conclusion and future work
 References.

You might also like