Software Engineering Project A

Unit Code:HIT3158

Credit Points	Duration	Contact Hours	Campus	Prerequisite	Corequisite
12.5 Credit Points	1 Semester or equivalent	48 Hours	Hawthorn, Sarawak	HIT2253 Data Structures and Algorithms or HIT3303 Data Structures and Patterns or HIT3172 Object-Oriented Programming in C++, and HIT2056 Software Project Management or HIT3309 Software Project Practices and Management. Must be followed immediately by HIT3258 Software Engineering Project B or HET553 Software Engineering and Robotics Project or HET435 Games & Interactivity Project 2	Nil

Credit Points

Duration

Contact Hours

Campus

Prerequisite

Corequisite

12.5 Credit Points

1 Semester or equivalent

48 Hours

Hawthorn, Sarawak

HIT2253 Data Structures and Algorithms or HIT3303 Data Structures and Patterns or HIT3172 Object-Oriented Programming in C++, and HIT2056 Software Project Management or HIT3309 Software Project Practices and Management. Must be followed immediately by HIT3258 Software Engineering Project B or HET553 Software Engineering and Robotics Project or HET435 Games & Interactivity Project 2

Nil

Related Course/s:

A unit of study in the Bachelor of Science (Computer Science), Bachelor of Science (Computer Science and Software Engineering), Bachelor of Engineering (Robotics and Mechatronics)/ Bachelor of Science (Computer Science and Software Engineering), Bachelor of Engineering (Telecommunication and Network Engineering)/ Bachelor of Science (Computer Science and Software Engineering)Bachelor of Multimedia (Games and Interactivity) / Bachelor of Science (Computer Science and Software Engineering) ( J070) and Bachelor of Engineering (Electronics and Computer Systems)/ Bachelor of Science (Computer Science and Software Engineering)

Aims & Objectives:

This is the first half of a capstone team project for the BSc(CSSE) and related degrees. Students develop a software system in a medium-size team (about 6 members) and apply the range of knowledge and skills gained throughout the course, especially in software engineering, programming, data communications, database and multi-user/multi-platform technologies.

Learning Outcomes
After successfully completing this unit, you should be able to:

Work effectively in at least two roles within a project team
Understand and address challenges in the management and coordination aspects of a project
Balance time, meet deadlines, maintain enthusiasm throughout two teaching periods
Demonstrate understanding of issues within the whole SDLC
Conduct meetings, prepare agendas and take minutes
Give technical presentations
Critically evaluate personal performance
Develop software within a development process
Interact with real clients especially with respect of discovering software requirements
Design software to solve problems in the area of the specific project
Write and debug programs in at least one computer language (depending on the specific project)
Design, build and evaluate appropriate user interfaces
Plan, specify and perform manual and automated tests of software
Write, review and maintain good quality technical documents according to relevant standards
Appreciate and describe techniques to control software quality
Perform and record document and code reviews
Systematically record and act upon bug reports and change requests
Appreciate the use of version control and use it effectively

Teaching Methods:

Lectures (24 hrs), regular contact with Supervisor and Project team Sessions (12 hrs) and a 2 day workshop in February.

Assessment:

Project Reports and participation. Pass/Fail only

Generic Skills Outcomes:

Students will be provided with feedback on progress in attaining the following generic skills:
· teamwork skills,
· analysis skills,
· problem solving skills,
· communications skills,
· ability to tackle unfamiliar problems, and
· ability to work independently

Content:

Communication skills in dealing with clients and colleagues
(Object Oriented) Analysis and requirements gathering
(Object Oriented) Design
Quality assurance via process
Test planning, execution and record-keeping
Working to standards
Technical documentation
Version control
Software process
Tools

References:

Boehm, BW, Software Risk Management, IEEE Computer Society Press, Washington, 1989.

Fenton, NE & Pfleeger, S, Software Metrics: A Rigorous and Practical Approach, 2nd edn, Thomson Computer Press, 1996.

Horstmann, C & Cornell, G, Core Java 2, Vols 1 & 2, Sun Microsystems Press Java Series, Prentice-Hall, California, 2002.