University of the West of Scotland
MSc Information Technology
COMP11112 Enterprise Architecture
Coursework FAQ 2024-25 T3
1. Do we have to use StarUML to draw the diagrams?
No, you don’t. You are free to use any tool to draw your diagrams as long as your diagrams conform
to standard UML.
2. We have formed a group of 4 students. Shall we make 4 coursework submissions?
Only one submission is required from each group. Please make sure names and Banner IDs of
group members appear on the cover page of your coursework report.
3. Do we have to put citations and references in our coursework report? If yes, which referencing
style do we have to use?
You are not conducting any literature review for your coursework or including works of others from
external sources in your report. Therefore, you are not expected to provide any citations or
references.
4. When is the submission deadline for the coursework?
Coursework submission deadline is Friday 25th July 2025 16:59. Late submissions are subject to
UWS regulations.
5. What is the weight of the coursework on my overall grade?
There is only one assessment component in this module. Therefore, the coursework will contribute
to 100% of your overall grade.
6. We believe that some process information related to DVD rental business provided in the case
study described in the coursework specification is not compatible with what we know from our
real-world and work experience. Can we change the scenario to make it more realistic?
No, you cannot. You must accept the provided case study in its current form. It is what you have
been told by your client and your business analysts. So, you must assume it is correct and valid,
and then you must design and develop your solution accordingly.
7. Our use case diagram looks very simple. Do we have to make it look more sophisticated by
dividing big use cases into smaller ones and then by including/extending them?
Use cases represent individual scenarios that can be performed independently. For example, a
person comes and registers with our e-commerce web site. The same person comes and logins the
1
system on another day. These two (register and login) are two individual use cases. They are not
including or extending each other. Of course, logically, a person must register before being able to
login, but this does not imply that “login” use case will include “register” use case! Registering
starts by entering some personal information, continues by some data validations, and finally ends
after storing user data in the system. Similarly, login process starts by entering user id and
password, then maybe receiving an access code by SMS, entering that code, then validating the
supplied information, and finally ends by letting the user in or rejecting them.
8. In Information Systems Analysis and Design (ISAD) module we have learned that there must be
a <<control>> class in our class diagram. Do we have to identify a control class in the information
model in Q5?
In ISAD module, you are designing an Object-Oriented system by identifying classes, their
attributes, operations and associations. In this module, on the contrary, you are designing a
service-oriented solution and the purpose of the information model class diagram is different. It
will only display the entities, their attributes, and their associations. Therefore, classes must not
have any operations, and there must not be a <<control>> class on the diagram.
