A.L. Lohvinenko

Kharkov national university of radioelectronics

Analysis of requirements for web-based system of student’s achievements accounting for sports team in swimming

Software requirements consist of three layers - the business requirements, user requirements and functional requirements. Moreover, each system has its non-functional requirements.

Business requirements include a high-level goals of the organization or customers of the system.

User requirements describe the goals and objectives that will enable users to solve the system. The distinctive ways of presenting this kind of requirements are use cases. Functional requirements define the functionality of the software developers need to develop so that users can perform their tasks within the business requirements. Functional requirements describe what the developer wants to implement.

Sports school - extracurricular school sports profile. In the organizational structure of school sport involving administration and coach.

Currently there are no web-based accounting student achievement sports schools, so it is necessary to create such a system. Development of the system needs to identify the requirements for potential users and data processing capabilities.

All potential users can be divided into four groups: school administration, coaches, students and unregistered users.

Consider the functional model of the system and list its functions:

- insert, store, edit, and view information of teams, coaches, students, and news;

- users authentication;

- the possibility of changing student’s group;

- ability to view and edit the sport diary notes;

- training schedule formation;

- viewing, editing of swimmer’s cards;

- forming application forms for the competition;

- formation visiting swimmers accounting;

- forming tasks for each training session;

- reporting control starts;

- formation of competitions results/

The system will be able to give answers to the following questions:

- the list of coaches in sports school;

- what is the latest results from a given student;

- which competitions were held over a specified period of time;

- view of the results dynamics for given student;

- what students in different groups have similar results;

- what is the coach of this age group;

- membership a given group;

- the movement of students between groups.

Use case diagrams describe the functionality of the system, or what the system must do. Swimming section pupil has a smaller features for the system interacting and all the available features for pupils are shown in Figure 1.

Figure 1 – Use-case for pupils

The functions of school sports administrators can be formalized with the use case diagrams, which is shown in Figure 2.

Figure 2 – Use-case for administrator

The use cases for user of category "trainer" is shown in Figure 3.

Figure 3 – Use-case for trainers

Unregistered users can browse the news, a list of coaches and training schedule.

Defined functional requirements allow us to go to the stages of design and software implementation of web-based system for accounting sporting achievements of section swimming pupils.