IFN552:Systems Analysis and Design Assessment Task 1 – Requirements Analysis, Use Case and Activity Diagram

Assessment Task1–Individual

Task overview

Assignment Name-theerrorhasontheusefulnessoftherequirement,referringto the SMART principles]

1. For the Sample Use Case Diagram, identify four (4) errors. For each error,list the specificUse Case(/s)and/orrelationship between Use Cases and/or other feature of the diagram that the error relates to, describe what the error is and why it is an error.
   • Each error description should onlybe1-2sentences and can be listed as dot points, in table format or as an annotation to acopy of the diagram
2. FortheSampleActivityDiagram,identifyfour(4)errors.Foreach error, list the specific Activity(/s) and/or shape(/s) between Activities and/orotherfeatureofthediagramthattheerrorrelatesto,describe what the error is and why it is an error.
   • Eacherrordescriptionshouldonlybe1-2sentencesandcanbe listed as dot points, in table format or as an annotation to acopy of the diagram
3. ReadCase2(below).
4. DevelopanewRequirementsMatrixtoshowthefunctional requirements of the system that would fall under subsystems Collaboration Management, Knowledge and Resource Management, and Project Management. Aim for:
5. 15EssentialFunctionalRequirements
6. 5DesirableFunctionalRequirements
7. 1OptionalFunctionalRequirement

You should include the suggested number for each priority of requirements, totalling around 21 Functional Requirements in your matrix. A small amount less or more may be ok depending on the quality of the ones you include,but you will need to stay around the number stated above.Whilsteachwillhavecertainpriority,andthe list may not be comprehensive, you need to ensure that all are relevant to the case and are concise, specific, measurable and actionable. You will also need to define 2 modules within each of the above subsystems and include these in your matrix.

1. Draw1(one)UseCaseDiagramcapturinghowactorsinteractwith the system across the range of important functions available in the system (focus on the ones described in the case description).
2. Aim to include around 15 Use Cases in your diagram (no more than17).Ensurethattheusecasesyoudoincludeareimportant and relevant to the system being represented.
3. Remembertoincluderelevantrelationshipsbetweenelements of the diagram such as use cases and actors, and use cases and other use cases
4. DescribeyourUseCaseDiagrambyansweringthebelow3 questions (2-3 sentences each):
5. Pick one extends or includes relationship in your diagram (be specific)and justify why you have drawnitasanextendsorincludes relationship
6. Describeoneactorintermsofwheretheyinterfacewiththe system, based on your diagram

Assignment1 (Sample) Case1–University Timetabling System

The university class registration system is a digital platform designed to facilitate the enrolment process for students. It provides an interface for students to view available courses,assessprerequisites,andconstructtheiracademicschedulefortheupcomingterm. The system integrates with the university's administrative staff, where class capacities are managed, room allocations are determined, and the overall academic timetable is finalised. This platform ensures a streamlined process that balances student preferences with institutional capabilities and constraints.

Sample Functional Requirementlist

Note–thisisanincompletelistwitherrors.Itisyourtasktoidentifyasubsetoftheseerrors. For best practices, please refer to the examples and standards in lectures and tutorials.

1. Verifytheidentityofstudents,faculty,andadministratorsthroughasecureloginprocess.
2. Grantaccesstofeaturesanddatabasedonuserroles(students,faculty,administrators).
3. Presentalistofallavailablecoursesfortheupcomingterm,includingdetailssuchascourse titles, descriptions, prerequisites, credits, and scheduled times.
4. Checkifastudentcanenrol.
5. Monitorandupdatetheenrolmentcapacityforeachcourseandpreventenrolmentifacourse is full.
6. Allowstudentstoenrolincoursesforwhichtheymeettheprerequisitesandthathave available seats.
7. Enablestudentstodropcoursesfromtheirschedulebeforethedropdeadline.
8. Placestudentsonawaitlistforcoursesthatarefullandenrolthemasspacesbecome available.
9. Respondtouserinputsandrequestswithin2secondsundernormaloperationconditions.
10. Createpersonalisedacademicschedulesforstudentsbasedontheirenrolledcoursesand distribute these to students via reminders.
11. Notifystudentsofanyscheduleconflictsbetweenselectedcourses.
12. Designfunctionalityforstudentstomodifytheirschedulestoresolveconflictsandmeettheir preferences.
13. Synchroniseenrolmentdatawiththeuniversity'sadministrativebackendforreal-timeupdates on class capacities and room allocations.
14. Automaticallyupdatestudents'academicrecordswiththeirenrolmentstatus,including courses added, dropped, or waitlisted.

