MSc:ManagingSoftwareDevelopment old old
Revision as of 14:59, 30 July 2021 by 10.90.136.11 (talk) (Created page with "= OLD OLD Managing Software Development = * <span>'''Course name:'''</span> Managing Software Development * <span>'''Course number:'''</span> SE-04 * <span>'''Area of instruc...")
OLD OLD Managing Software Development
- Course name: Managing Software Development
- Course number: SE-04
- Area of instruction: Computer Science and Engineering
Administrative details
- Faculty: Computer Science and Engineering
- Year of instruction: 1st year of MSc
- Semester of instruction: 1st semester
- No. of Credits: 5 ECTS
- Total workload on average: 180 hours overall
- Frontal lecture hours: 2 hours per week.
- Frontal tutorial hours: 0 hours per week.
- Lab hours: 2 hours per week.
- Individual lab hours: 2 hours per week.
- Frequency: weekly throughout the semester.
- Grading mode: letters: A, B, C, D.
Course outline
Large scale software development requires the ability to manage resources - both human and computational - through control of the development process. This course is a breadth oriented course, designed to help technically-trained software engineers to acquire the knowledge and skills necessary to lead a project team, understand the relationship of software development to overall project engineering, estimate time and costs, and understand the software process. The nature of software development is sufficiently unique to require specialized management techniques, especially in the areas of the estimating and scheduling.
Expected learning outcomes
- Methods to understand, manage and - as much as possible! - control the software development process
- Best practices for managing software development processes, including their current state and their evolution
- From past successes and failures, and how to learn from future ones
- Effective approaches to make decisions with software projects
Required background knowledge
None
Prerequisite courses
None
Detailed topics covered in the course
- MSD Introduction
- OBU Case Introduction
- Managing Technical People
- Team formation, Decision Making and Conflict Resolution
- Managing Customer Expectations
- MCE Case discussion
- Defining and measuring processes
- CASE Exercise Discussion Study
- Software Development Lifecycles
- Process Frameworks and How to choose
- Requirements Management
- CASE Exercise Discussion
- Requirements case study/lecture
- Identifying and Managing Software Risk
- TBQ, Threshold of Success
- Risk Statement Discussion
- Introduction - Planning & Controlling Software Development Projects
- Risk
- Work Breakdown Structures
- Estimation Methods
- Activity Planning
- Milestone Planning
- Release Planning
- Tracking Reporting & Controlling
- Strategic Planning with Architecture - Architecture as a Strategic Asset
Textbook
Reference material
- This course makes use of many reference materials that are posted to Moodle.
Required computer resources
None
Evaluation
- Project (50%)
- Case Studies (30%)
- Questions on Readings (10%)
- Participation (10%)