COMP 1712
Business Analysis and System Design
| School | School of Computing and Academic Studies |
|---|---|
| Program | Computer Systems Technology (CST) Diploma |
| Course Credits | 4 |
| Minimum Passing Grade | 50% |
| Start Date | January 06, 2020 |
| End Date | April 17, 2020 |
| Total Hours* | 60 |
| Total Weeks | 15 |
| Hours/Weeks | 4 |
| Delivery Type | Lecture |
| CRN | 86105 |
Acknowledgement of Territories
The British Columbia Institute of Technology acknowledges that our campuses are located on the unceded traditional territories of the Coast Salish Nations of Sḵwx̱wú7mesh (Squamish), səl̓ilwətaɁɬ (Tsleil-Waututh), and xwməθkwəy̓əm (Musqueam).
Instructor Details
| Name | Maryam Khezrzadeh |
|---|---|
| mkhezrzadeh@bcit.ca | |
| Location | SW2 - 363 |
| Office Hours |
|
Course Description
Business Analysis and Systems Design is the study of concepts, processes and tools that professionals use to plan and develop information systems to industry standards. Students learn how to ask implicit questions, to create and document communication plans and to make better decisions prior to creating a software system. Beginning with an introduction to the Software Development Life Cycle (SDLC), students work in teams to initiate the system process, analyze problems, discover requirements and create a logical design. Topics include: techniques used in the discovery of business requirements, traditional approaches to data and process modelling, entity-relationship diagrams, and an introduction to relational database normalization. Agile life cycles such as Scrum are also introduced and compared to more planned life cycles such as waterfall. By the end of this course, successful participants will be able to use tools and methods commonly used in industry to analyze, design, and implement information systems as confirmed by a term project.
Course Learning Outcomes/Competencies
Upon successful completion of this course, the student will be able to:
- Explain and use the various phases and organizations of the SDLC including agile and planned life cycles.
- Describe the factors indicating whether agile or planned life cycles are appropriate for a given project and use these factors to evaluate a case study
- Perform system requirements capture and analysis.
- Read, interpret and develop models that can be used to document requirements capture, analysis, design, implementation and test for a software/systems project.
- Construct a cost benefit analysis to determine the feasibility of a software/systems project.
- Develop a software architecture.
- Describe implementation and support activities.
- Identify appropriate formats for system documentation.
- Create a logical data design using ER diagrams (or equivalent)
- Create a normalized relational database schema..
Learning Resources
Systems Analysis and Design, Eleventh Edition or Tenth Edition, Scott Tilley and Harry J.Rosenblatt (Shelley Cashman Series)
Course Goals
- Desiging an information systems for an enterprise
- To understand the changing landscape of business analysis
- To apply industry standard tools and methods.
- To work with groups of people to gather and communicate detailed requirements for the design of information systems.
Evaluation Criteria
| Criteria | % | Comments |
| Lab submissions | 25 | Every week |
| Mid term Exam | 25 | |
| Assignments | 20 | 2 assignments per term |
| Final Exam | 30 |
Attendance Requirements
Regular attendance in lectures, seminars, and labs is seen as critical to student success, and may be monitored by faculty.
Unapproved absence of 2 or more classes may result in failure or forced withdrawal from the course or program.
Please see Policy 5101 - Student Regulations: https://www.bcit.ca/files/pdf/policies/5101.pdf
Course Specific Requirements
Ethics & Professionalism:
This course expects high degree of professionalism in ethical behavior in the class room. Incidents such as cheating, plagiarism may result in zero grading or expulsion from the course.
Course Outline: Course outline and materials may be changed by the instructors at any point of time during the course according to the knowledge level of the students.
Computer use Policy: BCIT has an Institute-wide policy (#3501) pertaining to information technology and services and to the resources available in support of the Institute mission. Computer Systems Technology students are expected to exercise the highest degree of professionalism and ethical behaviour related to information technology. Violations of BCIT Policy #3501 will result in disciplinary action which may include suspension or expulsion of students. Also refer to the Computer Systems Technology Student Conduct Guidelines.
Lab submission: Lab attendance is mandatory. Lab exercises due varied according to the intensity level of the exercises. Please follow the instructors advise strictly. By default, the submission is due at the end of the lab period.
Group Project: Students are advised to contribute equally. Students will be given peer review form. Professional etiquette expected.
Absence in Exams, Quiz or Tests: If the students miss the exams, quizzes, assignments or tests they will receive zero marks. Medical conditions will be considered as exception cases.
Late submission: Late submissions will not be accepted.
Mid-term, Final Exam, Group Project: Exam papers will not be returned to the students.
Course Schedule and Assignments
|
Week # |
Week of |
Topics covered |
Readings |
|
Week 1 |
Jan. 6 |
Introduction to Systems Analysis and Design |
Chapter 1 |
|
Week 2 |
Jan. 13 |
Analyzing the Business Case |
Chapter 2 |
|
Week 3 |
Jan. 20 |
Managing Systems Projects |
Chapter 3 |
|
Week 4 |
Jan. 27 |
Requirements Modelling |
Chapter 4 |
|
Week 5 |
Feb. 3 |
Data and Process Modelling |
Chapter 5 |
|
Week 6 |
Feb. 10 |
Object Modelling |
Chapter 6 |
|
Week 7 |
Feb. 17 |
Midterm Exam (Chapter 1 to 6 ) |
|
|
Week 8 |
Feb. 24 |
Development Strategies |
Chapter 7 |
|
Week 9 |
Mar. 2 |
Agile software Development |
Handout on Learning Hub |
|
Week 10 |
Mar. 9 |
Spring Break |
|
|
Week 11 |
Mar. 16 |
- User interface design - System architecture |
Chapters 8 and 10 |
|
Week 12 |
Mar. 23 |
Data design |
Chapter 9 |
|
Week 13 |
Mar. 30 |
Managing system implementation |
Chapter 11 |
|
Week 14 |
Apr. 6 |
Managing system support and security |
Chapter 12 |
|
Week 15 |
Apr. 13 |
Final Exam (Chapters 8 to 12 and Agile) |
|
BCIT Policy
The following statements are in accordance with the BCIT Policies 5101, 5102, 5104, and 7507, and their accompanying procedures. To review these policies and procedures please click on the links below.
Attendance/Illness:
In case of illness or other unavoidable cause of absence, the student must communicate as soon as possible with his/her instructor or Program Head or Chief Instructor, indicating the reason for the absence. Students who are seeking accommodation for a medical absence must have a BCIT approved medical certificate submitted to the department, substantiating the reason for absence. For other absences, the student should be prepared to provide appropriate supporting documentation. Unapproved absence in excess of the prescribed regulations within this outline may result in failure or forced withdrawal from the course or program. Please see Policy 5101 - Student Regulations, and accompanying procedures.
Academic Integrity:
Violation of academic integrity, including plagiarism, dishonesty in assignments, examinations, or other academic performances are prohibited and will be handled in accordance with Policy 5104 - Academic Integrity and Appeals, and accompanying procedures.
Accommodation:
Any student who may require accommodation from BCIT because of a physical or mental disability should refer to BCIT's Policy on Accommodation for Students with Disabilities (Policy #4501), and contact BCIT's Accessibility Services (SW1 2360, 604-451-6963) at the earliest possible time. Requests for accommodation must be made to Accessibility Services, and should not be made to a course instructor or Program area.
Any student who needs special assistance in the event of a medical emergency or building evacuation (either because of a disability or for any other reason) should promptly inform their course instructor(s) and Accessibility Services of their personal circumstances.
Human Rights, Harassment and Discrimination:
The BCIT community is made up of individuals from every ability, background, experience and identity, each contributing uniquely to the richness and diversity of the BCIT community as a whole. In recognition of this, and the intrinsic value of our diversity, BCIT seeks to foster a climate of collaboration, understanding and mutual respect between all members of the community and ensure an inclusive accessible working and learning environment where everyone can succeed.
Campus Mediation Services is a supportive resource for both students and employees of BCIT, to foster a respectful learning and working environment. Any student who feels that they are experiencing discrimination or harassment (personal or human rights-related) can confidentially access this resource for advice and support. Please see Policy 7507 – Harassment and Discrimination and accompanying procedure.
Students should make themselves aware of additional Education, Administration, Safety and other BCIT policies listed at https://www.bcit.ca/about/administration/policies.shtml
Guidelines for School of Computing and Academic Studies
Attempts:
Students must successfully complete a course within a maximum of three (3) attempts at the course. Students with two attempts in a single course will be allowed to repeat the course only upon special written permission from the Associate Dean. Students who have not successfully completed a course within three attempts will not be eligible to graduate from their respective program.
Approved
I verify that the content of this course outline is current.
Maryam Khezrzadeh, Instructor
December 17, 2019
I verify that this course outline has been reviewed.
D'Arcy Smith, Program Head
January 05, 2020
I verify that this course outline has been reviewed and complies with BCIT policy.
Mike Starkey, Associate Dean
January 05, 2020
Note: Students will be given reasonable notice if changes are required to the content of this course outline.
*Course hours and credits are calculated per Policy 5012 and the associated procedure.
Total hours – Example of 3 credit lecture/lab course:
- Full-time course: 45 hours of scheduled learning
- Flexible Learning course: 36 hours of scheduled learning plus 9 hours of independent (non-scheduled, non-instructional) learning