140 likes | 160 Views
Course Introduction Software Engineering. Yonsei University 2 nd Semester, 2013 Sanghyun Park. Course Goals (1/2). Software systems are ubiquitous Even simple software systems have a high inherent complexity
E N D
Course IntroductionSoftware Engineering Yonsei University 2nd Semester, 2013 Sanghyun Park
Course Goals (1/2) • Software systems are ubiquitous • Even simple software systems have a high inherent complexity • Software engineering is an engineering disciplinewhose goal is the cost-effective development of software systems
Course Goals (2/2) • This course introducesconcepts, theories, tools, and methodsfor the specification, development, management, and evolution of software systemsin the perspective of software engineering
Prerequisite • Basic computer science background • Programming skill (C, C++, Java, …) • Data structure • Willing to cooperate as a team member
Web Site • http://embio.yonsei.ac.kr/course/67 (class homepage) • Syllabus, announcements, lecture notes, homework, solutions, useful links, etc • http://www.pearsonhighered.com/sommerville/(publisher’s web site)
Textbook • Software Engineering, 9th Edition,Ian Sommerville, Pearson, 2010
Grades • 30% midterm exam • 30% final exam • 30% project • 10% attendance and class participation • ‘F’ will be given if absent more than 1/3
Class Schedule • Week 1 Introduction to the course, Introduction to software engineering • Week 2 Project management and planning, Software processes • Week 3 Software processes (Agile software development) • Week 4 Requirement engineering • Week 5 System modeling • Week 6 Architectural design • Week 7 Design and implementation • Week 8 Midterm exam
Class Schedule • Week 9 Design and implementation • Week 10 Software testing • Week 11 Software evolution • Week 12 Special topics • Week 13 Project presentation • Week 14 Project presentation • Week 15 Project presentation • Week 16 Final exam
Project • One team with 4 members • More than 4 members if project is large (maximum 5) • Less than 4 members if project is small (minimum 3)
Project Schedule (1/2) • End of 3rd weekOne page document which describes team members and project topic • End of 5th weekDocument for requirement analysis • End of 9th weekDesign document • End of 12th weekCompletely working source code and test plan with test cases
Project Schedule (2/2) • End of 15th weekUser manuals,one-click installable source code,and test cases Submit required materials to TA by 10 pm of due date Late penalty: 10% each day
TA Information • Name: 정다예 • Office: C533-1 (2123-7757) • Email: tethys6264@gmail.com