Transcript Requirements Definition and Design Description

Distributed Software Development
2016-04-10
1
Requirements Definition and
Design Description
2016-04-10
2
Contents
•
•
•
•
•
•
•
•
General Project Reqs.
Use Case diagram for LAT.
Various Requirements Groups
Functional & non Functional Reqs.
Abstract view of Architecture
Detailed view of Architecture
User Authentication
End
2016-04-10
3
General project requirements
•
•
•
•
•
•
Visualize transactions
Main graph (clickable and zoomable)
Activity matrix
Zoomed out graph
Search depth, time period, colorful
Highlighted transactions
2016-04-10
4
Use Case Diagram
5
2016-04-10
Requirements Group
• Network Graph (GRP)
• Activity Matrix (ATM)
• Control Panel (CTP)
2016-04-10
6
Funtional Requirements
• Authenticate the User
• Only authenticated users
can access
• Diagram reflects real data.
• Can connect to the database
correctly .
2016-04-10
7
Non Funtional
Requirements(Primary)
•
•
•
•
Usability
Scalability
Maintainability
Graphs different color
2016-04-10
8
Non Funtional
Requirements(Secondary)
•
•
•
•
Testability
Security
Performance
OS is Unix
2016-04-10
9
Architecture Abstract View
2016-04-10
10
System Architecture Description
• Presentation Layer: User Login page is
shown
• Application Layer: Different Graphs and
Matrices are made at Runtime
• Business Layer: Java provides
connectivity to the Database
• Database Layer: Actual SQL queries are
run on the Database.
2016-04-10
11
System Architecture
2016-04-10
12
User Authentication
•
•
•
•
•
User athentication done in php
Username required(of specific length)
Password required(of specific length)
Submit buton
Username and password is checked
against the records in the DB.
2016-04-10
13
User Authentication
2016-04-10
14
Questions If any???
2016-04-10
15