Course Objectives
[1] Can explain the process of software-centric system development.
[2] Can explain the process of designing a system according to user requirements.
[3] Can explain the need for project management and its methods (WBS, PERT chart, etc.).
[4] Can explain the need for quality control using quantitative index values.
Rubric
| Ideal Level | Standard Level | Unacceptable Level |
Achievement 1 | Can fully explain the process of software-centric system development. | Can explain the process of software-centric system development. | Cannot explain the process of software-centric system development. |
Achievement 2 | Can fully explain the process of designing a system according to user requirements. | Can explain the process of designing a system according to user requirements. | Cannot explain the process of designing a system according to user requirements. |
Achievement 3 | Can fully explain the need for project management and its methods (WBS, PERT chart, etc.). | Can explain the need for project management and its methods (WBS, PERT chart, etc.). | Cannot explain the need for project management and its methods (WBS, PERT chart, etc.). |
| Can fully explain the need for quality control using quantitative index values. | Can explain the need for quality control using quantitative index values. | Cannot explain the need for quality control using quantitative index values. |
Assigned Department Objectives
Teaching Method
Outline:
The instructor who have been developing and researching software in a company will take advantage of their experience to teach in class. The basics of software development in theory will be taught using textbooks, also the actual developments at the field will be introduced.
Style:
Classes, exercises and the actual developments at the field
Notice:
As the members performing group work will be drawn randomly from students who had registered to the course, and it involves knowledge from the first and second semester, it is important to be careful not to miss classes as well as the days of group work.
Students who miss 1/3 or more of classes will not be eligible for a passing grade.
Characteristics of Class / Division in Learning
Course Plan
|
|
|
Theme |
Goals |
1st Semester |
1st Quarter |
1st |
The nature and development of software |
Can raise at least one aspect of software development and its challenges and give reason.
|
2nd |
Software development process |
Can list several development process models and their characteristics.
|
3rd |
Request Analysis |
Can talk about the relationship and usefulness of demand analysis and prototyping.
|
4th |
Software design |
Can talk about the dependencies between modules with low and high module binding, and can provides examples of low module binding.
|
5th |
Programming and testing |
Can talk about programming techniques to prevent error contamination and techniques to improve test efficiency.
|
6th |
Testing and Maintenance |
Can come up with measures to ensure maintainability and explain them.
|
7th |
Group work |
Engage in group work assignment related to the content taught in week 6 of the first half of the semester.
|
8th |
Midterm exam
|
Check understanding of the content from first half of the semester.
|
2nd Quarter |
9th |
Object orientation 1 |
Can explain things around me using the expressions class and instance.
|
10th |
Object orientation 2 |
Can talk about the characteristics of object-oriented programming.
|
11th |
Software reuse |
Can talk about the importance and difficulty of software reuse.
|
12th |
Project Management |
Can state the importance of project management.
|
13th |
Quality control |
Can talk about quality control techniques.
|
14th |
Development size and estimate of software |
Can talk about the method for estimating the size of software development.
|
15th |
Group work |
Engage in group work assignment related to the content taught in week 6 of the second half of the semester.
|
16th |
Final exam
|
Check understanding of the content from second half of the semester.
|
Evaluation Method and Weight (%)
| Examination | Groupwork | Mutual Evaluations between students | Behavior | Portfolio | Other | Total |
Subtotal | 60 | 20 | 0 | 0 | 20 | 0 | 100 |
Basic Proficiency | 0 | 0 | 0 | 0 | 0 | 0 | 0 |
Specialized Proficiency | 60 | 20 | 0 | 0 | 20 | 0 | 100 |
Cross Area Proficiency | 0 | 0 | 0 | 0 | 0 | 0 | 0 |