Functional Specification Development Process


Functional Specification Development Process

Project-Based Discussion

Contents

1.      Introduction. 2

2.      Project Requirements. 2

3.      System Specifications. 2

4.      References (Project Development Platforms) 2

5.      System Framework and Modules. 2

6.      UI screen and Function description. 2

7.      UC Specifications. 2

8.      Non-Functional Requirements. 2


1.   Introduction

The course name is Software Engineering Practice. This course’s intent to learn Software engineering practically and also as a team. Our project is to develop a website or a mobile application on a particular topic in this course. So, we made the team with four members whose name is “Team Zero” to complete this project. Our team decided to make a Help-Desk platform for SWPU’s international Students. Our team made a mobile application and a website because our application’s OS is android, and every person doesn’t use android. For them, the website will be an inconvenience. So, the functional specification development process will be described below.

2.   Project Requirements

2.1.        Project Objectives

As new Students, people face some difficulties and a lack of information. To reduce this problem, our project aims to make a beautiful Help-Desk platform for the new students of SWPU.

 

2.2.        Target Users

·        international Students of SWPU.

·        Guest (Who have interest in SWPU)

 

2.3.        Client’s Specifications

For a successful project, the most important thing is the Client’s Specifications. For our project, we have surveyed to collect the client’s specifications. The survey will be added at the end of this document. Form our survey, the data we have collected are:

  • *       Certain Locations.
  • *       Information about campus life.
  • *       Registrations Help-Guide.
  • *       How to do certain things.

 

2.4.        Features of Project

After analyzing the data to focus on Client’s Specifications, we decorated features of our project. There Are some most important features of our project.

·        OIA Address and Information

·        Academic building location

·        Nearest hospital location

·        Nearest bank address

·        How to open a bank account?

·        Where to buy a new sim card

·        How to connect campus Wi-Fi?

But these don’t represent all the features of our project.

 

2.5.        About Project

Our team is working on two platforms one is a mobile application, another is a website. The features are slight differences between the app and the website. The website is basically informative, and there are no requirements for identification so that anyone can easily access it. And the intent to make an app basically for students of SWPU.

3.   System Specifications

3.1.        Website

Any kind of Web-browser. (Recommended: Google Chrome, Mozilla Firefox, Opera mini.)

3.2.        Application

Application Minimum SDK: API 21 Android 5.0 (Lollipop)

Recommended Screen Resolution: 720 x 1280 pixels, 16:9 ratio, Until 1080 x 2340 pixels.

Note: In the lower version of space could not be workable. And also, VPN could be needed in certain areas.

4.     References (Project Development Platforms)

4.1.        Website

Coding environment: Notepad++, Firebox Browser.

Language: HTML, CSS, Javascript.

Database: Google Drive.

4.2.        Application

Coding environment: Android Studio.

Language: Java.

Database: Firebase

1. https://developer.android.com/

2. https://stackoverflow.com/

3. https://codinginflow.com/

4. https://firebase.google.com/docs

 

5.   System Framework and Modules

5.1.        Modules


The app and website construct with modules. We can determine modules from the site map. So, the site map of each of them are,

 

Application’s Site Map

 

 



Website’s site map

 

 

 


Website’s site map

 

From the App’s site map, we can see that there are nine modules that construct the framework of the application and also eight modules construct the framework of the website.

 

5.2.        Framework

5.2.1.  User layer

 

Application: Users interact with UI. The UI of the application contains news feeds, university information, shortcuts like home, features, etc.

 

website: UI of the website contains news feeds to display, shortcut buttons, necessary information, etc.

5.2.2.  Function layers

Application: Provide main functions such as home, features, including the administrator, login method, etc.

·        Home

Display All necessary Information news feeds, explore university etc.

·        Features

After entering online user can access this function.

·        About

This displays the information about app and developers.

Website: It’s an informative statics web-page. It’s consisted of two pages.

·        Home

Display all contents.

·        Team

Display team information.

·        Contacts

Consist with contact information.

  

5.3.        Flow diagrams


Application

