BN209 Software Engineering Group Assignment #1: Submission of the project Software Requirements Specification (SRS) document and MS Access Prototype. Submission Due: Week 07 - 05 May 2017 @ 05:00 PM, online using the MOODLE system Total Marks: 75 Marks, for 15% Total Assessment #1 Marks 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% Purpose of the assessment: The purpose of this assignment is to produce and submit a consolidated FIRST VERSION of the SRS Document and MS Access Prototype for your chosen 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) for investigate, analyze, and prototype: Education Shopping Library Airline Financial etc. Once student select their project, they need to do in-depth analysis for the project to complete SRS document and then develop MS Access prototype relate with your selected project. Students need approval from lecture / tutor for their project. Description: Students have to submit: 1. The SRS Document (Templates are available on MOODLE): a) Project introduction b) Functional and non-functional requirements c) An appropriate diagrams e.g. storyboards, mock-ups etc. d) Project goals, objectives, target audience etc. e) Technical assumptions and constraints. Students should also pursue the following steps to complete SRS Document: a. Required diagrams e.g. Context Diagram, ERD, DFD-L0 etc. (First Version) b. Proper References. c. Well written, properly formatted, correct grammar, no spelling mistakes etc. document. d. Length of the document between eight to ten A4 pages. e. Also, document presentation suitable for an external client. 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. References and appendices • Reference sources must be cited in the appropriate section of the document. • All cited references in IEEE style • List all the appendices Marking guidelines: Marks are allocated as follows: Assignment #1 SRS Document = 50 Marks (10% of the 15% total) SRS Description of the section Marks Introduction Outline of the project 5 General description Description of the project 5 Specific requirements Functional and non-functional specifications, etc., as indicated in the template 10 Analysis models Diagrams, figures, etc., as in the template 15 Goals, objective, assumptions, constraints Project goals, objectives, assumptions, and constraints 5 Appendices, references IEEE style 5 Presentation Appearance, grammar, clarity etc. 5 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 5 General navigation and appearance Appearance, clarity 5 Total 25 Marking Rubric for SRS document: Total Marks 75 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 Summary not easy to follow, context unclear Generally easy to follow, with some deficiencies. OK, with some obvious shortcomings. Poor, not acceptable General Description 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 Goals, objective, assumptions, 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 100 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 Extensions: Requests for an extension will not normally be granted. A request, accompanied by supporting documentation, must be received in writing before 3 working days from the due date. Special consideration form is available on level 8 reception. An extension will be granted only for the extent of the period covered in the accompanying certificates. That is, if granted, a one-day illness will result in a one-day extension. Penalties may apply for late submissions without an approved extension. Penalties: Academic misconduct such as cheating and plagiarism will incur penalties ranging from a zero result to program exclusion.