Skip to Content

Future Students - Courses

click here for a printable version of this page  

Software Engineering Project B

Unit Code: HIT3258




Duration

Contact Hours

Campus

Prerequisite

Corequisite

1 Semester or equivalent

48 hours

Hawthorn, Sarawak

HIT3158 Software Engineering Project A passed in the same calendar year

Nil

Credit Points: 12.5 Credit Points

Related Course/s:

Back to Top

Aims & Objectives:

This is the second 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

Back to Top

Teaching Methods:

Lectures (24 hrs), Regular contact with Supervisor and Project Team Sessions (24 hrs)

Back to Top

Assessment:

Group Project, Individual work

Back to Top

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

Back to Top

Content:

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

Back to Top

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.

Back to Top