Software Engineering Assignment

Question 2
Name Create a new object

Actors Manager

Description Object here is a new customer, artist, art, art group or exhibition.
User is Manager.

Triggers Manager can trigger this scenario when a new object is to be

created.

Pre Conditions None.

Post Conditions A new object is created.

Mainline Scenario 1. User requests a new object form.

2. The user is asked for the type of object he/she wants to create.
3. The form is sent to the user.
4. The user fills in appropriate information and sends the form back
to the server.
5. The server checks the sent information.
6. A new object is created and it’s information is stored in the
database.

Alternative Same till step 1 of mainline scenario

Scenario - 1 3. The user doesn't have the authority to create the requested
object.
4. The user is sent a message “You can’t create the requested
object”.

Alternative Same till step 4 of mailine scenarios

Scenario - 2 5. The characters used are found to be invalid.
6. The user is sent a message, “Enter valid characters”.
7. Step 3.
Name View Customer information

Actors Customer / Manager

Description User here is a Customer or Manager.

Triggers User can trigger this scenario when he/she wants to see information
related to the customer.

Pre Conditions None.

Post Conditions None.

Mainline Scenario 1. User requests customer information.

2. User is sent customer information from the database.

Alternative None.
Scenario

Name Update customer information

Actors Customer / Manager

Description User here is a Customer or Manager.

Triggers User can trigger this scenario when a piece of information related to
the customer is incorrect or no longer valid.

Pre Conditions Customer information is incorrect or no longer valid.

Post Conditions Customer information is updated and is now correct.

Mainline Scenario 1. User views customer information.

2. User requests a customer information update form.
3. The form is sent to the user along with the information currently
stored in the database filled in the form.
4. The user updates information and sends the form back to the
server.
5. The server checks the sent information.
6. The new information overwrites the current information in the
database.

Alternative 3. The user doesn't have authority to update the requested

Scenario - 1 information.
4. The user is sent a message “You can’t update the requested
information”.

Alternative 6. The characters used are found to be invalid.

Scenario - 2 7. The user is sent a message, “Enter valid characters”.
8. Step 3.
Name View Artist information

Actors Customer / Artist / Manager

Description User here is a Customer or Artist or Manager.

Triggers User can trigger this scenario when he/she wants to see information
of an artist of their interest

Pre Conditions None.

Post Conditions None.

Mainline Scenario 1. User requests artist information.

2. User is sent artist information from the database.

Alternative None.
Scenario

Name Update Artist information

Actors Artist / Manager

Description User here is an Artist or Manager.

Triggers User can trigger this scenario when a piece of information related to
the artist is incorrect or no longer valid.

Pre Conditions Artist information is incorrect or no longer valid.

Post Conditions Artist is updated and is now correct.

Mainline Scenario 1. User views artist information.

2. User requests an artist information update form.
3. The form is sent to the user along with the information currently
stored in the database filled in the form.
4. The user updates information and sends the form back to the
server.
5. The server checks the sent information.
6. The new information overwrites the current information in the
database.

Alternative 3. The user doesn't have authority to update the requested

Scenario - 1 information.
4. The user is sent a message “You can’t update the requested
information”.

Alternative 6. The characters used are found to be invalid.

Scenario - 2 7. The user is sent a message, “Enter valid characters”.
8. Step 3.
Name View Art information

Actors Customer / Artist / Manager

Description User here is a Customer or Artist or Manager .

Triggers Customer can trigger this scenario when he/she wants to see
information of an art of their interest

Pre Conditions None.

Post Conditions None.

Mainline Scenario 1. User requests art information.

2. User is sent art information from the database.

Alternative None.
Scenario

Name Update Art information

Actors Artist / Manager

Description User here is an Artist or Manager.

Triggers User can trigger this scenario when a piece of information related to
an art piece is incorrect or no longer valid.

Pre Conditions Art information is incorrect or no longer valid.

Post Conditions Art is updated and is now correct.

Mainline Scenario 1. User views art information.

2. User requests an art information update form.
3. The form is sent to the user along with the information currently
stored in the database filled in the form.
4. The user updates information and sends the form back to the
server.
5. The server checks the sent information.
6. The new information overwrites the current information in the
database.

Alternative 3. The user doesn't have authority to update the requested

Scenario - 1 information.
4. The user is sent a message, “You can’t update the requested
information”.

Alternative 6. The characters used are found to be invalid.

Scenario - 2 7. The user is sent a message, “Enter valid characters”.
8. Step 3.
Name View Art Group information

Actors Customer / Artist / Manager

Description User here is a Customer or an Artist.

Triggers A User can trigger this scenario when he/she wants to see
information of an art group of their interest

Pre Conditions None.

Post Conditions None.

Mainline Scenario 1. User requests art group information.

2. User is sent art group information from the database.

Alternative None.
Scenario

Name Update Art Group information

Actors Manager

Description User here is a Manager.

Triggers User can trigger this scenario when a piece of information related to
an art group is incorrect or no longer valid.

Pre Conditions Art Group information is incorrect or no longer valid.

Post Conditions Art Group is updated and is now correct.

Mainline Scenario 1. User views art group information.

2. User requests an art group information update form.
3. The form is sent to the user along with the information currently
stored in the database filled in the form.
4. The user updates information and sends the form back to the
server.
5. The server checks the sent information.
6. The new information overwrites the current information in the
database.

Alternative 3. The user doesn't have authority to update the requested

Scenario - 1 information.
4. The user is sent a message, “You can’t update the requested
information”.

Alternative 6. The characters used are found to be invalid.

Scenario - 2 7. The user is sent a message, “Enter valid characters”.
8. Step 3.
Name View Exhibition information

Actors Customer / Artist / Manager

Description User here is a Customer or Artist or Manager..

Triggers A User can trigger this scenario when he/she wants to see
information of an exhibition of their interest

Pre Conditions None.

Post Conditions None.

Mainline Scenario 1. User requests exhibition information.

2. User is sent exhibition information from the database.

Alternative None.
Scenario

Name Update Exhibition information

Actors Manager

Description User here is a Manager.

Triggers User can trigger this scenario when a piece of information related to
an exhibition is incorrect or no longer valid.

Pre Conditions Exhibition information is incorrect or no longer valid.

Post Conditions Exhibition is updated and is now correct.

Mainline Scenario 1. User views exhibition information.

2. User requests an exhibition information update form.
3. The form is sent to the user along with the information currently
stored in the database filled in the form.
4. The user updates information and sends the form back to the
server.
5. The server checks the sent information.
6. The new information overwrites the current information in the
database.

Alternative 3. The user doesn't have authority to update the requested

Scenario - 1 information.
4. The user is sent a message, “You can’t update the requested
information”.

Alternative 6. The characters used are found to be invalid.

Scenario - 2 7. The user is sent a message, “Enter valid characters”.
8. Step 3.
Question 3
 Question 4
Association:
An association is defined as an organization of people with a common purpose and
having a formal structure. It represents a binary relationship between two objects
that describes an activity. It is a relationship between objects. For example, A star
can be associated with multiple planets.

Aggregation:
An aggregation is a collection, or the gathering of things together. This relationship
is represented by a “has a” relationship. In other words, aggregation is a group, body,
or mass composed of many distinct parts or individuals For example, the list of
planets in our solar system is an example of aggregation.

Association Aggregation

1. Flexible 1. Inflexible

2. It is represented by a “has a”+ 2. It is represented by a “has a”

“whole-part” relationship relationship

3. Diamond shape structure is used 3. Line segment is used between the

next to the assembly class. components or the class
Question 5