The arrow from left-right to the right considers as input data and right to left output data.

Main Process:

  • ·        User access the app.

·        There are two methods of access.

  • Online.
  • Offline.
  • UI directly shows the contents of dash bord if the user is offline.
  • If the user is online, he can access the database and can see the online contents.
  • If user log in as an administrator, he can input and change data, then the UI will show the new update.

 

Website

It’s a static website. Use can’t be updated, edit or change data while online. The user only can interact with the UI. 

6.   UI screen and Function description

6.1. Application


After launching, the user can see this dashboard. In the dashboard, there is three main functions name: Home, Features, About. In Home-function, there are some features like getting Latest Information, Explore University, Get yourself registered. Each of them got three buttons. By clicking those buttons, users can see the content they got.

 

 

Features function contains three sub-functions. Which are, Online Version, Search information, Administrators. But these sub-functions can use after the user enter online. Offline users can’t access these features. They can only see the dashboard.

·        Online version

Help users to get login or sign up.

·        Search Information

Help users to search for the information they need.

·        Administrator

If user, log in as an administrator. This feature helps to get access to change or modify the data of the app.

 


 

 

This function’s content is a description of the app and the information about developers. It can access in both ways, online or offline.

 


6.2.        Website

After the User launching the website user will UI will interact with the user. There Are main three pages on the website, Home, Team, Contact.

  • ·        Home

Home is the default page of this website. It consists of the most important contents. A part of the Home page’s UI:


 

 

CORONA VIRUS UPDATE

It’s a news feed. It has two partitions; one is China Update and another one World Update. It delivers the news information about corona issue of particularly china and also worldwide.

 

NEW STUDENTS REGISTRATION GUIDE

This content constructs with every necessary information to get a student registered in the university. It has twelve descriptive steps.

 

STUDENT’S DAILY LIFE

This content is divided into 5 separate sub-contents. This content will provide students get information about campus and campus life.

 

Know More Button

It will help users to get more specific information about that particular topic. Likewise:


Here user can see in the information of developer Team.

  • Menu Button: Deliver to Main Menus.
  • Third Party Button: These buttons provide the developer’s personal contact info. So that, user can contact the developer.

  • ·         Android Apps

From here, User can download our android application also.

7.   UC Specifications

Use cases help to explain how the system should behave and, in the process, they also help brainstorm what could go wrong. 

7.1.        Use case diagrams

7.2.        Use Cases

Use Case-1

Primary Actor

User Admin

Triggers

Access Dashboard/Admin Panel

Precondition

Login (requirement Admin Key)

Main Success Scenarios

·       Login

·       Have admin key

·       Verify Login

If wrong,, Display Login error.

Forget password.

·       Access On

Dashboard.

Can see updated information in Real-Time.

Create Data.

Delete data.

Edit Data.

·       Log out.

 

Application:


Use Case-2

Actor

Students

Triggers

Access Dashboard

Precondition

Login (requirement None)

Main Success Scenarios

·       Offline

Dashboard (All users are considered as a viewer)

·       Online

Login

·       Verify Login

If wrong Display Login error.

Forget password.

·       Access On

Dashboard.

Can see updated information in Real-Time.

·       Log out.

 

  

Website:

Use Case-1

Primary Actor

User Admin

Triggers

Access Dashboard/Admin Panel.

Precondition

No requirements

Main Success Scenarios

·       Offline

·       Access On

  1. Dashboard.
  2. Create Data.
  3. Delete data.
  4. Edit Data.

·       Online

Can see updated information in Real-Time.

 

 

Use Case-2

Actor

Students/Guest

Triggers

Access Dashboard

Precondition

No requirements

Main Success Scenarios

·       Online

Can see updated information in Real-Time.


8.   Non-Functional Requirements

8.1.Project Development (Estimate in Days)


 

1 Comments

Never enter the spam link in the comment section. If you have any inquiry, please let me know in the comment section.

Post a Comment

Never enter the spam link in the comment section. If you have any inquiry, please let me know in the comment section.

Previous Post Next Post