Professional Documents
Culture Documents
LinkedIn SRS
LinkedIn SRS
Specification
For
1. Introduction.......................................................................................................................... 1
1.1 Purpose............................................................................................................................ 1
1.2 Document Conventions.................................................................................................... 1
1.3 Intended Audience and Reading Suggestions...................................................................1
1.4 Definitions, acronyms, abbreviations................................................................................ 1
1.5 Scope……………………………………………………………………………………
3
2. Overall Description.............................................................................................................. 3
2.1 Product Perspective.......................................................................................................... 3
2.2 Product Features............................................................................................................... 4
2.3 User Classes and Characteristics....................................................................................... 5
2.4 Operating Environment.................................................................................................... 5
2.5 Design and Implementation Constraints...........................................................................5
2.6 Assumptions and Dependencies........................................................................................ 7
3. Specific Requirements.......................................................................................................... 7
3.1 Functional Requirement................................................................................................... 7
3.2 Requirements of the bank computer for the ATM…………………………………… ………..11
4. External Interface Requirements...................................................................................... 13
4.1 User Interfaces............................................................................................................... 13
4.2 Hardware Interfaces....................................................................................................... 13
4.3 Software Interfaces......................................................................................................... 14
5. Other Nonfunctional Requirements.................................................................................. 14
5.1 Performance Requirements............................................................................................. 14
5.2 Safety Requirements....................................................................................................... 14
5.3 Security Requirements.................................................................................................... 14
5.4 Software Quality Attributes............................................................................................ 15
6. Other Requirements........................................................................................................... 15
7. Design………………………………………………………………………………………..
8. Test cases……………………………………………………………………………………..
Page 1
1. Introduction
LinkedIn is the world's largest professional network with hundreds of millions of members, and
growing rapidly. Their mission is to connect the world's professionals and growing students to
make them more productive and successful. It can help you:
1.Establish your professional profile and control one of the top search results for your
name.
2.Build and maintain your professional network.
3.Find and reconnect with colleagues and classmates.
4.Learn about other companies, and get industry insights.
5.Find other professionals in the same industry using groups.
6.Share your thoughts and insights through LinkedIn's long-form publishing platform.
7. Tap into the knowledge of your network.
8.Discover new career opportunities by searching for jobs.
1.1 Purpose
Font: TNR 11
Users who should have the basic Knowledge of computers and internet in order to perform
tasks and who wishes to read about what this project can do. User can access only the
services given by the Admin. End users can also go through this document to know what
basically this application can do.
Administrators should have the basic Knowledge of computers and Visual Basic in order to
perform tasks. An Admin can access to any users profile whereas a user cannot access
neither to admin’s profile nor to any other users profile.
Developers who can view project’s abilities and can easily understand to add more features
for future development.
1.4.1 Definitions
1.4.2 Abbreviations
IP - Internet Protocol
OS – operating system
To connect the world's professionals to make them more productive and successful,” and
because the business is a for profit company, the main objective of the LinkedIn application is for
the business to make a profit based on our use of the application.
In regards to the users, the main objectives of LinkedIn are to develop a professional
network by building a professional profile, nurturing your growing network and generating a
professional reputation.
LinkedIn is perhaps the most overlooked social network. But overall, it is actually more
popular than Twitter, generally considered the number two social network in the U.S.
The latest data shows a higher proportion of U.S. adults on the internet (22%) have used
LinkedIn, compared to the percentage who have used Twitter.
Page 4
2. Overall Description
2.1 Product Perspective
A Database is included for more than one user in the system. Every user has a unique
login id and it will uniquely open the database for each user. Admin provides different username
and password for each user.
I. Communication interface: The website must connect with a DNS and a web server i.e.,
internet. Software interface: The website should support nearly all web clients or web
browsers which work as a platform to run web applications.
II. Hardware interface: The application must run on any OS. Ex. Windows, Mac, android.
III. User interfaces
Administrator: The administrator of the website is allowed to access all the services
in the application. The username and password for the end user is given by the administrator.
User: The user is allowed to access the services given by the administrator like
searching, updating profile, login etc. User interface must be user friendly so that he/she finds no
problem to enter their details and getting themselves register.
Maintainer: The maintainer is responsible for adding new feature to the website. A
maintainer should be possible to update the data in the database.
REGISTRATION CONSTRAINTS
Validate Username:
Validate Password:
Password should follow the password constraints like minimum no. of characters, etc.
Validate profile:
Profile must have suitable information like input string only in name column
Page 6
LOGIN CONSTRAINTS
Validate username:
Username should be correct.
Validate password:
Password should be correct
3. Specific Requirements
Input: Username and Password, Enter the app if credentials are validated successfully
Processing: Open the login page and enter the correct login credentials i.e. Username and
Password. The details are then validated;
If validated successfully, authenticate user into their account
Else, prompt “Wrong username/password” and ask user to re-enter credentials
or click “forgot password”.
Page 7
Output: Account homepage opens if validation successful, else stays in login page or
redirected to forgot password page if required
Output: Prompt appears saying “Reset link sent to mail and mobile”. The user can change
their password from that link
Functional requirement 3: PROFILE MANAGEMENT
Description: If the cash card is valid, the ATM should read the serial number and bank
code.
Functional requirement 7:
Description Authorization dialog: The user is requested to enter his password. The ATM
verifies the bank code and password with the bank computer
Processing: Send serial number and password to bank computer, receive response from
bank.
Description: Different negative answers from bank computer for authorization dialog.
Processing: If the ATM gets any of these messages from the bank computer, the card will
be ejected and the user will get the relevant error message.
Description: If password and serial number are ok, the authorization process is finished.
Input: The ATM gets accept from the bank computer from authorization process.
Description: If a card was entered more than three times in a row at any ATM and the
password was wrong each time, the card is kept by the ATM. A message will be displayed
that the customer should call the bank.
Processing: Initiate authorization process Response from bank computer is to keep the card.
Output: Display error message that the customer should call the bank.
Page 9
Functions: These are the requirements for the different functions the ATM should provide after
authorization.
Functional requirement 11:
Description: Initial withdrawal sequence. If it is too much withdrawal redo the transaction.
Output: Start transaction or re-initiate transaction dialog if the amount is not within the pre-
defined transaction policy.
Functional requirement 13:
Input: ATM gets message “transaction succeeded” from the bank computer.
Processing: ATM prints receipt, updates t and ejects the card. Dialog: Customer should take
the card.
Output: After the Customer has taken the card the money is dispensed.
Processing: the attaches the amount of money against the serial number of the card.
Output: Amount together with the serial number. Response sent to bank for money
dispensed.
Description: If the transaction is not successful, an error message should be displayed. The
card should be ejected.
Input: ATM gets message “transaction not successful” from the bank computer.
Processing: ATM displays error message. Dialog: Customer should take the card.
Authorization
The bank computer gets a request from the ATM to verify an account.
Functional requirement 1:
Description: The bank computer checks if the bank code is valid. A bank code is valid if
the cash card was issued by the bank.
Input: Request from the ATM to verify card (Serial number and password.)
Description: If it is not a valid bank code, the bank computer will send a message to the
ATM.
Output: The bank computer sends the message “bad bank code” to the ATM.
Functional requirement 3:
Description: The bank computer checks if the password is valid for a valid cash card.
Page
11
Description: If it is not a valid password, the bank computer will send a message to the
ATM.
Processing: Process message. Update count for invalid password for the account.
Output: The bank computer sends the message “bad password” to the ATM.
Functional requirement 5:
Description: If it is a valid cash card and a valid password but there are problems with the
account, the bank will send a message to the ATM that there are problems.
Description: If it is a valid cash card a valid password and there are no problems with the
account the bank computer will send a message to the ATM that everything is ok.
Processing: Process transaction (together with the software of the bank.) Update k for
amount.
Output: If transaction succeeded, the bank computer sends the message “transaction
succeeded” to the ATM. If not, it will send “transaction failed”.
Functional requirement 8:
Description: Each bank has a limit k for each account about the amount of money that is
available via cash card each day monthly.
Output: If the amount exceeds the limit, the transaction will fail.
Functional requirement 10:
Description: The bank only provides security for their own computer and their own
software.
The user interface should be attractive and easily understandable so that the user does not face any
difficulty and require no assistance to use the application.
Administrator: The interface must be such that administrator is allowed to access all the
services in the application. The username and password constraints for the end user is given
by the administrator. He is able to control all over happenings of the application.
User: The user is allowed to access the services given by the administrator like searching,
updating profile, login etc. User interface must be user friendly so that he/she finds no
problem to use the app and avail the services.
Page
13
Maintainer: The maintainer is responsible for adding new features to the application. So,
interface of maintainer is such that he is able to update the data in the database and update
the existing features too.
The application must run on any OS like Android, IOS, Windows, etc.
The application must support in every latest version of any operating system and the website should
support almost every web browser which works as a platform to run the application.
Application/Website must run in slow internet connection too (at least some functions)
User end data must be encrypted and should only be able to accessed by the Admin and that
User.
Website and Application must have a strong firewall and safe from intruders
Admin Id must be unique and encrypted so that no one else can use it
Page
14
Users are insisted to change their passwords regularly for security reasons
Security.
Performance
6. Other Requirements
6.1 DNS
The website/application has to connect to a DNS so that it can convert its IP to a name and
user face no difficulty in remembering it.
6.2 Web Server
The application must be available on Play store and Apple app store and other app
libraries so that the users can install the application easily
6.3 Database
The user’s details and data must be saved in a database provided by server. The database
must be secured and end-to-end encrypted.
Page
15
7. DESIGN
DATA FLOW DIAGRAMS
I. Zero level DFD – LinkedIn
STRUCTURED CHART
Page
17
8. TEST CASES