Tải bản đầy đủ (.pdf) (40 trang)

fpt events management software requirement specification

Bạn đang xem bản rút gọn của tài liệu. Xem và tải ngay bản đầy đủ của tài liệu tại đây (2.37 MB, 40 trang )

<span class="text_page_counter">Trang 1</span><div class="page_container" data-page="1">

<b>FPT Events Management Software Requirement Specification </b>

Project Code: SWR302G2 Document Code: SE1609G2

<b>Ho Chi Minh, 08/10/2022</b>

</div><span class="text_page_counter">Trang 2</span><div class="page_container" data-page="2">

<b>RECORD OF CHANGE</b>

*A - Added M - Modified D - Deleted

<b>Effective Date </b>

<b>Changed Items A* M, D </b>

<b>Change Description New Version </b>

08 0/20/1 22 Initial A Add project overview 11/10/2022 Purpose, scope, use

case, use case detail

A Add 12 use case detail, purpose, scope

15/10/2022 Use case detail M Modified the use case detail 25/10/2022 Supporting information M Modified the heading to exact format 25/10/2022 Use case detail A, M Add 1 use case detail, overal

description,

</div><span class="text_page_counter">Trang 3</span><div class="page_container" data-page="3">

Nguy n Tu n Tú - SE160917 (Member) ễấ

<b>REVIEWERS: </b>Lại Đức Hùng (Lecturer)

<b>APPROVAL: </b>

</div><span class="text_page_counter">Trang 4</span><div class="page_container" data-page="4">

<b>TABLE OF</b>

<b> CONTENTS </b>

</div><span class="text_page_counter">Trang 5</span><div class="page_container" data-page="5">

Students always have difficulty in finding events that suit their time and needs. Information about the event was dispersed everywhere: FAP, Club Page, FPT Around, FPT University HCM. Event usually planned in short period of time, therefore students are often easily missed out on interesting events

Besides student's difficulties, event creators (students, lecturers, clubs) also face many difficulties reaching out to students. Although the content is good, there is no marketing strategy. They also have problems in handling event documents and applying for funding from superiors

Realizing the problem, FPT Event was founded with the goal of connecting students, event creators and administrators to each other, making it easier for students to find events. Students can look for events that they find attractive. Furthermore, FPT Event is a service-providing platform; we aim to provide not only event, but also convenience in procedures and accompanying utilities and services

<b>1.2. Project scope and limitations 1.2.1.Major features </b>

<b>FE01: Authentication and Authorize FE02: Event Management FE03: StudentManagement FE04: Registration Management FE05: System Handler </b>

<b>1.2.2.Limitations & Exclusions </b>

LI-1: only developed for FPT University campus HCM, not working for other campuses. LI-2: only people of FPT University (student, lecturer, staff) can use the system, people from outside can not join.

LI-3: Mobile application does not have admin function LI-4: The system does not support events with ticket fees

</div><span class="text_page_counter">Trang 6</span><div class="page_container" data-page="6">

<b>1.3. Definitions, Acronyms, and Abbreviations </b>

Staff Users who have permission to create, edit, view registration list of event

Manager Users who have permission to approve/reject event, view registration list of event

Admin Users who have permission to manage system, user, event Event The event entity uploaded to FPT Event system, created by staff

● Group Name : SE1609G2

● Software type : Web Application, Mobile Application ○ 1.5.2 Project Team

<b>a.Supervisors </b>

Lại Đức Hùng Lecture

</div><span class="text_page_counter">Trang 7</span><div class="page_container" data-page="7">

06be-BM/PM/HDCV/FSOFT v1/1 7/40

<b>b.Team Members </b>

Võ Ng c Trúc Lam ọ 0928 192 718 Leader Huỳnh V n Phú ạ 0398 550 944 Member Nguyễn Thanh Bình 0906 332 948 Member Nguyễn Tuấn Tú 0909 710 750 Member Võ Minh M n ẫ 0392 511 912 Member

</div><span class="text_page_counter">Trang 8</span><div class="page_container" data-page="8">

○ General users (student): Use the system to view information about FPT events and choose to bookmark, attend those events and check in. These people have a basic understanding of using mobile apps.

○ Staff: Use the system to create an event for the variety purposes: academic, culture, art, music, marketing, etc. These people have a basic understanding of how to use the website.

○ Manager: Use the system to view the event detail, approve/reject event. ○ Administrators(departments): Use the system to view, reject or accept the events as well as view statistics on items related to the platform. These people are the ones who know the best about the system and the business rules to be able to administer it. These people have a basic understanding of how to use the website.

</div><span class="text_page_counter">Trang 9</span><div class="page_container" data-page="9">

06be-BM/PM/HDCV/FSOFT v1/1 9/40

<b>3.FUNCTIONAL REQUIREMENT </b>

