CS315/IT275 – MAJOR PROJECT/PRACTICUM

COURSE SYLLABUS

I. COURSE OVERVIEW

A. Course Number : CS315/IT275

B. Course Title : Major Project/Practicum
C. No. of Units : 3 Units
D. Semester Offered : 2nd Semester
E. Lecturer : Oneil B. Victoriano
F. Consultation Hours :
G. Course Description

The SAD and Summer Practicum Program are part of the Systems track which
all BSCS/BSIT/BSIM students have to undergo during the 2nd semester and
the summer term of their third year. Students will be assigned to local
companies for them to be exposed to the actual system environment. They are
expected to be involved in developing a major system project, from planning,
analysis, design, until its final implementation. The course aims to put into
practice their knowledge and skills in systems development and programming.

H. Linkage with Subsequent Courses

This course is not a prerequisite to any of the major subjects of the

BSCS/BSIT/BSIM program.

I. Values to be integrated

This course aims to develop the critical thinking skills of the students as they
try to portray the role of a systems analyst. They are expected to become good
development planners equipped with the proper knowledge and values as
they try to formulate humane decisions and solutions to real-world issues.

J. Textbook and References

1. Gary Shelly, Thomas Cashman, Harry Rosenblatt, Systems Analysis and Design,
Course Technology, 2010
2. Roger Pressman, Software Engineering A Practitioner’s Approach, McGraw Hill,
2010
3. John Satzinger, Robert Jackson, Stephen Burd Systems Analysis and Design in a
Changing World, Course Technology, 2010
4. Kenneth Kendal and Julie Kendall, Systems Analysis and Design, Prentice Hall,
2009
5. Jeffrey Hoffer, Joey George, Joseph Valacich, Modern Systems Analysis and
Design, Prentice Hall, 2010

Page 1 of 8
COURSE OUTLINE

1. Output and User Interface Design

1.1. Output Design
1.2. Printed and Screen Output
1.3. User Interface Design
1.4. Input Design

2. System Architecture
2.1. System Architecture Checklist
2.2. Planning the Architecture
2.3. Client/Server Architecture
2.4. Internet-Based Architecture
2.5. Processing Methods
2.6. Network Models

3. Systems Implementation
3.1. Software Quality Assurance
3.2. Application Development
3.3. Coding
3.4. Testing the System
3.5. Documentation
3.6. Management Approval
3.7. System Installation and Evaluation
3.8. Operational and Test Environments
3.9. Training
3.10. Data Conversion
3.11. System Changeover
3.12. Post-implementation Tasks

4. Software Process and Project Metrics

4.1. Measures, Metrics, and Indicators
4.2. Metrics in the Process and Project Domains
4.3. Software Measurement
4.4. Reconciling Different Metrics Approaches
4.5. Metrics for Software Quality
4.6. Integrating Metrics within the Software Process

5. Software Quality Assurance

5.1. Quality Concepts
5.2. The Quality Movement
5.3. Software Quality Assurance
5.4. Software Reviews
5.5. Formal Technical Reviews
5.6. Formal Approaches to SQA
5.7. Statistical Software Quality Assurance
5.8. Software Reliability

Page 2 of 8
6. Software Testing Techniques
6.1. Software Testing Fundamentals
6.2. Test Case Design
6.3. White-Box Testing
6.4. Basis Path Testing
6.5. Black-Box Testing
6.5.1. Graph-Based Testing Methods
6.5.2. Equivalence Partitioning
6.5.3. Boundary Value Analysis
6.5.4. Comparison Testing
6.6. Testing for Specialized Environments, Architectures, and Applications

7. Software Testing Strategies

7.1. A Strategic Approach to Software Testing
7.2. Strategic Issues
7.3. Unit Testing
7.4. Integration Testing
7.5. Validation Testing
7.6. System Testing

8. Systems Operations, Support, and Security

8.1. Overview of Systems Support and Maintenance
8.2. User Support Activities
8.3. Maintenance Activities
8.4. Managing Systems Operation and Support
8.5. Managing System Performance
8.6. System Obsolescence
8.7. Facing the Future: Challenges and Opportunities
8.8. Strategic Planning for IT professionals

Page 3 of 8
II. COURSE SYLLABUS

LECTURE

ACTIVITIES/
WEEK # TOPIC(S) LEARNING OBJECTIVES
APPROACHES
– Learn about relevant information about the course such as the course
Orientation description, objectives, textbooks/references that will be used as well as
1 course requirements, the grading system and some specific classroom  LECTURE
policies
– Set Schedules
– Analysis to Design (DFDs to Modules or Structured Charts)
–
– Explain the importance of software quality assurance and software
engineering
 LECTURE
