0% found this document useful (0 votes)
404 views31 pages

PayTm SRS - Sushant

Sushant Kumar submitted a Software Requirements Specification for course CSE:320 at Lovely Professional University. The 31-page document includes a declaration, synopsis, functional and non-functional requirements, use case diagram, class diagram, data flow diagram, activity diagram, flow chart diagram, test cases designed, and screenshots from modeling tools. The SRS provides details on the software requirements for a course project.

Uploaded by

Sushant Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
0% found this document useful (0 votes)
404 views31 pages

PayTm SRS - Sushant

Sushant Kumar submitted a Software Requirements Specification for course CSE:320 at Lovely Professional University. The 31-page document includes a declaration, synopsis, functional and non-functional requirements, use case diagram, class diagram, data flow diagram, activity diagram, flow chart diagram, test cases designed, and screenshots from modeling tools. The SRS provides details on the software requirements for a course project.

Uploaded by

Sushant Kumar
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 31

Software Requirements Specification

Course Title: Software Engineering | Course Code: CSE:320

Submitted by:

Sushant Kumar

Registration No: 12218023

Programme Name: B.Tech. CSE

Under the Guidance of


Jatinder Kaur

School of Computer Science & Engineering


Lovely Professional University, Phagwara

S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 1 | 31
DECLARATION
I, Sushant, declare that this SRS report, titled Software Requirements
Specification, is solely prepared by me as a requirement for CSE:320 at Lovely
Professional University. The report is based on my original work and represents
my own efforts, ideas, and analysis.

I further declare that the guidance provided by my instructor, Jatinder Kaur, was
instrumental in shaping my understanding and analysis of the subject matter.
However, the final report and its contents are my own and do not reflect the
views of Lovely Professional University or any other organization.

I take full responsibility for the accuracy and authenticity of the information
presented in this report. I have cited all sources and references used in this
report in accordance with the guidelines provided by my instructor and the
academic standards of Lovely Professional University.

I understand that any act of plagiarism or academic misconduct may result in


severe consequences, including the revocation of my academic degree, and I
affirm that I have not engaged in any such activities.

Signed:
Sushant

Date:

S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 2 | 31
Software Requirements Specification
Synopsis On

Sushant Kumar

Scan to get the PDF.

S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 3 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 4 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 5 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 6 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 7 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 8 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 9 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 10 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 11 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 12 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 13 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 14 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 15 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 16 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 17 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 18 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 19 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 20 | 31
S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 21 | 31
Use Case Diagram

S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 22 | 31
Class Diagram

S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 23 | 31
Data Flow Diagram

S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 24 | 31
Activity Diagram

S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 25 | 31
Flow Chart Diagram

S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 26 | 31
Test Case Designed

S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 27 | 31
Screenshot – Use Case Visual paradigm

Screenshots – Sequence Visual paradigm

Sequence

S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 28 | 31
Screenshot - Class Visual paradigm

Screenshots – Activity Visual paradigm

S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 29 | 31
Screenshots – Data Flow Visual paradigm

S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 30 | 31
Thank You

S u s h a n t K u m a r | h t t p s : / / e n a l l y . i n / f i l e s - m a n a g e r / C S E 3 2 0 - S R S | P a g e 31 | 31

You might also like