3.1. Use Cases Diagram

Use Case Diagram - FPT Event Management

3.2. Use Case Detail 3.2.1. Search Event

</div><span class="text_page_counter">Trang 10</span><div class="page_container" data-page="10">

<b>USE CASE 1 SPECIFICATION </b>

<b>Use-case Name </b> Search Event

The system will return a list of events that matches the keyword or return a list of all

<b>events if no result matches, and display it into the screen. Triggers </b>

The actor wants to find some suitable events to view or register that have name match keyword. Actor inputs keyword in search textbox, then <b>presses Enter</b> or <b>clicks on the “Search” button. </b>

<b>Preconditions: </b>

● The actor has access to the system.

<b>Post Conditions: </b>

<b>● The input keyword must not be empty. </b>

● The keyword must be contained in Event Title or Event Description of existing Events in the system.

<b>Main Success Scenario: </b>

</div><span class="text_page_counter">Trang 11</span><div class="page_container" data-page="11">

06be-BM/PM/HDCV/FSOFT v1/1 11/401 <sub>Actor types keyword into search </sub>

System shows a list of events that match what the actor requires. [Exception 1]

<b>Alternative Scenario: </b>

N/A

<b>Exceptions: </b>

1 Keyword not found. System inform “Sorry! We can not find any result that matches the keyword.” and display a list of all events that existed in the system.

2 Keyword is empty. System not allow the actor searches an event with an empty keyword. The system will not forward the page, nor activate the search function

<b>Relationships: </b>

N/A

<b>Business Rules: </b>

● The keyword must not exceed 50 words.

● The keyword should be found in Event Title or Event Description.

● The default values of fields of sorter are: Recent events, and paging each page 10 events.

3.2.2. Bookmark Event

</div><span class="text_page_counter">Trang 12</span><div class="page_container" data-page="12">

<b>USE CASE 2 SPECIFICATION </b>

<b>Use-case Name </b> Bookmark event

<b>The actor wants to save the event to a wishlist in order to read it later. Actor clicks </b>

on “Save to wishlist” button to trigger the Bookmark event function.

<b>Preconditions: </b>

● The actors has logged in by student/lecture account.

<b>Post Conditions: </b>

● Actor must not have saved this event to wishlist before.

<b>Main Success Scenario: </b>

1 In event detail page of a particular event, actor clicks on “Save to Wishlist” button.

The system adds this event into that actor’s wishlist and inform the result on the screen. [Exception 1]

</div><span class="text_page_counter">Trang 13</span><div class="page_container" data-page="13">

1 That event has been saved to the actor’s wishlist.

System inform “Save failed! You have saved this event into your wishlist.”

3.2.3. Register For Event

<b>USE CASE 3 SPECIFICATION </b>

<b>Use-case Name </b> Register for event

</div><span class="text_page_counter">Trang 14</span><div class="page_container" data-page="14">

This feature allows actors to send their information to the manager to register for events so that they can <b>attend</b> events at FPT University.

<b>Main Success Scenario: </b>

1 - In the event detail page of a specific event, the actor clicks on the “Register For Event” button.

- System display a confirmation up on the screen: “Do you really want to register for this event?”

pop-2 - Actor clicks on the “Yes” button of the confirmation pop-up.

- Actor clicks on the “No” button of the confirmation pop-up.

- System adds the actor’s information to the Registrants List of that event.[Exception 1] - System adds that event to “My

Registered” list of that actor. [Exception 2]

- System inform “Register for this event successfully!”

- System close the confirmation up.

<b>pop-Alternative Scenario: </b>

N/A

<b>Exceptions: </b>

1 The actor has not filled out all necessary information in his/her profile.

- The system informs “You have to fill out all required information in your profile”. And then redirect to the Profile Page.

2 The actor has registered for this - The system infom “You have

</div><span class="text_page_counter">Trang 15</span><div class="page_container" data-page="15">

06be-BM/PM/HDCV/FSOFT v1/1 15/40event already. registered this event already.”

<b>USE CASE-4 SPECIFICATION </b>

</div><span class="text_page_counter">Trang 16</span><div class="page_container" data-page="16">

<b>● The request of event has been created successfully and send request to staff Main Success Scenario: </b>

11 Actor clicks on “Request event” button System displays a form with field: ● Name: text input ● Location: text input ● StarTime: datetime input ● EndTime: datetime input ● RegistrationEndTime: datetime

input

● Description: text input ● Category: select input ● EventImage: image input ● Document: file input

2 <sub>Actor fill information and clicks on </sub>

‘Request’ button <sup>System validate and and create a new </sup>event request and show message [Exception 1,2,3]

<b>Alternative Scenario: </b>

N/A

<b>Exceptions: </b>

1 The actor has not filled out all necessary information in his/her event.

