NIT2213 Software Engineering Assignment

Assignment

READ THE FOLLOWING GUIDELINES CAREFULLY AND UNDERSTAND ALL REQUIREMENTS BEFORE STARTING THIS ASSIGNMENT

Assessment Overview

You are to answer a set of questions about material of the unit. Any diagrams required in response to questions must be drawn in Lucidchart. Textual responses will be written using Microsoft Word.

This assignment is worth 25% of the total marks for the unit. Students complete the assignment individually.

Description

The questions stated below require answers regarding:

  • Use cases
  • Sequence diagrams
  • Class diagrams
  • State Machine Diagram

The marks for each question will total to 25 marks.

You will review relevant material of the unit wherever required to answer the questions.

Ensure that you have completed all lab work relevant to a particular question of the assignment before commencing work on that aspect of the assignment. Lab exercises are where learning, errors and practice occur before embarking on a larger task (the assignment) worth many marks.

All diagrams are to be drawn correctly and neatly. Recall that Learning Outcome 4 of this unit is “Correctly construct and lay out all types of diagrams”. A diagram that does not conform to this learning outcome will be subject to deduction of marks.

In answering questions, submit diagrams as either .pdf or .jpg files from Lucidchart, and textual responses as .doc, .docs or .rtf files.

Important issues

Plagiarism is a form of academic dishonesty that in this case would involve theft of material, and this would result in penalisation of the student.

To avoid students plagiarising material, and therefore prevent penalisation of students, all content that is used in the student’s answers must be totally written in their own words.

You should watch the plagiarism-related videos placed on VU Collaborate.

NIT2213 2017

Assignment Mode

Students carry out the assignment individually. Students must not share any part of their work with each other.

NIT2213 2019

Case Study

Case Study: University Library System

This case is a simplified (initial draft) of a new system for the University Library. Of course, the library system must keep track of books. Information is maintained about both book titles and the individual book copies. Book titles maintain information about title, author, publisher, and catalog number. Individual copies maintain copy number, edition, publication year, ISBN, book status (whether it is on the shelf or loaned out), and date due back in.

The library also keeps track of patrons to the library. Since it is a university library, there are several types of patrons, each with different privileges. There are faculty patrons, graduate student patrons, and undergraduate student patrons. Basic information about all patrons is name, address, and telephone number. For faculty patrons, additional information is office address and telephone number. For graduate students, information such as graduate program and advisor information is maintained. For undergraduate student’s program and total credit hours are maintained.

The library also keeps information about library loans. A library loan is a somewhat abstract object. A loan occurs when a patron approaches the circulation desk with a stack of books to check out. Over time a patron can have many loans. A loan can have many physical books associated with it. (And a physical book can be on many loans over a period of time. Information about past loans is kept in the database.) So, in this case, it is recommended that an association class be created for loaned books.

If a book is checked out that a patron wants, he/she can put that title on reserve. This is another class that does not represent a concrete object. Each reservation is for only one title and one patron. Information such as date reserved, priority, and date fulfilled is maintained. When it is fulfilled, the system associates it with the loan on which it was checked out.

For this case, develop the following diagrams:

  1. Use Case description for checking out books with one any exceptional case
  2. A use case diagram for the whole case study
  3. A class diagram for the whole case study
  4. A sequence diagram for the given case – checking out books 5. Draw a SMD for the case study – Library Management System.

[5 + 4 + 6 + 6 + 4 =25 marks]

NIT2213 2019

Assignment Submission

Your submission will contain separate diagram and text files. All of these files will be zipped for submission at VU Collaborate.

Please be clear that the unit coordinator will not be responsible for a student who is unable to successfully submit different files or the zip file of marking. The student will have no further chance to submit files or receive any remarking, if this is the case.

Please also be clear that unsuccessful (or no) submission of the assignment on VU Collaborate also means no further chance to submit the assignment or receive any remarking. However, VU Collaborate:

  • allows you at a couple of points during the submission process to verify what you are about to submit (i.e., you can click on links to the zip file to check the zip file’s contents that you are about to submit)
  • automatically sends an email your account to confirm successful submission of the assignment.

To help yourself in ensuring that your zip file can be unzipped and the assignment can be marked, download the zip file you submitted via the Assignment VU Collaborate form, “Submit Files - Assignment” (mentioned below), and unzip it somewhere to check its contents. If there is a problem for you in unzipping the files, then there will also be a problem during marking, and you will receive 0 marks.

In submitting your zip in the Assignment area at Assessment Dropbox, you will need to go to the page with a form (“Submit Files - Assignment”) where you upload the zip file. This form contains the “terms and conditions” of the assignment such as declaring that you have not plagiarised, have kept a copy of your work, etc. In uploading and submitting your zip file, you are agreeing to these “terms and conditions”, which you are being bound by in submitting work for the assignment and receiving a mark for it.

The files are compressed into a zip file where the name of the zip file is composed of your student ID.

Note that the time of submission at the VU Collaborate site as recorded in the unit coordinator’s area of VU Collaborate will be used as the official time of submission.

If you submit an assignment more than once (which is unusual and rarely would students do), then the last one will be marked. If the last version is submitted during the lateness period, a lateness penalty will be applied to that last version so that it will attract a penalty according to how many days late it was submitted.