software recruitment specification document, Assignments of Software Engineering

Download software recruitment specification document and more Assignments Software Engineering in PDF only on Docsity!

Software Requirements

Specification

CodeBenders

Haldun Yıldız 1819663

Ali Şihab Akcan 1818871

Deniz Can Yüksel 1819697

Onur Aydınay 1819002

Contents

• 1. INTRODUCTION
  • 1.1 PROBLEM DEFINITON
  • 1.2 PURPOSE........................................................................................................................................
  • 1.3 SCOPE
  • 1.4 USER AND LITERATURE SURVEY
  • 1.5 DEFINITION, ACROYNMS AND ABBREVIATIONS............................................................................
  • 1.6 OVERVIEW
  • 1.7 REFERENCES
• 2. OVERALL DESCRIPTION........................................................................................................................
  • 2.1 PRODUCT PERSPECTIVE
    • 2.1.1 System Interfaces
    • 2.1.2 User Interfaces
    • 2.1.3 Hardware Interfaces
    • 2.1.4 Software Interfaces
    • 2.1.5 Communications Interfaces....................................................................................................
    • 2.1.6 Memory Constraints
    • 2.1.7 Operations
    • 2.1.8 Site Adaptation Requirements
  • 2.2 PRODUCT FUNCTIONS
    • 2.2.1 Login
    • 2.2.2 Register
    • 2.2.3 Logout
    • 2.2.4 Follow
    • 2.2.5 Unfollow
    • 2.2.6 Add Friend
    • 2.2.7 Delete Friend
    • 2.2.8 Check-In
    • 2.2.9 See Other’s Post
    • 2.2.10 Post on the Wall
    • 2.2.11 Edit Profile
    • 2.2.12 See Friend’s Profile
    • 2.2.13 See Online Friends
  • 2.3 USER CHARACTERISTICS
  • 2.4 CONSTRAINTS
  • 2.5 ASSUMPTIONS AND DEPENDENCIES
  • 2.6 Apportioning of Requirements
• 3. SPECIFIC REQUIREMENTS
  • 3.1 INTERFACE REQUIREMENTS
    • 3.1.1 Welcome Page
    • 3.1.2 Login Page.............................................................................................................................
    • 3.1.3 Register Page
    • 3.1.4 Profile Page...........................................................................................................................
    • 3.1.5 Edit Profile Page
    • 3.1.6 Friends Page
    • 3.1.7 Check-In Page
    • 3.1.8 Main Page
    • 3.1.9 Recent Activities Page
    • 3.1.10 Places’ Wall Page
    • 3.1.11 Other User’s Profile Page
    • 3.1.12 Friend Chat Page.................................................................................................................
    • 3.1.13 Application Settings Page
  • 3.2 FUNCTIONAL REQUIREMENTS.....................................................................................................
    • 3.2.1 Login
    • 3.2.2 Register
    • 3.2.3 Logout
    • 3.2.4 Follow
    • 3.2.5 Unfollow
    • 3.2.6 Add Friend
    • 3.2.7 Delete Friend
    • 3.2.8 Check-In
    • 3.2.9 See Other’s Post
    • 3.2.10 Post on the Wall in a Place
    • 3.2.11 Edit Profile
    • 3 .2.12 See Friend’s Profile
    • 3.2.13 See Online Friends
  • 3.3 NON-FUNCTIONAL REQUIREMENTS............................................................................................
    • 3.3.1 Performance Requirements
    • 3.3.2 Logical Database Requirements
    • 3.3.3 Design Constraints
    • 3.3.4 Software System Attributes
• 4. DATA MODEL AND DESCRIPTION
  • 4.1 DATA DESCRIPTION
    • 4.1.1 Data Object
    • 4.1.2 Data Dictionary
• 5. BEHAVIORAL MODEL AND DESCRIPTION
  • 5.1 DESCRIPTION FOR SOFTWARE BEHAVIOR
  • 5.2 STATE TRANSITION DIAGRAMS
• 6. PLANNING
  • 6.1 TEAM STRUCTURE
  • 6.2 ESTIMATION(BASIC SCHEDULE)...................................................................................................
  • 6.3 PROCESS MODEL
• 7. CONCLUSION
• Figure 1: Welcome Page Table of Figures
• Figure 2: Login Page
• Figure 3: Register Page
• Figure 4: Profile Page
• Figure 5: Edit Profile Page
• Figure 6: Friends Page
• Figure 7: Check-In Page
• Figure 8: Main Page...............................................................................................................................................
• Figure 9: Recent Activities Page
• Figure 10: Place’s Wall Page
• Figure 11: Other User’s Profile
• Figure 12: Friend Chat page
• Figure 13: Application Settings page
• Figure 14: use case diagram-Login
• Figure 15: use case diagram-Register
• Figure 16: use case diagram-Log out.....................................................................................................................
• Figure 17: use case diagram-Follow
• Figure 18: use case diagram-Unfollow
• Figure 19: use case diagram-Add Friend
• Figure 20: use case diagram-Delete Friend
• Figure 21: use case diagram-Check-in
• Figure 22: use case diagram-See other’s Posts
• Figure 23: use case diagram-Post on the wall in a place
• Figure 24: use case diagram-Edit Profile
• Figure 25: use case diagram-See friend’s profile
• Figure 26: use case diagram-See online friends
• Figure 27: ER Diagram
• Figure 28: Class Diagram
• Figure 29: State Diagram

