-
Notifications
You must be signed in to change notification settings - Fork 1
Ex‐Requirements
-
Visitor
-
Member
-
1.1.1. Account
- 1.1.1.1. Users shall be able to open an account.
- 1.1.1.1.1. Users shall enter their e-mail, username, and password to open an account to become an authanticated user.
- 1.1.1.1.1.1. Authanticated users shall be able to enter the application using their own username and password.
- 1.1.1.1.1.2. Authanticated users shall be able to make the application remember their username and password.
- 1.1.1.1.2. Users shall be able to put up a profile picture.
- 1.1.1.1.3. Users shall be able to write their personal information in their personal pages while either creating their account or after registering the application.
- 1.1.1.1.1. Users shall enter their e-mail, username, and password to open an account to become an authanticated user.
- 1.1.1.2. Guest users shall be able to use the application.
- 1.1.1.2.1. System shall disable some functions for the guests.
- 1.1.1.3. Users shall enter their e-mail or username and password to re-enter their account if they are logged out.,
- 1.1.1.4. System shall offer the choice to keep to user logged in
- 1.1.1.1. Users shall be able to open an account.
-
User Requirements
Visitor
Visitor : Don't need to be authenticated. Can sign up Postlari gezebilir Belirli static sayfalari gezebilir.(Ligin tarihcesi, takimlarla ilgili bilgiler,) Visitor can see posts and comments but cannot add anything. Communitylerin icerigini gorebilir ayni sekilde post ve comment atamaz.Member in icinde Account
Account
- Member: Needs to be logged in and authenticated.
Birbirlerini takip edebilirler.
can see: Ana sayfa postlari ve yorumlari Community postlari ve yorumlari Static sayfalar
can edit: Ana sayfa postlari ve yorumlari eger kendisi paylasmissa Deletion Community postlari ve yorumlari eger kendisi paylasmissa ve comm a uye ise. Post ve yorum likelama
- Community: Kendi iclerinde post atilabilir: O comm a uye ise kullanici Ayni sekilde likelama, silme ekleme (edit) Bunlar da static (turk takimlari) Predetermined Katil ve Cikma haklari fakat sadece favori takimin communda edit yetkisi. En ustte description + lig tablosundaki durumu.
Comments: Baska bir commente ref verilebilir ki bu sayede cevap verildigi anlasilsin Kullanici ref verebilir syntax: @username
Notifications: comment etiketleme ve username refi ve postunun likelanmasi (x kisi likeladi) durumlarinda bildirim postun veya commentin sahibine.
Post: Fotograf eklenebilir. Kelime siniri: 200. 1 Fotograf hakki. max: 25mb (cloud tarafi calisma gerektiriyo kaydetmek icin.) Tag: takimlar olabilir. Community tagi. Galatasaray fener tagli bir post: derbi yorumu ve Galatasaray communitysinde paylasilmis olsun: Tag GS FB , GSComm
Authorization: Authority Types: SystemAdmin or Standard
Giris yaparken kayit formu favori turk takimi. Favori takimi secilince otomatik olarak o communtiy e dahil olucak. Takim sectikten sonra degistiremezsin ve sadece fav takiminin comm una girebilir.
Signup: emaille kaydolunmak zorunda (unique) ve sifre
Login: emaille giris yapilmak zorunda ve sifre
Username: Unique olmak zorunda ve degistirme hakki ayda 1.
Personal Page: Kullanicinin kendisini tanittigi desc Profile picture Favori takimi Twitter mantiginda son postlar gozuksun Takip edilenler takipciler gozukmeli.
Anasayfa: Semantic query sonucu gelen postlar gozukmeli PostDate descending sorted
Static pages: Lig tablosu canli Gunun maclari/ Sezon maclari Takimlar (Communitylerini gosteren linkler)
Search: 1.2.2.3. System shall keep a history of the searches of authenticated users. 1.2.2.3.1. Authenticated users shall be able to delete their history at will. Postlarin icinde bulunan taglere gore arama veya filter yapilabilir.
Users shall be able to search another user by their username. Kullanici aramak icin @ yazilmak zorunda. (Bunun icin search bara aciklayici placeholder) @ yoksa postlar arasi arama
Filter: Fotograflari postlari goster Belirtilen tagleri icieren postlari goster.(Comm, takimismi) Tarih araligi goster
order: most liked
🏠Home
- First Customer Milestone Report
- RAM
- Requirements
- Mockups
- Sequence Diagrams
- Scenarios
- Use Case Diagram
- Class Diagram
- Milestone1 Presentation Scenarios
- Meeting Notes 7 - Nov 12
- Meeting Notes 6 - Nov 5
- Optional Meeting Notes 1 ‐ Oct 21
- Meeting Notes 5 - Oct 15
- Meeting Notes 4 - Oct 8
- Meeting Notes 3 - Oct 3
- Meeting Notes 2 - Oct 1
- Meeting Notes 1 - Sep 24
- Deniz Ulaş Poyraz
- Eren Donmez
- Ersel Çanakçılı
- Oğuz Kağnıcı
- Onur Çerli
- Yekta Ercul
- Ali Alperen Sönmez
- Huseyin Turker Erdem
- Mehmet Tuluyhan Sozen
352 Material
- Final Milestone Report
- Milestone 2 Report
- RAM
- Use Case Diagram
- Sequence Diagrams
- Class Diagrams
- Requirements
- Elicitation Questions
- Mockups
- Scenarios
- Milestone 1 Report
- Our Favourite Repositories
- Linked Data and SPARQL
- Web Application Development
- API Development and Utilization
- Wikidata and Wikidata API
- Mobile Application Development
- Android Studio
- Git
- Meeting Notes 10 ‐ May 10th
- Meeting Notes 9 ‐ Apr 25th
- Meeting Notes 8 ‐ Apr 21st
- Meeting Notes 7 ‐ Apr 12th
- Meeting Notes 6 ‐ Mar 14th
- Meeting Notes 5 ‐ Mar 11th
- Meeting Notes 4 - Mar 7th
- Meeting Notes 3 - Mar 3rd
- Meeting Notes 2 - Feb 22nd
- Meeting Notes 1 - Feb 18th