Make a use case diagram for Gym Management System and for that system provide vision document and also provide the textual use case description of every use case in the diagram (In points).

Hi Sir/Ma'am! First draw a use case diagram then please provide textual information related to the diagram and then make its vision scope document thorughly. And make sure to add basic information like log in or Registering the customer to the application and then choosing plans and making payments, assigning him his exercises and trainee etc...

 

Textual Information

1. In the user/member module, he can login if already register. If not already registered he/she can get registered.
2. User can view details of all the memberships, trainers, and subscriptions.
3. user can renew his membership too.
4. he can purchase new membership, choose a trainer
5. when decided the new membership he can make payments and it will get verified too from the credit card verification module.
6. He can modify the purchase before the final call ends.
7. he can then view the training session timings
8. enroll in them accordingly.
9. Get notifications/documents via the email server from trainer.
10. In the Trainer module, he can make, postpone and view the sessions and their scheduling. If we want to add the delete session feature we can add that too, then he can view all the details of the members, their fitness etc.
11. In the Admin module, he can maintain all the users account.
12. view user details as well as logs.
13. Display session timings.
14. block and cancel memberships.
15. Credit card verification module will verify the credit details.

    1. VISION DOCUMENT

       GYM MANAGEMENT SYSTEM

       User Requirements:

       The user requirements are given as follows:

    2. Firstly the already registered user will just login with his details, but a new user will have to sign up for his account.
    3. User will have to give the details of their name, contact number and shipping address.
    4. The website must have the feature provided to the user, to search the interested book through title, author or categories.
    5. Then after purchasing the book, if it is available in the store, it will be sent to the shopping cart, then user will be able to pay using credit/debit card.
    6. User must be given the facility to cancel the order, if it is not shipped.
    7. User can modify the order as well.
    8. User can edit the details, by follow the system requirements.
    9. The user can also give feedback to a book by giving ratings on a score of five or ten.
    10. If the user wants to end his session and sign out of the website then he can use the logout option.

    11. In short: A customer can, create, sign in to his account, place items into a shopping cart and purchase using his credit card details.

        System Requirements:

    12. The Main Requirements include Microsoft Visual Studio 2005 and ASP.NET to develop the web application, SQL Server 2005 to design the database and Mozilla as a main web browser to run the website. 
    13. When a user will enter a book name, title or description, the system will display the entire information from the number of books available till the total amount of it.
    14. The system will tell the exact time and date of deliver of the book, and delivery charges as well, most of the time overseas people didn't get this and after receiving the order they had to pay quite an amount which frustrates the customer, so it must be bought into their knowledge earlier.
    15. Our system will manage the entire transactions proficiently.
    16. All the queries of the customer will be entertained my our 24/7 available professional staff, dealing the customer nicely.
    17. If the system gets a request from the user side, it will be entertained in the best possible way.
    18. If the order is not skipped, it will be modified on user demand.
    19. A final shopping cart summary must be displayed to the customer which includes all the items the user has selected and the final total cost. 
    20. Down time of the system will be abruptly notified by our system to the user.
    21. The system shall then display the shipping date, mailing address, projected delivery date, and status (in transit, delivered, etc.)
    22. The system shall allow user to view purchases made with their account within the past years.
    23. The system shall display the date of purchase, expiration date for each order.

    24.  

        Functional-Requirements:

    25. The system shall allow a non-registered user to create a new account and require the following information from the user: Name, Address, Phone Number, email Credit Card information and then ask the user for a username and password and confirm it whether they are acceptable.(Prompt an error msg). And it will store the information in the database.
    26. The system shall allow only registered user to log-in to their account and will take their username and password. The system will verify it, and the user will be considered logged-in.
    27. The system shall allow a user to search for books by title, author, subject, description etc and picture will be display too along with the searches.
    28. The system will allow temporarily save books that are being under consideration for purchase.
    29. When viewing the shopping cart list, the system shall display the total price of the books in the cart.
    30. The system shall allow user to remove/delete and add books into the cart.
    31. The credit card information provided during account registering phase is used for charging the total number of the books in the shopping cart and the user could modify their credit card information if they so desire (before the card is charged). The user will receive a confirmation number.
    32. The books being purchased will be displayed to the screen. final call before the amount is deducted from the card.
    33. The user must enter a confirmation number to view the shipping status of their order.

    34. Non-Functional Requirements:

    35. Flexibility: The system must provide flexibility to the user, so that for the new comer it is easy too grasp the environment of the website.
    36. Reusability: The system must be reusable, if new changes are being added they will be easily accommodated too.
    37. Security: Users will be able to access only their own personal information and not that of other users, and purchases will be handled through a secure server to ensure the protection of user's credit card and personal information.
    38. Reliability: The system must be reliable, minimum chances for system down should be their, in case of system failure backup server must come in action.
    39. Availability: The online book store must be available 24/7 to the user.
    40. Maintainability: Any updates or defect fixes shall be able to be made on server-side computers only.
    41. The System Must not be technical rather it must be Easy to Use.
    42. System login/logout shall take less than 5 to 8 seconds.
    43. Searches shall return results within 10 or 15 seconds.
    44. Orders shall be processed within 10 or 15 seconds.
        1. System shall support approximately 6000 simultaneous users.
           1. Please see the attached file for the complete solution