Üsküdar University

Faculty of Engineering and Natural Sciences

Department of Software Engineering

Software Requirment Engineering

CODE: SE-201
ASSESSMENT: Project-PhaseOne NUMBER: 1 TIME: 4 Hours TITLE: REQUEST FOR PROPOSAL (RFP)
1. This work should be done indvidually within a group. 1.This work is based on Chapter

2. This work needs to be documented and presented. a. Identify the system or compan
(Use the provided template) Preferable a real client. (Group W

3. This work needs to be completed and Submited by b. Identify the objective, mission
WEEK 07 (05/12/2021-08:59 am) (Group Work)

4. This work needs to be submit online via ALMS in c. Identify minimum 2 stackhold
PDF format. non-functional requirment ident
Work)
INSTRUCTION: TASK:

d. Identify and Define 1 Functio

1 Non-Functional Requirement
Minmum of Nine FR & Nine N
(Individual Work)
e. Document based on the provı
TEMPLATEv1.0) and submit t

2. Select a suitable slot in the 3.

sheet for Week 8 on the 6th or 8
team members should be presen
me the selected slot for me to se
ences
ng

ST FOR PROPOSAL (RFP)

his work is based on Chapter 1, 2 & 3:

dentify the system or company you will work with.

ferable a real client. (Group Work)

dentify the objective, mission and goals of the system

oup Work)

dentify minimum 2 stackholders for the functional and

-functional requirment identifed in d. (Individual
rk)

dentify and Define 1 Functional Requirement (FR) and

on-Functional Requirement (NFR) per student
nmum of Nine FR & Nine NFR for the selected system
dividual Work)
Document based on the provıded template (RFP-
MPLATEv1.0) and submit the output

elect a suitable slot in the 3. Peer Review Schedule

et for Week 8 on the 6th or 8th December 2021 (all
m members should be presented) Group Leader send
the selected slot for me to set it.
 Üsk
Faculty of Engin
Department

SE201 – Softw
R

ITEM 5 4

All Items are completed and

System Request suitable company <inbetween>
Objective/ Mission/
Vision Complete and logical Mission <inbetween>
Users of the System Complete and matching the system
(Stakeholder) functions <inbetween>
Identify the major work
components for the requirements
Functional requirements analysis <inbetween>
non-Functional Identify the major non-functional
requirements requirements <inbetween>
1: Sponsor Meetings
2: Collaborates effectively with
team members.
Collaboration 3: Combining ideas. <inbetween>
Submit on Time 10 days late <inbetween>
Formating Consistency <inbetween>

ITEM

Individual

Group
 Üsküdar University
Faculty of Engineering and Natural Sciences
Department of Software Engineering

SE201 – Software Requirements Analysis

RFP DOCUMENT

3 2 1

>3 Items are Completed <inbetween> >1 Items are Completed

< 2 major not complete and logic
>3 Items are Completed and
Matching
< 2 major work components for
the requirements analysis are
missing
< 2 major non-functional
requirements are missing
<inbetween> < 3 major not complete and logic
<inbetween> >1 Items are Completed
< 3 major work components for
the requirements analysis are
<inbetween> missing
< 5 major non-functional
<inbetween> requirements are missing

1: Sponsor Meetings 1: Collaborates effectively with

2: Collaborates effectively with team members.
team members. . <inbetween> 2: Combining ideas.
5 days late <inbetween> 1 day late
3< non consistence error <inbetween> 5< non consistence error

ITEM MARKS
5
5
Individual
2
0
2
4
Group
1.5
0.5
s

Fill in this column

only
0 MARKS GIVEN WEIGHT TOTAL

Not Completed 5 0.4 2

Not logic Mission 5 0.8 4

Not Completed 5 1 5

No Functional Requirement 5 1 5

No non-Functional Requirement 5 0.4 2

No Sponsor Meeting
No Team Collaboration
No Ideas Combintion 5 0.3 1.5
On Due Date 0 -1 0
No Formating 5 0.1 0.5
20
FINAL MARK

12

8
 Üsküdar University
Faculty of Engineering and Natural Sciences
Department of Software Engineering

Software Requirment Engineering

CODE: SE-201
TITLE: REQUEST FOR
ASSESSMENT: Mid Term NUMBER: 1 TIME: 4 Hours PROPOSAL (RFP)
Peer Review Schedule
Time Slot Date Team Status
9:30 6th Dec
10:00 6th Dec
10:30 6th Dec E Completed
11:00 6th Dec O Completed
11:30 6th Dec D Completed
12:00 6th Dec T Completed
12:30 6th Dec X Completed
14:00 6th Dec S Completed
14:30 6th Dec G Completed
15:00 6th Dec A Completed
15:30 6th Dec K Completed
11:30 8th Dec N Completed
12:00 8th Dec H Completed
12:30 8th Dec R Completed
14:00 8th Dec C Completed
14:30 8th Dec F Completed
15:00 8th Dec M Completed
15:30 8th Dec L Completed
16:00 8th Dec I Completed
16:30 8th Dec Z Completed
17:00 8th Dec J Completed
17:30 8th Dec Y Completed
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
R
S
T
X
Y
Z
 Üsküdar University
Faculty of Engineering and Natural Sciences
Department of Software Engineering

Software Requirment Engineering

CODE: SE-201
ASSESSMENT: Project-PhaseTwo NUMBER: 1 TIME: 4 Hours TITLE: Software Requirment Specification SRS
1. This work should be done indvidually within a group. 2.This work is based on Chapter 4

