UNIVERSITY OF TECHNOLOGY, SYDNEY
31269 Business Requirements Modelling
Assignment 2 - Object Oriented Requirements Analysis and Specification Job Advertisement and Application Submission (JAAS) System
Due Date: Tuesday, 19 October 2015 at 11:00 am
Submission:
Each group will submit a softcopy of the group assignment 2 via Turnitin before Monday 19/10/2015 11:00 AM AEST. Accepted file formats for this assessment task include DOC, DOCX or PDF. A group leader will submit the assignment on the behalf of the whole group. Use the Assessment item 2: Object Oriented Requirements Analysis and Specification Assignment Turnitin link (View/ Complete) on UTS Online for submitting your assignment. You submission file title and name must follow the following naming pattern.
BRM-TUT1-your tut activity number – Group number
BRM and TUT1 are constants or fixed. For instance, if your TUT1 activity number is 02 (see timetable for your activity) and group number in your tutorial class is 03 then your submission file title/name must be worded as BRM-TUT1-02-03.
You must check assignment Turnitin report and ensure that your work does not contain plagiarism. You may submit your assignment to Turnitin many times before the submission due date. Final Turnitin reports can be used as evidence by the teaching staff in the event that plagiarism is suspected in an assignment and will be dealt as per University rules. Do not allow anyone to copy your solution – this is considered misconduct; all miscreants will receive a mark of 0, at best for the report and will be dealt as per University rules. You may be required to provide the hard or soft copy of the assignment anytime during the semester.
Marks: 15%
Word Limits
There is no compulsory minimum and maximum word limit. The recommended word limit for this assignment is maximum 3000 words excluding diagrams, bibliography and appendices. Word limit will be regarded as recommended rather than compulsory, and no student will be disadvantaged by being under or over the recommended word limit
Group work
You will work in a team of maximum three students. The assignment will be done in a group of 3 students from the same tutorial class. For the group assessment in this subject, students will be assessed as a team; here each member of the team will receive the same mark for the assignment. Students will self-organise themselves in groups. It is not the responsibility of teaching staff to find a group for you; however, they would help you to put in a group if you have not found group members yet. Once the groups are formed and for any reason(s) you want to change the group, then it is solely your responsibility to make other arrangements and find another alternative group who is willing to accept you. This is a group assignment and you must respect other students in the same group, different groups and teaching staff. If you have any group issues then you must inform your tutor as soon as possible and well before (at least 1 week or earlier) the assignment submission or due date. Group assignment issues reported on or after the assignment submission date may not be considered. There will be zero tolerance for any academic and non-academic misconduct. For more details, refer University Rules, read Subject Outline, and read the section on Academic Misconduct provided in this document.
Workload
Each student in a group is expected to allocate and work approx. 9-13.5 hours on this assignment. Each student in a group must take the fair share of the workload. Where there are problems with the performance of individuals in the group, the lecturer may choose to introduce peer assessments for the group.
Objectives: (1, 2, 3 and 5)
1. Understand who are the stakeholders and learn what/how to capture requirements in the system development process.
2. Appreciate how modelling techniques can help to understand the working of business systems.
3. Discover why system specifications are important and how modeling can be used to specify systems and user requirements.
5. Use object oriented system analysis techniques to develop a system model
Task
The assignment will require the group of 3 students to assess the same Case Study as Assignment 1 and produce a report containing UML diagrams and parts of software requirement specifications using the template provided. This assignment requires analysing the current Advertise Position and Acquire Job Applications processes of the Assignment 1 Case Study (see Appendix A). You are required to produce a Requirements Specification Document for developing the online Job Advertisement and Application Submission (JAAS) system. The JASS will allow the authorised hiring manager to advertise vacant positions online and also allow the authorised candidates to view and directly submit the job applications for the advertised positions. The authorised hiring manager should be able to view the relevant job applications against the advertised positions. The authorised candidate should be able to view the job application they have submitted against the specific advertised position. The requirements specification document tasks and marking scheme are as follows:
• Identify possible User Stories and develop a User Story Map for the online JAAS system. You need to estimate and prioritise each user story (see requirement specification lecture and tutorial).
• Select 4 user stories in total in consultation with your tutor during the tutorial sessions; document/narrate 2 Use Cases for the 2 selected hiring manager user stories and 2 use cases for the 2 selected candidate user stories.
• Draw 2 Sequence Diagrams - 1 for the hiring manager and 1 for the candidate use cases
• Document 1 Class Diagram
• Document 1 State Transition Diagram for “Job Application” object
• Document 2 user interfaces or Wireframes (1 wireframe describing the hiring manager use case and 1 wireframe describing the candidate use case). Refer week 3 lecture and tutorial.
• Document security and performance requirements
• Include document management, introduction, bibliography, contribution to team work Note: For more details, please see the section on marking scheme.
Criteria
The requirements analysis and specification report assignment will be assessed based on the following criteria.
Criteria Items Objectives Weight Marks
Coverage of the system
2 87% 13.0
Correct use of any diagrammatic modelling technique 5
Overall quality of report presentation (e.g. (spelling, grammar, structure, cover sheet, table of contents, bibliography, document management, references and clarity which their diagrams or models convey) 3 10% 1.5
Contribution to team work (evidence) (e.g. succinctness, courtesy, motivation, taking a fair share of the work) 1 3% 0.5
Total 100% 15
Marking Scheme and template of submission report:
Use the following marking scheme to prepare and submit your Analysis and Specification Report. A template showing the structure of this submission report is available on uts online. Students must use that template. The report should include the following sections:
SECTION Maximum Marks Note
Cover Sheet & Header Page 0.25 Overall Quality of Report Presentation: Signed FEIT declaration of originality cover sheet containing correct group name, student ids, names and signatures (scan and attached to your assignment). Document header page with project deliverable title. If you do not include these then assignment will not be marked and you may receive zero for the whole assignment.
Table of Contents 0.25 Follow the format and sections expected in the report in correct order (use the template)
1. Document Management 0.25 Overall Quality of Report Presentation: Max. 1 Page
1.1 Revision History
1.2 Intended Audience
1.3 Reference Documents
1.4 Glossary
2. Introduction 0.25 Overall Quality of Report Presentation: Max 2 Pages
2.1 Document Purpose
2.2 Project Purpose
2.3 Project Scope Use Case Diagram as a Project Boundary Diagram
2.4 Assumptions
SECTION Maximum Marks Note
3. Functional Requirements 7.0 Coverage and Correctness:
Apply user story and UML rules
3.1 User Story Map (1) Identify possible user stories for the online JASS system. Develop a user story map by using the user story map template. Estimate and prioritise each user story on the map.
3.2 User Stories and Use
Cases (4) Select only 4 user stories from the user story map (in consultation with your tutor). Detail the selected 4 user stories in terms of 4 use cases by using the use case narrative template - 2 for hiring manager and 2 for candidate use cases.
3.3 Sequence Diagrams (2) Document 2 sequence diagrams - 1 for hiring manager and 1 for candidate use case narrative
4. Data Requirements 4.0 Coverage and Correctness: Apply UML rules
4.1 Class Diagram (2) Document 1 class diagram
4.2 Job Application State
Transition Diagram (2) Draw 1 state transition diagram for “Job Application” object
5. Non-functional
Requirements 2.0 Coverage and Correctness:
Use non-functional requirements rules
5.1 User Interface
Requirements (1) Document 2 user interfaces or wireframes - 1 for describing the hiring manager use case and 1 for describing the candidate use case
5.2 Security Requirements (0.5) Document security requirements - 1 for the hiring manager use case and 1 for the candidate use case. *Requirement statements must satisfy the “SMART” requirements quality criteria.
5.3 Performance
Requirements (0.5) Document performance requirements - 1 for the hiring manager use case and 1 for the candidate use case.
*Requirement statements must satisfy the “SMART” requirements quality criteria.
6. Bibliography 0.25 Overall Quality of Report Presentation: Use correct Harvard referencing style
7. Appendices
(Assignment Team Log) 0.5 Contribution to Team Work (Evidence): 1) Keep record and submit the contribution of each team member to each task. Every team member should try to work on each task, though the contribution can be different. 2) Keep record and submit the team
communication (e.g. emails, meeting minutes, etc.)
8. Other Aspects related to the Overall Quality of Report
Presentation 0.25 Overall Quality of Report Presentation: Use correct spelling, grammar, structure, clarity, header, footer, page numbers, consistent font, new sections on new pages, presentation of diagrams, etc.
Total Maximum Marks 15
NOTE: You MUST use Assignment 2 Report template/structure provided on uts online.
Assessment Feedback and Return
You must regularly get feedback on the assignment tasks and deliverables from subject coordinator, lecturer and tutors during the lectures and tutorial sessions. Marked assignments with feedback will be returned within 2 weeks after the assignment due or submission date. Students can collect their marked assignment from their tutors. Once the marked assignments are available for collection, an announcement will be made on uts online.
Referencing Standards
All material derived from other works must be acknowledged and referenced accordingly using the Harvard Referencing Style (see http://www.bell.uts.edu.au/referencing/harvard_system).
Late Submission and Penalty
Assignment 2 is due at 11:00 am on Monday, 19th October 2015. Each 24 hour period after this time is considered to be an extra day late. For example, a submission at 11:01 am on Monday, 19th October is considered 1 day late, while a submission at 11:01 am on Tuesday, 21st October is considered 2 days late.
Your assignment will lose 20% of its original mark per day late, unless permission has been given for extension by the subject co-ordinator, before the due date.
Special Consideration
Special consideration, for late submission, must be arranged beforehand with the subject coordinator through the UTS Special Consideration Process. Please also see the UTS Special Consideration Process: www.sau.uts.edu.au/assessment/consideration
Special Needs
Students should email the subject coordinator as soon as possible (and prior to the assessment deadline) to make them aware of the impact on them meeting assessment component/requirements, and that they are seeking assistance through UTS Special Needs as detailed in Section 5.1.3 of Procedures for the Assessment of Coursework Subjects.
Academic Misconduct
Students are reminded of the principles laid down in the -Statement of Good Practice and Ethics in Informal Assessment- (pages 5 & 6 of the Faculty Handbook). Unless otherwise stated in a specific handout, all assessment tasks in this subject should be your own original work. Any collaboration with another student (or group) should be limited to those matters described in -Acceptable Behaviour- section of the Handbook. For essay questions, students should pay particular attention to the recognition of -Plagiarism- as described in that section of the Handbook (page 6). Any infringement by a student will be considered a breach of discipline and will be dealt with in accordance with Rules and By-Laws of the University. Posting your assignment on the web and getting help through blogs, forums or other websites may lead to academic misconduct. Penalties such as zero marks for assignment or subject may be imposed.
Please also see the subject outline in conjunction with UTS policy and procedures for the assessment for coursework subjects, available at:
www.gsu.uts.edu.au/policies/assessment-coursework.html
Querying Marks/Grades and Final Results
If a student disagrees with a mark or a final result awarded by a marker:
• where a student wishes to query a mark, the deadline for a query during teaching weeks is 10 working days from the date of the return of the task to the student More information can be found at: https://my.feit.uts.edu.au/pages/course/student_policies_rules
ELSSA
If you think you need help with your English for this subject, contact the English Language Study Skills Assistance (ELSSA centre) level 18, Tower building, Broadway, phone: 9514 2327.
------------------------------------------------------------------------------------------------------------------
Appendix A.
ABC Human Services Department Case Study Project Processes
Advertise Position (Process Time - 5 Days)
The Hiring Manager sends the vacant position description (PD) related to a specific location (e.g. Sydney, Melbourne) to Human Services (HS). The HS stores the PD (id, department, job description, requirements, hiring manager, closing date, location, type, and status etc.) in a vacant position file. Position type could be a permanent or part-time. HS creates the job or position advertisement based on the PD, which is posted along the job application form on the ABC company website. HS also forwards the job advertisement and job application form to a number of recruitment agencies and university placement departments for advertisement via email. HS lacks the support for automatically uploading the job advertisements and job application form to the websites of different recruitment agencies and university placement departments.
Acquire Job Applications (Process Time - 10 Days)
Candidates complete and submit the job applications (id, candidate, position, status) and resume directly or through recruitment agencies or university placement departments to HS via email. A candidate can submit only one job application for each position. An email is sent out to all candidates to acknowledge the receipt of their applications. This is done upon the receipt of their job application. All job applications and resumes received by the HS are stored in a job application file and are checked for completeness. The incomplete applications are rejected and candidates are informed. For the complete applications, if the candidate is new (applying for the first time) then new candidate information (e.g. id, name, address, qualification, experience etc.) is stored in the candidate file. All the complete job applications and resumes received by the HS are forwarded to Hiring Manager for their review and validating their suitability for the role. Due to a manual processes and data in the excel spread sheets, HS needs to spend a lot of time working through incomplete/unsolicited resumes and applications.
It is also not easy to search and identify whether the candidate is new or not.