fbpx

Get Cheapest Assignment in Australia, UK, US, UAE, Canada and NZ Order Now

HI5030 Systems Analysis and Design

0 Comments

HI5030 Systems Analysis and Design                                

Objective(s)

This assessment item relates to the unit learning outcomes as in the unit descriptor. This assessment is designed to reinforce the lecture material and give students practice at applying Database design techniques, as well as providing a relational schema using DDL statements and relational DML statements to demonstrate sophisticated access of the Database to be built.

Instructions

This assessment will be completed in groups of 3 students (or as determined by the unit coordinator). Groups will be formed within the first 2 weeks of class. If, in the view of the coordinator, groups are not forming within a reasonable time period, the coordinator will randomly allocate students to groups. Students will be expected to work within these groups for the remainder of the semester on the group case study.

Associated with this assessment is a case study. This case study is in the associated document CaseStudy-yyyy-SemX, where yyyy is the current year and X is the current trimester. All group members need to thoroughly read this case study to get an understanding of the business for which they will be designing an information. If there are any questions on this case study you should contact your unit coordinator.

This assessment is worth 40% of the units grade and is a major assessment. Groups are advised to begin working on this assessment as soon as you have your group

There are two (2) deliverables for this assessment.

DeliverableWeightWeek Due
Submission 1 – see requirements below15%Week 6
Submission 2 – see requirements below25%Week 11/12

Note: It is important to realize, that you must have prior approval for you IS System/ database plan before you can submit. If you submit something for assessment without approval for the IS database, it will not be graded. Once you have an approved system/ database, you cannot change it without consent from your subject lecturer.

The day and time of the due week that the assessment must be submitted will be announced by your

subject coordinator.

Deliverable Descriptions

Below is a description of the different deliverables and the requirements. Note that the case study is a brief description of the company for which we are designing aspects of an information system. If something in the case study is not clear, you can seek clarification from your unit coordinator, or make assumptions. All assumptions must be clearly stated in the documents you submit.

Submission 1

In this submission you have a number of items to produce, these are

  • A full set of requirements for the system as outlined in the case study, these include both functional and non-functional requirements (if any)
  • A fully leveled set of dataflow diagrams for the system in the case study. Note that these must be internally consistent at all levels. Also note that this leveled set of DFD’s must include a Context diagram, and a Level 0 diagram.
  • An event table with entries for all events you can discover in the case study

All diagrams should be built using Draw.io and incorporated into your word document.

Submission 2

In this submission, again you have a number of items to produce for your group

  • An activity diagram for each subsystem identified in the level 0 diagram of the first submission with a clear introduction and heading for each diagram
  • User Stories. Each group should develop at least 1 user stories for each subsystem
  • A data dictionary describing all the attributes/ elements in entities identified for each Subsystem. The group must write physical data element descriptions for the data entities in their level 0 diagram (please use the correct notations).
  • Use Case Diagrams. Must contain one diagram for each subsystem.
  • Use Case Descriptions. Each group must supply a fully developed use case description for each use case
  • Sequence Diagram. One Sequence diagram for each subsystem
  • Database ER model using the Crows foot notation
  • Quality discussion of the applicability of a range of types of solutions and selection of best possible alternative. Advantages and disadvantages relevant to the case study should be discussed to score higher marks. All team members must contribute

All diagrams should be built using Draw.io and incorporated into your word document.

Submission Guidelines

Your documents should be a single MS Word or OpenOffice document containing your report. Do not use PDF as a submission format,

All submissions will be submitted through the safeAssign facility in Blackboard. Submission boxes linked to SafeAssign will be set up in the Units Blackboard Shell. Assignments not submitted through these submission links will not be considered.

Submissions must be made by the due date and time (which will be in the session detailed above) and determined by your Unit coordinator. Submissions made after the due date and time will be penalized per day late (including weekend days) according to Holmes Institute policies.

The SafeAssign similarity score will be used in determining the level, if any, of plagiarism. SafeAssign will check conference web-sites, Journal articles, the Web and your own class members submissions for plagiarism. You can see your SafeAssign similarity score (or match) when you submit your assignment to the appropriate drop-box. If this is a concern you will have a chance to change your assignment and resubmit. However, re-submission is only allowed prior to the submission due date and time. After the due date and time have elapsed your assignment will be graded as late. Submitted assignments that indicate a high level of plagiarism will be penalized according to the Holmes Academic Misconduct policy, there will be no exceptions. Thus, plan early and submit early to take advantage of the re-submission feature. You can make multiple submissions, but please remember we grade only the last submission, and the date and time you submitted will be taken from that submission.

Academic Integrity

Holmes Institute is committed to ensuring and upholding Academic Integrity, as Academic Integrity is integral to maintaining academic quality and the reputation of Holmes’ graduates. Accordingly, all assessment tasks need to comply with academic integrity guidelines. Table 1 identifies the six categories of Academic Integrity breaches. If you have any questions about Academic Integrity issues related to your assessment tasks, please consult your lecturer or tutor for relevant referencing guidelines and support resources. Many of these resources can also be found through the Study  Sills link on Blackboard.

Academic Integrity breaches are a serious offence punishable by penalties that may range from deduction of marks, failure of the assessment task or unit involved, suspension of course enrolment, or cancellation of course enrolment.

Table 1: Six categories of Academic Integrity breaches

CollusionWorking with one or more other individuals to complete an assignment, in a way that is not authorised.
CopyingReproducing and submitting the work of another student, with or without their knowledge. If a student fails to take reasonable precautions to prevent their own original work from being copied, this may also be considered an offence.
ImpersonationFalsely presenting oneself, or engaging someone else to present as oneself, in an in-person examination.
Contract cheatingContracting a third party to complete an assessment task, generally in exchange for money or other manner of payment.
Data fabrication and falsificationManipulating or inventing data with the intent of supporting false conclusions, including manipulating images.

Source: INQAAHE, 2020

Leave a Reply

Your email address will not be published. Required fields are marked *