Hit The Order Button To Order A **Custom Paper**

>> CLICK HERE TO ORDER 100% ORIGINAL PAPERS FROM AustralianExpertWriters.com <<

16 Aug
2020

Software Design Document

Category:ACADEMICIAN

SOLUTION AT Australian Expert Writers

Unit Name/Code
ISY3002/ISY302 IS Project 1
Assessment Number
3
Assessment Name
Software Design Document
Report and Presentation
Unit Learning Outcomes
ULO 1: Work effectively in a team to liaisewith clients to determine systemsrequirements and elicit information necessaryto create a software solution.ULO 2: Demonstrate an understanding of theroles and responsibilities of softwaredevelopers, clients and users of a systemsoftware developers, clients and users of asystem.
Graduate Attributes Assessed
CommunicationsCollaborationsResearch
Critical thinking & problem solving
CommunicationsCritical Thinking & problem solvingEthical Behavior
Flexibility
ULO 3: Conduct a feasibility study thatoutlines costs, timeframes, a developmentschedule, and the features and benefits of aprospective software solution.ULO 4: Demonstrate skills in projectplanning and management,problem solving, analysis, andevaluation.ULO 5: Demonstrate skills in software design,development, implementation, testing anddocumentation of an authentic industry typeproject, that is, a less well-structured ormessy problem, requiring demonstration ofhigh-level skills.
CommunicationCollaborationResearchCritical Thinking & problem solvingEthical Behavior
CommunicationCollaborationResearch
Critical thinking & problem solving
Ethical behaviourCommunicationResearchCritical Thinking & problem solvingEthical BehaviorFlexibility
Due Date and Time
Weighting
Assessment Description
Detailed Submission
Requirements
Report submission deadline is 12.06.2020 by 5 PM AEST.40% (30% Report and 10% Presentation)A 4000 word Report on Software Design based on your Client’s project details.15-minute Presentation in week 11 (08-02-2020) during class time by whole group.Report: This report is to be submitted in MS Word format. Upload thereport via Moodle/Turnitin. Follow the instructions as required by this assessment brief.Presentation: All group members must give the presentation to get the marks. Zeromarks will be given to the group member who does not give the presentation or whois absent on the presentation day.
INSTRUCTIONSReport: The word limit of the report is 4000. It should be written in size 12 Arial Font. You must submit your own work anduse appropriate references in Harvard style where needed. The similarity index of your report should not be more than 20%.Draft report must be discussed with the instructor in the class on 06-02-2020 and 13-02-2020. All groups must bring a hardcopy of the Draft report for discussion.Presentation: Maximum time allowed for presentation is 15 min. All group members must present the work to obtain marks.Zero marks for being absent on the presentation day.NATURE OF THE TASKThis is a group assessment. Please make groups of three students for this assessment.HOW TO PRESENT YOUR ASSIGNMENT / SUBMISSION INSTRUCTIONSYour report must follow the structure given below;1. Executive Summary• It should summarize the key points of the Software Design Document.• 250-300 words2. IntroductionIntroduction has the following sections;• Background of Project: Explain the aims, objectives and importance of the project.• Purpose: Explain the purpose of the Software Design Document.• Structure: Explain the structure of the Software Design Document.3. Conceptual ModelThis section has the following three components;• Technologies used: Explain the various technologies that will be used by you in this project.• System overview: Provide an overview of main functionalities of the system.• Architectural Pattern: Explain the architectural design pattern (s) that will be used by you inthis project. Draw a block diagram of the software architecture.4. Design Viewpoints• Logical Viewpoint: Explain the logical viewpoint related to your project. Draw class diagrams toexplain the logical viewpoint.• Information Viewpoint: Explain the information viewpoint related to your project. Draw EntityRelationship (ER) diagrams to explain the Information viewpoint.• Interface Viewpoint: Explain the various interfaces of the project. Provide screenshots of variousaspects of Front End of the software.• Interaction Viewpoint: Explain the interaction viewpoint related to your project. Draw SequenceDiagrams to explain the Interaction viewpoint.5. Traceability Matrix• Draw and explain the traceability matrix related to your project.6. References• In Harvard referencing style7. Appendix (if needed)• Programming code, screenshots, tables etc.• Must be referred in the main body of the report.RETENTION OF RECORDSStudents are required to keep a copy of all items submitted or completed for assessment or evaluation until the end of the gradeappeal period.GROUP CONTRIBUTION FORMYou must submit the Group Contribution Form with the report. Group Contribution Form is given at the last page of thisassessment brief.MARKING CRITERIASee the rubric given at the next few pages.
Assessment Rubric of Report
Executive Summary and Introduction (6 marks)
Executive Summary(3 marks)
Clearly summarizesthe key point of theSoftware DesignDocument(3 marks)
Lacks in summarizing somekey points of theSoftware Design Document(2 – 2.75 marks)
Not clearly summarizeskey points of theSoftware DesignDocument(1 – 1.75 marks)
Poorlysummarizes thekey points of theSoftware DesignDocument(0.25 – 0.75 mark)
ExecutiveSummary ismissing and notpart of the report(0 marks)
Introduction(3 marks)
Clearly describes thebackground of project,purpose and structureof Software DesignDocument(3 marks)
Lacks some description ofbackground of project,purpose and structure ofSoftware Design Document(2 – 2.75 marks)
Not clearly describes thebackground of project,purpose and structure ofSoftware DesignDocument(1 – 1.75 marks)
Poorly describesthe background ofproject, purposeand structure ofSoftware DesignDocument(0.25-0.75 marks)
Introduction ismissing and notpart of the report(0 marks)
Conceptual Model (9 marks)
Technologies Used(2 marks)
Clearly explains thetechnologies that willbe used in the Project(2 marks)
Lacks some description ofthe technologies that will beused in the Project(1.5 -1.75 marks)
Not clearly describes thetechnologies that will beused in the Project(1-1.25 marks)
Poorly describes thetechnologies thatwill be used in theProject(0.25-0.75 marks)
Technologiesthat will be usedin the project arenot written(0 marks)
System Overview(2 marks)
Clearly explains themain functionalities ofthe system(2 marks)
Lacks some description ofthe main functionalities of thesystem(1.5 -1.75 marks)
Not clearly describes themain functionalities of thesystem(1-1.25 marks)
Poorly describes themain functionalitiesof the system(0.25-0.75 marks)
SystemOverview sectionis missing(0 marks)
Architecture Pattern(3 marks)
Architectural Patternis clearly explained(3 marks)
Few aspects of ArchitecturalPattern are not clearlyexplained(2.25 – 2.75 marks)
Many aspects ofArchitectural Pattern arenot clearly explained(1.25 – 02 marks)
Many aspects ofArchitectural Patternare missing and arepoorly explained(0.25 – 1 marks)
Architecturalpattern used ismissing and notpart of the report.(0 marks)
Block Diagram(2 marks)
Block Diagram isclearly drawn(2 marks)
Some aspects of BlockDiagram are not clearlydrawn(1.5-1.75 marks)
Many aspects of BlockDiagram are not clearlydrawn(1-1.25 marks)
Block Diagram ispoorly drawn(0.25 – 0.75 marks)
Block Diagram ismissing(0 marks)
Design View Points (12 marks)
Logical Viewpoint(3 marks)
Class Diagrams areclearly drawn andexplained(3 marks)
Few class diagrams are notclearly drawn and/or notclearly explained(2 – 2.75 marks)
Many class diagrams aremissing and/or not clearlyexplained(1-1.75 marks)
Many classdiagrams aremissing and poorlyexplained(0.25-0.75 marks)
LogicalViewpointsection ismissing and notpart of the report(0 marks)
Information Viewpoint(3 marks)
Entity Relationship(ER) diagrams areclearly drawn andexplained(3 marks)
Entity Relationship (ER)diagrams are not clearlydrawn and/or not clearlyexplained(2 -2.75 marks)
Many Entity Relationship(ER) diagrams aremissing and/or not clearlyexplained(1-1.75 marks)
Many EntityRelationship (ER)diagrams aremissing and poorlyexplained(0.25 – 0.75 marks)
InformationViewpointsection ismissing and notpart of the report(0 marks)
Interface Viewpoint(3 marks)
All Interfaces areclearly explained andappropriatescreenshots areprovided(3 marks)
Few interfaces are notclearly explained and/orappropriate screenshots arenot provided(2-2.75 marks)
Many interfaces are notclearly explained and/orappropriate screenshotsare not provided(1-1.75 marks)
Many interfaces arenot clearlyexplained andappropriatescreenshots are notprovided(0.25 – 0.75 marks)
InterfaceViewpointsection ismissing and notpart of the report(0 marks)
Interaction Viewpoint(3 marks)
Sequence diagramsare clearly drawn andexplained(3 marks)
Few Sequence diagramsare not clearly drawn and/ornot clearly explained(2-2.75 marks)
Many Sequencediagrams are missingand/or not clearlyexplained(1-1.75 marks)
Many Sequencediagrams aremissing and poorlyexplained(0.25-0.75 marks)
InteractionViewpointsection ismissing and notpart of the report(0 marks)
Traceability Matrix (3 marks)
Traceability Matrix(3 marks)
Traceability Matrix isclearly drawn andexplained(3 marks)
Few aspects of TraceabilityMatrix are not clearly drawnand/or not clearly explained(2-2.75 marks)
Many aspects ofTraceability Matrix aremissing and/or not clearlyexplained(1-1.75 marks)
Many aspects ofTraceability Matrixare missing andpoorly explained(0.25-0.75 marks)
TraceabilityMatrix ismissing and notpart of thereport(0 marks)
Marking Criteria for the Oral PresentationAssignment 3
Task
Description
MaximumMarks
MarksObtained
1
Comprehensive introduction:– Introduced self– Introduced the project and its importance
01
2
– Content– Delivery– Timing
03
3
– Well-designed Slides– Readable/ Spellings/Grammar– Slides are numbered– References in Harvard Style
03
4
Answers to Questions
03
Total
10
Group Contribution Form
Unit Name/Code
ISY3002/ISY302 IS Project 1
Assessment Number
3
Assessment Name
Software Design Document
Due Date and Time
Report submission deadline is 12.06.2020 by 5 PM AEST.
Instructions
• Report will not be marked without the submission of this form with the report.• This form should be completely filled.• This form should be signed by all group members.• Attach this form at the end of the report.• Do not upload it separately on the moodle.
Names of Student
Tasks Worked on
Percentage Contribution toAssessmente.g. If you havecontributed equally thenmention 33.33%contribution by each
Signature
<insert student name>
<Insert tasks>
<Insert % >
<Insert signature here>
<insert student name>
<Insert tasks>
<Insert % >
<Insert signature here>
<insert student name>
<Insert tasks>
<Insert % >
<Insert signature here>
<insert student name>
<Insert tasks>
<Insert % >
<Insert signature here>

Order from Australian Expert Writers
Best Australian Academic Writers

QUALITY: 100% ORIGINAL PAPERNO PLAGIARISM – CUSTOM PAPER

READ ALSO  Nursing School Admission Assignment