Information system for fitness centre Tomáš Gazsi Štefan Karabin

Introduction Potential of fitness industry Innovations E-portal Firstly, I would like to welcome you. For our design of IS we chose fitness centrum. It is still being considered as relatively new industry. Lots of gyms have used papers with named lists of members, and still used paper tickets to record attendance. We see that IS brings modernizations into local gyms which has still used old system of recording attendance and communication with members. Using e-portal is great way to reduce installing new expensive software.

Goals Recording attendance Advices of personal trainer Purchase of membership Our IS will be folded with several modules which will provide many elemental functions. Main module should be provide recording attendance, not only members of gym but employee too. Next, what we want to provide is consulting with personal trainer about training plan or tips and tricks how to be beast in gym (how to workout). The last of the main functions is purchase of membership from the comfort of home.

Hardware components Main goal RFID desktop reader RFID tags EPC code Benefits Štefan Main goal of informatin system is recording attendance of members. We decided to use RFID technologoi for identification of members. RFID tag is integreted to plastic card. RFID tags include EPC. This EPC code is captruing by RFID reader. Plastic card provides some marketing benefit.

Three main functions of IS The IS keeps records of members, memberships, training plans, club cards, etc. TheIS records employees' activity Memory Three main functions of IS The IS provides information of attendance to members and to staff The IS provides dashboard for employees The IS informs members about their membership expiration date Informative The IS provides online purchase of membership. . The IS is integrated with RFID readers to capture RFID tags. Active Štefan - 3 main funcitons of IS

Process analysis Functional model Data Flow Diagram Context diagram System diagram Structured analysis contains two types of model Data flow diagram and Entity relationships diagram. For modelling processing architecture we used Context diagram which is part of process analysis. It’s the first level of modelling IS. Then we decomposed Context diagram to get System diagram. It’s case for modelling functional architecture.

In system diagram is main process decompose to more smaller functions, which are more specified. There are, add data storage which were used to generate the ERD diagram.

Data analysis Data model - Entity Relationship Diagram ERD There we can see entities and thier relations. We use primary keys. Cardinality of relations

Object-oriented analysis technical approach for analysing, designing better stakeholder communication and product quality 3 diagrams - characterized structure a behaviour of the system Use Case Diagram Class Diagram Activity Diagram

Use Case diagram Behavior diagram represents the actions that are performed by actors 5 actors Logged off user Logged in user (member) Trainer Employee External payment service <<System>>

Use Case Specification Actor selects the starting date of the membership. The system shows the current offer of membership types. Actor chooses o membership type. The system processes the order and requests the external payment system for payment gateway. Actor is redirected to the payment gateway. The system gets reply about successful payment. The system records a new membership and stores it in the database. Actor is informed about successful purchase.

Class diagram Structure of the system System‘s classes Attributes Methods Relationships singleton that coordinates actions across the system

Activity diagram Behavior diagram graphical representations of workflows Flowchart Actions Decision Start and end node Fork/join swimlanes