Sample Use Case Diagram

Note–thisisanincompletediagramwitherrors.Itisyourtasktoidentifyasubsetofthese errors. For best practices, please refer to the examples and standards in lectures and tutorials.

Sample Activity Diagram

Note–thisisanincompletediagramwitherrors.Itisyourtasktoidentifyasubsetofthese errors. For best practices, please refer to the examples and standards in lectures and tutorials.

[turntonextpage]

Thisconcludes(Sample)Case1.Case2isonthefollowingpage,andrelatestothesecondpartof this assignment (see full instructions above).

Assignment 1 Case 2–Open Energise:OpenInnovation Collaborative Knowledge Network (CKN)

The OpenEnergise Open Innovation Collaborative Knowledge Network (CKN) is a digital platformdedicatedtosolvingproblemsinsustainableenergyproductionandstoragethrough crowd-sourced digital collaboration. Each month, platform members vote on a specific challenge in sustainable energy. The highest-voted problem becomes the focus for the month, inviting participants worldwide to discuss, share knowledge, exchange ideas, and build on solutions to prototype a solution.

Participantsinitiallydiscussandbrainstorminaplatform-facilitatedchannel.Afterward,they form teams to develop their concepts further toward putting forward a proposal for peer- review.Theplatformprovidescollaborativeworkspaceswithsharedwhiteboards,document editors, and project tracking tools. These workspaces are designed to help teams efficiently organise their work, from drafting proposals to refining project details. For software development projects, the platform offers links to Git for code collaboration, version control, and iterative development.

The platform includes a searchable knowledge base with articles, research papers, and documentationfrompreviousprojects,whichisaccessedandorganisedviaaninterface.

Participantscandiscusswithinandbetweenteamsusinganin-builtcommunicationtool, which includes announcements ("shout outs") and within-team discussion channels ("huddles"). These tools facilitate collaboration, document commenting, real-time online meetings, and asynchronous messaging.

AdistinctivefeatureoftheCKNisitsabilitytotrackthedevelopmentofideasovertime.This feature records project progress from initial concept to final stages, highlighting key contributions and developments. Each team's progress is displayed on a live timeline visible to everyone, encouraging engagement and healthy competition.

Communityfeedbackisfacilitatedthroughastructuredsystemwhereproposalscanberated and reviewed. This feedback can come from platform visitors who are not members but are given opportunities to provide advice.

Submission Information

Moderation:

1. ClickontheSubmitbutton
2. Givethesubmissionatitle,selectthecorrectfileandclickUpload.
3. ClickConfirm.
4. ClickReturntoAssignmentlist
5. ALWAYSdoublecheckyoursubmissionhasgonethrough.

Allstaffwhoareassessingyourworkmeettodiscussandcompare their judgements before marks or grades are finalised.

Important note

In submitting your assignment, you acknowledge that you have understood and adhered to the conditions of submission.Thisincludesthattheworkhandedinbyyouisyourownwork,whichmeansthatideas,words, visuals and any other form of submitted work is created solely by you, except where specifically referenced in your document as originating from another source (citing who that source is).

This includes any diagrams and tables. If the same elements are included in diagrams and/or text submitted by multiple students from this or other semesters, regardless of whether shapes are rearranged, colours changed,orsynonymsareusedtoreplacewords,thiswillbeflaggedforplagiarism,andstandardprocedures will be followed, which often results in a grade of 0 or 1 for the plagiarised assignment, or more serious penalties for multiple offenses.

Thebestwaytoavoidplagiarismistoensurethat you:

1. Nevershareyourworkwithanyoneelse(unlesstheyareinyourowngroupinagroupassignment)
   1. Nevercopyandpasteanythingintoyourassignmentdocument(unlessitisaquoteyouare referencing – e.g., John Smith said “this is a quote” pg. 4)
   2. Write your own words and create your own diagrams. If you start with a sentence, paragraph, table or diagram from somewhere/someone else and try to change it to make your own, you will always risk plagiarism, even if you attempt to change or alter it. It will also not be based on your own understanding,whichdoesnothelpyoudemonstratetoyourselforteachingstaffwhatyouhavelearnt. Trust in your own abilities!

