University of Technology, Sydney

Staff directory | Webmail | Maps | Newsroom | What's on

31269 Business Requirements Modelling

Warning: The information on this page is indicative. The subject outline for a particular session, location and mode of offering is the authoritative source of all information about the subject for that offering. Required texts, recommended texts and references in particular are likely to change. Students will be provided with a subject outline once they enrol in the subject.

Subject handbook information prior to 2018 is available in the Archives.

UTS: Information Technology: Software
Credit points: 6 cp

Subject level:

Undergraduate

Result type: Grade and marks

Requisite(s): 31266 Introduction to Information Systems OR 31060 Information Systems Principles OR 31472 Introduction to Collaborative Systems OR 31484 Information Systems Foundations OR 31414 Information Systems
These requisites may not apply to students in certain courses. See access conditions.
Anti-requisite(s): 31424 Systems Modelling AND 31475 Requirements Engineering AND 31485 Systems Development

Description

This subject introduces information system concepts and describes how these concepts can be used to model business requirements. It outlines how the ability to capture information about the system in ways understood by its eventual users improves the final quality of the system. An overview of agile and non-agile software engineering principles, methods, tools and techniques is presented and practised in small teams. The subject introduces various analysis approaches found in contemporary system development including object-oriented methods, agile methods, business process modelling and entity-relationship modelling. It explores the relationships between these techniques and their application, and how they are used to capture and model the business requirements. Students apply various requirements elicitation, analysis, modelling and specification techniques to case studies in small teams.

Subject learning objectives (SLOs)

Upon successful completion of this subject students should be able to:

1. Identify stakeholders, understand their needs, and learn what/how to capture requirements in the system development process.
2. Apply modelling and systems analysis techniques that help understand the working of a business system.
3. Document and specify various requirements via Software Requirements Specification (SRS).
4. Develop various models using a range of systems analysis techniques to analyse and specify system and user requirements.
5. Work effectively in a small team.

Teaching and learning strategies

This subject uses a combination of formal lectures and collaborative and active learning workshops to support a practice focussed learning strategy. This subject is a practical case study based and continuous feedback driven subject. The teaching and learning approach is based on learning by doing collaborative work based on case studies.

In lectures, topics from the recommended texts are covered, with additional material from other sources being introduced where necessary.

Workshop sessions are used to support the lectures with illustrative examples, practice exercises and case studies that further reinforce the material originally presented in lectures. Workshops are also an extra opportunity for students to ask questions and generate a discussion based on UTSOnline material. Workshop sessions involve a range of activities such as role playing, think-pair-share, attempting short quizzes each week, short presentations, working in groups, group discussion, critiquing other students work, problem solving exercises, analysing stakeholder needs, etc. In workshops, students will apply the material and build a working relationship with other team members in a collaborative group learning environment. The collaborative and active learning environment will require students to work with other students in small groups on workshop and assignment case study exercises.

As pre-work, each week students will need to read and understand the material and then prepare the models and diagrams and bring it to the workshop for feedback. Regular feedback will be provided to students each week. Immediate feedback will be provided each week, straight after students have attempted the assessable weekly quizzes. Quizzes will be marked each week and marks will be uploaded to UTSOnline so that students can track their progress and performance in the subject regularly and before the census date. Weekly feedback will be provided to students on the work students have done on the workshop and assignment case studies.

Each week, students are required to do some pre-work and bring this work in progress for assignment case study to the workshop sessions. Each week, tutors will then provide face-to-face feedback (both written and verbal) on this work before formal submission. This will enable the students to identify and correct any issues before formal submission, and consequently improve their learning and performance in the subject.

Please note students are expected to put in some additional study time outside of class time. The university regards a 6 credit point subject as requiring 9-12 hours of study per week, including class time. Students must read the recommended and reference books outside of class time so that they can effectively participate in group work and discussions that are integral to the understanding of the topics.

Content (topics)

1. Process

  • System development processes (traditional and agile)
  • Requirements engineering processes

2. Elicitation

  • Stakeholders identification
  • Understanding the application domain
  • Requirements elicitation tools and techniques

3. Modelling

  • Process modelling with BPMN
  • Data modelling with ERD
  • Object-oriented modelling with several OO models using UML

4. Specification

  • Software requirements specifications
  • Quality attributes of requirements specifications

Assessment

Assessment task 1: Assignment 1 - Requirements Analysis

Objective(s):

This assessment task addresses the following subject learning objectives (SLOs):

2, 3, 4 and 5

This assessment task contributes to the development of the following course intended learning outcomes (CILOs):

A.1, B.1, B.2, C.1, C.2, E.1 and E.2

Type: Report
Groupwork: Group, group assessed
Weight: 10%
Length:

The recommended word limit for this assignment is maximum 1000 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.

