[Recommended] - Formative Assessment

SOLUTION AT Academic Writers Bay

Assessment Brief 3 – Final SRS Report
Assessment Brief 3 Software Requirement Specifications
Version 3: 8th November 2021
Kent Institute Australia Pty. Ltd.
ABN 49 003 577 302 CRICOS Code: 00161E RTO Code: 90458
TEQSA Provider Number: PRV12051

COURSE: Bachelor of Information Technology
Unit:	Capstone Project
Unit Code:	CPRO 306
Type of Assessment:	Formative Assessment
Length/Duration:	2500 words
Unit Learning Outcomes addressed:	a) Critically analyse the methods and techniques used when seeking to apply information technology at the corporate level b) Identify and present systematically the requirements for an information system in a large and complex organisation c) Design, develop, test, and evaluate an appropriate systems solution d) Identify and resolve critical technical issues with minimal supervision e) Work effectively as part of a team in the production of an information system and documentation and reports.
Submission Date:	Week 5
Assessment Task:	Final SRS Report
Total Mark:	100
Weighting:	35%
Students are advised that submission of an Assessment Task past the due date without a formally signed approved Assignment Extension Form (Kent Website MyKent Student Link> FORM – Assignment Extension Application Form – Student Login Required) or previously approved application for other extenuating circumstances impacting course of study, incurs a 5% penalty per calendar day, calculated by deduction from the total mark. For example. An Assessment Task marked out of 40 will incur a 2-mark penalty for each calendar day. More information, please refer to (Kent Website MyKent Student Link> POLICY – Assessment Policy & Procedures – Student Login Required)

ASSESSMENT DESCRIPTION
In this part of the assessment task the student needs to identify Systems requirements, business
requirements and the user requirements of the system they have proposed in the previous
assessment. The report will be named as “software requirement specification” for your proposed
project. The report needs to be prepared professionally and presentable to the clients they are
working with. The report also will include the hardware and software requirements, detailed user
requirements using a use case diagram and from that then the report needs to identify and record
functional and non-functional requirements, work breakdown structure, user interface etc. you also
need to include technical details of the system which will carried on development of the project based
on the project you have chosen and to comply with the functional and non-functional requirements.
The report should include your software development environment, files and folder structure, data
flow diagram, data dictionary, entity relationship diagram, user interface storyboard etc. The report
also needs the test plan and the implementation plan which will be used later for testing and
implementing the system. The report will have the following criteria and a sample of software
requirement specification is available in the student resources folder as a guide for you to follow:
 An updated scope statement, including more detailed descriptions of key deliverables
 A system architecture will provide the required functionality and meet its non-functional
objectives.
 Show that the proposed user interface design will achieve its objectives.
 Suggested changes and improvements are reasonable and useful.
 A summary/sample of completed deliverables under IS requirements and design.
 The system development has been planned and managed.
 Teamwork has been managed.
 The business requirements have been elicited and understood.
 Use case diagram, Data flow diagram
 A database design will provide the necessary data management.
 A user interface design will help and facilitate users to perform their tasks.
 Your responses on the feedback from your Lecturer.
Based on the organization that you and your team has chosen; you have to design the Information
System project and prepare the software requirement specification report.
MARKING GUIDE (RUBRIC) FOR GROUP ASSIGNMENT
Though the nature of this assessment is purely qualitative, your Lecturer will consider the below
marking criteria while assessing your report.
Assessment Brief 3 Software Requirement Specifications
Version 3: 8th November 2021
Kent Institute Australia Pty. Ltd.
ABN 49 003 577 302 CRICOS Code: 00161E RTO Code: 90458
TEQSA Provider Number: PRV12051

Marking Criteria	Not Satisfactory (0-49% of the criterion mark)	Satisfactory (50-64% of the criterion mark)	Good (65-74% of the criterion mark)	Very Good (75-84% of the criterion mark)	Excellent (85-100% of the criterion mark)
Criterion -1 (20 mark) Demonstrates good understanding of key concepts	No attempt done for Business description, Project description & problems scenario, Project objectives, purpose describe in	Little attempt of Business description, Project description & problems scenario, Project objectives, purpose describe in	General description of Business description, Project description & problems scenario, Project objectives, purpose describe in	Specifically stated Business description, Project description & problems scenario, Project objectives, purpose describe in	Specifically, and comprehensive ly stated Business description, Project description & problems scenario, Project objectives,

