Module 11580 (2002)
Syllabus page 2002/2003
06-11580
Software Engineering B
Level 2/I
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.)
Relevant Links
Outline
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:
- 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 | demonstrate an understanding of the importance of requirements definition in commercial software development | Continuous assessment, examination |
| 2 | identify the difficulties involved in successful requirements definition in a commercial environment | Continuous assessment, examination |
| 3 | demonstrate an understanding of appropriate techniques which help to define clear and unambiguous requirements | Continuous assessment, examination |
| 4 | demonstrate 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 |
| 5 | carry out business analysis using a specified methodology | Continuous assessment, examination |
| 6 | demonstrate an understanding of current e-commerce terms, applications and packages | Continuous assessment, examination |
| 7 | 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-08755 (Introduction to Software & Hardware Engineering B) OR 06-11224 (Introduction to Software Engineering)
Co-requisites:
06-11579 (Software Engineering A) (linked module)
Teaching
Teaching Methods:
2 hrs/week, conventional lectures and tutorials.
NOTE: some of the teaching for this module 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%), divided equally between this module and 06-11579 (Software Engineering A). Resit by examination only.
Recommended Books
| Title | Author(s) | Publisher, Date |
| Software Engineering | I Sommerville | Addison-Wesley, 2001 |
| 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
-
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 course work, review of course work
- Introduction to E-commerce and Business Analysis
- Fundamental E-commerce Concepts (B2C, B2B, B2G, G2C, B2E, C2C)
- Business Analysis illicited from Customised E-commerce Development Tools (IBM WebSphere, Microsoft Site Server 3.0, Macromedia Allaire Cold Fusion)
- Business Analysis illicited 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: 21 January 2003
Source file: /internal/modules/COMSCI/2002/xml/11580.xml
Links | Outline | Aims | Outcomes | Prerequisites | Teaching | Assessment | Books | Detailed Syllabus