Name the five steps in user interface design? Why is iteration so important? Bri

Question

Name the five steps in user interface design? Why is iteration so important? Briefly explain Storyboard, HTML Prototype and Language Prototype as Interface design Prototyping. Which prototyping technique (s) will work best if analyst want to be closer to the final version of interface design? As a system analyst, you are required to redesign the interface for the ATM at your local bank. Develop two use scenarios for Authentication and Withdrawing Cash from ATM activity. Case study: Ahmad is an analyst. The human resources department is very unhappy with their payroll package. They want the information systems department to write them a new package as they think they have unique needs. What should Ahmad do? Design an Interface Structure Design for the ATM at your local bank that shows how a user would navigate among the screens.

Explanation / Answer

Question4

1. Find what you want to achieve

The most vital goal for any UI-user interface should be to fit in smoothly with the product and company branding. Embedded software is a significant touch point for any brand, so it’s imperative that it is consistent with the rest of the product, and the company’s image.

2. Understand the target user

The user interface should firstly be fit for purpose. By this we mean, ‘does it do what the user will want/need it to do?’.

This doesn’t necessarily mean it should be easy or intuitive. There are plenty of successful software kits, such as Photoshop or AutoCAD, that are definitely not easy or intuitive for first-time users. However, they are packed full of necessary functions and features for professional power-users that, once they are trained and well-practiced, become exactly what they want and need.

Therefore, it’s incredibly important that we fully understand who the typical users are, and how their knowledge, experience and needs affect the way they use the product. Are the users old or young? Are they used to using technology on a day-to-day basis? Are they looking for a quick solution or an in-depth system? Do they mind having to read lengthy instructions?

These are the questions that should be asked about the typical user base, to ensure that the interface is appropriate for them.

3. Create prototypes and undertake A/B testing

Providing prototypes for our clients means that they are able to see and test out a tangible element of the project and provide us with feedback for future development. However, it would require a lot of time to provide an initial prototype for the software as a whole, so we use vertical slicing to provide samples of certain features instead.

4. Provide iterations to gain feedback

Working with embedded software user interfaces is very different to computer or application UIs, because we don’t usually have the option of continuous delivery and regular software updates once the product is in the hands of the users. For this reason, we use a variety of testing methods and release software iterations at the end of each sprint (2 to 3 weeks) to the client.

While we usually recommend a firmware update system, these updates should be implemented early on in the project, which is why we try to get as much feedback as possible each time. We encourage regular feedback loops with each of our team members, our clients’ team members, the end users, and the customer service/tech support operatives, so that we can understand a variety of different user journeys and issues that could arise. As well as this, we always want to get feedback from our clients’ Marketing department, to ensure that the interface integrates smoothly with the company’s brand.

5. Take the product the market

Using Lean-Agile methodologies, our goal is to adapt rather than predict, which is difficult with embedded systems running on circuit boards and digital displays, as by nature they aren’t very flexible. Therefore we want to avoid Complaint Driven Development, which can be caused by taking the product to market too soon, so we aim to get as much feedback as we can during development. It is only when the iterations receive purely positive feedback do we suggest taking it to market.

Question 5

Storyboarding

This process of simulation uses sketches on paper of the screen layout for individual screens and explains the linking through arrows.

Advantages

Disadvantages

HTML Prototype

This simulation uses web pages designed either directly in HyperText Markup Language (HTML) or indirectly by using another software package which produces the HTML coded pages for viewing via an Internet browser.

Advantages

Disadvantages

Language Prototype

This simulation process uses programming language, such as Visual Basic, to create a prototype of the new system. This language is often the programming language used to develop the final system. Users can navigate through the screens but often no data is actually processed.

Advantages

Disadvantages

Related Questions

Navigate

• Browse (All)
• Browse N
• Subjects

---

---

Integrity-first tutoring: explanations and feedback only — we do not complete graded work. Learn more.