Module 18191.1 (2004)
Syllabus page 2004/2005
06-18191
Software Engineering
Level 2/I
Joan Jackson:5
Unknown/Left:5
Peter Coxhead (coordinator)
Links | Outline | Aims | Outcomes | Prerequisites | Teaching | Assessment | Books | Detailed Syllabus
The Module Description is a strict subset of this Syllabus Page. (The University module description has not yet been checked against the School's.)
Changes and updates
New module for 2004/05 (replaces Software Engineering A & B).
Relevant Links
Web page for Joan Jackson's material
Outline
Management of the software development process, including: how projects arise, choosing the right project, software life cycles, human factors in project management, basic project management techniques (e.g. planning, estimating, monitoring progress), advanced project management techniques (e.g. risk management, configuration management, quality management, process improvement). Overview of requirements engineering, requirements elicitation & analysis, requirements definition & specification, requirements validation, requirements management, overview of specification techniques. Object-oriented analysis and design using UML.
Aims
The aims of this module are to:
- show the need for professional discipline and effective management throughout the software development process
- show the importance of teamwork and good interpersonal skills in successful software development
- give an appreciation of the importance of requirements engineering as the first phase of the software development process
- introduce some methods and techniques available to the software engineer for use in the requirements engineering process
- introduce the principles of object oriented analysis and design used by the software engineer to transform the definition of requirements into detailed implementation descriptions
Learning Outcomes
| On successful completion of this module, the student should be able to: | Assessed by: | |
| 1 | explain the basic principles of project management, including the role of the project manager | Continuous assessment, examination |
| 2 | apply standard techniques in project management | Continuous assessment, examination |
| 3 | analyse the organizational issues surrounding the development and implementation of systems solutions | Continuous assessment, examination |
| 4 | identify appropriate interpersonal skills to manage and perform the systems development process more effectively | Continuous assessment, examination |
| 5 | explain the importance of successful requirements definition in commercial software development, identifying the difficulties involved | Continuous assessment, examination |
| 6 | explain and apply appropriate techniques which help to define clear and unambiguous requirements | Continuous assessment, examination |
| 7 | explain and apply the knowledge and skills required to act as a contributing junior analyst in a project team working within a disciplined project environment | Continuous assessment, examination |
| 8 | carry out business analysis and software design using a specified methodology | Continuous assessment, examination |
| 9 | explain current e-commerce terms, applications and packages | Continuous assessment, examination |
| 10 | explain the extra considerations needed to test object-oriented software over and above traditional software testing | Continuous assessment, examination |
Restrictions, Prerequisites and Corequisites
Restrictions:
None
Prerequisites:
06-11224 (Introduction to Software Engineering) (or equivalent)
Co-requisites:
None
Teaching
Teaching Methods:
2 hrs/week, conventional lectures and tutorials.
NOTE: some of the teaching for this module in Semester 2 is likely to take
place outside normal working hours. Students choosing this module as an
option should be prepared for this eventuality.
Contact Hours:
Assessment
- Supplementary (where allowed): As the sessional assessment
- 2 hr examination (50%), continuous assessment (50%). Resit by examination only.
Recommended Books
| Title | Author(s) | Publisher, Date |
| Project Management | Field & Keller | International Thomson Business Press, |
| Software Engineering | Ian Sommerville | Addison-Wesley, |
| Lecture Notes | J Jackson | |
| Object Oriented Systems Analysis and Design using UML | S Benett, S McRobb & R Farmer | McGraw Hill, |
| Object Oriented Systems Development -- A Gentle Approach | C Britton & J Doake | McGraw Hill, |
| Data Warehousing and Business Intelligence for E-Commerce | Alan R. Simon & Steven L. Shaffer | Morgan Kaufmann Publishers, |
Detailed Syllabus
- Introduction to the module (1)
- Project Genesis (2)
- How projects arise, choosing the right project, software life cycles.
- Human Factors in Project Management (3)
- Organizations and players in the game, interpersonal skills, project teams.
- Basic Project Management Techniques (6)
- Planning, estimating, monitoring progress.
- Advanced Project Management Techniques (6)
- Risk management, configuration management, quality management, process improvement.
- Revision Lectures (2)
- Tutorials (4)
- Introduction to coursework, review of completed coursework.
- Overview of Requirements Engineering (2)
- Processes, the requirements document
- Requirements Elicitation & Analysis (2)
- Techniques, prototyping, analysis and negotiation
- Requirements Definition & Specification (2)
- Functional and non-functional requirements
- Requirements Validation (1)
- Reviews, prototyping, validation, testing
- Requirements Management (1)
- The need for change, change management
- Overview of specification techniques (1)
- Objects, functions, formal methods
- Revision Lecture (1)
- Tutorials (2)
- Introduction to coursework, review of coursework
- Introduction to E-commerce and Business Analysis
- Fundamental E-commerce Concepts (B2C, B2B, B2G, G2C, B2E, C2C)
- Business Analysis elicited from Customised E-commerce Development Tools (IBM WebSphere, Microsoft Site Server 3.0, Macromedia Allaire Cold Fusion)
- Business Analysis elicited from Commercial E-Commerce Solutions (Vignette, Business Objects Ithena and Revenio)
- Object Oriented Systems Analysis using UML (2)
- Class diagram, CRC cards, aggregation, association, multiplicity, inheritance
- Object Oriented Systems Design using UML (2)
- Use cases, scenarios, sequence diagrams, state charts
- Object Oriented Systems Implementation and Testing (2)
- How to map an OO Design model onto a relational database schema model
- Black box, white box, unit, integrated and system testing
- Special considerations for testing OO software
- Introduction and Terms of Reference to assessed Case Study Assignment (2)
Last updated: 24 Mar 2004
Source file: /internal/modules/COMSCI/2004/xml/18191.xml
Links | Outline | Aims | Outcomes | Prerequisites | Teaching | Assessment | Books | Detailed Syllabus