Title | SWE2000 1 Assignment 01 2014 S1 |
---|---|
Course | Software Development Practices |
Institution | Swinburne University of Technology |
Pages | 2 |
File Size | 181.8 KB |
File Type | |
Total Downloads | 37 |
Total Views | 113 |
Assignment 1, Assignment 1, Assignment 1...
SWE20001 SDP
Semester 1 2014
SWE20001 Software Development Practices Assignment 1 – Problem Analysis Due on Wednesday 2nd April at 8:30 am Worth: 10%
1
Aim
2 Submission Requirements This is an assignment for students to work individually. Before submission, students are strongly advised to show their work to tutor during tutorial class for comments. An electronic copy of the final document (in either MS Word or pdf format) with completed “Assignment Cover Sheet” (see unit outline) on the front page must be submitted to Blackboard before commencement of the Week 5 lecture. Further instructions for submission will be posted on Blackboard one week before assignment due date. Late submission of assignment will incur a 10% penalty per day for up to maximum 5 calendar days before a zero result will be recorded (refer to unit outline). Your submission has the following constraints: x Your project/product must have a name. x The document must be 3 Submission contents Your submission will need to contain the following: (i) that show a and (1%) (ii) and their key (1%) (iii) for each actor in (ii) (1%) (iv) and in the space (1%) (v) a. Domain (1%) b. Domain (1%) (vi) High level system a. requirements (1%) b. requirements (1%) (vii) , including solution (1%) (viii) for the chosen solution proposed in (vii), using the (1%) 4 Marking criteria Submissions shall be assessed against the items stated in Section 3 above. Each item will be assessed based on a scale from 0 (non-existing) to 5 (outstanding). A copy of the marking guide is appended for your reference.
© Swinburne University of Technology
Page 1
SWE20001 SDP
Semester 1 2014
Marking sheet for SDP Assignment 1, Semester 1/2014 Student ID Student Name
Tutorial Date/Time/Room Tutor Name
Project/Product Name 0 1 2 3 (Missing) (Very Poor) (Poor) (OK)
4 5 (Good) (Outstanding) Marking Criteria
Scenarios Actors Goals Constraints & Assumptions Problem Domain Vocabulary Model System Requirements Functional Non-functional Chosen Solution Vision Statement
high level, solvable w ith softw are for each actor, pain points for each actor, do they correlate w ith the pain points realistic in their context definitions, rules, constraints, key actions, explanations nouns match vocab, cardinality, relationships named, associations, aggregations consistent, reallistic and verifiable consistent, reallistic and verifiable valid justifications w ith solution attributes based on the template from lectures – i.e. for/w ho/the/that/unlike/our/product
0 /50 /10 Mark Adjustment (if applicable) Constraints Product/project name Document length
missing product name - deduct 1 mark less than 3 pages or exceed 4 pages, or not in 12-point font - deduct 1 mark
Penalty Late penalty Group penalty
deduct 1 mark (i.e. 10% of 10 marks) per day after due date
Plagiarism
if detected, marks w ill be overridden and informal process started
pro-rata mark based on student number in the group, list all other stud# in the group
FINAL MARK
/10 (Round to 1 decimal place) ZERO f inal mark w ithout cover sheet or w ithout student signature on cover sheet
© Swinburne University of Technology
Page 2...