Recent Question/Assignment

Assessment Details and Submission Guidelines
Unit Code BN209
Unit Title Trimester 2, 2018 – Software Engineering
Assessment Type Assignment 1
Assessment Title Group Assignment
Purpose of the assessment (with ULO Mapping) This assignment assesses the below Unit Learning Outcomes; students should be able to demonstrate their achievements in them:
- Define System requirement through requirement elicitation and workshops
- Explain the process for, and execute, verification and validation of system requirements
- Apply use case, data and process modelling techniques to specify system requirements
Weight 15%
Total Marks 75
Breakups of assessment are as follows:
• SRS Document - 50 marks, 10% of the total 15%
• MS Access Database - 25 marks, 5% of the total 15%
Word limit 6-8 A4 Pages
Due Date Friday Week 7: 31st August, 2018 23:55
Submission Guidelines • All work must be submitted on Moodle by the due date along with a completed Assignment Cover Page.
• The assignment must be in MS Word format, 1.5 spacing, 11-pt Calibri (Body) font and 2 cm margins on all four sides of your page with appropriate section headings.
• Reference sources must be cited in the text of the report, and listed appropriately at the end in a reference list using IEEE referencing style.
Extension If an extension of time to submit work is required, a Special Consideration Application must be submitted directly to the School's Administration Officer, in Melbourne on Level 6 or in Sydney on Level 7. You must submit this application three working days prior to the due date of the assignment. Further information is available at:
http://www.mit.edu.au/about-mit/institute-publications/policies-proceduresand-guidelines/specialconsiderationdeferment
Academic
Misconduct
Academic Misconduct is a serious offence. Depending on the seriousness of the case, penalties can vary from a written warning or zero marks to exclusion from the course or rescinding the degree. Students should make themselves familiar with the full policy and procedure available at: http://www.mit.edu.au/aboutmit/institute-publications/policies-procedures-and-guidelines/Plagiarism-
Academic-Misconduct-Policy-Procedure. For further information, please refer to the Academic Integrity Section in your Unit Description.
Purpose of the assessment:
The purpose of this assignment is to produce and submit a consolidated FIRST VERSION of the Software Requirement Specification (SRS) Document and MS Access Prototype for your chosen project.
Form a team of exactly 5 people and write a Software Requirements Specification, based on a selected
project
Projects Selection:
Students can choose/select any website/application/system/software with enabled database component as a reference for their project from the following domains (industries) to investigate, analyse, and prototype:
o Education o Shopping o Library o Airline o Financial o Entertainment
Task:
Once students select their project, they need to do in-depth analysis for the project to complete Software Requirement Specification document and then develop MS Access prototype that relate to their selected project. Students need approval from lecture / tutor for their selected project.
Guidelines:
Follow the IEEE 830-1998 Recommended Practice for Software Requirements Specifications as your guide. I recommend reading the entire document before starting your project.
Another good source of guidelines for software requirements specifications is :
http://www.processimpact.com/articles/qualreqs.html
Format:
Your SRS document should follow the template of the IEEE standard.
Your Assignment 1 SRS document should include the following:
1. The SRS Document Version 1.0 (Templates and guideline are available on MOODLE):
a) Introduction
b) Purpose
c) Scope
d) Glossary
e) References
f) Document Overview
g) Product Description
h) Functional and non-functional requirements
i) Technical assumptions and constraints
j) Context Diagram, Use Case Diagram, Entity Relationship Diagram (First Version)
2. The Access prototype should include (Reference, week 01 LAB DB File and available on MOODLE):
a) The prototype will have a splash page at the start.
b) All the tables and attributes properly documented and structured.
c) Enough functionality to see the prototype working.
d) The corresponding reading and writing forms for the tables.
3. An up to date copy of the Project Activity Journal where you show the weekly working of the group.
Team submission:
This is a group assignment hence, only one member from a group will upload the ONE ZIP FILE on MOODLE.
Submission guidelines:
The report should have a consistent, professional, and well-organized appearance. Your report should include the following:
1. Cover page must identify students’ (name and number), teaching staff, and assignment.
2. The pages of the assignment must be clear on each page.
Marking criteria:
Marks are allocated as follows:
Assignment #1 SRS Document = 50 Marks (10% of the 15% total)
SRS Description of the section Marks
Introduction In this subsection, describe the purpose of the particular SRS and specify the intended audience for the SRS 5
Scope, objectives and goals • Explain the software product(s) to be produced
• Explain what the software product(s) will, and will not do
• Describe the relevant benefits, objectives, and goals of the project
12
Specific requirements Functional and non-functional requirements 10
Analysis models Context Diagram, Use Case Diagram, Entity Relationship Diagram 12
assumptions, constraints assumptions, and constraints 5
Appendices, references IEEE style 3
Presentation Appearance, grammar, clarity etc. 3
Total 50
Assessment #1 MS Access Prototype = 25 Marks (5% of the 15% total)
During Lab Classes (Week 02- Week 06)
Access DB Description of the section Marks
Splash page DB opening form 5
Data structure DB data and metadata for the project, keys, etc. 5
Functionality Functions implemented 5
Forms All the forms in the project implemented 5
General navigation and appearance Appearance, clarity 5
Total 25
Marking Rubric for SRS document: Total Marks 50
Grade/Mark HD 80% -100% D 70%-79% C 60%-69% P 50%-59% Fail 50
Excellent Very Good Good Satisfactory Unsatisfactory
Introduction Project properly summarized and set
in context Generally easy to follow, with some deficiencies. Summary not easy to follow, context unclear Some relevance and briefly presented. This is not relevant to the assignment
Scope, objectives and goals All topics are pertinent and covered in depth. Most topics are pertinent and covered in depth Correct, with some deficiencies OK, with some obvious shortcomings. Poor, not acceptable
Specific requirements Requirements are
all
covered and properly specified Most requirements are covered and properly specified Some
requirements are missing or not properly specified OK, with some obvious shortcomings. Poor, not acceptable
Analysis models All elements and diagrams are present and well designed Most elements and diagrams are present and well designed Some components are missing or not properly designed
OK, with some obvious shortcomings.
Poor, not acceptable
Assumptions
and constraints
Very well defined
Most of the areas defined
Some areas defined
OK, with some obvious shortcomings.
Poor, not acceptable
Appendices
References Excellent use of sources. Accurate referencing. Obvious that outstanding effort made
Very good effort
Good effort made but not outstanding
Acceptable
Poor, not acceptable
Presentation Excellent, outstanding effort made
Very good effort Good effort made
but not outstanding Made some
effort, but only acceptable
Poor, not acceptable
Marking Rubric for Access database: Total Marks 25
Grade/Mark HD 80% -100% D 70%-79% C 60%-69% P 50%-59% Fail 50
Excellent Very Good Good Satisfactory Unsatisfactory
Splash page
Project opens properly Project opens properly, but
not enough effort
Generally OK, with some deficiencies.
OK, with some obvious shortcomings.
Poor, not acceptable
Data structure All tables and attributes have been included Most tables and attributes have been included Some
deficiencies in the tables and attributes
OK, with some obvious shortcomings.
Poor, not acceptable
Functionality
All functions are properly covered
Most functions are properly covered Some functions are missing or not properly covered
OK, with some obvious shortcomings.
Poor, not acceptable
Forms
All forms are present and well designed Most forms are present and well designed Some forms are missing or not properly designed
OK, with some obvious shortcomings.
Poor, not acceptable
General navigation and appearance Excellent, outstanding effort
made
Very good effort Good effort made but not outstanding
Acceptable
Poor, not acceptable
Prepared by: Samira Baho Moderated by: Dr Sue Zhou April, 2018

Looking for answers ?


Recent Questions