CMSC 128 Introduction to Software Engineering

Second Semester 2009-2010

Quick Links: [ Lecture ] [ Laboratory ][ Resources ][ Class Record ][ Projects ]

News/Announcements

[02/25/10] On March 1, 2010, make sure that you have released a pre-alpha version of your project in .tar.gz or .zip format. Make this available at the Downloads tab of your project. Include an INSTALL file that contains a detailed description on how users will install and configure your project (software dependencies, database, IDE, etc).
[02/18/10] Please find time to read this article.
[02/18/10] Second Exam will cover L6-L10. Bring blue book.
[02/02/10] Include in your google project page links to Gantt chart, estimation, use case, activity diagrams, and M-V-C design. Also check the Evaluation section of this page for the templates of the required documents.
[01/20/10] Perform effort, duration, and cost estimation for your project using the sample spreadsheet. Submit a printed copy of the spreadsheet next meeting.
[01/05/10] Bring blue books tomorrow.
[12/18/09] Merry Christmas and a Happy New Year!
[12/12/09] Class Record is now up.
[12/10/09] A word of warning to those who leave early from class: If you get caught, you get a grade of 5.
[12/09/09] Please read Why did your project fail?(hardcopy available from lecturer). Prepare for a quiz.
[11/17/09] Please read You Don't Know Jack About Software Maintenance. Prepare for a quiz.
[11/09/09] Welcome!

Course Information

Course Number: CMSC 128
Course Title: Introduction to Software Engineering
Description: Principles and methods for the design, implementation, validation, evaluation and maintenance of software systems.
Prerequisites(Official): CMSC 123 or COI
Prerequisites(Recommended): CMSC 100 and CMSC 127
Lecture: Section AB, 8-9 WF ICS LH1

Instructor Information

Lecture:
Joseph Anthony C. Hermocilla (jachermocilla@gmail.com)
PhySci C120

Laboratory:
Michael B. Pascua (mbpascua@uplb.edu.ph)
PhySci C115

Rommel V. Bulalacao (rvbulalacao@uplb.edu.ph)
PhySci C115

Student Assistant:
Girlie Gonzales(girliegonzales@gmail.com)

Aim

This course will give students an initial "feel" of their future work in the industry as software engineers. The course will put special emphasis to software development project management, object-oriented development, and web applications development.

Objectives

At the end of this course the students should be able to:

Discuss the process for developing large software;
Analyze and model a particular system;
Develop alternative solutions for the system; and
Implement, test and validate a systems design.

Topics

The Product
The Process
Project Management Concepts
Software Process and Project Metrics
Software Project Planning
Risk Analysis and Management
Project Scheduling and Tracking
Software Quality Assurance
Software Configuration Management
System Engineering
Analysis Concepts and Principles
Analysis Modeling
Design Concepts and Principles
Architectural Design
User Interface Design
Component-Level Design
Software Testing Techniques
Software Testing Strategies
Technical Metrics for Software
Object-Oriented Concepts and Principles
Object-Oriented Analysis
Object-Oriented Design
Object-Oriented Testing
Technical Metrics for Object-Oriented Systems

Evaluation/Grading(tentative)

Lecture (50%)

3 Long Exams 45%

Quizzes/Homework/Reporting 5%

Laboratory (50%)

Project Plan Document (template) 5%

Software Requirements Specification Document (template) 5%

Software Design Specification Document (template) 5%

QA, Test Cases, and Results (QA template,Testing template) 5%

User's Manual (template) 5%

Final Software Product 15%

Client Evaluation 5%

Exercises/Activities 5%

Pre-Final Grade 100%

Final Grade = 80*(Pre-Final Grade) + 20*(Final Exam). The student should pass both the lecture and the laboratory to pass the course.

Lecture Schedule (tentative)

All slides are available here

Lec Date Topic Readings Slides/Audio

1 11/11/09 W Introduction PDF

