Modelling 2012 Project Assignment

Instituto Superior Tcnico,

Universidade Tcnica de Lisboa, Portugal

Group C-NN
Project Phase N
student 1 number, name, e-mail
student 2 number, name, e-mail
student 3 number, name, e-mail
student 4 number, name, e-mail
Submission date: DD/MM/2012

Table of Contents
Introduction .................................................................................................................................................................. 5
Artefact #1 Effort and Work-Breakdown..................................................................................................................... 6
Artefact #2 AWS context model.................................................................................................................................. 7
Artefact #3 AWS requirements list ............................................................................................................................. 7
Artefact #4 AWS Use Cases ........................................................................................................................................ 8
Artefact #5 AWS Use Case Scenarios.......................................................................................................................... 9
Artefact #6 XXXXX ...................................................................................................................................................... 9

Phase N, Group C-NN

Figures
Figure 1. AWS context model. A short text may be added to the caption if required. ................................................... 7
Figure 2. Use Case diagram for the AWS system. .......................................................................................................... 8

Phase N, Group C-NN

Tables
Table 1. Effort per student. ........................................................................................................................................... 6
Table 2. Work-breakdown per student. ........................................................................................................................ 6
Table 3. AWS requirements list. .................................................................................................................................... 7
Table 4. Use cases refining each requirement (traceability matrix). .............................................................................. 8
Table 5. Scenarios of the AWS UC1 Sell Product. ........................................................................................................ 9

Phase N, Group C-NN

Introduction
Maximum one page, with the description of the main decisions, assumptions and relevant issues the group
had to address.

Phase N, Group C-NN

Artefact #1 Effort and Work-Breakdown

Number
Student #1
Student #2
Student #3
Student #4

Name
Student name 1
Student name 2
Student name 3
Student name 4
Total per phase

Phase 1

Phase 2

Phase 3

Phase 4

Total per student

Table 1. Effort per student.

Note: each cell phase x student on Table 1 shall contain the number of effort hours per student. The total per
student column shall contain the sum per row and total per phase row the total per column.
Artefact
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29

Page

Student #1 number

Student #2 number

Student #3 number

Student #4 number

Table 2. Work-breakdown per student.

Phase N, Group C-NN

Artefact #2 AWS context model

A textual description of decision decisions is optional. Alternatively, the text may be included as a note along
with the diagram.

Figure 1. AWS context model. A short text may be added to the caption if required.

Artefact #3 AWS requirements list

ID
1
1.1
1.1.1
1.2
1.3
2
2.1

Source
Line 10

Type
F/NF

Description
Well-formed description of the requirement.

Table 3. AWS requirements list.

Phase N, Group C-NN

Artefact #4 AWS Use Cases

Figure 2. Use Case diagram for the AWS system.

Req ID
1
1.1
1.1.1
1.2
1.3
2
2.1

UC1

UC2

UC3

UC4

X
X
X
X
X
X
X

Table 4. Use cases refining each requirement (traceability matrix).

Phase N, Group C-NN

Artefact #5 AWS Use Case Scenarios

Create one table for each UC described before. All UCs must have one primary scenario and may have zero or
more alternative scenarios (alternative scenarios include exception scenarios).

ID and Name

UC# name of the UC (e.g. UC1 Sell Product)

Summary

One line description of the UC

Bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla
bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla
bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla
bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla bla
bla bla bla bla bla
Actors involved on the UC

Rationale

Actors
Pre-conditions
Primary
Scenario
Post-conditions
Alternative
Scenario
Name

Precondition that apply to the primary scenario

1. Short description of the actions related to step #1.
2.
3.
4.
Precondition that apply to the primary UC scenario
1.
2.
3.
Indicate the pre- and post-condition of each alternative scenario if applicable.
Table 5. Scenarios of the AWS UC1 Sell Product.

Artefact #6 XXXXX
The rest of the report describes the artefacts as required. Pragmatism will be appreciated (lazy layouts will
be penalized). The artefacts shall be presented in the same order as described earlier on this section. If required a text explanation should be included in the diagram (as a note) or above or below the corresponding
diagram.
Note that all diagrams shall be designed for readability and ease of communication. This implies that the
global layout of a diagram (which includes the placement of all graphical elements and connectors) must be
clear and well organized. Always select the text size and use colours and ornaments that facilitate reading
the diagram and communicating a clear message. All diagrams that do not adhere to these requirements will
be penalized.

Phase N, Group C-NN