1. INTRODUCTION

This document is a Software Requirement Specification for the Android application wHere. This document is prepared by following IEEE conventions for software requirement specification. This document includes all the functions and specifications with their explanations to solve related problems as a project of METU CENG Department.

1.1 PROBLEM DEFINITON

In the last decade, Internet and smartphone users have increased rapidly. This leads many simplicities on people’s life in terms of communication. However, there are also some concepts that could not be resolved yet. One of these problems is gathering people together in a social platform when they are sharing the same place to share their opinions or communicate between each other. So let’s think about a University campus. There are more than ten thousand people sharing the same campus. If we try to reach other people on the same campus, unfortunately there is no way to make it. What we need is a place to gather all of these people into one artificial place, a social platform to make those people communicate each other easily, share their feelings or opinions about anything in the same environment.

1.2 PURPOSE

Purpose of this software requirement specification document is providing a complete description of the features which will be implemented in this social platform project. Moreover, it includes user scenarios, working principles of the system, internal and external interfaces. Intended audiences are users and developer team. Use case diagrams will provide visual description for users and class diagrams will provide technical information for developers. Also, tests can be defined according to use case descriptions in this document.

1.3 SCOPE

As it is described in problem definition section, there is no such platform that is currently popular which allows people to communicate in the same place. Our application will provide the users a social platform which they can communicate easily with all other users in the same place. Our system is an online sharing and communicating system which is intended to solve this problem described above. The system provides an mobile platform which people can easily register and use. When they registered, they can go a place and post to this place’s wall and also see who are online at this moment and communicate with online people in the place. Also when they are not in a place, they can follow their friend’s activities, posts etc.

1.4 USER AND LITERATURE SURVEY

The popularity of smartphones and internet is rising rapidly. Nowadays, there are few people who use traditional messenger to communicate. They have been replaced by the mobile messaging applications launched by various companies. The applications have become an integral part of human life. People wake up with messages and sleep after sending messages. Most of the chat applications use Internet Relay Chat. IRC is very fast and can be used worldwide. Only requirement is the internet connection. In the

2. OVERALL DESCRIPTION

This part of the SRS is about general factors that affect the product and requirements of the product. Moreover, this part will provide a background for requirements which will be defined in Section 3 in detail.

2.1 PRODUCT PERSPECTIVE

2.1.1 System Interfaces The application will be implemented in Java and it will use Android SDK, Facebook SDK and Google Maps SDK. Eclipse will be used as IDE while implementing. MySQL Workbench will also be used as DBMS. Database of the system will be temporarily held in METU Ceng servers.

2.1.2 User Interfaces

2.1.2.1 Welcome Interface This is the first interface that user will see when he/she uses the application for the first time. In this interface, a brief information in order to use the application will be written and there will be a button which will direct user to the login page of the application.

2.1.2.2 Login Interface In this interface, there will be 2 text fields which are namely username and password and 3 buttons which are login, login with Facebook and register. If the user has his/her account, he/she will login the system with his/her username and password. If user doesn’t got an account, he/she will use either the Facebook login button in order to login with his/her facebook account or register button in order to get an account.

2.1.2.3 Register Interface In this interface, there will be text fields which are used for gather the information from the user and a button which is namely register. User will fill required fields with his/her related information (username, password, gender, city etc.), click to the register button and be able to login the application.

2.1.2.4 Main Interface In this interface, there will be a news feed which contains the check-in’s and the comments that posted to a place’s wall by user’s friends. Also there will be a small field which contains profile picture, name and surname of the user, a check-in button and two sub-interfaces namely profile and chat. User will reach these sub-interfaces by sliding main interface right and left.

2.1.2.5 User Profile Interface Profile interface is a sub-interface which can be reached from main interface. User will use this interface to edit his/her profile information, see the pending friend requests, see his/her friends list, previous check-in and post information, general settings of the application and logout.

2.1.2.6 Friend Chat Interface This is also a sub-interface of the main interface. In this interface user will be able to see a list contains his/her online friends and chat with them by simply clicking the profiles of them.

2.1.2.7 Edit Profile Interface This interface will be used by user in order to update the information about him/herself. There will be fields that contains users previous information and 2 buttons namely apply and cancel in order to perform update or cancel it.

2.1.2.8 Latest Activities Interface In this interface, user will be able to see his/her previous actions in chronological order. ( Check-ins, posts, sent or received friend requests, etc.)

2.1.2.9 Friend List Interface This interface will contain the complete friendlist of the user. User will be able to select a friend and see his profile information. And also user will be able to see the pending friend requests, look to their profiles by clicking on them and accept or decline the request.