Analysis to Design, & – Describe the application development process
2  STRUCTURED
Systems Implementation – Draw a structure chart showing top-down design, modular design,
CHARTS DEADLINE
cohesion, and coupling
– Explain the coding process and how code is generated
–
– Validation Criteria
– Main Menu
– Input/Transaction Screens  LECTURE TYPE
Output and User Interface
3 – Output Screens STUDENTS
Design
– Printed Output REPORTING
– Message/Prompt Screens
 LECTURE TYPE
4 System Architecture – Entire chapter 8 STUDENTS
REPORTING
– Explain unit testing, integration testing, and system testing
– Differentiate between program, system, operations, and user
documentation
– List the main steps in system installation and evaluation
– Develop an overall training plan with specific objectives for each group of  LECTURE TYPE
5 Systems Implementation participants, compare in-house and outside training providers, and describe STUDENTS
effective training techniques REPORTING
– Describe the data conversion process
– Identify and describe changeover methods
– Explain post-implementation evaluation
– Describe the final report to management

Page 4 of 8
 – Define basic terms like Measures, Metrics, and Indicators
– To be able to collect measures and convert into metrics for process
improvement
– Differentiate direct and indirect measures  LECTURE
Software Process and
6 – Discuss Size-Oriented and Function-Oriented Metrics  SEATWORK
Project Metrics
– To be able to reconcile different Metrics approaches  QUIZ #1
– Apply effective methods coupled with modern tools within the context of a
mature software process
– Integrate Metrics within the software process
– Learn on fundamentals in Software Testing which includes Testing
Objectives and Principles
– Discuss fundamentals on Test Case Design
– Differentiate White and Black-Box Testing
– Create Test Case using Basis path testing  LECTURE
Software Testing
7 – Create Test Case using Graph-Based testing  SEATWORK
Techniques
– Create Test Case using Equivalence Partitioning  QUIZ #3
– Create Test Case using Boundary Value Analysis
– Create Test Case using Comparison testing
– Learn different testing approaches for Specialized Environments,
Architectures, and Applications
– Explain how the systems operation and support phase relates to the rest of
the system development process
– Describe user support activities, including user training and help desks
– Discuss the four main types of system maintenance: corrective, adaptive,
perfective, and preventive
– Explain techniques for managing systems operation and support, including  LECTURE
Systems Operation,
8 maintenance teams, maintenance request procedures, configuration  SEATWORK
Support, and Security
management, maintenance releases, version control, and baselines  QUIZ #4
– Describe techniques for managing system performance, including
performance and workload measurement, and capacity planning
– List factors indicating that a system has reached the end of its useful life
– Assess future challenges and opportunities that IT professionals will face as
technology continues to reshape the workplace

9 FINAL EXAM

LABORATORY

WEEK # TOPIC(S) LEARNING OBJECTIVES ACTIVITIES/ APPROACHES

Page 5 of 8
 – Learn to apply software application development using
1-5 visual programming software, web development tools  RAPID APPLICATION DEVELOPMENT
and DBMS

6 FINAL DEFENSE SCHEDULE

Page 6 of 8
III. COURSE POLICIES

A. Class Policies
 An appointed class beadle will check the attendance of the students in
every session. As stipulated in the handbook, the students are only
allowed to commit 10 absences (17 absences for a laboratory class). There
will be no excused absences. The excuse letter will only be regarded for
the purposes of granting make-up exams and activities. For more
information, please refer to the General School Policy regarding attendance
in the Student Handbook.
 All cellular phones must be put in silent mode for the duration of the
class, whether inside the classroom or laboratory. Anybody caught
violating this rule for three times will be given a penalty, which depends
on the circumstances of the offense.
 Candies are the only food allowed inside the classroom and laboratory
areas.
 No one is allowed to go out of the classroom during the class period.
Anybody who violated this rule without proper permission from the
teacher will also be given a penalty.

B. Course Requirements

 Take quizzes and long quizzes

 Pass papers and assignment
 Deliver reports/lecture presentation
 Complete Milestone Defense (Database Design and User Interface
Design)
 Accomplish Validation Criteria Walkthrough
 Major Project Defense

C. Grading System

Prelims and Midterms

 20% Quizzes/Papers/Assignments/Reporting
 30% Long Quizzes/Major Exam
 50% Milestone Defense (Database Design or User Interface Design)

Pre-Finals

 70% Major Project Defense (Panel/Adviser/Peer Evaluation Grades)

 30% Projects (Documentation/Assignments/Papers/Short Quizzes)

D. Special Arrangements

Page 7 of 8
 Make-up Examinations and Laboratory Activities may be granted to students
who missed them provided that the reasons are valid and documents are
shown to support them.

E. Software Used

 Microsoft Word/PowerPoint/Excel 2003

 Microsoft Project 2003
 Microsoft Visio 2003
 Microsoft Visual Studio .Net or any Visual programming application
 Microsoft Access 2003
 Sequel Server 2003
 MySQL other DBMS software available

Page 8 of 8