SEG 3101 - Assignments
Please create teams of 4 or 5 members for the project and
assignments. Make sure you have compatible schedules! Edit teams
online, and give yourself an exciting team name!
Assignment 1: Critique of a specification
In the lab, you have inspected and criticized a specification of
software requirements and a request for proposals. Now is your
chance to do the same for a system requirements specification.
The goals of this lab are:
- To give you an opportunity to examine a real requirements
- To give you an opportunity to familiarize yourself with real
requirements specification templates (e.g., as in the ISO/IEC/IEEE
29148:2011 standard, available on campus or via VPN).
- To give you an opportunity to inspect a specification in a
different context (system level).
- To check your understanding of good requirements writing
practices based on constructive criticism.
- To improve an existing document on an unknown application
Part I : Critique of the structure (4x8=32 marks)
You are invited to consult the ISO/IEC/IEEE 29148:2011 standard for this
- Briefly discuss, on 1/2 to 3/4 of a page, two
major positive aspects related to the SysRS document
structure. Justify your answer by specifying what you find
appropriate for the document (e.g., a standard element relevant
to the domain context).
- Briefly discuss, 1/2 to 3/4 of a page, two
major negative aspects related to the SysRS document
structure. Propose improvements based on your understanding of
the document goals (what would improve the document such that it
is better able to meet its goals) and standards (i.e.,
Part II : Critique of the content (4x8=32 marks)
Using the characteristics of good requirements documents
discussed in class and in the tutorial, identify four
major problems in the specification document related to
its content. For each, clearly indicate the part of the document
in question (subsection, or recurring problem covering several
sections/requirements), the observed weakness, and your corrective
measure (advice). Aim to suggest improvements that will bring the
most value to the readers of the specification.
Part III: Improvements to individual requirements (6x5=30 marks)
Criticize the following individual requirements of the inspected
specification (you have a very elaborated context here), and
rewrite them to improve their precision when necessary:
- 220.127.116.11 The Core System shall identify misbehavior with
- 18.104.22.168 The Core System shall manage the health of the Core
- 22.214.171.124 The Core System shall manage 1609.2 Certificates to
- 126.96.36.199 The Core System shall synchronize the time of day
with all the Core Subsystems every 10ms (TBD).
- 188.8.131.52 The Core System shall interface with other Core
- 184.108.40.206.3 The Core System's facility shall be protected by
physical access controls.
Part IV: Discussion of the process (3x2=6 marks)
- Explain the process that was followed for the inspection of
the requirements document (role of each group member, goals
identified before the inspection, strategy of inspection
- Did you change the strategy during the process?
- Did you discover problems which you did not expect in this
kind of "professional" document?
Quality of the report
Pay attention to the tone of the report (needs to be constructive),
to the relevance of your recommendations, to clarity, and to
grammar. The report can be written in French or English. Marks can
be removed for a bad report quality.
- Due before October 2nd, 22:00.
- This assignment is to be done by teams of 4-5 students, i.e.,
the same teams formed for the project
- Only one team member needs to submit the report via
Brightspace, but make sure all team members are
identified (name and student number) on the cover page.
Assignment 2: Precise modelling with UML, UCM,
To submit before Friday November 24,
22:00 on BrightSpace. To be done with your project team.
The goals of this assignment are to get familiar with and
demonstrate mastering of
- domain modelling using UML 2 class diagrams and constraints
- system and lifecycle modelling using UML 2 state diagrams
- scenario / business process integration, interaction, and
validation using URN/UCM modelling
- software product lines and feature models
- See this zip
file. Contains the Word and PDF versions of the
assignment, as well as a .jucm file.