CENG3004: Software Engineering

My Garden Project

Software Requirements Specification Document

20/04/2021

Team Members:

Mert Can DENLİ

Ayça ÖKSÜZTEPE
Mehmet Kıvanç ERBUDAK
Contents
1 Overview.............................................................................................................................3
2 Requirements......................................................................................................................4
2.1 Functional Requirements.............................................................................................4
2.2 Nonfunctional Requirements.......................................................................................5
3 Actors and Roles.................................................................................................................6
4 Use Cases............................................................................................................................7
5 System models....................................................................................................................8
5.1 Use Case Diagrams (at least three use cases per team member).................................8
5.2 Class Diagrams (at least twelve classes).....................................................................8
5.3 Sequence Diagrams (at least one per team member)...................................................8
5.4 Actvitiy Diagrams (at least one per team member).....................................................8
5.5 Statechart Diagrams (at least one)...............................................................................8
6 User Interface Diagrams (at least one)...............................................................................9
7 Glossary............................................................................................................................10
8 References.........................................................................................................................11
9 Appendix...........................................................................................................................12

2
1 Overview

The customer can be any person who owns the garden.

The inexperienced client comes to find out what he/she can grow in his/her garden.
After learning the weather conditions and soil balance, analysis will be done.
Based on the analysis results, recommendations are made to the customer.
If there is a need for fertilizers or pesticides, these are recommended after the customer’s
preference.
Actually, it is a computer application that does these.
When necessary, the expert person steps in and uses the program.
As a result, plants are grown in the most efficient way.

3
2 Requirements

2.1 Functional Requirements

Requiremen Source Priority Description
t Identifier (e.g. (High/
Interview Medium/
with XX Low)
on
DD/MM/
YYYY)
FR-11 Medium The app automatically provides accurate planting times for plants
and trees.
FR-2 High The app provides information about soil according to user location.
FR-3 Medium The app stores information about users to provide personalized
information.
FR-4 High The app reminds users when to water their plants.
FR-5 Low The app has a tool for garden planning.
FR-6 Low The user can purchase seeds online.
FR-7 Low Users posts their questions to forum.

1
Use prefix “FR-“ for functional requirement identifiers

4
2.2 Nonfunctional Requirements

Requiremen Source Priority Description

t Identifier (e.g. (High/
Interview Medium/
with XX Low)
on
DD/MM/
YYYY)
NR-12 Low App shold cover all soil types in Turkey
NR-2 High App should contain more than 100 plants.
NR-3 High App should contain more than 50 tree types.
NR-4 Medium App should have information that covers all climates that present in Turkey.

2
Use prefix “NR-“ for non-functional requirement identifiers

5
3 Actors and Roles
The customer communicates directly with the system.
When necessary, the expert tries to help about subject.

6
4 Use Cases

Use Case UC-13

Identifier
Use Case Name Plant Search
Participating User
Actors
Flow of events Enter plant name and search.
Entry condition Search button on click.
Exit conditions Item found.
Related non- App should contain more than 100 plant
functional
requirements4

Use Case UC-25

Identifier
Use Case Name Getting Plant Recommendation
Participating User
Actors
Flow of events Getting information, analzying, giving advice.
Entry condition User clicks the respective button.
Exit conditions User clicks out.
Related non-
functional
requirements6

Use Case UC-37

Identifier
Use Case Name Reques expert help
Participating User, expert
Actors
Flow of events Getting information, Online video call, analzying, giving advice.
Entry condition User creates help request on respective section.
Exit conditions User ends the call.
Related non-
functional
requirements8

3
Use prefix “UC-“ for use case identifiers
4
Use the non-functional requirement identifier from Section 2 when appropriate
5
Use prefix “UC-“ for use case identifiers
6
Use the non-functional requirement identifier from Section 2 when appropriate
7
Use prefix “UC-“ for use case identifiers
8
Use the non-functional requirement identifier from Section 2 when appropriate

7
 Use Case UC-49
Identifier
Use Case Name Pay for expert
Participating User, expert
Actors
Flow of events Choose credit card and pay
Entry condition User wants to create expert help request.
Exit conditions Payment complete or incomplete
Related non-
functional
requirements10

Use Case UC-511

Identifier
Use Case Name Add products to system
Participating Product manager
Actors
Flow of events Entering necessary informations and price.
Entry condition New products comes to market.
Exit conditions Product is added.
Related non-
functional
requirements12

Use Case UC-613

Identifier
Use Case Name Update Product
Participating Product manager
Actors
Flow of events Choose product update its price and other attributes.
Entry condition Product attributes needs to change.
Exit conditions Changed succesfully.
Related non-
functional
requirements14

Use Case UC-815

Identifier
9
Use prefix “UC-“ for use case identifiers
10
Use the non-functional requirement identifier from Section 2 when appropriate
11
Use prefix “UC-“ for use case identifiers
12
Use the non-functional requirement identifier from Section 2 when appropriate
13
Use prefix “UC-“ for use case identifiers
14
Use the non-functional requirement identifier from Section 2 when appropriate
15
Use prefix “UC-“ for use case identifiers

8
 Use Case Name Add item to cart
Participating User
Actors
Flow of events Choose products and add them to cart.
Entry condition User adds item to cart.
Exit conditions Added succesfully.
Related non-
functional
requirements16

Use Case UC-917

Identifier
Use Case Name Send Product
Participating Product manager
Actors
Flow of events Put item in a cargo
Entry condition An item is being bought
Exit conditions Cargo is on the way.o
Related non-
functional
requirements18

16
Use the non-functional requirement identifier from Section 2 when appropriate
17
Use prefix “UC-“ for use case identifiers
18
Use the non-functional requirement identifier from Section 2 when appropriate

9
5 System models
5.1 Use Case Diagrams

10
5.2 Class Diagrams

5.3 Sequence Diagrams

11
12
5.4 Actvitiy Diagrams

13
5.5 Statechart Diagrams

14
6 User Interface Diagrams (at least one)

15
16
7 Glossary

17
8 References

18
9 Appendix

19