-
Notifications
You must be signed in to change notification settings - Fork 0
SRS
| Date | 25.10.2016 |
| Version | 1.0 |
| Description | Initial fill up |
| Author | Louisa, Marco |
1.1 Purpose
This SRS gives an overview about the specifications for our project “in aeternum”
1.2 Scope
We want to build a website where you can plan your own funeral.
1.3 Definitions, Acronyms and Abbreviations
1.4 References
| Title | Blog in aetrernum |
| Date | 25.10.2016 |
| Author | in aeternum Team |
1.5 Overview
2.1 Vision
When we die, our family and friends are in deep mourning. Added to this, they must also organize our funeral. But what if we don’t want a funeral where everyone wears black and listen to sad music? What if we want the people to wear colorful clothes and listen to “Highway to hell”?
We decide to make a Website, where you can planing. Because dead is a topic which goes more with older people we decide to make a layout which is senior friendly.
3.1 Functionality - Website
3.1.1 Register for a new account
There is the possibility to register for a new user.
3.1.2 Login for existing account
There is the possibility to login for an existing account.
3.1.3 Overview page
A page for the user, where he or she can maintain her profil and change answers.
3.1.4 General informations
The user can save general data about their funeral, e.g. their burial method.
3.1.5 Create a guest list
The user can create a guest list.
3.1.6 Save as pdf
The user can save all the information about his funeral as pdf.
3.1.7 Integrating a playlist
The user can integrate a playlist from e.g. Deezer to his or her account.
3.1.8 Specify your budget
The user is able to specify his or her budget for the funeral.
3.2 Usability
(tbd)
3.3 Reliability
3.3.1 Availability
The website should be available 90% of the time. When a downtime is needed to for data loads or bug fixes it should be between 10pm. and 6am.
3.4 Performance
3.4.1 response time for a transaction
The response time for a transaction should be as short as possibly.
3.5 Supportability
3.5.1 Language Support
The following languages will be used:
Internet Standards HTML5, CSS3 and JavaScript
PHP 7
My SQL
3.6 Design Constraints
(tbd)
3.7 On-line User Documentation and Help System Requirements
The website will have a senior friendly, intuitive design. Also there will be a help button, where a user can get more information about the current page.
3.8 Purchased Components
(tbd)
3.9 Interfaces
3.9.1 User Interfaces
Mockups are generated next week
3.9.2 Hardware Interfaces
(tbd)
3.9.3 Software Interfaces
(tbd)
3.9.4 Communications Interfaces
(tbd)
3.10 Licensing Requirements
(tbd)
3.11 Legal, Copyright, and Other Notices
(tbd)
3.12 Applicable Standards
(tbd)
(tbd)