ISP250 SRS - srs report PDF

Preview

Summary

Software Requirement Specification (SRS)SEMESTER MAC – JULAI 2020GROUP: CS1104AMuhammad Adiputra Bin Syafirul Hisyam, 2019362143 Muhammad Arif Irfan Bin Khiruddin, 2019957415 Nurhalim Haikal Bin Ahmad Zulkipli, 2019754779 Muhammad A’fifuddin Bin Rahim, 2019166853Confidential  CS1104(A/B/C/D) 2020So...

Description

Software Requirement Specification (SRS)

SEMESTER MAC – JULAI 2020

GROUP: CS1104A Muhammad Adiputra Bin Syafirul Hisyam, 2019362143 Muhammad Arif Irfan Bin Khiruddin, 2019957415 Nurhalim Haikal Bin Ahmad Zulkipli, 2019754779 Muhammad A’fifuddin Bin Rahim, 2019166853

Confidential

 CS1104(A/B/C/D) 2020



Version: Date:

Software Requirement Specification (SRS)

Table of Contents 1. Overall Description. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 7 1.1 1.2 1.3 1.4 1.5 1.6

Product Perspective. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 3 Product Functions. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 5 User Characteristics. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 Operating Environment. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 General Constraints. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6 References. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 7

2. External Interface Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1 4 2.1 2.2 2.3 2.4

User Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 8 1 3 Hardware Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 3 Software Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 13 Communications Interfaces. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 1 4

3. Functional Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 4 4. Other Nonfunctional Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 4.1 4.2

Performance Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5 Safety and Security Requirements. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 5

Appendix. . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . . 6

Revision History Name

Date

Reason For Changes

Version

Software Requirement Specification (SRS)

Version: Date:

1. Overall Description 1.1 Product Perspective This Shooting Sports Club System is developed to allows athletes in the club to tick their attendance. It is web-based system that displayed their training time and team to athletes but the athletes required to login before get to ticks, and see the details from the database. It aims to ease the athletes to check their schedule of training time anywhere.

Context Diagram

Software Requirement Specification (SRS)



Version: Date:

1.2 Product Functions Admins, instructors and athletes need to login into the system first before continuing to use the system.



Instructor has the ability to update and delete but only on a certain form such as team, attendance, and training. After login this three user will go to dash board to see club feed and news.



Instructors has to key in data for athletes and which team they on , other things is book instrument



from armory and book training session.



Admins give approval of booking from the instructors and generate payment slip for instructors.



If the booking has be approved by the admin ,instructors will proceed the training and the training details will be available for athlete to see.



On the training day, Instructors and athletes has to ticks their attendance.

DFD Diagram

Software Requirement Specification (SRS)

Version: Date:

Software Requirement Specification (SRS)



Version: Date:

1.3 User Characteristics Admins : Login into system to update, delete and view all of the data. The other thing is to generate payment slip for instructor and give approval for instrument that being book by instructor .



Instructor : Login into system. Instructor have to tick attendance, update and delete athlete attendance, team and training. Instructor has to book instrument to use in training and has to book training also after being approved by admins.



Athlete : Login into system. Athlete can tick attendance and view all of their profile, training schedule, team and instrument usage.

1.4 Operating Environment The Shooting Sports Club Information system will be operating in the following environment:a) Device : This software product works on every computer, be it in desktops or laptops. There is no official minimum for hardware requirements that are needed to operate the product. However, we can provide basic requirements in order for the software works smoothly. The basic requirement we recommend is 3gb ram and above, 40 GB of free space or more for hard disk

b) Operating System : The system can be accessed by multiple operating systems, Windows, macOS, Android and other operating systems that have access to the web browser like Google Chrome or any other web browsers.

c) Application : Browsers like Google Chrome, Mozilla Firefox, Microsoft Edge or other browsers are required to access the system. d) Connection : The system use internet as the network for the system. The reason they use internet is because easy for athlete to check their training session and easy for instructor to see their information and payment slip.

e) Platform : The platform of Windows can be in 32-bit or 64-bit. The product works together with “Xampp” to run the databases. This system use HTTP server. 1.5 General Constraints 1) The system can only be accessed by registered account. 2) Admins has the fully control of the system. 3) Training can be proceed only if the admins approve it. 4) Athlete and Instrutor has to tick attendance 5) Users can open this system in the web browser on their phone in order to use it.

Software Requirement Specification (SRS)

Version: Date:

1.6 References

1) C. Tosun, G. Sabırsız, and G. Shaidolda, “Software Requrements Specification,” https://senior.ceng.metu.edu.tr/2016/fixit/SRS.pdf, 2016. [Online]. Available: senior.ceng.metu.edu.tr. [Accessed: 2020]. 2) kavitha S. 17, sadaf J. 19, sasuke J. 13, mojahedul islam J. 15, admin P. authorJ. 15, and shosho M. 15, “Software Requirements Specification document with example,” Krazytech, 17-Oct-2019. [Online]. Available: https://krazytech.com/projects/sample-software-requirements-specificationsrs-reportairline-database. [Accessed: 06-Dec-2020].

