TRON06023 2013 Software Engineering

General Details

Full Title
Software Engineering
Transcript Title
Software Engineering
Code
TRON06023
Attendance
N/A %
Subject Area
TRON - Electronics
Department
MENG - Mech. and Electronic Eng.
Level
06 - NFQ Level 6
Credit
05 - 05 Credits
Duration
Semester
Fee
Start Term
2013 - Full Academic Year 2013-14
End Term
9999 - The End of Time
Author(s)
Ian Craig
Programme Membership
SG_EELEC_C06 201500 Higher Certificate in Engineering in Engineering in Electronics SG_ETRON_B07 201600 Bachelor of Engineering in Electronic Engineering SG_EELCO_B07 201700 Bachelor of Engineering in Electronic and Computer Engineering SG_EELCO_C06 201700 Higher Certificate in Engineering in Engineering in Electronic and Computer Engineering SG_EELCO_C06 201800 Higher Certificate in Engineering in Electronic and Computer Engineering SG_EELCO_B07 201800 Bachelor of Engineering in Electronic and Computer Engineering
Description

This is a module for programmers and electronic engineering students which the learners acquire experience  in well established software engineering principles and practices using a project based approach.

The learner will learn how to take a business case and turn it into a Requirement's Document.  They will produce a Design Specification for a project, implement a project (using code inspections), test a project (unit test and system test) and release a project. 

Learning Outcomes

On completion of this module the learner will/should be able to;

1.

Identify the main aspects of a software engineering project.

2.

Compose a requirements specification consisting of normal and error use cases and project requirements to a given template for a set of business cases/project briefs.

3.

Develop a design and produce a Design/Functional Specification for an engineering/software based on the requirements

4.

Participate and minute a code inspection during the implementation phase of a engineering/software project

5.

Design, execute and  record a set of unit tests for a unit of an engineering/software project.

6.

Interpret a set of test results and formulate feedback to the implementation personnel.

7.

Organise the release the engineering/software project.  This will include version assignment, user documentation and acceptance testing of finished system against the requirements specification

Module Assessment Strategies

Assessment is via

1) Written mid term exam

2) Continuous Assessement (Project Participation)

3) Final Written Exam

Indicative Syllabus

 

Requirements Specification

  • Taking a business case or project brief and understanding what needs to be done
  • Writing a normal use case
  • Write any probable or obvious error use cases
  • Writing a Requirement Specification based on a given template using 'will/must', 'should', 'could/may' language.
  • Maintaining correct revision numbering/history of all documents
  • Peer Review of specifications

 

Design Specification

  • Working out how a design will work
  • Producing a Design or Functional Specification, considering User Interaction, Hardware, Software, Quality, Performance, Safety and Ethical issues.

Code/Project Implementation

  • Software versioning systems (svn, cvs, etc)
  • Code inspections

Testing (unit/system)

  • Designing a robust and comprehensive set of Unit tests for a project unit based on inputs, expected outputs and actual outputs.
  • Executing and recording unit test results
  • Automating Unit testing

Release control

  • Software control
  • Versioning
  • User manuals
  • Acceptance testing system against the Requirement Specification

Coursework & Assessment Breakdown

Coursework & Continuous Assessment
40 %
End of Semester / Year Formal Exam
60 %

Coursework Assessment

Title Type Form Percent Week Learning Outcomes Assessed
1 Project Evaluation of participation in project Continuous Assessment Practical Evaluation 30 % OnGoing 2,3,4,5,6,7
2 Other Exam Mid term written test Continuous Assessment Assessment 10 % Any 1,2,5
             

End of Semester / Year Assessment

Title Type Form Percent Week Learning Outcomes Assessed
1 Written Exam Final Exam Closed Book Exam 60 % End of Term 1,2,3,4,5,6,7
             
             

Full Time Mode Workload


Type Location Description Hours Frequency Avg Workload
Lecture Engineering Laboratory Lecture/Project work 2 Weekly 2.00
Laboratory Practical Engineering Laboratory Practical/Project Work 2 Weekly 2.00
Total Full Time Average Weekly Learner Contact Time 4.00 Hours

Part Time Mode Workload


Type Location Description Hours Frequency Avg Workload
Lecture Not Specified Lecture/Project work 2 Weekly 2.00
Problem Based Learning Not Specified Practicals 2 Weekly 2.00
Total Part Time Average Weekly Learner Contact Time 4.00 Hours

Module Resources

Non ISBN Literary Resources

Software Engineering (Latest Edition), Ian Sommerville

Other Resources

Electronic Component Kit for project is advisable for learners.

Additional Information

It would be highly advantagous that the this module was delivered in a second year of a programme.

The learner should have basic programming skills prior to commencement.