2.1.2.10 Other User’s Profile Interface When user clicked to a profile of a user, this interface will show up. In this interface user will be able to see the other users profile information according to other user’s privacy settings, send this user a friend request if they are not friends or set the settings about the user (follow, unfollow etc.).

2.1.2.11 Check-in Interface This interface will show up when user clicks check-in button in the main interface. In this interface, there will be a map which shows the current location of the user and nearby places list which user can select a place from that list and check-in and a button named check-in.

2.1.2.12 Place Interface This interface will show up after check-in operation will completed. This interface contains the posts and comments that posted by other users. Also there will be 2 buttons which are namely Main Page and Check-out. Users will be able to visit the main page and check-out from the place. Also there will be a sub-interface in this page which is online user interface and user will be able to see this page by sliding the page to the left.

2.1.2.13 General Settings Interface This interface will contain general options of the application.(notification, sound, language etc.) User will be able to change the general settings of the application.

2.1.3 Hardware Interfaces This application will work on android phones and tablets. Since the application must run connected to internet and need a location data, Android devices must have a gps unit and internet connection in order to run this application.

2.1.4 Software Interfaces Since this application is a mobile application, it will only need an Android version 4.0 or higher in order to perform.

2.2.7 Delete Friend User can delete any friend from friend list. In addition to that, user who delete the friend is also deleted from also other user’s friend list. In order to delete a friend he/she must be user’s friend. Friend who will be deleted from friend list must already be user’s friend.

2.2.8 Check-In If the place which is already added in the database, user can check in directly or if place doesn’t exist in the database, place which user try to check in will be added the database automatically.

2.2.9 See Other’s Post User can see posts which have posted before in a place which user have already checked in and still there. If user checked in and time out he/she cannot see the posts on the place wall. Before see other’s post, checked in this place is required.

2.2.10 Post on the Wall After checked in, the wall is appeared on the screen automatically. User can see the posts sent before. User can also post on the wall if he/she wants. Check in is required to post on the wall. After posting new post can be seen on the wall.

2.2.11 Edit Profile User can edit his/her own profile. Edit means changing profile picture, e-mail address, user name; adding personal information or adding pictures which are not profile pictures. After edition, profile will be updated.

2.2.12 See Friend’s Profile In the friend list, after touching friend’s profile picture user will be redirected to friend’s profile where user can see all his/her friends.

2.2.13 See Online Friends After touching friends button, user will be redirected to friends page. Online friend list can be seen on this page.

2.3 USER CHARACTERISTICS

A user who has a general knowledge about using an Android device can easily use this application.

2.4 CONSTRAINTS

wHere shall operate on Android v4.0 or higher operating system. There should be at least 50 MB of free space on the device. CPU speed or RAM of the device is not a big concern. Java shall be the implementation language with Android, Facebook, Google SDK’s. Informations of the users shall be encrypted before transferred to database in order to maintain the security of the crucial informations about users.

2.5 ASSUMPTIONS AND DEPENDENCIES

User interfaces and some of the functionalities may change during the implementation of the project and also new features may be added which can change

the functionalities and system requirements. Future versions of the application will also operate on the devices mentioned above.

2.6 Apportioning of Requirements

The basic functions like login, register, check-in etc. should be implemented first in order to construct the general structure of the application. Other features does not have an implementation order.

3.1.2 Login Page

Figure 2: Login Page

After using wHere application first time, Login page will be the starting page. After user fill the username and password, he/she can login.Moreover he can login using Facebook profile. If he/she does not have account ,he/she can register to the application using Register button. Forget your password is for one who could not remember his/her wHere password.

3.1.3 Register Page

Figure 3: Register Page

Users who have no wHere account can register in Register Page. After filling the requiered fields, user should touch the register button and he/she will be redirected to Login Page again.

3.1.5 Edit Profile Page

Figure 5: Edit Profile Page

In Edit Profile Page, user can edit his/her profile information. When registering the application, most of the fields in profile page will be empty so those fields can be updated in Edit Profile page. After changing the fields, user should touch Apply button to update his/her profile. User can also cancel changes by touching Cancel button.

3.1.6 Friends Page

Figure 6: Friends Page

Friends Page includes friend requests and friends of user. User can accept or decline friend request by touching the icon right side of the person. Under the friend requests there are friends, user can delete those friends by touching delete icon. Also more friends can be shown by touching “more..” text.

3.1.8 Main Page

Figure 8: Main Page

This page is main page. After login the application, user will be redirected to main page. In this page, user can see his/her friend’s check-ins and also see friend’s posts on places’ wall. There are three button at the bottom of the page. User can check-in by touching Check-in button, see his/her profile by touching My profile button or see favorite places by touching My W-places.

3.1.9 Recent Activities Page

Figure 9: Recent Activities Page

In this page, user can see his/her recent activities like checked-in places, posts which are sent by user, recently added friends. Also user can touch the profile picture to go his/her profile page.