Assessment Brief 3 Software Requirement Specifications
Version 3: 8th November 2021
Kent Institute Australia Pty. Ltd.
ABN 49 003 577 302 CRICOS Code: 00161E RTO Code: 90458
TEQSA Provider Number: PRV12051

detail. Detailed scope definition, New & proposed system design specifications stated, Methodologie s chosen for the project	detail. Detailed scope definition, New & proposed system design specifications stated, Methodologie s chosen for the project	detail. Detailed scope definition, New & proposed system design specifications stated, Methodologie s chosen for the project	detail. Detailed scope definition, New & proposed system design specifications stated, Methodologie s chosen for the project	purpose describe in detail. Detailed scope definition, New & proposed system design specifications stated, Methodologies chosen for the project
Criterion-2 (10 mark) Group cohesiveness	No Team formed or No team works has been distributed and the team members are not aware of their tasks and participation	Team formed, less distribution of team works, and the team members are aware of few of their tasks and participation	Team formed, some team works has been distributed and the team members are aware of some of their tasks and participation	Team formed, almost all team works has been distributed and the team members are aware of all their tasks and participation	Team formed, all team works has been distributed and the team members are aware of all their tasks and participation
Criterion-3 (20 marks) Clearly analysed the system	No attempt done for Business requirement, System requirement and System configuration	Has attempted small bits of Business requirement, System requirement, System configuration such as Hardware Configuration , Software Configuration , Little bit of User requirement analysis is done using few use case diagram, use case definition & based on use case definition. Few Functional and Non functional requirement analysed	Generally analysed the Business requirement, System requirement, System configuration such as Hardware Configuration , Software Configuration , User requirement analysis using use case diagram, use case definition & based on use case definition. Both the Functional and Non functional requirement analysed	Clearly analysed the Business requirement, System requirement, System configuration such as Hardware Configuration , Software Configuration , User requirement analysis using use case diagram, use case definition & based on use case definition. Both the Functional and Non functional requirement analysed	Clearly and professionally analysed the Business requirement, System requirement, System configuration such as Hardware Configuration, Software Configuration, User requirement analysis using use case diagram, use case definition & based on use case definition. Both the Functional and Non-functional requirement analysed

Criterion-4 (20 marks) Database design completed and cited	Not designed any of the Database requirement, Entity Relationship Diagram (ERD) & Class Diagram, Tables, Data Flow Diagrams (DFD)	Has attempted few Database requirement, Entity Relationship Diagram (ERD) & Class Diagram, Tables, Data Flow Diagrams (DFD)	Has attempted some of the Database requirement, Entity Relationship Diagram (ERD) & Class Diagram, Tables, Data Flow Diagrams (DFD)	Clearly and professionall y designed almost all the Database requirement, Entity Relationship Diagram (ERD) & Class Diagram, Tables, Data Flow Diagrams (DFD)	Clearly and professionally designed all the Database requirement, Entity Relationship Diagram (ERD) & Class Diagram, Tables, Data Flow Diagrams (DFD)
Criterion-5 (20 marks) User interface design planned	(No attempt) Did not mentioned the User interface design methods, did not created any of the User Interface story board, input data forms, Output report forms, and Web site design concepts and layouts	Mentioned few User interface design methods, created few User Interface story board, input data forms, Output report forms, mentioned few Web site design concepts and layouts	Mentioned some User interface design methods, created some User Interface story board, input data forms, Output report forms, mentioned some Web site design concepts and layouts	Clearly mentioned almost all the User interface design methods, created almost all User Interface story boards, input data forms, Output report forms, clearly mentioned almost all Web site design concepts and layouts	Clearly mentioned all the User interface design methods, created all User Interface story board, input data forms, Output report forms, clearly mentioned all Web site design concepts and layouts
Criterion-6 (5 marks) Test plan and system implementati on planned	Did not created a test plan and a system implementati on plan	Created a vague test plan and a vague system implementati on plan	Created a basic test plan and a basic system implementati on plan	Created almost complete test plan and a system implementati on plan covering almost all the scenario	Created a complete test plan and a system implementation plan covering all scenarios
Criterion-7 (5 marks) Referencing	One or no academic resources be cited for the investigatio	Two academic resources be cited for the investigation	Three academic resources be cited for the investigation	Four academic resources be cited for the investigation	Five academic resources be cited for the investigation that should be

