16 lines
5.4 KiB
HTML
16 lines
5.4 KiB
HTML
<!doctype html>
|
||
<html>
|
||
<head>
|
||
<title>Description Topic 4 assignment description and upload</title>
|
||
<meta charset="utf-8">
|
||
|
||
</head>
|
||
<body>
|
||
<p dir="ltr" style="text-align: left;"></p><p><strong><u></u></strong></p><p><strong><u></u></strong></p><p><strong><u>About this task</u></strong></p><p><span>You can find the mandatory assignment description in here. On this, you work on together as a group and return as a PDF for grading using the associated Moodle assignment link.</span></p><p></p><p><strong><br></strong></p><p><strong>Mandatory Assignment (topic 4, submit via Moodle as PDF)</strong><br></p><p><u>General requirements</u></p><p>Max 2-4 pages (+1 cover page). Please concentrate on the diagrams and then explaining the rationale behind their design.</p><p>Submit this assignment via Moodle as PDF (see the exercises and assignment page for the return link).</p><p><br></p><p><u>Assignment description</u></p><p>This week's assignment involves analyzing a system description and creating a series of UML diagrams based on the description. We start with describing use case diagrams, proceed to conceptual modeling, and finally analyze where the users interact with technological objects through BCE modeling.</p><p>We use "Use Case Driven Object Modeling with UML: Theory and Practise" ( <a href="https://doi-org.ezproxy.cc.lut.fi/10.1007/978-1-4302-0369-8">https://doi-org.ezproxy.cc.lut.fi/10.1007/978-1-4302-0369-8</a> ) as our step by step guide. It is an older edition, but the steps are well described and very clear, compared to some alternative books.</p><p><br></p><p><strong>First step</strong>, read the deliverables listed and then then case description. Then, create a simplified domain model based on the description written in Chapter 2.</p><p><br></p><p><strong>Second step</strong>, read Chapter 3 and draw an use case diagram. You can also review a <a href="https://www.visual-paradigm.com/guide/uml-unified-modeling-language/what-is-use-case-diagram/">visual paradigm tutorial on use case diagrams</a>.</p><p><br></p><p><strong>Third step</strong>, review Chapter 5 and use the robustness analysis method to create a Boundary - Entity - Controller diagram. A BCE diagram (called a robustness diagram) is a way of analyzing and identifying which kind of technological objects or interfaces the user works with.</p><p><br></p><p>Critical advice: Do not make the BCE diagram too complex. For example, you can have a level of detail similar to a diagram describing an ATM (originally by Pearce from SJSU), presented as an example below.</p><p><img src="files/image011.jpg" alt="" width="733" height="273" role="presentation" class="img-fluid atto_image_button_text-bottom"><br></p><p><br></p><p>Motivation: The author of the book expresses the need for a BCE analysis (also called robustness analysis) as follows: "To get from use cases to detailed design (and then to code), you need to link your use cases to objects. The technique we describe in this chapter, robustness analysis, helps you to bridge the gap from analysis to design by doing exactly that. In a nutshell, it’s a way of analyzing your use case text and identifying a first-guess set of objects for each use case. These are classified into boundary objects, entity objects, and controllers (which are often more like functions than objects)."<br></p><p><u><br></u></p><p><u>Case description</u></p><p>In this case you and your team are tasked to design an UML design for a single use case from either EnviroSense or AudioNow system.</p><p>Select and define <em>one </em>of these use cases from EnviroSense (if you are working on that one): Uploading a sensor observation with hand-held measuring device, triggering a download from all remote sensors that are online, or refreshing an analytics view from the database as a batch process.</p><p>Select and define <em>one </em>of these use cases from AudioNow (if you are working on that one): Buying physical merchandise, buying a podcast subscription, or joining a shared listening experience online room.</p><p><u><br></u></p><p><u>Deliverables</u></p><p></p><span lang="EN-US">Following the instructions above, draw a 1) simplified domain model, 2) use case diagram, and 3) BCE diagram (robustness diagram). Describe the design rationale and what happens in each diagram in your own words. Use complete sentences, add captions to your figures, and pay attention to flow and readability of your report.<br><br>Return this work as a single PDF file into Moodle.<br><br><p>Include the Declaration of AI Use at the end of the assignment. The declaration is required for grading the work whether you used AI tools or not.</p><br></span><br><strong><u>Declaration of AI Use</u></strong><br>
|
||
<p>In a separate chapter at the end of the document, list the following.</p>
|
||
<p>1) Name all AI systems that were used in the development of the contents of this document, and for each</p>
|
||
<p>2) How and where they were used (illustrations, proofreading, getting ideas for text, to generate diagrams etc.) or</p>
|
||
<p>3) Clearly state that no AI assistance or tools were used in this assignment.</p>
|
||
<p>This Declaration is mandatory part of the submission and leaving it out means that the work is incomplete and should not be graded. Declaring that no AI was used in the development of the document, but getting high number in TurnItIn AI check is also a valid grounds for failing the work just by itself. </p><br><p></p>
|
||
</body>
|
||
</html> |