SOFTWARE DESIGN AND ARCHITECTURE

SOFTWARE REQUIREMENT SPECIFICATION

SOCIAL NETWORKING
Instagram
BCSE-6C
SUBMITTED TO: MAM SANA AKBAR
SUBMITTED BY: NEHA IJAZ (7048)
RAYA FATIMA AMJAD (6731)
ZAHRA AZHAR GHORI (6813)

TABLE OF CONTENTS
1. INTRODUCTION.3
1.1 Document convention3
1.2 Intended Audience and Reading suggestions3
1.3 Product Scope....4
1.4 References.4
2 OVERALL DESCRIPTION.4
2.1 Product perspective...4
2.2 PRODUCT FUNCTIONS..4
2.2.1 the user.4
2.2.2 Administrator...4
2.2.3 Operating environments...4
2.3 USER CHARACTERISTICS..4
2.3.1 Design and implementation constraints...5
2.4 EXTERNAL INTERFACE REQUIRMENTS....5
2.4.1 Hardware requirements....5
2.4.2 Software requirements..5
2.4.3 User Interface...5
3 FUNCTIONAL REQUIREMENTS.5
3.1 THE USER..6
3.2 ACCESS TO OTHER USERS6
3.3 UPLOADING.6
3.4 SHARE PHOTOGRAPHS.6
3.5 CREATE ALBUM.7
3.6 ADMINISTRATOR...7
3.7 LOGIN7
4 NON-FUNCTIONAL REQUIRMENTS..8
4.1 SECURITY.8
4.2 SAFETY REQUIREMENTS.8
5 PERFORMANCE REQUIREMENTS.8
5.1 ERROR HANDLING.8
5.2 AVAILABILITY8
5.3 USABILITY...8
5.4 OTHER REQUIREMENTS...8
6 BEHAVIORAL REQUIREMENTS9
6.1 USE CASE.9
6.2 ANALYSIS MODEL10
6.3 ACTIVITY DIAGRAM11
6.4 DATA FLOW DIAGRAM12
6.5 CLASS DIAGRAM...13
6.6 SEQUENCE DIAGRAM..14

1. INTRODUCTION

Purpose of this document

The purpose of this SRS document is to provide a detailed overview of our software
product-an online photograph- sharing library. This document contains the functional and
nonfunctional requirements of the project. This document describes the project's scope, users
and its user interface, hardware and software requirements. It defines how user and system
management team see the product and its functionality.

Document Conventions
Main heading
Font: Times New Roman
Face: Capitalize, Bold and underlined
Size: 14
Sub-headings
Font: Times New Roman
Face: Capitalize and bold
Size: 12
Sub-headings of a sub-heading
Font: Times New Roman
Face: Bold
Size: 12

Intended Audience and Reading suggestions

The intended readers of this document are the developers of this software system,
owners and managers who will interact with this system. Designers will use this
information as the basis for creating the design of the project. This document will also
serve as an agreement between the clients i.e. the owner and the development team about
the functionality of the system.

Product scope
The goal is to develop and design a photograph library. When you login and
create your own photo album, its bound to be an honest, authentic representation of your
life. It offers designs that are simple to work with to make your albums look beautiful.
And when you want your friends and family members to see your amazing photo album,
you can add them to the profile and share albums. You can even edit, update and maintain
profile as needed.
The product will provide the following benefits:
You can access the system via internet on a pc or mobile at any place.
Provides convenience to users.
Its a great platform of viewing pictures and moments in an organized way.

Provides a more creative environment for the users.

References
https://play.google.com/store/apps/details?id=com.instagram.android&hl=en
www.csse.monash.edu.au
http://searchsoftwarequality.techtarget.com/answer/How-to-write-a-SoftwareRequirements-Specification-SRS-document

2. OVERALL DESCRIPTION
2.1 Product perspective
Photograph sharing library is a new, self-contained product. However it is possible to
exchange data with other social network platform through external interface if required.
2.2 PRODUCT FUNCTIONS
Some functions that our photograph library will perform are as follows:
2.2.1 The user

Create profile and delete profile at any time.

Modify profile at any time.
Can accept or reject a new user.
Can add any other user.
Search any other user.
Create albums and view the created album at any time.
Upload, share and view photos at any time.
Delete photo at any time.
Edit photo at any time.

2.2.2 Administrator

The administrator should login and logout the user.

Maintain library records.
Update library.

2.2.3 Operating environment

The online photograph sharing library shall operate in all famous browsers.
2.3 USER CHARACTERISTICS