The system informs “You have to fill out all required information in your create event form”. And then redirect to the Edit Event Page.

2 The actor enter RegistrationEndTime after StartTime

The system informs “Registration end time must be before Start time”

3 The actor enter StartTime after EndTime

The system informs “Start time must be before End time”

<b>Relationships: </b>

N/A

</div><span class="text_page_counter">Trang 17</span><div class="page_container" data-page="17">

06be-BM/PM/HDCV/FSOFT v1/1 17/40

<b>Business Rules: </b>

● All fields must not be empty. ● Name events must not exceed 50 words. ● Document file must be compressed in rar or zip file.

3.2.5. Create event

<b>USE CASE-5 SPECIFICATION </b>

</div><span class="text_page_counter">Trang 18</span><div class="page_container" data-page="18">

<b>Step Actor System Response </b>

1 Actor clicks on “Create new event” button

System displays a form with field: ● Name: text input ● Location: text input ● StarTime: datetime input ● EndTime: datetime input ● RegistrationEndTime: datetime

input

● Description: text input ● Category: select input ● EventImage: image input ● Document: file input

2 <sub>Actor inputs information that need to </sub>

be edited and clicks “Create” button <sup>System validate and and update </sup>information of event and show message [Exception 1,2,3]

<b>Alternative Scenario: </b>

N/A

<b>Exceptions: </b>

1 The actor has not filled out all necessary information in his/her event.

The system informs “You have to fill out all required information in your create event form”. And then redirect to the Edit Event Page.

</div><span class="text_page_counter">Trang 19</span><div class="page_container" data-page="19">

06be-BM/PM/HDCV/FSOFT v1/1 19/403.2.6. View registration list

<b>USE CASE-6 SPECIFICATION </b>

<b>Main Success Scenario: </b>

</div><span class="text_page_counter">Trang 20</span><div class="page_container" data-page="20">

1 Actor clicks on “View registration” button of specific event of the event list

System shows screen contains list of students that registered to the event

</div><span class="text_page_counter">Trang 21</span><div class="page_container" data-page="21">

06be-BM/PM/HDCV/FSOFT v1/1 21/403.2.7. Reject Event

<b>USE CASE 7 SPECIFICATION </b>

</div><span class="text_page_counter">Trang 22</span><div class="page_container" data-page="22">

<b> The manager to make sure about the content of the event Triggers </b>

Admin click to button “Deny”

<b>Preconditions: </b>

1. The actor has logged in by a staff account or manager account 2. Receive information about the event

<b>Post Conditions: </b>

The events will be denied and notification to student who send the request

<b>Main Success Scenario: </b>

1 Receive the form about the

event <sup>Form includes information of the event </sup>● Name ● Location

● Start Time ● End Time ● Registration ● Description ● Category ● eventImage ● document

2 Click the Button “Deny” to deny the event

Manager will check the content and the purpose of the event is comfortable with the students

or have any problem

3 Write into the textbox about the reason why it have been denied

The Manager will write the reason and send to Staff

<b>Alternative Scenario: </b>

</div><span class="text_page_counter">Trang 23</span><div class="page_container" data-page="23">

06be-BM/PM/HDCV/FSOFT v1/1 23/40 N/A

</div><span class="text_page_counter">Trang 24</span><div class="page_container" data-page="24">

<b>USE CASE-8 SPECIFICATION </b>

The Manager or Staff accept the event after check and don’t have any problem

<b>Main Success Scenario: </b>

</div><span class="text_page_counter">Trang 25</span><div class="page_container" data-page="25">

06be-BM/PM/HDCV/FSOFT v1/1 25/40

1 Receive form about the event Form includes information of the event ● Name

● Location ● Start time ● End time ● End time registration ● Description ● Category ● eventImage ● document

2 Click to the Button “Accept” Manager will check the content and the purpose of the event is comfortable with the students or have any problem

3 Write the message to the Staff in the textbox (if have)

Manager want to notice the important information

4 Set day, time ,place into the general timetable

Manager want another student don’t register the event should be duplicated

</div><span class="text_page_counter">Trang 26</span><div class="page_container" data-page="26">

3.2.9. View Request Detail

<b>USE CASE 9 SPECIFICATION </b>

</div><span class="text_page_counter">Trang 27</span><div class="page_container" data-page="27">

06be-BM/PM/HDCV/FSOFT v1/1 27/40

1 Admin click in Manage Staff The System will show all Staff’s detail 2 Admin click in taskbar “Search” and

type the name Admin want to search

The System will show the Staff Admin want

</div><span class="text_page_counter">Trang 28</span><div class="page_container" data-page="28">

3.2.10. Get Account List

<b>USE CASE-10 SPECIFICATION </b>

</div><span class="text_page_counter">Trang 29</span><div class="page_container" data-page="29">