2 11/13/09 F The Product: Industry Perspective PDF

3 11/18/09 W The Product: Software Applications

4 11/20/09 F The Process: Layered Technology PDF

5 11/25/09 W The Process: CMM Levels

6 11/27/09 F Rapid Application Development Model

7 12/02/09 W Invited Lecture: An Introduction to the Scrum Methodology(Ms. Ria Mae G. Corda) PDF

8 12/04/09 F The Process: Product and Process

9 12/09/09 W Project Management: Coordination and Communication Techniques PDF

10 12/11/09 F Project Management: The Process

11 12/16/09 W Software Process and Project Metrics: Fishbone Diagram PDF

12 12/18/09 F (no class)

* 12/19/09 S CHRISTMAS VACATION

13 01/06/10 W FIRST EXAM

14 01/08/10 F Software Project and Project Metrics: Project Metrics

15 01/13/10 W Project Planning: Estimation using Process Decomposition PDF,estimation

16 01/15/10 F Project Scheduling and Tracking: Task Networks PDF

17 01/20/10 W Project Scheduling and Tracking: Work Breakdown Structure

18 01/22/10 F Software Configuration Management PDF

19 01/27/10 W Software Configuration Management

20 01/29/10 F Requirements Analysis PDF

21 02/03/10 W Structured Analysis PDF

22 02/05/10 F Object Oriented Concepts PDF

23 02/10/10 W Design Concepts and Principles: Abstraction PDF

24 02/12/10 F Design Concepts and Principles: Cohesion

25 02/17/10 W Design Concepts and Principles: Heuristics for Modularity

26 02/19/10 F SECOND EXAM

27 02/24/10 W (no meeting)

28 02/26/10 F Object-Oriented Analysis: CRC Cards PDF

29 03/03/10 W Object-Oriented Analysis

30 03/05/10 F Software Testing Techniques (Mr. Rommel Bulalacao) PDF

31 03/10/10 W Software Testing: Graph-based Testing

32 03/12/10 F

33 03/17/10 W

34 03/19/10 F THIRD EXAM

* 03/20/10 S END OF CLASSES

Laboratory Schedule (tentative)

Week Date Topic Readings/Exercise

1 11/09/09-11/13/09

2 11/16/09-11/20/09

3 11/23/09-11/27/09

4 11/20/09-12/04/09

5 12/07/09-12/11/09

6 12/14/09-12/18/09

7 01/04/10-01/08/10

8 01/11/10-01/14/10

9 01/18/10-01/22/10

10 01/25/10-01/29/10

11 02/01/10-02/05/10

12 02/08/10-02/12/10

13 02/15/10-02/19/10

14 02/22/10-02/26/10

15 03/01/10-03/05/10

16 03/08/10-03/12/10

17 03/15/10-03/18/10

Resources

Textbook: Roger S. Pressman.Software Engineering: A Practitioner's Approach, 4th Ed..McGraw-Hill,1997.
Supplementary Text and References

Carlo Ghezzi, et al.Software Engineering, 2nd Ed..Pearson Education Inc.,2003.
Erich Gamma et al.Design Patterns: Elements of Reusable Object-Oriented Software.Addison-Wesley,1995.
Frederick P. Brooks, Jr.The Mythical Man-Month.Addison-Wesley,1995.
Ian Sommervile.Software Engineering, 6th Ed..Pearson Education Ltd.,2001.
Stephen R. Schach.Classical and Object-Oriented Software Engineering, 4th Ed..McGraw-Hill,1999.

Relevant Links to other OS courses

Software

Class Policies

(TBA)

Grading Programming Exercises

0 did not submit; no email received; student cheated

1 email received; no attachment found; did not follow submission guidelines

3 program does not compile due to syntax errors;missing files

5 program has sufficient code, builds, but has wrong results when run

7 program has sufficient code, builds, fails on some test case or lacks documentation;

10 program has sufficient code, builds, correct results on all test cases

[Home][Teaching]

