Scribd
Upload
8 views

Software Engineering Principles II Exam - Practical (1)

The document outlines the requirements for a Software Requirements Specification (SRS) assignment for students in the Faculty of Science and Computing, due on May 5, 2024. Students must identify a small/medium-sized business needing software to improve efficiency and prepare an SRS document with specific sections including preface, introduction, user requirements, and system models. Additionally, students are required to submit a video of their group discussion and adhere to formatting guidelines, with plagiarism leading to examination cancellation.

Uploaded by

mahorokathy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
8 views

Software Engineering Principles II Exam - Practical (1)

The document outlines the requirements for a Software Requirements Specification (SRS) assignment for students in the Faculty of Science and Computing, due on May 5, 2024. Students must identify a small/medium-sized business needing software to improve efficiency and prepare an SRS document with specific sections including preface, introduction, user requirements, and system models. Additionally, students are required to submit a video of their group discussion and adhere to formatting guidelines, with plagiarism leading to examination cancellation.

Uploaded by

mahorokathy
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 3

FACULTY OF SCIENCE AND COMPUTING

SEMESTER II EXAMINATIONS, MAY 2024

BSE I

PAPER: SOFTWARE ENGINEERING


PRINCIPLES II (PRACTICAL)

PAPER CODE: 1202

DATE: 18TH APRIL 2024

DEADLINE: 5TH MAY 2024

Instructions:

1. This section will be shared with the students on 18th April 2024 to give them ample
time to carry out the appropriate requirements engineering activities.
2. Students will then prepare a Software Requirements Specification (SRS) document.
3. The deadline for the SRS document submission will be on Friday 5th May 2024 at
1:00 pm on the Learning Management System (ODeL).
4. The SRS document must be at least 5 pages but should not exceed 10 pages.
5. Students will be expected to upload a PDF document to the ODeL platform.
6. Text format: Type your text in 12 point Times New Roman, 1.5-line spacing, A4 paper
size, normal margins (1-inch top, bottom, left, right).
7. You will be required to submit a video recording of your first group discussion of this
particular assignment. This should be done via email or Telegram before 25th April
2024.
8. Plagiarism will lead to cancellation of examination.
SECTION A: Preparation of Software Requirements Specification (SRS) document
[50 marks]

You are tasked with identifying a small/medium-sized business/organization that is in


need of a software project intended to improve efficiency in its business processes or
customer satisfaction.

Using the identified business/organization, prepare a Software Requirements


Specification (SRS) document for the proposed software project.

Your document must have the following sections:

1. Preface: This should define the expected readership of the document. This
section should also describe the rationale for the creation of this first version of
the document.
2. Introduction: This section should describe the need for the proposed system. It
should briefly describe the system’s functions and explain how it will work with
other systems. It should also describe how the system fits into the overall business
or strategic objectives of the organization commissioning the software.
3. Definitions and Acronyms: This should define the technical terms used in the
document. You should not make assumptions about the experience or expertise
of the reader.
4. User Requirements Definition: Here, you describe the user requirements.
Remember that user requirements are written for the customers and when
describing them, you should make use of natural language specification that is
understandable to customers.
5. Requirements Elicitation: In this section, describe the requirements elicitation
techniques that you used to discover the user requirements. Explain the reasons
for using those techniques.
6. System Requirements Specifications: This section should describe the
functional and non-functional requirements in more detail. Domain requirements
may be described too. Interfaces to other systems should also be defined.
7. System Models: This section must include graphical system models showing the
relationships between the system components, the system, and its environment.
You should prepare the following models:
i) Context Model that shows the system and its environment
ii) Use case diagram representing all the actors in your case study. Prepare a
use case diagram that represents the current business processes and then
a revised version with some of the proposed changes to these processes.
iii) A class diagram that defines the static structure of classes in a system and
their associations

© Ndejje University 2023/2024

Page 2 of 3
8. System Evolution: This should describe the fundamental assumptions on which
the system is based, and any anticipated changes due to hardware evolution,
changing user needs, and so on. This section is useful for system designers as it
may help them avoid design decisions that would constrain likely future changes
to the system.
9. Conclusion: Write a suitable conclusion to the document.

© Ndejje University 2023/2024

Page 3 of 3

You might also like