n that
should be
placed for a
particular
project

that should
be placed for
a particular
project

placed for a
particular
project

GENERAL NOTES FOR ASSESSMENT TASKS
Content for Assessment Task papers should incorporate a formal introduction, main points, and
conclusion.
Appropriate academic writing and referencing are inevitable academic skills that you must develop
and demonstrate in work being presented for assessment. The content of high-quality work
presented by a student must be fully referenced within-text citations and a Reference List at the end.
Kent strongly recommends you refer to the Academic Learning Support Workshop materials available
on the Kent Learning Management System (Moodle). For details please click the link
http://moodle.kent.edu.au/kentmoodle/mod/folder/view.php?id=3606 and download the file titled
“Harvard Referencing Workbook”. This Moodle Site is the location for Workbooks and information
that are presented to Kent Students in the ALS Workshops conducted at the beginning of each
Trimester.
Kent recommends a minimum of FIVE (5) references in work being presented for assessment. Unless
otherwise specifically instructed by your Lecturer or as detailed in the Unit Outline for the specific
Assessment Task, any paper with less than five (5) references may be deemed not meeting a
satisfactory standard and possibly be failed.
Content in Assessment tasks that includes sources that are not properly referenced according to the
“Harvard Referencing Workbook” will be penalised.
Marks will be deducted for failure to adhere to the word count if this is specifically stated for the
Assessment Task in the Unit Outline. As a general rule there is an allowable discretionary variance to
the word count in that it is generally accepted that a student may go over or under by 10% than the
stated length.
GENERAL NOTES FOR REFERENCING
References are assessed for their quality. Students should draw on quality academic sources, such as
books, chapters from edited books, journals etc. The textbook for the Unit of study can be used as a
reference, but not the Lecturer Notes. The Assessor will want to see evidence that a student is capable
of conducting their own research. Also, in order to help Assessors, determine a student’s
understanding of the work they cite, all in-text references (not just direct quotes) must include the
specific page number(s) if shown in the original. Before preparing your Assessment Task or own
contribution, please review this ‘YouTube’ video (Avoiding Plagiarism through Referencing) by clicking
on the following link: link: http://moodle.kent.edu.au/kentmoodle/mod/folder/view.php?id=3606
A search for peer-reviewed journal articles may also assist students. These type of journal articles can
be located in the online journal databases and can be accessed from the Kent Library homepage.
Wikipedia, online dictionaries, and online encyclopaedias are acceptable as a starting point to gain
knowledge about a topic but should not be over-used – these should constitute no more than 10% of
your total list of references/sources. Additional information and literature can be used where these
are produced by legitimate sources, such as government departments, research institutes such as the
National Health and Medical Research Council (NHMRC), or international organisations such as the
Assessment Brief 3 Software Requirement Specifications
Version 3: 8th November 2021
Kent Institute Australia Pty. Ltd.
ABN 49 003 577 302 CRICOS Code: 00161E RTO Code: 90458
TEQSA Provider Number: PRV12051
World Health Organisation (WHO). Legitimate organisations and government departments produce
peer reviewed reports and articles and are therefore very useful and mostly very current. The content
of the following link explains why it is not acceptable to use non-peer reviewed websites (Why can’t I
just Google?): https://www.youtube.com/watch?v=N39mnu1Pkgw (thank you to La Trobe University
for access to this video).
Assessment Brief 3 Software Requirement Specifications
Version 3: 8th November 2021
Kent Institute Australia Pty. Ltd.
ABN 49 003 577 302 CRICOS Code: 00161E RTO Code: 90458
TEQSA Provider Number: PRV12051

CLICK HERE TO GET A PROFESSIONAL WRITER TO WORK ON THIS PAPER AND OTHER SIMILAR PAPERS