2. This work needs to be documented and presented. a. Study the ISO/IEC/IEEE Standa
(Use the provided template) Check the tailored SRS-TEMPLA
Work)
3. This work needs to be completed and Submited by b. Prepare the USE CASES from t
WEEK 13 (16/01/2022-12:03 am) requirments and non Functional R
on Phase One (Individual Work)
INSTRUCTION
4. This work needs to be submit online via ALMS in c. Prepare the components of the S
: PDF format. TASK:

d. Document based on the provıde

TEMPLATEv1.0) and present the
revıew
2. Select a suitable slot in the 6. Pe
sheet for Week 13 & 14 on the 17
January 2022 (all team members s
Group Leader send me the selected
 iences
ing

Requirment Specification SRS

his work is based on Chapter 4,5, 6, 7 & 8:

tudy the ISO/IEC/IEEE Standard 29148 (2011).

eck the tailored SRS-TEMPLATEv1.0. (Individual
rk)
repare the USE CASES from the functional
uirments and non Functional Requirement you selected
Phase One (Individual Work)
repare the components of the SRS (Group Work)

Document based on the provıded template (SRS-

MPLATEv1.0) and present the output ın formal
ew
elect a suitable slot in the 6. Peer Review Schedule
et for Week 13 & 14 on the 17th, 19th, 24 or 26
uary 2022 (all team members should be presented)
up Leader send me the selected slot for me to set it.
 Üsküdar University
Faculty of Engineering and Natural Sciences
Department of Software Engineering

SE201 – Software Requirements Analysis

SRS DOCUMENT

Fill in this
No Items 0 1 2 3 4 Weight
column
only Marks

Frame, page number, table of Frame, page number, table of

Frame, Table of content, and
Not Page number of document is content, list of figure table and content, list of figure table and
1 Software Document Basic Elements page number of document are 1
Available available Document ITEM number are Document ITEM number are
available
available available and follow the format
4 4

Difficulty following the content Most information in logical,

Cannot understand the content Most information in logical
Not of the document because the interesting sequence which
2 Organization because there is no sequence of sequence which reader can 1
Available information is not on the right audience don’t have any
information. follow and easy to understand
sequence difficulty to understand
4 4

Document have more than 5 Document have less than 5 error

Not Document have more than 10 error Document have no error in
3 Consistency error in outlining the topic and in outlining the topic and sub 1
Available in outlining the topic and sub -topic outlining the topic and sub -topic
sub -topic -topic
4 4
Most Content are relate to the Most Content are relate to the
Not Most of the content not really relate Most content occasionally relate
4 Content topic with the simple explanation topic with the explanation that 2
Available to the topic. to the topic
that can be understand easy to understand
4 8
All table or figure caption
All table or figure caption All table or figure caption
Not Maximum 3 table or figure caption available and reader can easy to
5 Table and Figure available but reader difficult to available and reader can easy to 1
Available not available understand and the explanation
understand. understand.
is available. 4 4
Most of related reference
Not Minimal related reference document The related reference document document are stated with the
6 Reference Document <inbetween> 1
Available are stated are stated correct reference item number
and source. (must include RFP) 4 4

The context diagram represent The context diagram represent The context diagram accurately
Not The context diagram not accurately
7 Context Diagram few of the system boundary with few of the system boundarywith represent most of the system's 2
Available design and generally unclear
error minimal error boundary
4 8
Not Acceptable but cover minimal Acceptable and cover most
8 Requirement Listing Exist but illogical <inbetween> 1
Available functions functions
4 4
The use case description not The use case description The use case description The use case description
Not
9 Use Case & Use Case Description accurately design and generally represent few of the system represent few of the system accurately represent most of the 4
Available
unclear functions with error functions with minimal error system's functions 4 16
The diagram represent few of The diagram accurately
Not The diagram not accurately design The diagram represent few of
10 Sequence Diagram the system functions with represent the functions of the 4
Available and generally unclear the system functions with error 4 16
minimal missing system
Not 80% Complete and acceptable Complete , consistent and
11 User Interface not complete & many errors 50% complete of UI 4
Available user interface acceptable user interface 4 16
Not Shows individually works Shows 75% been quality Shows almost all been
12 SRS Quality Shows unchecking 0.5
Available throughout SRS checking quality checking
4 2

13 Members Understanding based on Formal review 2.5

4 10

Total 100

FINAL
ITEM MARKS MARK
16
16
16
Individual 60
10
2
0
4
4
4
8
Group 40
4
4
8
4
 Üsküdar University
Faculty of Engineering and Natural Sciences
Department of Software Engineering

Software Requirment Engineering

CODE: SE-201
TITLE: REQUEST FOR
ASSESSMENT: Mid Term NUMBER: 1 TIME: 4 Hours PROPOSAL (RFP)
Peer Review Schedule
Date Time Slot Team Status
17th Jan 9:30
17th Jan 10:30
17th Jan 11:30
17th Jan 13:30
17th Jan 14:30
19th Jan 9:30
19th Jan 10:30
19th Jan 11:30
19th Jan 13:30
19th Jan 14:30
19th Jan 15:30
24th Jan 9:30
24th Jan 10:30
24th Jan 11:30
24th Jan 13:30
24th Jan 14:30
26th Jan 9:30
26th Jan 10:30
26th Jan 11:30
26th Jan 13:30
26th Jan 14:30
26th Jan 15:30
A
B
C
D
E
F
G
H
I
J
K
L
M
N
O
P
R
S
T
X
Y
Z