Software Requirement Specification (SRS)

Version: Date:

2. External Interface Requirements 2.1 User Interfaces

Wep r o v i d et h es o f t wa r ewi t he a s ya n du n d e r s t a n d a bl eu s e ri n t e r f a c e sf o ro u ru s e r . Ov e r a l l , wewi l lb eu s i n go n l yo n el a n g u a g ef ort h es o f t wa r ewh i c hi sEn g l i s h .Th ep ur p o s eo fi ti s t h a tu s e ra tr a n g eo fa g eb e t we e n10ora b o v ec a nu s et h es o f t wa r ee a s i l y . Th e r ea r e4t y p e s o fi nt e r f a c et h a tweh a dpr o v i d e di nt h ep r o d u c t :    

Ad mi n( a d mi n i s t r a t o r ) Ar mo r y I n s t r u c t o r At h l e t e

1 )Ad mi nI n t e r f a c e Ad mi n i s t r a t o r so ra swec a l l e di ta s“ Ad mi n”a r et h et y p eofu s e r swh oa r er e s po n s i bl e f o ri n s e r t i n g ,d e l e t i n ga n du p d a t i n gd a t ai nt h ed a t a ba s e .I nt h i si n t e r f a c e ,t h eu s e rwi l l h a v et ol o g i nt h es of t wa r eb yi n s e r t i n gt h e i re ma i la n dp a s s wo r d .Fo rs a f e t yp u r p o s e s , t h eu s e rmu s tb ev e r i fie db yo t h e ro rp r e v i o u sa d mi n i s t r a t o r sa n dwi l lb eg i v e nt h ee ma i l a n dp a s s wo r df o rt h e mt ol o g i nt h es o f t wa r e . Th ep i c t u r eb e l o ws h o wst h el o g i n i n t e r f a c ef o ra dmi nu s e r .

Software Requirement Specification (SRS)

Version: Date:

Af t e ras u c c e s sl o g i n ,t h ev e r yfir s tp a g et h a ta p p e a ro nt h es o f t wa r ei st h e“ Da s h b o a r d ” .

Th ema i nf e a t u r eo fi ti s , t h e r ewi l lb eat o t a lo fs e v e nb u t t o n sf o rv a r i o u sf u n c t i o n s . Be l o wa r et h es e v e nb u t t o n sa n di t sf u n c t i o n a l i t y : 

At h l e t ed e t a i l s - Toa d d ,v i e wo rma n i p u l a t ed a t ao fa t h l e t e s .

Software Requirement Specification (SRS)

Version: Date:



I n s t r u c t o rd e t a i l s - Toa d d ,v i e wo rma n i p u l a t ed a t ao fi n s t r u c t o r s .



I n s t r u me n tu s a g e - Tot r a c e ,s e a r c ha n dv i e wt h eu s a g eo fi n s t r u me n t sp e r f or me db ya t hl e t e s .

Software Requirement Specification (SRS)

Version: Date:



Te a md e t a i l s - Toc r e a t e ,s e a r c ha n dv i e wt h et e a md e t a i l s . - Tou p d a t eo rd e l e t eat e a m.



At t e nd a n c e - Tot r a c e ,s e a r c ho rv i e wt h ea t t e nd a n c eo fa t h l e t e sa n di n s t r u c t o r s . - Th ea t t e nd a n c ei sb a s e do nt h e i rp r e s e n c ea tt r a i n i n g .



Tr a i ni n g - Toc r e a t e ,v i e wo rs e a r c ht h et r a i n i n g sma d eb yt h ei n s t r u c t o r s .

Software Requirement Specification (SRS)



Version: Date:

Pa y r o l l s - Tov i e wa n du p d a t ea t h l e t e ’ sa l l o wa n c e . - Tov i e wa n du p d a t ei n s t r u c t o r ’ ss a l a r y . - Tog e n e r a t ea n dp r i nts l i pf o ra n ys pe c i ficp u r p os e s .

Software Requirement Specification (SRS)

Version: Date:

2 )Ar mo r yI n t e r f a c e I nt h i si n t e r f a c e ,i twi l lh a v eo n ema i nf u n c t i o nwh i c hi st h eI ns t r u me ntUs a g e Re c o r d ( I UR) . I URi swh e r ea na r mo r e rwi l lk e e pt r a c kt h ei n sa n do u t so fa l l i n s t r ume n t s .I ti st oma k es u r et h a ta l li n s t r u me nt sa r es a f e l ys t o r e db a c ki n t ot h ea r mo r y a f t e rb e i n gu s e d . 3 )I n s t r u c t o rI n t e r f a c e I nt h i si n t e r f a c e ,t h e r ea r et h r e eb u t t o nsc a nb eu s e df o ri n s t r u c t o r s . Be l o wa r ed e t a i l so f t h eb u t t o n sa n di t sf u n c t i o n a l i t y :   