It is also expected that you have undertaken the mandatory Academic Integrity Module (see: https://qutvirtual4.qut.edu.au/group/student/study/study-essentials/academic-integrity#h2-1),priortosubmitting.

Generative AI

Theassignmentsinthisunitaredesignedtogiveyouanopportunitytoshowcaseyourknowledgeofthetopics presented in this unit and demonstrate your learning and skill. Because an AI language model or other generative model cannot attend classes, ask questions, engage in tutorials and discussions with peers and teaching staff, it will not be able to provide answers to the assignment tasks to a level of quality and specificity that is required to pass.

Whilst theuseof suchtools as assistanceis not discouraged, westress that it will requireinput andthought on your part to apply what you have learnt to view anythingAI provides with a critical eye in the context of what istaughtintheunit.AlltasksintheassignmentshavebeenthoroughlytestedwithGenerativeAI,andwithout actual knowledgeable input from a person who understands the content of the unit, the output and end result does not reach a quality needed to pass.

IFN552|SystemsAnalysisandDesignAssessmentTask1Rubric

Case1Tasks

Critiqueoferrors–SampleUseCaseDiagram

Demonstrate

Flawless/Exemplary:Allerrorsidentifiedwereaccurate,relevantandjustifiedwithexcellentclarity

Verygood:Errorsidentified were allrelevant,mostlyaccurate,andjustified with verygood clarity and

Good:Errorsidentified were allrelevant,mostlyaccurate,andjustifiedwithgoodclarityand

Satisfactory:Mosterrorsidentifiedwere relevant andaccurate,andjustifiedwithsatisfactorylevelof

Unsatisfactory:Mosterrorsidentifiedwerenotrelevantand/ormostlyinaccurate.

Unsatisfactory:Noneoftheerrorsidentifiedwererelevantoraccurate.

Unsatisfactory:No discernible listoferrors provided.

critiquingasamplediagram.

Weighting:5%

UseCaseDiagram+Description

ApplyappropriateUML

techniquestoclearlydescribeimportantaspectsofthecase in a UseCaseDiagram

Weighting:27%

Flawless/Exemplary:flawless,deepunderstandingofusersandtheirgoalsin using the systemand different usecases,presentationof all details, usingappropriatelabellingandcorrectassociationsandpresentingacohesiveview.

Answers to thedescriptionquestionsindicateadeep knowledge ofthe case and clearunderstandingofUMLtechniques

Very good: doesnot miss anythingimportant,showsadeepunderstandingofusers and theirgoalswithappropriateusecases,andprovides a clearpresentation.

Therearehoweversome very minormodellingmistakesoromissions.

Answers to thedescriptionquestionsindicateadeepknowledgeof the case andclearunderstandingofUMLtechniques

Good:revealsattention to detail,buttherearesomeminormistakesandinconsistenciesinmodelling.

Answers to thedescriptionquestionsindicateareasonableknowledge of thecase and a basicunderstandingofUMLtechniques

Satisfactory:revealslittleattentiontodetail,there are someimportantinconsistencies,omissionsandmistakesinmodelling.

Answers to thedescriptionquestionsindicateareasonableknowledge of thecase and a basicunderstandingofUMLtechniques

Unsatisfactory:lacksimportantdetails,therearesignificantinconsistencies,andthemodelisdifficulttounderstandorseem to besomehowirrelevant.

Answers to thedescriptionquestionsdoesnotindicateareasonableknowledge of thecase and/or doesnot evidence asatisfactoryunderstandingofUMLtechniques

Unsatisfactory:lacksmanyimportantdetails,there are manysignificantinconsistencies,andlargepartsofthemodelseemsunrelatedorunreadable.

Answers to thedescriptionquestionsdoesnotindicateareasonableknowledge of thecase and/or doesnot evidence asatisfactoryunderstandingofUMLtechniques

Unsatisfactory:Diagramiseithermissing or isunrelated to thecase.

Nodescriptionprovided.

IFN552:SystemsAnalysisandDesign–AssessmentTask1