$Id: CMSC128-2nd-Sem-2009.html 1560 2010-03-10 05:25:13Z jachermocilla $

Lecture (50%)
	3 Long Exams	45%
	Quizzes/Homework/Reporting	5%
Laboratory (50%)
	Project Plan Document (template)	5%
	Software Requirements Specification Document (template)	5%
	Software Design Specification Document (template)	5%
	QA, Test Cases, and Results (QA template,Testing template)	5%
	User's Manual (template)	5%
	Final Software Product	15%
	Client Evaluation	5%
	Exercises/Activities	5%
Pre-Final Grade		100%

Lec	Date	Topic	Readings	Slides/Audio
1	11/11/09 W	Introduction		PDF
2	11/13/09 F	The Product: Industry Perspective		PDF
3	11/18/09 W	The Product: Software Applications
4	11/20/09 F	The Process: Layered Technology		PDF
5	11/25/09 W	The Process: CMM Levels
6	11/27/09 F	Rapid Application Development Model
7	12/02/09 W	Invited Lecture: An Introduction to the Scrum Methodology(Ms. Ria Mae G. Corda)		PDF
8	12/04/09 F	The Process: Product and Process
9	12/09/09 W	Project Management: Coordination and Communication Techniques		PDF
10	12/11/09 F	Project Management: The Process
11	12/16/09 W	Software Process and Project Metrics: Fishbone Diagram		PDF
12	12/18/09 F	(no class)
*	12/19/09 S	CHRISTMAS VACATION
13	01/06/10 W	FIRST EXAM
14	01/08/10 F	Software Project and Project Metrics: Project Metrics
15	01/13/10 W	Project Planning: Estimation using Process Decomposition		PDF,estimation
16	01/15/10 F	Project Scheduling and Tracking: Task Networks		PDF
17	01/20/10 W	Project Scheduling and Tracking: Work Breakdown Structure
18	01/22/10 F	Software Configuration Management		PDF
19	01/27/10 W	Software Configuration Management
20	01/29/10 F	Requirements Analysis		PDF
21	02/03/10 W	Structured Analysis		PDF
22	02/05/10 F	Object Oriented Concepts		PDF
23	02/10/10 W	Design Concepts and Principles: Abstraction		PDF
24	02/12/10 F	Design Concepts and Principles: Cohesion
25	02/17/10 W	Design Concepts and Principles: Heuristics for Modularity
26	02/19/10 F	SECOND EXAM
27	02/24/10 W	(no meeting)
28	02/26/10 F	Object-Oriented Analysis: CRC Cards		PDF
29	03/03/10 W	Object-Oriented Analysis
30	03/05/10 F	Software Testing Techniques (Mr. Rommel Bulalacao)		PDF
31	03/10/10 W	Software Testing: Graph-based Testing
32	03/12/10 F
33	03/17/10 W
34	03/19/10 F	THIRD EXAM
*	03/20/10 S	END OF CLASSES

Week	Date	Topic	Readings/Exercise
1	11/09/09-11/13/09
2	11/16/09-11/20/09
3	11/23/09-11/27/09
4	11/20/09-12/04/09
5	12/07/09-12/11/09
6	12/14/09-12/18/09
7	01/04/10-01/08/10
8	01/11/10-01/14/10
9	01/18/10-01/22/10
10	01/25/10-01/29/10
11	02/01/10-02/05/10
12	02/08/10-02/12/10
13	02/15/10-02/19/10
14	02/22/10-02/26/10
15	03/01/10-03/05/10
16	03/08/10-03/12/10
17	03/15/10-03/18/10

0	did not submit; no email received; student cheated
1	email received; no attachment found; did not follow submission guidelines
3	program does not compile due to syntax errors;missing files
5	program has sufficient code, builds, but has wrong results when run
7	program has sufficient code, builds, fails on some test case or lacks documentation;
10	program has sufficient code, builds, correct results on all test cases