User interface design, Software Engineering

Assignment Help:

Develop a detailed design to support the use case specified in the accompanying document: ‘ Asg2 . (Hint: Follow the process for use case realization and develop analysis class Use Case Specification' and sequence diagram describing the use case before adding the details of UI interactions.) 

a. List as many requirements for the user interface as you can, without assuming anything about the implementation technology.

b. Design a graphical user interface to support the use case, using a standard set of graphical ‘widgets' such as those supported in .NET or Java Swing. Present this as either a screen shot of a GUI prototype, or a ‘storyboard' or ‘wireframe' diagram illustrating the interface. Ensure that you take account of Norman's principles in your design, and accompany your design with a brief explanation as to how your design reflects these principles.

c. Draw a state diagram modelling the behaviour of the high level class representing the user interface. In an accompanying table, identify what GUI elements are active, and what actions are possible in each state.

d. Draw a sequence diagram illustrating how the control class for the use case interacts with the UI and entity classes to support for the use case for the normal flow. Make sure this diagram is consistent with the state diagram developed for part c.


Related Discussions:- User interface design

Software availability, Software Availability: In the present day conte...

Software Availability: In the present day context, software suppliers have realised the potential demand and also the special requirements of library and information professio

What are the advantages of software maintenance, What are the advantages of...

What are the advantages of Software maintenance Software maintenance is a very broad activity which includes error correction, deletion of obsolete capabilities, enhancement of

How many types of traceability in software engineering, How many types of t...

How many types of traceability in software engineering? i. Source traceability - These are generally the links between requirement to stakeholders who suggests these requiremen

FTR., Formal technical review in railway reservation system

Formal technical review in railway reservation system

Define the structural testing, Q. Define the Structural Testing? For a ...

Q. Define the Structural Testing? For a moment it called white-box testing. At this point derivations of test cases are according to the program structure. Knowledge of the pro

Joomla, want to learn joomla

want to learn joomla

Name the commonly used architectural styles, Name the commonly used archite...

Name the commonly used architectural styles. i. Data centered architecture. ii. Data flow architecture. iii. Call and return architecture.

Explain throw-away prototyping, Throw-Away Prototyping: Also known as clos...

Throw-Away Prototyping: Also known as close ended prototyping. Throwaway or Rapid Prototyping refers to the formation of a model that will eventually be discarded rather than beco

Explain acceptance testing and beta testing, Q. Explain acceptance testing ...

Q. Explain acceptance testing and beta testing? Acceptance Testing as well as Beta testing: System tests are designed to authenticate a fully developed system to guarantee th

Write Your Message!

Captcha
Free Assignment Quote

Assured A++ Grade

Get guaranteed satisfaction & time on delivery in every assignment order you paid with us! We ensure premium quality solution document along with free turntin report!

All rights reserved! Copyrights ©2019-2020 ExpertsMind IT Educational Pvt Ltd