The user types are;

Member of the library

System administrator

2.3.1 Design and implementation constraints

The information must be stored in a database.

The online photograph library must be running 24 hours a day
Users must have their correct user name and passwords to enter into their accounts.
Internet connection is needed.

2.4 EXTERNAL INTERFACE REQUIRMENTS

2.4.1 Hardware requirements
Since the application must run over the internet, all the hardware shall require to
connect internet will be hardware interface for the system. As for e.g. Modem, WAN
LAN, Ethernet Cross-Cable.
2.4.2 Software requirements
Along with internet connection, the system makes indirect use of an internet
browser or an android in mobile phones.
2.4.3 User interface
First interface is the log-in screen. The user enters his user name and password to
gain access to the database. After logging in, the profile of the user is displayed. User can
upload, delete, edit or do whatever he likes to with the profile. Every page on the screen
is the user interface.

3. FUNCTIONAL REQUIREMENTS
3.1 USER:
He should be able to access his profile.
Preconditions: User has account and he is logged in for all requirements below:
Input:
User.
Output:
User profile.
Actor:

User and database.

Process flow:
User will visit the web page and attempt login by entering user id and password.
User is verified by using the database and then directed to his homepage.
3.2 ACCESS TO OTHER USERS
The system shall retrieve records of person from systems database.
Input:
User name and email address.
Output:
Data of the users from the database.
Actor:
User and database.
Process Flow:
After the user is successfully logged in his profile he will request other users
page by typing the users id. The system will determine if the user is already added to the
found list. If yes then he is directed to friends page, otherwise he will have options to
add or remove friend.
3.3 UPLOADING
Input:
User upload photographs
Output:
Uploaded photographs
Actor:
User, server, database
Process flow:
User selects the album in which he wants to update the photos. After verifying
from database users will upload photos and database is updated. Now the user can either
view the photographs or edit them. In case of editing the original photos is replaced and
the user is directed back to homepage.
3.4 SHARE PHOTOGRAPHS
Input:
User share photographs by uploading them.
Output:

Received photographs.
Actor:
User or database.
Process flow:
Users share photos and post photos after they are verified from the database.
3.5 CREATE ALBUM
Input:
User creates album.
Output:
The album is displayed.
Actor:
User, database.
Process flow:
User creates and saves album in the database and it is displayed to the other users.
3.6 ADMINISTRATOR
The database should be kept up to date.
Input:
Administrator.
Output:
Updated database.
Actor:
Administrator, database.
Process flow:
Administrator will update the database.
3.7 LOGIN
Input:
User
Output:
Login homepage (In case of the successful login stay, or else display error
message)
Actor:
User, Administrator, database.

Process flow:
User will attempt login by entering its username or password. The administrator
verifies login from database. In case of successful login move to profile or else stay on
homepage.

4. NON-FUCTIONAL REQUIREMENTS
4.1 SERCURITY:

System will have several users and every user has access constraints.
System user secure database.
Users cannot copy photographs of other users (safety requirements)

4.2 SAFETY REQUIREMENTS:

System shall not cause any harm to human usage.

5. PERFORMANCE REQUIREMENTS

The system shall accommodate high number of users without causing errors.
The system will have a quick response time of 5seconds.
Database can handle unlimited amount of users data.

5.1 ERROR HANDLING:

System shall handle expected and unexpected errors to avoid loss.
5.2 AVAILABILITY:
24/7 availability of the system.
5.3 USABILITY:
User interface should be friendly, easy to use and understandable.
5.4 OTHER REQUIEMENRS
There may be other requirements which are in need for development purpose.

BEHAVIORAL REQUIREMNTS
USE CASE
ACTOR ACTION

SYSTEM OPTIONS
1) Verify user login

2) Add friend, accept or deny request

3) update profile

4) Maintain profile

5) Create Album

6) Photograph editing

7) Upload Photograph

8) Update user library

9) delete photograph extension

10) Invalid user name or password

11) Picture is too large to be uploaded

FREQUENCY OF USE: Every Day.

USE CASE DIAGRAM

Appendix A: Glossary
Appendix B:
ANALYSIS MODEL:

ACTIVITY DIAGRAM:

To access profile

To access friend

Upload a photo in album

DATA FLOW DIAGRAM

Level 0

Level 1

Level 2

CLASS DIAGRAM

SEQUENCE DIAGRAM
Administrator

Login

Friend request

Create new album

Upload Photographs

Shared Photos