g4t6 [Main]
Requirements Specification
Method of requirement engineering: Analysis of scenarios
We thought of different methods for requirement engineering, but finally
we selected this method because we want to focus on the interactions of users with our system.
Method of requirement engineering: Analysis of form
Additionally we used this method for functionalities using forms.
Functional Requirements
Dance schools in Vienna/Austria
We can also use google maps for exact location of the dance schools. Registered users can leave a feedback about their experience in the school
Scenario: Find Dance School (guests)
- go to dance schools page
- search after name of school, district, type of dance or age groups
- display list and display comments
- display location of dance school in google maps
Scenario: Find Dance School (registered users)
- go to dance schools page
- search after name of school, district, type of dance or age groups
- display list
- display location of dance school in google maps
- find the way from users home to dance school (google maps)
Scenario: Add comment about Dance School (registered users)
- go to dance schools page
- search after name of school, district, type of dance or age groups
- display list
- leave comment
Searching dance partner
That's for finding a dance partner for a course or an event.
Scenario: Search dance partner (registered users)
- go to search partners page
- search after:
- gender
- district
- age (min – max)
- height (min – max)
- dance level (min – max)
- knowledge of dancing types (more than one possibility)
- display list
- display details
- contact partner
Scenario: Registration
- go to registration page
- save following info:
- email = username (r)
- password (r)
- name (r)
- surname
- upload picture and downsize to 50 x 100 px
- district (d)
- address
- phone number
- gender (d)
- age (d)
- height (d)
- dance level (d)
- knowledge of dancing types (more than one possibility) (d)
- comment
- publish advert to partner search (checkbox)
(r) required field
(d) required field, is user wants to publish advert to partner search
Scenario: Change personal details (registered users)
- go to registration page
- change personal info (see registration)
Calendar: Balls, Competitions and other events
Registered users can add an event to the calendar.
Optional: Users can subscribe calender - using ical (see «Wikipedia»)
Scenario: Display calendar (guests, registered users)
- go to calenders page
- display current month (default)
- look forward (displaying monthly)
- when event is founded, click to display details
Scenario: Add event to calendar (registered users)
- go to calenders page
- display current month (default)
- click to add new event
- choose colour for event type (competitions, balls, other events)
- save following information:
- name
- date
- comment
- ….
Non-Functional Requirements
Requirements during Process of Development
- Used technologies: PHP
- System requirements: using provided enviroment of course
Runtime Requirements
- Performance, because internet users don't want to wait….: maximum 1 second per page view
- Usability: all pages reachable in maximum 5 clicks
Organizational Framework
- Budget: 0
- Time: Be inline with submission dates of course
Letzte Änderung: 03.11.2009, 17:41 | 483 Worte