LinkedInFeeds

Wireframe a Prime part in Design

By
Wire frame using pencil drawings

                                                                                               Why Wireframe is Important?

The timely feedback from the project stakeholders is most important. The early feedback from stakeholders will boost the satisfactory solutions to the problem identified or goal in a project. Never expect anyone to read through hundreds of pages of text only specifications. Instead, the better is to provide any visual representation to which they can refer and react or post any suggestions or comments for better solution which will be delighted and expected for the goal achievement. Wireframes provide an excellent solution to this problem in a web based platform / window based in a designed view of pages / screens.

What is Wireframe?
Wireframes are created for arranging the elements to best accomplish a particular goal or purpose. It mainly explains the page layout or the place / arrangement of website’s content. It mainly depicts the functionality behavioral and navigational elements. Wireframes can be pencil drawings, sketches, whiteboard or produced by any software with defined layout.

Who create Wireframe?
Wireframes are mostly created by business analysts, user experience analyst, developers, visual designers and other roles with expertise in interaction design(GUI), information architecture and user research.

What answers from Wireframe?
 The wireframe answer the following questions
                        i.          What are the elements that will be displayed in the UI?
ii.         What is the placement of elements and how will be the elements organized?
                        iii.        How will the interface look like and work?
                        iv.        How the users interact with the website / application?

           
How it is used in development?
            The business analyst or other title holders mentioned will use this wireframe to design the screens or product as a prototype. The other project teams like design, UX, coding team make use of this for reference and will be used for the deployment as the same.


Tools referred Wireframe:
            The tools that are widely used for wire framing. The tools are needed support for business analyst skills.

            a. Axure
            b. Justin mind prototyper
            c. Balsamiq Mockups
            d. Visio           
            e. Protoshare
            f. Pencil Project
            g. OmniGraffle
            h. Gliffy
            i. Mockflow
            j. Framebox
            k. Iphone Mockup
            l. Justproto
            m. Mockingbird
And finally also don’t forget your Pen and Paper.
Thank you

Comments

Post a Comment

Popular posts from this blog

SpeckBook in requirement elicitation

By
Image
SpecBook Do you know what SpecBook is? It is specifications book. Spec Book - Requirement Elicitation This is traditional method of requirement elicitation technique. This is also widely used now. SpeckBook will contain list of questions about a function, feature or any component. It is a drilled down approach. You should not end this process till no further question can be asked. This can be also said as granular approach. In the SpeckBook, it is not like all questions have to be posted on your client. On basis of discussion and requirement gathering few questions can be answered by you and some questions will answer by itself. The Missed questions can be always posted at client. Questions can also ask to multiple stakeholders to get detailed / required information. Things to look on while preparing the questions a. Questions should be simple and understandable. b. It should be mapped to any of the Business requirements. c. It should not cross the s
Read more

Writing Requirements - Consider Some Points For Success

By
Be specific In Requirements      When stakeholders are be very clear in their need, Business Analyst should not consider that it is final requirement and write it down on paper. There is still more specific in requirements. Ask more questions to business users to make requirements more specific. The other trap is you should identify the correct user to question on requirements. To be more specific, i have stated a below example for better understanding Need identified is : I need a invoice report every month. Other Questions to be asked to stakeholders are : Why you need, When you need, How you need, Which time you need, In which format you need and still more. Drill down to become the requirements more specific. Bring Your Testers Early In project     Every requirement should be testable, reliable. For each requirement translate in to a test case. Quality is very important in meeting the Business need. Success Factors Of A Project     We cannot say provid
Read more