SKA's website is modern, but at the same time clear and accessible for its large and diverse audience. We created a full-cycle project for SKA: from pre- project research (we enjoyed studying the KHL regulations the most) to prototyping and SRS. Here we'll also show you one's which have some pictures (we're presenting our project, after all).
First, we profile those users who visit the website the most. Although it is impossible to identify all users, our analytics allow us to identify specific behavioral patterns and create user profiles for both regular and exceptional visitors.
Our other focus was on what users wanted in a website. After round-table brainstorming sessions with our client, we divided user desires into three categories: "must have", "maybe", and "unnecessary". Our final design fully integrated the "must haves", postponed the implementation of the "maybe" features, and ignored the "unnecessary".
It's brass tacks time. At this point we finalized:
1. The entities within the system and their interaction with one another
2. Website structure
3. Content blocks and their priorities.With these decisions made, we moved on to prototyping
Prototype. Requirements specification
In addition to design and development materials, prototype and requirements specifications are an integral part of the prototyping stage . Prototyping provides both questions and answers to questions that are not immediately apparent working with text alone.
The requirements specification comes immediately after prototyping; new ideas, problem solving, and creative insights found during prototyping are not limited by prematurely established specifications.