Andy rated it liked it Oct 06, John rated it really liked it Sep 24, Amy rated it did not like it Aug 29, Evamarie added it Feb 13, Rod Hilton added it Oct 01, Panayiotis added it Oct 31, Beck added it Feb 18, Prem Kumar marked it as to-read Feb 02, Jenn marked it as to-read Oct 16, Lili marked it as to-read Jun 14, BookDB marked it as to-read Oct 01, Andy added it Nov 22, Wayne marked it as to-read Aug 12, Vinoth is currently reading it Jan 23, Nikom marked it as to-read May 10, Measure: Number of deviations per screen.
What to measure. Reqs: At most one deviation per screen. Pros: Adherence helps users switch between systems. Company-specific guidelines for internal systems can help even more. Cons: Cannot guarantee high usability. Developers find guidelines hard to follow - examples help best.
Development, early Ease of remember. Development, late Understandability Subjective satisf. Score for underst. Slides for Chapter 2 November Fig 2. Analysis Traditional systems Design development Experts?
Usability test? Test Scaring results! Too late to correct Operation. D3 When you select a certain date, why Minor Hit does the list show earlier dates too? D8 Doesn't understand why the list Medium becomes empty made a spelling error problem D9 Believes the task is complete when she Task failure sees the guest on the list. D10 Doesn't understand that the Stay screen Task failure Task must be opened. Heuristic evaluation: 7 false problems 21 predicted problems 8 likely, but not observed.
Hand-drawn Tool-drawn mockup: mockup: min min. Full contents of a mockup Handling a system Empty screens for copying with screens? Screens with realistic data Screens to be filled in by user Menus, lists, dialog boxes Accelerator effect: Error messages If the central screens are good, Help texts the rest are okay Notes about what functions do almost automatically.
Open navigation menu. Close suggestions Search Search. User Settings. Skip carousel. Carousel Previous. Carousel Next. What is Scribd? Explore Ebooks. Bestsellers Editors' Picks All Ebooks. Explore Audiobooks. Bestsellers Editors' Picks All audiobooks.
Explore Magazines. Editors' Picks All magazines. Explore Podcasts All podcasts. Difficulty Beginner Intermediate Advanced. Explore Documents. A Software Engineering Perspective. Uploaded by Nalog Razno. Document Information click to expand document information Description: Power point. Original Title A software engineering perspective. Did you find this document useful? Is this content inappropriate? Report this Document. Description: Power point. From United Kingdom to U.
Ships from the UK. Published by Addison-Wesley , Item is in good condition. Some moderate creases and wear. This item may not come with CDs or additional parts including access codes for textbooks. Photos are stock pictures and not of the actual item. Seller: 3rd St.
Books , Springfield, MO, U. Soft cover. Very good, clean, tight copy. Text free of marks. Professional book dealer since All orders are processed promptly and carefully packaged. Used - Softcover Condition: UsedAcceptable.
Condition: UsedAcceptable. Published by Addison-wesley, Seller: Anybook Ltd. There are many rules for when leave is possible, whether vacation is allowed, etc. The user interface deals with all these complexities, is efficient to use, yet elegant.
The main screen shows all data, much of it on embedded tab-sheets. The top part shows a timeline of who has leave or vacation. A column indicates how much leave has been used and how much leave is planned. When there are several employers, each of them has a tab-sheet. Tabs are also used in case of more than one father or more municipalities. The screen at the right is part of Britt's paper prototype.
Britt designed a full paper prototype and usability-tested the entire user interface with several mothers, several employers, several officials and several iterations. She wrote and handed in the project report 92 pages. Next she presented the whole thing for the software house that had strugled with the project and challenged her.
They didn't believe what they saw. How long had she worked on this? Answer: 5 months - that is what a thesis project allows. It turned out that 40 developers in the software house had worked on the project for two years - without designing a single user screen. Furthermore, they had given up on serving all the parties in a maternity case parents, employers and municipalities.
In contrast, Britt had designed the system in such a way that all parties could see the same screens and tabs. This was convenient when parties discussed on the phone. However, for privacy reasons, some information was hidden to some of the parties.
The Virtual Windows method was a key part of the solution, and Britt wrote her thesis in such a way that other developers could see how the method worked in this complex case. Microsoft-Access Tutorial Soren Lauesen, version 2. Students learned to make great user-task descriptions, data models, user interface mockups and usability testing.
However, they never tried to implement the database and the user interface. Many tools would be involved to do this in a professionel way. It dawned to me that MS Access was the only tool that could do it all. However, it was hard to learn. Existing documentation wasn't suited. The result was an Access tutorial to be used at the course. It uses a hotel reception system as an example. We tried it in three semesters, but the conclusion was that it was too much to squeeze into one semester.
Furthermore, technology had moved on to html, etc. However, for many years the Access tutorial was the most downloaded document on the IT-University's web-site.
And I still get requests for help from people using the advanced parts of the tutorial. Unfortunately, we still have a gap: There are no other textbooks for teaching implementation of real user interfaces based on a real database.
Furthermore, programming teachers cannot design user interfaces, and UX teachers cannot program.
0コメント