Note: The article's name should be simply 'nsICookieMonster' but is not in order to make it more obvious this is an example. Also, you should add the 'Interfaces' tag to your article, as well as 'Interfaces:Scriptable' if the interface is scriptable. Implemented by: @mozilla.org/cookie-monster;1. To create an instance, use: var cookieMonster = Components.classes'@mozilla.org/cookie-monster;1'.createInstance(Components.interfaces.nsICookieMonster); Method overview void (in cookieToEat); AString (in integer number); void (in AString language); Native code only! Void ; Attributes Attribute Type Description favoriteCookie integer The cookie monster's favorite kind of cookie. Must be one of the constants defined under on this page.
HungerLevel integer A value from 0-100 indicating how hungry the cookie monster is. 0 means 'stuffed to the brim with cookies' and 100 means 'I'm so empty of cookies! Feed me now!' Name The cookie monster's name.
Constants Cookie flavor constants Constant Value Description COOKIEFLAVORSUGAR 1 Simple sugar cookie. COOKIEFLAVORCHOCOLATECHIP 2 Chocolate chip cookie.
COOKIEFLAVORPEANUTBUTTER 3 Peanut butter cookie. COOKIEFLAVORDOUBLECHOCOLATE 4 Chocolate cookie with chocolate chips. COOKIEFLAVOROTHER 0 An unknown type of cookie. Yumminess constants Constant Value Description COOKIENOTYUMMY 1 The cookie is disgusting. COOKIESORTOFYUMMY 2 The cookie is good but not awesome.
COOKIEEXTREMELYYUMMY 3 The cookie is really, really yummy. COOKIEOMGYUMMY 4 OMG THIS IS THE BEST COOKIE EVAR!1!!1. Methods eatCookie Feeds a cookie to the cookie monster. Void eatCookie( in nsICookie cookieToEat ); Parameters cookieToEat The cookie to eat.
GetFunnySaying Returns a string containing a funny quote the cookie monster might say. AString getFunnySaying( in integer number ); Parameters number The saying number to return. Return value An containing the requested funny quote. If the specified quote number is invalid, an exception is thrown. Exceptions thrown NSERRORFAILURE Unable to locate the requested quote. Native code only! SayYummy Says something appreciative of the tastiness of the cookie in the specified language.
Void sayYummy( in AString language ); Parameters language The localization identification indicating the language in which the cookie monster is to express his love of cookies. Sing Sings the song 'C is For Cookie.' Void sing; Parameters None. Remarks Remember, this isn't a real interface. This is where you would provide additional information about the interface as necessary.
See also.
User Interface Specification Templates User Interface Specification Templates We have created two types of templates for user interface specifications, a style template and a content template. The style template determines the appearance of the document.
The content template describes its content. The templates have been produced in Microsoft Word 97. Microsoft Word is not the best document creation system available.
It has a number of shortcomings. Technical communicators generally prefer Adobe FrameMaker. We have chosen Microsoft Word for these templates because it is more widespread. We hope to add FrameMaker templates sometime in the future. Style Template You can download the style template as a Word 97 document file: The document illustrates the various style tags.
In order to use the document as a template, delete the content of the document and save it as a template:. From the Edit menu, choose Select All to select the entire contents of the document. Press Delete to delete the contents. From the File menu, select Save As.
The Save As dialog appears. At the bottom of the Save As dialog in the Save as type combo box, choose Document Template (.dot) to save the document as a template. Select the Save button.
Ui Templates Free
In order to use the template, you can either select it in the New dialog when you open a new document or you can attached it to an existing document. To attach the template to an existing document, from the Tools menu choose Templates and Add-Ins.
In the Templates and Add-Ins dialog attach the template as Document template. The template is already attached to the content template discussed in the next section.
So you can simply use the content template. To define the style of a paragraph-like piece of text, place the text cursor somewhere in the text and select a style.
![]()
You can select a style in either of two ways:. Select a style in the Style combo box which is located on the right side of the Formatting toolbar. From the Format menu, choose Style. In the Style dialog, select a style from the Styles list and select Apply. Content Template You can download the content template as a Word 97 document file: The content template describes the various sections of a user interface specification. Its format has been developed over a number of projects.
To use the content template, simply save it under a different file name, remove the descriptions in each section, and start entering your design specification.
Download, a a, or as a. Participatory design (and initial design in general) tends to be done at a low degree of resolution.
The typical document consists of hand-drawn screens or mock-ups. At some stage, the design must be converted to a format that is more formal, and better suited for use by developers and others. Moving from mock-up to a formal document encourages the design team to consider proposed solutions in more depth. Providing a formal specification also minimises the need for developers to second-guess design decisions.
Example Spec Document
How to Write a Painless Product Requirements Document by Jerry Cao. While the bulk of documentation is produced in the earlier stages, the implementation stage is one of the most crucial phases of the UX design process. While you do a lot of concepting during the research, analysis, and design phases, it’s now time to get to the heavy lifting. We understand that documentation doesn’t always equal a product, so that’s why we’ll just explore the essentials. In this piece, we’ll look at ‘s product requirements document as a best practice and explain how to make it work for you. Follow along, then use our. The Anatomy of the Product Requirements Document Once you get to the “Build It” phase, the previous research and prototyping should give your team a high-level understanding of your product.
All companies are different, so some stages of product development can happen simultaneously (instead of sequential). Regardless, you should be able to ask any 5 team members about the overall purpose, features, release criteria, and timeline for the product and they should give you roughly the same answer. In today’s Lean and Agile world, the PRD may be trimmed down (or simply represented by a prototype) so we’ll focus on just the core elements.
The PRD is the heart of your product and serves as a living document for any designer, developer, or stakeholder to understand the status and purpose of the product. As illustrated above, failure to document requirements can lead to wildly different assumptions. Because there’s been debate around theas well as, the PRD helps balance the design team’s focus on usability and aesthetics against engineering’s functional concerns. The product curation company Product Hunt shows that a PRD — just define the problems the product will solve with a general description of features (and plenty of mockups from previous stages). The technical details should be saved for the FSD. Source: According to Ben Horowitz and David Weiden, both notable venture capitalists, and should be the product Bible for marketing, design, and engineering. Good product managers not only keep PRDs up-to-date on a daily or weekly basis, but they view the entire PRD process as ongoing — the document is never truly complete, it simply evolves as the team iterates.
Marty Cagan, Partner at the Silicon Valley Product Group, explains — defining purpose, describing features, setting release criteria, sketching rough timing — which we’ve adapted for our purposes below. According to Cagan, the PRD’s goal is to explain the “What”, not the “How”. In each section, remember to be clear on the problem being solved versus the solution otherwise you may lead the team to make incorrect assumptions. The engineers, designers, and UX folks are the ones designing solutions for the product — don’t piss them off by making the PRD a recipe rather than a guideline.
Define the Product Purpose Make sure you discuss the user problems (not solutions) that must be addressed, the target demographic (companies, customers, users) and various use cases for each demographic. Ms money & ms works 2004.iso. While this has probably been discussed to death before, it’s important to reiterate them during as you build the product otherwise it might get lost in the development shuffle. What separates a top 1% product manager from a top 10% product manager is understanding that the, so forget the marketing jargon and only talk about “Why?”, “Who cares?”, and “So What?”.
Describe the Product Features The features section is the body of the PRD. Features must be described with regards to the interaction design and user experience to give engineering the most flexibility. More importantly, you must map features to product objectives (known as requirements traceability) so that the business impact can be clearly understood if someone cuts a certain feature during development. Will also help you prioritize in case there’s scheduling shifts or you discover some features should be replaced as you progress in development. To learn more about how some of today’s most successful companies prioritize features, check out the. Outline the Release Criteria How will you know the product is ready to release for beta testing?
While this section can be the most technical of the PRD, we still are just describing goals — not a means to achieve them. You’ll want to outline criteria in these five areas:. Functionality — Is there a baseline percentage of the original features that must be retained? What are the absolute mandatory functions?. Usability — Is the program aesthetically striking and intuitive to users?
What is the acceptable time to complete tasks for each use case?. Reliability — What’s the maximum acceptable failure rate? Are these failures predictable? Can the system recover from these failures?. Performance — How fast must it be? What is the maximum response time, throughput, and memory consumption?.
Supportability — Is it testable, serviceable, installable, and configurable? It’s important to, iterate, and formalize them as you approach the build stage. These should be reviewed and agreed by stakeholders during the early stages of development. Otherwise, if you wait, you might just set the bar at wherever the product currently stands. Grab design ebooks created by best designers All for free.
Do you want to know more about UI Design? Download 'Designing UX With Developers' FOR FREE! State the Constraints & Establish a Schedule Excruciating over exact timing is dangerous since. Instead, a rough window provides flexibility while helping to better avoid feature creep since it sets stakeholder expectations. In addition, writing down any workflow constraints (for example, budgeting or resources) can also provide a more accurate picture of the factors affecting timing.
With both the constraints and rough date in writing, you have a more informed way to work backwards from the end date and assign realistic sprint lengths to each feature. Use What Works and Scrap the Rest Building your product is an ongoing process and the last thing you probably want to do is throw more paperwork into your sprints. Source: But a certain level of documentation is necessary to keep some order in all the chaos. It doesn’t need to be exhaustively detailed, but it should provide some idea of what exactly everybody is building. User requirements coming from product management needs to be translated.
Dependencies among different technical entities have to be understood. And internal and external testing feedback must be captured to justify changes. In between all this, you’ll need to answer stakeholder questions like “How is everyone staying on the same page?” and “How will we realize our goals in the set time limit?” The product requirements document is just another helpful reference point as you prepare for the ultimate product test — your launch date.
Download your created by a product manager with 10+ years experience. Found this useful?
Contents. Purpose The UI specification is the main source of implementation information for how the software should work. Beyond implementation, a UI specification should consider usability, and limits.
![]()
A UI spec may also be incorporated by those within the organization responsible for, and. As future designers might continue or build on top of existing work, a UI specification should consider constraints in order to assist the implementation team. The UI specification can be regarded as the document that bridges the gap between the product management functions and implementation. One of the main purposes of a UI specification is to process the product requirements into a more detailed format. The level of detail and document type varies depending the needs and design practices of the organizations. The small scale prototypes might require only modest documentation with high-level details.
In general, the goal of are to describe what a product is capable of, whereas the UI specification details how these requirements are implemented in practice. The process Before UI specification is created, a lot of work is done already for defining the application and desired functionality.
Usually there are requirements for the software which are basis for the use case creation and use case prioritizing. UI specification is only as good as the process by which it has been created, so lets consider the steps in the process: Use case definition Use cases are then used as basis for drafting the UI concept (which can contain for example main views of the software, some textual explanations about the views and logical flows), these are short stories that explain how the end user starts and completes a specific task, but not about how to implement it. The purpose of writing use cases is to enhance the UI designer understanding of the features that the product must have and of the actions that take place when the user interacts with the product. Design draft creation The UI design draft is done on the basis of the use case analysis. The purpose of the UI design draft is to show the design proposed, and to explain how the user interface enables the user to complete the main use cases, without going into details. It should be as visual as possible and all the material created must be in such a format that it can be used in the final UI specification. (This is good time to conduct or and make changes.) Writing the user interface specification The UI specification is then written to describe the UI concept.
The UI specification can be seen as an extension of the design draft that provides a complete description that contains all details, exceptions, error cases, notifications, and so forth. The amount of detail provided depends on the needs and characteristics of the development organization (scope of the product, culture of the organization, and development methodology used, among others).
Usually, the UI concept and specifications are reviewed by the stakeholders to ensure that all necessary details are in place. Structure Having a formal structure for a UI specification will help readers anticipate where they can find the needed information to interpret the specifications correctly. Example structure of the UI specification may contain, but not limited to, following items:.
Change history. Open issues. Logical flow. Display descriptions. Error and exception cases The specific contents will vary to be appropriate to the organizational needs (another example is Nokia's UI Specification structure ). Change history Having an informative change history helps the reader to see what, when and why something was changed.
A UI specification quite often changes during implementation. Open issues Possible open issues. While there are unclear or open issues, those can be visible.
Logical flow The logical flow can be used to give high-level view of how different screens in the user interface relate to each other to support a task. Flow can reveal for example number of required steps to perform certain task.
Display descriptions The display description contains the screen contents and information about available functions. The screen contents may be wireframes, screen-shots of a prototype, or UI mock-ups.
A picture of the user interface state will provide a quick overview. Wireframes are recommended over high resolution graphics. Free employee handbook template microsoft word.
Caution should be taken in providing too polished a picture as details might change and time and resources have to be allocated to redraw pictures. Additionally, readers may become distracted into commenting on visual design elements such as color choice and images that were intended to be placeholders and not reflective of the final product.
In addition to a picture of the display, access points should be listed and the fields and controls on the screen should be described. The following table gives a list of the bare minimum you should be describing: Element Description Comment Label Label on the screen if the element has no label, number it and refer to it by number Description Describe the element its type (input, drop-down,calendar), what it does, etc. Default value what the field defaults to if no value is provided May not be applicable for every type of screen Values List boundary conditions or error conditions i.e., Dates must be in the past, integer numbers from 1 to 100 Error and exception cases Indicates how to display information regarding any network issues or other events that require error indications to user. References.
Comments are closed.
|
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |