BDA215 - Software Engineering and Project Management

Credit Points: 15 credit points

Workload: 48 hours

Prerequisite: N/A

Co-requisite: N/A

Aims & Objectives

This is a core unit out of a total of 24 units in the Bachelor of Data Analytics (BDA). This unit addresses the BDA course learning outcomes and complements other courses in related fields by developing students’ knowledge and skills in software engineering and project management. For further course information refer to: http://www.mit.edu.au/study-with-us/programs/Bachelor-DA. This unit is part of the AQF Level 7 (BDA) courses.

This unit provides an overview of the field of software engineering, with emphasis on key aspects of the system development lifecycle (SDLC), such as requirements engineering, analysis, design and testing.   The software engineering elements are further controlled by project management that include planning, monitoring, delivery and closure. 

The unit will introduce students to the most common concepts, processes, techniques, and theories essential in software development and project management, and analyse and discuss the common issues that software engineers and project managers often face and how to overcome them. 

This unit will cover the following topics:

  • Overview of software engineering and project management 
  • Software (System) development life cycles; requirement engineering, prototyping, implementation and quality assurance
  • Software specification and industry standards
  • Software design methodologies and ethics
  • Project management: planning, team management, budgeting, process control and closure.

Learning Outcomes

4.1 Course Learning Outcomes
The Course learning outcomes applicable to this unit are listed on the Melbourne Institute of Technology’s website: www.mit.edu.au 
4.2 Unit Learning Outcomes
At the completion of this unit students should be able to:
a. Comprehend the software (system) development life cycle and its relation to project management;
b. Analyse and select appropriate software engineering methodologies in consideration of business requirements and specifications
c. Apply appropriate software development methodologies including agile and incremental approaches in applications of requirement engineering, prototyping, validation, testing, and implementation;
d. Implement a software engineering solution following an appropriate project management methodology;
e. Investigate and communicate software engineering and project management solutions to industry clients in consideration of cultural differences and values.
 

Weekly Topics

This unit will cover the following content:

Week Topics
1 Overview of software engineering and project management
2 Software (System) development life cycles
3 Software requirements analysis and specification
4 Software specification and prototyping
5 Software design techniques
6 Software implementation and ethics standard in awareness of cultural differences and standards
7 Software quality assurance and risk management
8 Software delivery and maintenance
9 Project management: planning and scheduling
10 Project management: team development and management in consideration of cultural diversity and awareness
11 Project management: resource and budget planning
12 Project management: milestones and project closure

Assessment

Assessment Task Due Date A B Learning Outcomes Assessed
Formative Assignment 1 Part A
Assignment 1 Part B		 Week 3
Week 7		 5%
10%		   a-c
Assignment 2 Week 11 25%   d-e
Laboratory participation & submission Week 2 - 11 10%   a-e
Final Examination (2 hours) End of trimester   50% a-e
TOTALS   50% 50%  

Task Type: Type A: unsupervised, Type B: supervised.

Class Participation and Contribution
This unit has class participation and student contribution as an assessment. The assessment task and marking rubric will follow the Guidelines on Assessing Class Participation (https://www.mit.edu.au/about-us/governance/institute-rules-policies-and-plans/policies-procedures-and-guidelines/Guidelines_on_Assessing_Class_Participation). Further details will be provided in the assessment specification on the type of assessment tasks and the marking rubrics.

Presentations (if applicable)
For presentations conducted in class, students are required to wear business attire.

Textbook and Reference Materials

Textbook:

  • Kirill Dubovikov, Managing Data Science: Effective strategies to manage data science projects and build a sustainable team. Packt Publishing, 2019.

References:

  • I. Sommerville, Software Engineering 10th ed. Addison Wesley, Wokingham, England: 2015.
  • J. W. Satzinger, R. B. Jackson, and S. D. Burd, 7th ed. System Analysis and Design in a Changing World Cambridge. 2015.
  • K. E. Kendall and J. E.  Kendall, Systems Analysis and Design.  9th ed Pearson Education Inc. 2015.

Adopted Reference Style: IEEE

Students are required to purchase the prescribed text and have it available each week in the class.

Graduate Attributes

MIT is committed to ensure the course is current, practical and relevant so that graduates are “work ready” and equipped for life-long learning. In order to accomplish this, the MIT Graduate Attributes identify the required knowledge, skills and attributes that prepare students for the industry.
The level to which Graduate Attributes covered in this unit are as follows:

Ability to communicate Independent and Lifelong Learning Ethics Analytical and Problem Solving Cultural and Global Awareness Team work Specialist knowledge of a field of study

Legend

Levels of attainment Extent covered
The attribute is covered by theory and practice, and addressed by assessed activities in which the students always play an active role, e.g. workshops, lab submissions, assignments, demonstrations, tests, examinations.
The attribute is covered by theory or practice, and addressed by assessed activities in which the students mostly play an active role, e.g. discussions, reading, intepreting documents, tests, examinations.
The attribute is discussed in theory or practice; it is addressed by assessed activities in which the students may play an active role, e.g. lectures and discussions, reading, interpretation, workshops, presentations.
The attribute is presented as a side issue in theory or practice; it is not specifically assessed, but it is addressed by activities such as lectures or tutorials.
The attribute is not considered, there is no theory or practice or activities associated with this attribute.