Text Practice Mode

Designing Interfaces and dialogues

created Feb 1st 2020, 22:42 by Muath Nasr



1653 words
5 completed
- Designing Interfaces and dialogues : User-Focused activity  
- Deliverables and outcomes : creation of a design specification : a typical interface/dialogue design similar to form design but includes multiple forms and dialogue sequence specifications.
- Design include : narrative overview > sample design > testing and usability assessment > dialogue sequence .
- Design dialogues : the sequence of interaction between user and a system : it's involve  
1- the way user can move form one display to another > Building a prototype > assessing usability.
> Three sections of the box: Top-contains : unique display reference number used by other displays for referencing it .
> Middle-contains : Name of description of the display > Bottom : display reference numbers that can be accessed for the current display.
>> InterAction Methods and Devices :  
1- interface : method by which users interact with an information system .
- Methods Of interaction > command line > menu > form > object-based > natural language .
1. Command language interaction : human-computer interaction method users enter statement into a sys to invoke operations (MS , DOS).
2. Menu interaction : a human-computer list of sys options is provided and specific command is invoked by user selection of menu  
3. Pop_up menu: menu-positinoin method that places a menu near the current cursor position .
4. Drop-down menu : menu-positioning that places the access point of the menu   near the top line of the display  
5. Form interaction : human-computer method whereby data fields are formatted in a manner similar to paper-based forms .
6. Object-based : human-computer which symbols are used to represent commands or functions .
7. Icons: graphical pictures that represent specific function within a sys.
8. Natural language : human-computer inputs to and outputs form a computer-based application are in spoken language as English(Siri) .
# Design Interface: use standard formats similar to paper and reports> left-to-right , top-to-bottom > flexibility .#
1- Highlighting : use sparingly : to draw user to or away form certain info  
2- blinking and audible tones : use to highlight critical info required  
3- controlling data input : design to reduce data entry errors  
_Transcripting:  entering invalided data .
_ Transposign : reversing sequence of characters .
>> feedback >>
1- Status info : keep user informed of what's going on when usr has to wait for response.  
2- Prompting cute : tell user when input is needed, and how to provide the input .
3- Error or warning messages : inform user the something is wrong if with dar or sys.
1- Simplicity : help messages should be short and to the point .
2- Organize : Information in help should be easily absorbed by users  
3- Show : it is useful to explicitly show users how to perform an operation.
System Implementation : Too convert final physical system specifications into working and reliable software and document work that has been done and provide help and training for current and future users .
1- Coding : Physical design turned into working computer code by programming team .
2- Testing : are performed using various strategies in parallel with coding to confirm that the system satisfies the requirements ( master test plan during the analysis and and actual testing during implementation .
1. Inspection : Exam The program code for predictable language-specific errors .
2. Walkthrough : a peer group review of any product created during the system develop .
3. Desk checking : a testing technique in which program code is execute manually not by computer by someone who understands the logic code.
4.Unit testing " each module is tested alone to discover any errors in code.
5. Integration testing : process binging together all of the modules that a program comprises for test .
6. System Testing : bringing all of the programs that a system comprises for testing purpose .
7. Stub Testing : a technique used in testing modules and tested in a top-down fashion where few lines of code are used .
3- installation : The current system is replaced by a new system .
1> Direct Installation : changing over form the old system to a new one by turning of the old system when the new is turned on.
2> Parallel installation : running the old information system and the new one at the same time until management decides the old system can br turned off .
3> Single-location installation: trying out an info system at one site and using the new and the another site use the old and when the time will use the new for all .
4> Phased installation : changing from the old info system to the new one incremental starting with one or a few functional components until cover the whole new .
4- Documentation : Two audiences for final document > information systems who will maintain the system > people who will use the system as pf of daily lives .
1> System documentation : info about the system design its internal workings and its functionality .
2> User Documentation : written or visual info about an application system how it works and how to use it .
3> internal document : sys document is  part of the program source code or is generated at compile time .
4> External Document : sys includes the outcome of structured diagramming techniques like data flow and diagrams.
5- Training and supporting suers : support <problem solving and assistance to information users >
- for in-house developed system support materials and jobs will have to be designed as part of the implementations process .
- Potential training topics : > use of the system > General computer concepts > info system concepts > organisational concept > sys management > sys installation.
>> Type of training methods :  
1- Resident expert  2- traditional instructor-led classroom training  3- E-learning , distance learning  4- Blended learning (instructor plus e-learning) 5- software help components .
- Automating support : one approach > internet-based online support forums > on-demand fax > Voice response system > Knowledge bases .
> Help Desk : single point contact for all user inquiries and problems about a particular info sys or for all users in one department .
- requires : technical skill: extensive knowledge about how to use the sys and typical problems that can be solve .
- People skill: good listening and communication dealing with complaints and frustration .
>> support issues : User questions and problems > recovery and backup >> disaster recovery > pc maintenance > writing newsletters > setting up user groups .
6- Project Close-Down :  
> Evaluate team : reassign members to other projects > Notify al affected parties that the development is ending and that you are switching to operation and maintenance mode.
> conduct post project reviews > close out customer contract (Formal signoff).
>> Chapter 4<<
- Analysis : the process in which a sys analyst develops an I=understanding of the problem to be solved and definition of user need  
- Behavuiral and technical info : is gathered concerning goals, process tasks and data requirement for the system  
> Requirement determination involves :
1. Output > electronica/ printed info produced by the sys
2. Input > Necessary data that enters the sys .
3. Process > logical rules that are applied to transform data into meaningful info .
4. Performance > system character (speed ,volume , capacity , availability,reliability).
5. Security > hardware , software , procedural controls that protect the sys and data for treats.
# Sys Analysis Skills :  
- SA requires strong analytical and interpersonal skill to gather reequirements  
- An skill > ability to identify a problem evaluate the key issues and develop solution .
- Interpersonal skill > work with people at all levels able to balance conflicting need .
# Stages in Requirements :
- info gathering : SA & team will taster info about what the sys should do as sources.
- Representation : The info gathered should represent what the sys should do .
- Verification : The representation should be verified with customers and should fit as possible to the request .
# Method to Determining Requirements :  
- Interviewing individuals > interviewing groups (NGT) > Observing workers >document Analysis .
> Nominal Group Technique (NGT): process that supports idea generation by groups .
- Process : Members come together as a group but initially works separately , each person  
Writes ideas  reads ideas out loud and they are written on blackboard or Flipchart  
Idea are prioritied and combined selected reduced.
# Documents : written work procedure or SOP : for an individual or work group Describes how
job performed includes data and info used created process .
# Business form : used for all types of business functions indicates what data flow in and out of a sys
And data necessary for the sys to function give info about nature organisation .
# Reaper : Proimary output of current sys enables you to work backwards for the report to the data needed .
# Description of current info sys user manual .
> Formal sys : the official way a sys works as descried in org document  
> Informal sys : the way the sys actually work (interview ).
>>JAD<< process of bringing together key users , client and developers into the develop process as active  
Participants to collect sys requirement simultaneously for ke people .
_ JAD Participants :1- Session Leader : group process  2/3- Users /Managers: Active speaking    
4- Sponsor:high-level champion 5-6 System anal/ IS Staff : should listen 7-Scribe : Record session .
>> Group support sys : sharing of Idas and voicing of opinions about the sys require .
>> sys prototypes : introductory working version of system to be built .

saving score / loading statistics ...