MyT e a m - Tov i e wo wnt e a md e t a i l s . At t e nd a n c e - Tov i e wt h ea t hl e t e ’ sa t t e nd a n c eb a s e do nt h et r a i n i n gma d eb yt h ei n s t r u c t o r . Tr a i ni n g - Toc r e a t ea n dv i e wt r a i n i n g sma deb yt h ei n s t r u c t o r .

4 )At h l e t eI n t e r f a c e



Version: Date:

Software Requirement Specification (SRS)

I nt h i si n t e r f a c e ,t h e r ea r et h r e eb u t t o nsc a nb eu s e df o ra t hl e t e s .Be l o wa r ed e t a i l so ft h e b u t t o n sa n di t sf u n c t i o n a l i t y :   

MyT e a m - Tov i e wo wnt e a md e t a i l s . Tr a i ni n gSc h e du l e - Tov i e wa t h l e t e ’ st r a i n i n gs c h e d u l e . I n s t r u me n tUs a g eRe c o r d ( I UR) - Tov i e wa t h l e t e ’ su s a g eo fi n s t r ume n tr e c o r d e db yt h ea r mo r e r .

2.2 Hardware Interfaces

Th i ss o f t wa r ep r o d u c twor k so ne v e r yc o mp u t e r , b ei ti nd e s kt o p so rl a p t o p s .Th e r ei sn o o ffic i a lmi n i mu mf o rh a r d wa r er e q u i r e me n t st h a ta r en e e d e dt oo p e r a t et h ep r o d u c t . Ho we v e r , wec a np r o v i d eba s i cr e q ui r e me n t si no r d e rf o rt h es o f t wa r ewo r k ss mo o t h l y . Th e r ea r et wo d i ffe r e ntt y p e so fr e q u i r e me n t swep r o v i d e di nt h et a b l ebe l o wwh i c hi smi n i mu ma n d r e c o mme n de dr e q u i r e me n t s .

Pr o c e s s o r

Mi n i mu m Re q u i r e me n t s 2x1 . 6GHzCP U

Re c o mme n d e d Re q u i r e me n t s 4x1 , 6GHzCPU

RAM

3t o5GBRAM

6t o8GBRAM

HDD Mi c r o s o f tAz u r eVi r t u a l Ma c h i neCo n fig u r a t i on

1 x4 0GBo ff r e es p a c eo rmor e Ba s i cMe d i u m VM

Ba s i cLa r g eVM

2.3 Software Interfaces

I no r d e rt or u nt h es o f t wa r e ,o nemu s th a v eade d i c a t e dc o mp u t e r .Th ep r o d u c two r k s t o g e t h e rwi t h“ Xa mp p ”t or u nt hed a t a b a s e s .Byt h a t ,t hec o mpu t e ro p e r a t i n gs y s t e m mu s tb e a tl e a s tWi n d o wsVi s t a .Th ep l a t f o r mo fWi n d o wsc a nb ei n3 2b i to r6 4 b i t .

2.4 Communications Interfaces

Th ep r o d u c tr e q ui r e sI n t e r n e tc o n n e c t i o ne i t h e rf r o m Wi FiorEt h e r n e tLANc a bl e . I nt e r n e t i sr e q u i r e dt od e l i v e ri n f o r ma t i o nt ot h eu s e r so t he rt h a nt h ea d mi n i s t r a t o r ss u c ha s :     

Ne wsa n da n n o un c e me n t s . Up d a t i n gt e a mn a me , me mb e r sa n di n s t r u c t o r s . Tr a i ni n gs t a t u s . At t e nd a n c e . Pr i n tr e c o r d s ,t a b l e sa n ds l i p s .



Version: Date:

Software Requirement Specification (SRS)



Ge n e r a t ea l l o wa n c e / s a l a r ys l i p .

3. Functional Requirements Functional requirements capture the intended behavior of the system. List the detail of different user/stakeholder functions with specific explanations regarding every function. Users/Stakeholders

Function

Student

Free sign up for user

Student. Lecturer

Login process

Description User able to sign up and create user account without intermediate person to validate the registration process After completing the registration process, user able to log into the information system

Software Requirement Specification (SRS)

Version: Date:

4. Other Nonfunctional Requirements 4.1 Performance Requirements

   

All payment slips will be generated within 1 minute. All requested instrument usage will be approved within 1 minute. Each instrument that has been approved will be given within 15 minutes and must be taken within that time for security reasons. The results of the booking training will be notified whether it is still available or not within 1 minute.

4.2 Safety and Security Requirements

  

User login password will be encrypted using RSA Algorithm before stored in database. User details will not be shown publicly or commercially without user consent. The system will protect sensitive data and allows only authorized access to data.

Software Requirement Specification (SRS)

Appendix

Version: Date:...