SYS366 - Requirements Gathering Using OO Models

Outline info
Last revision date 2018-07-20 12:01:47.9
Last review date 2018-07-20 12:02:03.226

Subject Title
Requirements Gathering Using OO Models

Subject Description
This subject focuses on the techniques and tools involved in gathering requirements for business systems that will solve business stakeholders' processing problems. Students will be introduced to system development life cycles, interface design, and will learn how to use research, observation, interviews, prototypes and feedback to gather stakeholders' requirements. Students will also learn how to document requirements in both business and systems use case diagrams using the Unified Modeling Language (UML) and the Rational Rose modeling tool. They will learn to write the use case descriptions, both business and systems. An in-depth case study will be used throughout the subject to allow students to apply what they learn.

Credit Status
1 credit (3 units)
Required for CPA - Computer Programming and Analysis (Ontario College Advanced Diploma)
Required for CPD - Computer Programmer (Ontario College Diploma)

Learning Outcomes
Upon successful completion of this subject the student will be able to:

1. Follow an Object-oriented methodology

2. Draw systems use case diagrams showing actor to use case relationships and use case to use case relationships

3. Model the primary business functionality in Business Use Case Diagrams

4. Perform the research and information gathering required to determine what a proposed system needs to accomplish

5. Identify all activities within a proposed system, as well as who initiates them

6. Transform activities into use cases

7. Describe use cases in writing following a given template

8. Describe in writing the phases involved in developing a system

9. Apply basic interface design concepts to create mock-ups (e.g. web page, screen and mock-ups reports)

10. Work effectively as part of a system development team to deliver a requirements model

11. Perform a user interface walk-through

12. Articulate (in writing) what a proposed system needs to accomplish

13. Use Rational Rose software to create the use case view of a software model

14. Perform a requirements walk-through

Essential Employability Skills
Communicate clearly, concisely and correctly in the written, spoken and visual form that fulfils the purpose and meets the needs of the audience.

Apply a systematic approach to solve problems.

Use a variety of thinking skills to anticipate and solve problems.

Locate, select, organize, and document information using appropriate technology and information systems.

Analyze, evaluate, and apply relevant information from a variety of sources.

Show respect for diverse opinions, values, belief systems, and contributions of others.

Interact with others in groups or teams in ways that contribute to effective working relationships and the achievement of goals.

Manage the use of time and other resources to complete projects.

Take responsibility for one's own actions, decisions, and consequences.

Cheating and Plagiarism
Each student should be aware of the College's policy regarding Cheating and Plagiarism. Seneca's Academic Policy will be strictly enforced.

To support academic honesty at Seneca College, all work submitted by students may be reviewed for authenticity and originality, utilizing software tools and third party services. Please visit the Academic Honesty site on for further information regarding cheating and plagiarism policies and procedures.

All students and employees have the right to study and work in an environment that is free from discrimination and/or harassment. Language or activities that defeat this objective violate the College Policy on Discrimination/Harassment and shall not be tolerated. Information and assistance are available from the Student Conduct Office at

Accommodation for Students with Disabilities
The College will provide reasonable accommodation to students with disabilities in order to promote academic success. If you require accommodation, contact the Counselling and Disabilities Services Office at ext. 22900 to initiate the process for documenting, assessing and implementing your individual accommodation needs.


Topic Outline
The Systems Development Life Cycle 10%

  • Types of applications
  • What is software development?
  • Role of the Systems Analyst
  • How systems are built
  • Reasons behind system success and failure
  • The iterative development process
Introduction to The Requirements Gathering Process 20%
  • Defining a systems idea
  • Identifying stake holders
  • Methods for gathering requirements
  • Identifying businesses processes and activities
  • Identifying actors and stakeholders
  • Creating activity tables
  • Draw Business use case diagrams to demonstrate an understanding of the primary business processes
  • Write business use case descriptions
Identifying Systems Use Cases in Requirements Gathering 20%
  • What is a Systems use case?
  • Defining Systems use case size using "results of value"
  • Identifying Systems use cases
  • Creating Systems use case digrams showing associations with actors and between use cases
  • Identifying stereotyped relationships
  • Adding a Systems use case diagram to the software model
Documenting Requirements using Systems Use Case Descriptions 25%
  • Systems use case description standards
  • Testing descriptions
  • Adding Systems use case descriptions to a software model
  • Writing scenarios
  • Combining scenarios into Casual Use Case Descriptions
Walk-through 5%Purpose of a Walk-through
  • Walk-through standards
  • Performing a requirements walk-through
  • Performing a user interface walk-through
User Interface Design 20%
  • Types of user interfaces
  • Basic design principles
  • Creating interface mock-ups

Mode of Instruction
Class lectures, labs and discussions reinforced with class assignments are the  methods used in introducing course materials. Group discussion with real case projects are emphasized throughout the course to help students put it all together.

It is the student's responsibility to save documents, articles and notes that the instructor has provided on BlackBoard or in class. Students will not be able to access BlackBoard as of the last day of the student’s class.

Prescribed Texts
Use Case Modeling,
by Bittner, Kurt, Addison-Wesley, ISBN# 978-0-201-70913-1

Reference Material
Writing Effective Use Cases, 1st edition
by Alistair Cockburn, Addison-Wesley, ISBN# 978-0201702255

Promotion Policy

Grading Policy
A+ 90%  to  100%
A 80%  to  89%
B+ 75%  to  79%
B 70%  to  74%
C+ 65%  to  69%
C 60%  to  64%
D+ 55%  to  59%
D 50%  to  54%
F 0%    to  49% (Not a Pass)
EXC Excellent
SAT Satisfactory
UNSAT Unsatisfactory

For further information, see a copy of the Academic Policy, available online ( or at Seneca's Registrar's Offices.

Modes of Evaluation
Since this is a professional credit subject, marking standards reinforce professional practice by demanding legible, tidy work. Written materials should be well organized and grammatically correct, with proper spelling and punctuation.


  • Students must retain a duplicate of all assignments.
  • Computer assignments should be documented to the instructor's standards.
  • Assignments must be handed in on the scheduled due date. Late assignments are penalized.
  • For particulars, please obtain standards, dates, etc. from your instructor.

Absenteeism and Tests
  • Students should be aware that absenteeism will impact on their ability to achieve satisfactory grades.
  • If you miss a test, you must provide the reason in writing to the instructor prior to the next scheduled class. If your reason is accepted, you will be permitted to write a make-up test. Otherwise, you will be given a zero for the test. You must submit an original doctor’s certificate identifying the date, length of time of expected absence and the specific reason for your absence, or other appropriate documentation.

Term Work and Final Exam
  • Students must attain a combined grade of at least 50% on term work and the final exam. Students must pass the final exam in order to pass the subject.
  • For further information on evaluation and academic standing, see a copy of the Academic Policy available at Seneca registration offices.

Grading is based on the following marking scheme:

Tests (minimum 2)
Assignments (minimum1)
Final Exam

Approved by: Denis Gravelle