-
Notifications
You must be signed in to change notification settings - Fork 1
SDS doc
AlexCherniak edited this page Jan 14, 2014
·
6 revisions
#SDS:
SDS helps us to create a specification of a software artifact, intended to accomplish goals, which will summary what we need to do exactly. It will help us to detect what we will need in the future, and to understand the problems we will face, so we solve them now or find replacements before we get far in the project and start changing our code and design later.
#Deployment Diagram:
#CRC & Class Diagrams: CRC will help us later to know what functions and methods we need to connect everything togather.
#Sequence Diagram:
#Persistence Diagram:
![presistance] (http://s15.postimg.org/l5zf497yz/Presistance2.png)
#Risk management:
Problem/Risk | Probability | What it can cause | How can we make it better/safer | What will you do if the risk will happen |
---|---|---|---|---|
Software bugs | Medium | Customers stop using our software | We will run all tests before releasing the final product | We will add steps how to overcome those problems |
profitability | High | Customers stop using our service | We are working on new features that other services not supply | Design invitation, Arrival map to the event... |
Publicity | High | people won't hear about our service and no profits will be made | we will tell everyone we know about our service | we will share our ideas through the internet network as well |
Developing problems | Medium | we couldn't finish critical things to make it work | work harder,listen to advises,stay updated | give our best of the best |