COMP06174 2018 Requirements Engineering

General Details

Full Title
Requirements Engineering
Transcript Title
Requirements Engineering
Code
COMP06174
Attendance
N/A %
Subject Area
COMP - Computing
Department
COEL - Computing & Electronic Eng
Level
06 - NFQ Level 6
Credit
05 - 05 Credits
Duration
Semester
Fee
Start Term
2018 - Full Academic Year 2018-19
End Term
9999 - The End of Time
Author(s)
Mr. John Kelleher, Paul Powell, Vivion Kinsella, Keith McManus, Therese Hume
Programme Membership
SG_KGAME_C06 201800 Higher Certificate in Science in Games Development SG_KGADV_B07 201800 Bachelor of Science in Computing in Games Development SG_KSODV_C06 201800 Higher Certificate in Science in Software Development SG_KSODV_H08 201900 Bachelor of Science (Honours) in Computing in Software Development SG_KCMPU_H08 201900 Bachelor of Science (Honours) in Computing SG_KCMPU_C06 201900 Higher Certificate in Science in Computing in Computing SG_KCMPU_B07 201900 Bachelor of Science in Computing in Computing SG_KSODV_B07 201900 Bachelor of Science in Computing in Software Development
Description

This module sets the broader context for software development by giving an overview of alternate system development life cycles and  focuses on  the gathering, analysis and validation of software requirements using agile and more conventional methods. Using a practical approach, methods for requirements elicitation and documentation are introduced and explored through practical case work.  Requirements documentation and modelling, using a range of techniques such as user stories and object oriented analysis techniques are also addressed.  

Learning Outcomes

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

1.

Elicit user requirements

2.

Document user requirements

3.

Analyse and detail user requirements using a range of methods

4.

Apply theory to practical problems.

Teaching and Learning Strategies

The module will build skills through the continuous application of theoretical material to practical problems and scenarios in  weekly lab-based workshops. Students will be encouraged to work in groups and to peer-assess each other. Formative feedback can be given through these workshops. 

Module Assessment Strategies

Students will be assessed through the application of the techniques in a two stage practical project which will involve requirements elicitation, documentation and analysis using methods and diagramming techniques as described in the indicative syllabus above. Understanding of theoretical concepts will be assessed via an end of module examination.

Repeat Assessments

Repeat exam and/or  project work.

Indicative Syllabus

Context

Describe alternate software development life-cycles (waterfall, agile, BDD)and recognise the stakeholders involved.

 Elicit User Requirements 

  • Techniques for gathering user requirements involving conversations and interviews
  • The role of documents and existing systems to add more detail to requirements and provide examples

Document (and Validate) User Requirements 

  • Requirements documentation using user stories, scenario descriptions and acceptance criteria and tests.
  • UML Requirements documentation -use cases (diagrams / templates).
  • Validating requirements.

Analyse (and Verify) User Requirements 

  • Object oriented modelling : UMl Class diagramsIdentifying entity classes and Relationships
  • Methods for further analysis : detailed class diagrams, inheritance, robustness diagrams, method specification 
  • Dynamic vs static views of system : sequence diagrams, state control diagrams
  • Reviewing/verifying requirements.

Apply Theory to Practical Problems 

The module will build skills through the continuous application of theoretical material to practical problems and scenarios.

Coursework & Assessment Breakdown

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

Coursework Assessment

Title Type Form Percent Week Learning Outcomes Assessed
1 Group Project part 1 Continuous Assessment Project 30 % Week 9 1,2,4
2 Group Project Part 2 Continuous Assessment Project 20 % Week 13 2,3,4
             

End of Semester / Year Assessment

Title Type Form Percent Week Learning Outcomes Assessed
1 Final Exam Final Exam Closed Book Exam 50 % End of Term 1,2,3,4
             
             

Required & Recommended Book List

Recommended Reading
2015-09-11 Beyond Requirements: Analysis with an Agile Mindset (Agile Software Development) Addison Wesley
ISBN 0321834550 ISBN-13 9780321834553

Beyond Requirements

Recommended Reading
2010-04-16 Object-Oriented Systems Analysis and Design Using UML McGraw-Hill Education / Europe, Middle East & Africa
ISBN 0077125363 ISBN-13 9780077125363

The fourth edition of "Object- Oriented Systems Analysis and Design" has been revised and updated to reflect the most up-to-date approaches to information systems development. Still a best-seller in its field, Bennett's, McRobb's and Farmer's text remains a key teaching resource for Systems Analysis and Design courses at both undergraduate and postgraduate level. The book provides a clear, practical framework for development that uses all the major techniques from UML 2.2. It follows an iterative and incremental approach based on the industry-standard Unified Process, placing systems analysis and design in the context of the whole systems lifestyle. Structured in four parts, the first provides the background to information systems analysis and design and to object-orientation. The second part focuses on the activities of requirements gathering and systems analysis, as well as the basic notation of UML. Part three covers the activities of systems architecture and design, and UML notation for object design, and the book concludes with the implementation of systems and the issues of how the systems life cycle is organized and how reusable components can be developed.

Module Resources

URL Resources

There are a wide range of websites and blogs e.g. 

agilealliance.org

mountaingoat software.com (Mike Cohn)

omg.org

 

Other Resources

Examples  and lecture slides on Moodle.

Additional Information

None