SYS366 - Requirements Gathering Using OO Models

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.

Academic Integrity
Seneca upholds a learning community that values academic integrity, honesty, fairness, trust, respect, responsibility and courage. These values enhance Seneca's commitment to deliver high-quality education and teaching excellence, while supporting a positive learning environment. Ensure that you are aware of Seneca's Academic Integrity Policy which can be found at: http://www.senecapolytechnic.ca/about/policies/academic-integrity-policy.html Review section 2 of the policy for details regarding approaches to supporting integrity. Section 2.3 and Appendix B of the policy describe various sanctions that can be applied, if there is suspected academic misconduct (e.g., contract cheating, cheating, falsification, impersonation or plagiarism).

Please visit the Academic Integrity website http://open2.senecac.on.ca/sites/academic-integrity/for-students to understand and learn more about how to prepare and submit work so that it supports academic integrity, and to avoid academic misconduct.

Discrimination/Harassment
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 student.conduct@senecapolytechnic.ca.

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 Accessibility Services Office at ext. 22900 to initiate the process for documenting, assessing and implementing your individual accommodation needs.

Camera Use and Recordings - Synchronous (Live) Classes
Synchronous (live) classes may be delivered in person, in a Flexible Learning space, or online through a Seneca web conferencing platform such as MS Teams or Zoom. Flexible Learning spaces are equipped with cameras, microphones, monitors and speakers that capture and stream instructor and student interactions, providing an in-person experience for students choosing to study online.

Students joining a live class online may be required to have a working camera in order to participate, or for certain activities (e.g. group work, assessments), and high-speed broadband access (e.g. Cable, DSL) is highly recommended. In the event students encounter circumstances that impact their ability to join the platform with their camera on, they should reach out to the professor to discuss. Live classes may be recorded and made available to students to support access to course content and promote student learning and success.

By attending live classes, students are consenting to the collection and use of their personal information for the purposes of administering the class and associated coursework. To learn more about Seneca's privacy practices, visit Privacy Notice.

• Canadian Business - 5%
  •         What is a Business?
  •         Types of businesses
  •         What is a business opportunity?
  •         What is a business problem
     
• The Systems Development Life Cycle - 5%
  •         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
     
• Capturing the Business Environment during the Requirements Gathering Process - 25%
  •         Defining the problem to be solved
  •         Identifying stakeholders
    •             Identifying the needs of the stakeholders
    •             Developing the features of the system to address those needs
  •         Identifying businesses processes and activities
  •         Identifying actors
  •         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 - 25%
  •         What is a Systems use case?
  •         Defining the scope of the system to be developed through systems use case diagrams
    •             Identifying Systems use cases
    •             Creating Systems use case diagrams showing associations with actors
  •         Identifying relationships
  •         Adding a Systems use case diagram to the software model
     
• Documenting the requirements in Project Initiation Documents - 10%
  •  Identifies the problem to be solved in a Problem Statement
  •  Identifies the Stakeholders and Users
  •  Identifies user needs
  •  Identifies the requirements that the new system will place on the operating system
  •  Identifies the features of the new system
  •  Discusses the moral, legal and ethical issues involved in developing the new system
  •  Forms the foundation for the contract between the client and the development team
     
• Capturing Requirements Using Systems Use Case Descriptions - 25%
  •         Systems use case description standards
  •         Adding Systems use case descriptions to a software model
  •         Writing scenarios
  •         Writing Casual Use Case Descriptions composed of multiple scenarios
     
• Walk-through - 5%
  •         Purpose of a Walk-through
  •         Walk-through standards
  •         Performing a requirements walk-through