Forms Design Interface Design
4.5.2 Forms Design
Forms are usually used for input when a workstation is not available. It is sometimes used as a turnaround document. The following are the steps in designing forms. Forms Layout Guidelines 1. Instructions should appear on the form except when the same person fills it over and over again. General instructions are placed on top. They should be brief. Specific instructions should be placed just before the corresponding items. 2. Use familiar words. Avoid using not, except and unless. Use positive, active and short sentences. 3. The answer space should be enough for user to comfortably enter all necessary information. If the form will be used for a typewriter, 6 or 8 lines per inch is a good measurement. For handwritten answer spaces, 3 lines per inch with 5 to 8 characters per inch is a good measurement. Software Engineering 171 J.E.D.I 4. Use the following guidelines for typefaces of the fonts. • Gothic • Simple, squared off, no serifs • Easy to read, even when compressed • Capital letters are desirable for headings • Italic • Has serifs and a distinct slant • Hard to read in large amounts of long letters • Good for printing out a work or phrase • Roman • Has serifs but does not slant • Best for large quantities • Good for instructions 5. Lower case print is easier to read that uppercase. However, for small font size, they should not be used. Use upper letters to call attention to certain statements. Developing the Form Layouts STEP 1: Define the standards to be used for designing forms. An example of a standard for defining forms is listed below. • Paper size should not be bigger than 8 12” x 11”. • Colors Schemes • White copies goes to the applicant. • Yellow copies goes to the club staff. • Pink copies goes to the coach. • Important data should be positioned on left side of document. • Dates should use DDMMYY Format. • Logos are only used for all externally distributed documents. • Heading should include Page Number and Title. • Binding should use 3-hole paper. • Ruling should follow 3 lines per inch. STEP 2: Prepare Form Samples. Using the standard format defined in step 1, design the layout of the forms. Redesign if necessary. Software Engineering 172 J.E.D.I4.5.3 Screen and Dialog Design
Parts
» | Komputasi | Suatu Permulaan
» Quality Focus Process Method Tools
» What is quality? How do we define quality?
» Software Quality Characteristics of a Well-engineered Software
» Software Quality Assurance Activities Formal Technical Reviews
» Types of Software Process Models
» Understanding Systems | Komputasi | Suatu Permulaan
» End-users Understanding People in the Development Effort
» What is documentation? Criteria for Measuring Usability of Documents
» Abstraction Encapsulation Review of Object-oriented Concepts
» Modularity Hierarchy Review of Object-oriented Concepts
» Project Assignment Object-oriented Process Model
» Modeling Activity Unified Modeling Language UML
» UML Baseline Diagrams Unified Modeling Language UML
» Requirements Engineering Concepts | Komputasi | Suatu Permulaan
» Inception Requirements Engineering Tasks
» Elaboration Negotiation Requirements Engineering Tasks
» Specification Validation Requirements Engineering Tasks
» Management Requirements Engineering Tasks
» Scenario Modeling Requirements Analysis and Model
» Requirements Model Validation Checklist
» InvoiceNumber : Numeric Here, an attribute named InvoiceNumber contains a numeric value.
» Ternary association which is a relationship of three or more objects of
» The Analysis Model Analysis Model Validation Checklist
» Requirements Traceability Matrix RTM
» Requirements Metrics | Komputasi | Suatu Permulaan
» The Design Model Design Engineering Concepts
» Describing the Package Diagram Developing the Architectural Design
» Software Architecture Validation Checklist
» Developing the Data Design Model
» Report Design Interface Design
» Forms Design Interface Design
» Basic Component Design Principles Component-level Design Guidelines
» Component Diagram Developing the Software Component
» Project Assignment Design Model Validation Checklist
» Mapping the Design Deliverables to the Requirements Traceability Matrix Design Metrics
» Creating the Data Design Model Creating the Interface Design Creating the Control Design
» Project Assignment Programming Standards and Procedures
» Using Pseudocodes Control Structure Guidelines Documentation Guidelines
» Implementing Packages | Komputasi | Suatu Permulaan
» Abstract Classes Implementing Controllers
» Interfaces Why do we use Interfaces?
» Interface vs. Abstract Class Interface vs. Class Creating Interfaces
» Relationship of an Interface to a Class Inheritance among Interfaces
» Implementing Java Database Connectivity JDBC
» AWT GUI Components Implementing the Graphical User Interface
» Layout Managers Implementing the Graphical User Interface
» Controlling the Version of the Software
» Introduction to Software Testing
» White-Box Testing Techniques Software Test Case Design Methods
» Black-Box Testing Techniques Software Test Case Design Methods
» Testing your Programs | Komputasi | Suatu Permulaan
» Test-driven Development Steps Test-driven Development Methodology
» Testing Java Classes with JUnit
» Testing the System | Komputasi | Suatu Permulaan
» Mapping the Software Testing Deliverable to the RTM Test Metrics
» Project Assignment Software Project Management
» Problem Identification and Definition
» The Project Team Structure Project Responsibility Chart
» Project Work Breakdown Structure WBS
» Work Breakdown Schedule Format
» Size-oriented Metrics- Lines of Codes LOC Function-Oriented Metrics: Function Points FP
» Project Estimations | Komputasi | Suatu Permulaan
» The Risk Table Risk Management
» Risk Identification Checklist Risk Management
» Baseline Software Configuration Tasks
» Writing the Project Plan Project Assignment Case Tools
Show more