Business Requirements Modelling

UTS

Course Description

  • Course Name

    Business Requirements Modelling

  • Host University

    UTS

  • Location

    Sydney, Australia

  • Area of Study

    Computer Programming, Computer Science, Information Sciences, Information Technologies

  • Language Level

    Taught In English

  • Prerequisites

    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

  • Course Level Recommendations

    Lower

    ISA offers course level recommendations in an effort to facilitate the determination of course levels by credential evaluators.We advice each institution to have their own credentials evaluator make the final decision regrading course levels.

    Hours & Credits

  • Credit Points

    6
  • Recommended U.S. Semester Credits
    4
  • Recommended U.S. Quarter Units
    6
  • Overview

    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 and entity-relationship modelling, and describes the relationships between these techniques and their application, and how they are used to capture and model the business requirements.
     
    Subject objectives
    Upon successful completion of this subject students should be able to:
     
    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.
    4. Use system analysis techniques to develop a system model
    This subject also contributes specifically to the development of the following course intended learning outcomes:
     
    Identify, interpret and analyse stakeholder needs. (A.1)
    Apply systems thinking to understand complex system behaviour including interactions between components and with other systems (social, cultural, legislative, environmental, business etc.) (A.5)
    Identify and apply relevant problem solving methodologies (B.1)
    Design components, systems and/or processes to meet required specifications (B.2)
    Apply abstraction, mathematics and/or discipline fundamentals to analysis, design and operation (C.1)
    Develop models using appropriate tools such as computer software, laboratory equipment and other devices (C.2)
    Communicate effectively in ways appropriate to the discipline, audience and purpose. (E.1)
    Work as an effective member or leader of diverse teams within a multi-level, multi-disciplinary and multi-cultural setting (E.2)
    Teaching and learning strategies
    The material will be presented in three hours each week: one hour of a lecture, and two hours of tutorial class.
     
    Students must attend the lecture before attending their tutorial class.
    In lectures, topics from the recommended texts are covered, with additional material from other sources being introduced where necessary. Questions in lectures are allowed and encouraged, but the size of the lecture audience will mean that sometimes a full and detailed answer may not be possible. Also sometimes the student may have to wait till the end of the lecture if the question being asked is not going to benefit the entire class or is off topic. Usually, students should ask questions in lectures when:
    - if something is not immediately clarified they are likely to have trouble understanding the rest of the lecture. Questions driven by natural curiosity are welcome, but they should be asked at the end of the lecture, or at tutorials, or online discussion forums on UTS Online.
     
    Tutorial sessions are used to support the lectures with illustrative examples, practice exercises and case studies that further reinforce the material originally presented in lectures. Tutorials are also an extra opportunity for students to ask questions and generate a discussion.
    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.
     
    Content
    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: Assignment1 - Requirements Analysis
    Objective(s):
    This assessment task addresses the following subject learning objectives:
     
    1, 2, 3 and 4
     
    This assessment task contributes to the development of the following course intended learning outcomes:
     
    A.1, A.5, B.1, B.2, C.1, C.2, E.1 and E.2
     
    Type: Report
    Groupwork: Group, group assessed
    Weight: 13%
    Length:
    There is no compulsory minimum and maximum word limit. The recommended word limit for this assignment is maximum 2500 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, A.5, 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 1 E.2
    SLOs: subject learning objectives
    CILOs: course intended learning outcomes
    Assessment task 2: Assignment2 - OO Requirements Analysis and Specification
    Objective(s):
    This assessment task addresses the following subject learning objectives:
     
    1, 2, 3 and 4
     
    This assessment task contributes to the development of the following course intended learning outcomes:
     
    A.1, A.5, B.1, B.2, C.1, C.2, E.1 and E.2
     
    Type: Report
    Groupwork: Group, group assessed
    Weight: 15%
    Length:
    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.
     
    Criteria linkages:
    Criteria Weight (%) SLOs CILOs
    Coverage of the system 45 2 A.1, A.5, 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 1 E.2
    SLOs: subject learning objectives
    CILOs: course intended learning outcomes
    Assessment task 3: Tutorial Quizzes
    Objective(s):
    This assessment task addresses the following subject learning objectives:
     
    1, 2, 3 and 4
     
    This assessment task contributes to the development of the following course intended learning outcomes:
     
    A.1, A.5, B.1, B.2, C.1, C.2 and E.1
     
    Type: Quiz/test
    Groupwork: Individual
    Weight: 32%
    Length:
    There is no word limit.
     
    Criteria linkages:
    Criteria Weight (%) SLOs CILOs
    Understanding of the theory 100 1, 2, 3, 4 A.1, A.5, B.1, B.2, C.1, C.2, E.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:
     
    1, 2, 3 and 4
     
    This assessment task contributes to the development of the following course intended learning outcomes:
     
    A.1, A.5, B.1, B.2, C.1, C.2 and E.1
     
    Type: Examination
    Groupwork: Individual
    Weight: 40%
    Length:
    The exam will be 3 hours in duration.
     
    Criteria linkages:
    Criteria Weight (%) SLOs CILOs
    Coverage of the system or case in question 45 1, 2 A.1, A.5, B.1, B.2
    Correct use of any diagrammatic modelling technique to answer the question 45 1, 4 A.1, C.1, C.2
    Overall quality of the answer to a question (spelling, grammar and clarity which their diagrams or models convey) 10 3 E.1
    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.

Course Disclaimer

Courses and course hours of instruction are subject to change.

Credits earned vary according to the policies of the students' home institutions. According to ISA policy and possible visa requirements, students must maintain full-time enrollment status, as determined by their home institutions, for the duration of the program.