Rapid Prototype Blog

Posts Tagged ‘requirements’

Hi, I am having a tough time finding out anything in any easy way to describe each step of Software Development Process for an assignment of mine and time is running out FAST!!…
I would be most greatful to anyone out there that can possibly shed some light on this project.
Many thanks in advance.
X C.

Hi, I am having a tough time finding out anything in any easy way to describe each step of Software Development Process for an assignment of mine and time is running out FAST!!…
I would be most greatful to anyone out there that can possibly shed some light on this project.
Many thanks in advance.
X C.

Hi, I am having a tough time finding out anything in any easy way to describe each step of Software Development Process for an assignment of mine and time is running out FAST!!…
I would be most greatful to anyone out there that can possibly shed some light on this project.
Many thanks in advance.
X C.

Hi, I am having a tough time finding out anything in any easy way to describe each step of Software Development Process for an assignment of mine and time is running out FAST!!…
I would be most greatful to anyone out there that can possibly shed some light on this project.
Many thanks in advance.
X C.

Hi, I am having a tough time finding out anything in any easy way to describe each step of Software Development Process for an assignment of mine and time is running out FAST!!…
I would be most greatful to anyone out there that can possibly shed some light on this project.
Many thanks in advance.
X C.

The requirements editor

The requirements editor is composed of four main parts or functional groups: the search box, the actions toolbar, the requirements list and the requirement details. The default view of the requirements editor contains a list of all the requirements of the wireframe. The list display the properties code, version, name, type, author, last modification date and related component. If a requirement has more than one version, only the last is displayed.

Bind text requirements to wireframe elements

You can find a requeriments pane below the canvas of the “User Interface” section. This pane provides the tools to bind requirements to wireframe elements. In order to bind a requirement to a wireframe element you can use one of the following methods:

Create a requirement and drag and drop the requirement to the wireframe element. Select the wireframe element and then create the new requirement.

Advanced features of text requirements

Requirement versions.Existing requirement versions can not and must not be modified. Thus, any changes to a requirement lead to a new version being created. Once you have made some changes to the properties of a requirement, you must click the “New Version” button to save these changes as a new version in the current requirement. Changes can not be saved in the current version. To use an old requirement version as active version, select it in the list and click “Activate” in the requirement details zone.

Display a wireframe element from a requirement.Click on the “View Element” button to jump to the related element of the particular requirement, opening the pertinent editor and displaying the element.

Specifications document generation

Justinmind Prototyper generates Microsoft Word documents containing relevant information about the wireframe. Moreover, one may easily create a template in Microsoft Word to fully customize and adapt the documents outputted by the Justinmind Prototyper.

Have you ever created an early project plan, or a simple wireframe — maybe to get approval for the project — only to find it unworkable when you started tracking progress? With the right start, you can ensure that the plan you create at the beginning of your project is an effective management tool throughout the project.

The first step is to understand all the requirements. In this stage, you’ll need to gather everyone involved in conceptualizing what’s going to be done, and write that down. You can draw a simple wireframe and sketches of the final project too.

Business Analysts and Project Managers are vital for this, and also Key Users, to understand what they need and want from the final product. We recommend a team of 5 people maximum, to avoid empty discussion and eternal meetings.

They’ll get together and write the first list of requirements needed, as much detailed as it can be. The Requirements list will be a briefing of the project, for developers, designers and coders.

Understanding the audience

The users of the projects must be studied. The usage, too. How people will use it is very important and can decide the success or fail of any development project. It is very important that your project is useful and severs a purpose for your selected audience.

People are not equal, and not everyone use software or websites the way you do. It’s important to step on the users’ shoes and understand their thinking, needs and values. After all, they are the ones who’ll use it.

This is why we recommend to have key users involved in the planning phase, and, if it may be, future or potential users.

Creating killer content

It is very important to think about what really interests people and how will they react to what you are offering them. Earning peoples’ attention is normally a one timer: if they don’t get interested in the first time, it’s probable they won’t be a second one. So, think about your users and amuse them.

Designing for human beings – help people

Some people just cannot focus enough on design, on thinking how form and function interact and how people interact with them. There are several unconscious and sub-conscious elements that can change users’ perceptions about a website or a program, and simply helping them find the specific button, or understanding how the program works, or even simpler: having the application have a pretty look. The design can improve a lot with the use of wireframes. Nowadays, there’s no excuse for having a poor looking app.

Technology – it cannot be possibly done

We all know the story of the beetle that cannot fly, according to aerodynamic laws. However, sometimes project fail because someone thinks that creating something is possible, or can be easily done, but actually takes too many work hours or too many people involved or some technology that’s not currently available to all. So, it’s very important to plan everything and discuss with technicians and experts to understand what’s going to be done.

Project Management – following the plan

Even when we get a map, sometimes we get lost. Why? Because somewhere during the travel, we forgot to keep track of where we were. This is to show how important it is to control the evolution, the iteration cycles, the steps and accomplishments. They’ll avoid the feeling of being completely lost, of not knowing where you are and how you got there in the first place.