Criteria linkages:
Criteria Weight (%) SLOs CILOs
Coverage of the system 45 2 A.1, B.1, B.2
Correct use of any diagrammatic modelling technique 45 4 C.1, C.2
Overall quality of report presentation (spelling, grammar, structure, cover sheet, table of contents, references and clarity which their diagrams or models convey) 5 3 E.1
Contribution to team work (succinctness, courtesy, motivation, taking a fair share of the work) 5 5 E.2
SLOs: subject learning objectives
CILOs: course intended learning outcomes

Assessment task 2: Assignment 2 - OO Requirements Analysis and Specification

Objective(s):

This assessment task addresses the following subject learning objectives (SLOs):

2, 3, 4 and 5

This assessment task contributes to the development of the following course intended learning outcomes (CILOs):

A.1, B.1, B.2, C.1, C.2, E.1 and E.2

Type: Report
Groupwork: Group, group assessed
Weight: 20%
Length:

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.

Criteria linkages:
Criteria Weight (%) SLOs CILOs
Coverage of the system 45 2 A.1, B.1, B.2
Correct use of any diagrammatic modelling technique 45 4 C.1, C.2
Overall quality of report presentation (spelling, grammar, structure, cover sheet, table of contents, references and clarity which their diagrams or models convey) 5 3 E.1
Contribution to team work (succinctness, courtesy, motivation, taking a fair share of the work) 5 5 E.2
SLOs: subject learning objectives
CILOs: course intended learning outcomes

Assessment task 3: Workshop Quizzes

Objective(s):

This assessment task addresses the following subject learning objectives (SLOs):

1, 2, 3 and 4

This assessment task contributes to the development of the following course intended learning outcomes (CILOs):

A.1, B.1 and C.3

Type: Quiz/test
Groupwork: Individual
Weight: 24%
Length:

There is no word limit.

Criteria linkages:
Criteria Weight (%) SLOs CILOs
Correct use of any diagrammatic modelling techniques 10 2 C.3
Correct application and understanding of the theory 90 1, 3, 4 A.1, B.1
SLOs: subject learning objectives
CILOs: course intended learning outcomes

Assessment task 4: Final Exam

Objective(s):

This assessment task addresses the following subject learning objectives (SLOs):

1 and 4

This assessment task contributes to the development of the following course intended learning outcomes (CILOs):

A.1, B.1, B.2, C.1 and C.2

Type: Examination
Groupwork: Individual
Weight: 46%
Length:

The exam will be 2 hours in duration.

Criteria linkages:
Criteria Weight (%) SLOs CILOs
Coverage of the system or case study in question 50 1 A.1, B.1, B.2, C.2
Correct use of any diagrammatic modelling technique to answer the question 50 1, 4 A.1, C.1, C.2
SLOs: subject learning objectives
CILOs: course intended learning outcomes

Minimum requirements

A student must gain a minimum of 50 marks overall (cumulative) from all assessment tasks (quizzes, assignments and final exam) in order to pass the subject. A student must also obtain a minimum of 50% in the final exam in order to be considered for a pass in the subject regardless of the marks obtained elsewhere. Therefore, failure to attain a 50% mark in the compulsory assessment item such as final exam, even if the cumulative mark is 50% or more overall, will result in a Fail (X) grade in the subject. For example, 52 X, 58 X, 67 X, etc.

No supplementary examination will be given in this subject. If you miss any piece of assessment through documented illness or misadventure, you should consult with the Subject Coordinator. In the case of the final examination, your "Application for Alternative Examination (due to Illness or Misadventure)" form must be submitted with appropriate documentation to the Student Information & Administration Centre within three working days of the examination.
NO conceded passes are to be granted due to University Policy.

Recommended texts

Robertson, S. & Robertson, J. (2013), "Mastering the Requirements Process: getting requirements right", Addison Wesley, 3rd Edition.

IIBA (2009), "A Guide to the Business Analysis Body of Knowledge", BABOK Version 2.0.

References

Bennett, S., McRobb S., & Farmer, R. (2010), "Object-Oriented Systems Analysis and Design Using UML", McGraw Hill, 4th Edition.

Leffingwell, D. & Widrig, D. (2003), “Managing Software Requirements – A Use Case Approach”, Addison Wesley, Second Edition.

Brown, D.W. (2002), “An Introduction to Object-Oriented Analysis – Objects and UML in Plain English” Wiley, Second Edition.

Kendall & Kendall. (2014), “Systems Analysis and Design”, Pearson Education Inc.

Blaha, M & Rumbaugh, J. (2005), “Object-oriented modeling and design with UML”, Pearson Prentice Hall, 2nd Edition.

Other resources

Students are required to login and read notices on the University's standard web-based course management system,
UTSOnline: https://online.uts.edu.au/

In particular, students are required to read at least once a week 'Announcements' on UTSOnline and also read the
Discussion Boards. All subject material including lecture, workshop notes, and the assignment
specifications will be posted on UTSOnline.

Plan to devote at least 1 hour a week or more to UTSOnline. https://online.uts.edu.au/