Skip to content
Karin Benson edited this page Apr 21, 2017 · 10 revisions

SDS - Software Design Specification

1. Main Product Features & Capabilities

Introduction Document Goals

  • This document will assist in arraigning our project by implement UMLs and charts.
  • Keeping our project medullary.
  • Risk table and demands chart prioritizing.
  • Keeping our project’s code simple and easy to track and use.

Capability:

Ability Risk Description
1 Lack of database High Offering a free database or using an existing one
2 Creating new contact High Making sure that the database is usable
3 Generate GUI High Creating GUI that will be easy to use and clear to understand
4 Generate Posts Medium Creating a forum that support posting
5 App usage Medium Keeping user experience simple

Related Documentation

2. UML Modeling

Class Diagrams

State-Chart Diagrams

Sequence Diagrams

The user will go to the "Need Something" page and will create a new post and people will be able to contact him or replay to the post

Sequence Diagram

3. Persistence

Currently the organization dose not have a Database, we will try and give them a free database option or we will use the current database they have for their other website.

We will have a monthly update of PDF file that will have the newspaper information, we will also create web storage for the contact list and "Need Something" pages - using database.

4. Non-functional Requirements

  • The user interface will be simple and intuitive for use.

  • The upload time of the website will be less then 5 seconds.

  • The app will have high security level.

5. Risk Management

Risk Severity Probability Response Treatment Program
1 Lack of time 3 2 Divide the workload between the team members.
2 Lack of knowledge about the developed platform 2 1 Take an online course
3 Mistakes in the code 2 2 We will monitor one another code and will correct accordingly
4 Team's experience 2 3 Working together and helping one another 1.Learn new methods from the internet. 2.Get help from our teacher 3.Stack Overflow website 4. Google
5 App usage 2 2 Too complicated to use We will make prototype and present it to our clients
6 Work on exist DB 3 3 We will custom our app to the DB We will create Dedicated DB
7 The client have a lot requirements 2 2 We will ask the client for a specific requirements We will have a constant conversation with the client and we will keep them up to speed about the development of the app

6. User manual

7. Tests plan

In order to make sure that our app is doing the right thing like posting a post and creating new contact, there is a need in tests that will verify this issue.

  • After insert a new person to the Database there is a need to verify the information of the contact.
  • Generate a post after a user uploaded a new one.
  • Creating a forum that people can create new posts, we need to make sure that it is working correctly.