06be-BM/PM/HDCV/FSOFT v1/1 29/40

<b>Main Success Scenario: </b>

1 <b>Admin Click on the Account </b>

3.2.11. Get Event List

<b>USE CASE-11 SPECIFICATION </b>

<b>Version </b>

1.0

<b>Use-case Name </b> Get Event List

</div><span class="text_page_counter">Trang 30</span><div class="page_container" data-page="30">

<b>Date </b> 26/10/2022 <b>Priority </b> Low

1 Manager: Click on the Staff Management Button

Show all the list of Event Information

</div><span class="text_page_counter">Trang 31</span><div class="page_container" data-page="31">

06be-BM/PM/HDCV/FSOFT v1/1 31/403.2.12. View Account Detail

<b>USE CASE-12 SPECIFICATION </b>

</div><span class="text_page_counter">Trang 32</span><div class="page_container" data-page="32">

<b>Step Actor System Response </b>

1 Admin clicked on the Button displayed text “Account Management”

Show The Account List information

<b>Alternative Scenario: </b>

● N/A

<b>Exceptions: </b>

1. User Missing: Admin type the wrong id on location href

Send a error message that Student not Exist

<b>Relationships: </b>

● Account Management

<b>Business Rules: </b>

● N/A

3.2.13. Remove Event Request

<b>USE CASE-13 SPECIFICATION </b>

</div><span class="text_page_counter">Trang 33</span><div class="page_container" data-page="33">

● The request will in the event request list and still still not processed by staff.

<b>Main Success Scenario: </b>

1

Student clicks on the Button displayed

<b>text “Remove Request”. </b> <sup>System will show a dialog with the </sup>message ”Are u sure u want to delete?”

<b>tep </b>

<b>Student SystemResponse</b>

</div><span class="text_page_counter">Trang 34</span><div class="page_container" data-page="34">

1 <sub>Student clicks </sub>on the “Cancel” button to

<b>confirm dialog. </b>

<b>Exceptions: N/A Relationships: </b>

N/A

<b>Business Rules: </b>

N/A

3.2.14. Check In

<b>USE CASE-14 SPECIFICATION </b>

</div><span class="text_page_counter">Trang 35</span><div class="page_container" data-page="35">

<b>1 </b> <sub>Student clicks the button </sub><b>“QR code”. </b>

System shows QR code for check-in.

<b>2 <sub>Student scans the QR code. </sub></b> System will show the message “Check in successfully”. [Exception 1]

<b>-Alternative Scenario: </b>

N/A

<b>Exceptions: </b>

1 Student has a wrong QR code. System will show the message “Check-in failed”.

<b>Relationships: </b>

N/A

<b>Business Rules: </b>

</div><span class="text_page_counter">Trang 36</span><div class="page_container" data-page="36">

● The QR code will be invalid immediately after the event ends.

3.2.15. View Registration List

<b>USE CASE-15 SPECIFICATION </b>

● Registration List is displayed with additional pagination.

<b>Main Success Scenario: </b>

</div><span class="text_page_counter">Trang 37</span><div class="page_container" data-page="37">

06be-BM/PM/HDCV/FSOFT v1/1 37/40

<b>1 </b>

Student clicks on a specific register item on the register list shown on the “Register

management list” screen.

The system show a table to view detailed information of the register.

<b>Alternative Scenario: </b>

N/A

<b>Exceptions: </b>

<b>1. </b> Student has a bad connection. <sub>System forwards to Lost Internet page. </sub>

</div><span class="text_page_counter">Trang 38</span><div class="page_container" data-page="38">

<b>4.NON-FUNCTIONAL REQUIREMENTS </b>

<b>4.1. Usability ● Learnability: </b>

Mobile and Web UI/UX follows Material Design to be convenient and easy for use. All text, label and message should be uniformly written in Vietnamese or English.

<b>Maintenance access: 2-3 times a week </b>

Degraded operation: show an information that server is in maintenance

<b>Mean Time Between Failures (MTBF): 1.5 days (this will keep the web service almost </b>

always available so no one will concern about the web is inactive for too long)

<b>Mean Time To Repair (MTTR): 1 days (this time is enough to keep the server maintenance </b>

to find the bug and fixed the web)

<b>Accuracy: 95% (The 5% is the many types of number statistic such as people registered, </b>

users, active users,… from the numerous users accessing the web at the same time. This will keep the server performance in a good pace)

<b>Maximum Bugs or Defect Rate: 3 bugs/function-point (some user will see this is a unique </b>

feature of the web and they probably liked it)

<b>Bugs or Defect Rate: minor (the web is still usable) </b>

<b>4.3. Performance </b>

1. Response time is equal to or less than 03 seconds for each request.

2. The system always responds to Student clicks in less than one tenth of a second.

</div>

×