Base Knowledge
Software Engineering.
Software Modeling and Design.
UML Language.
Teaching Methodologies
The unit includes theoretical and practical classes.
In the theoretical classes, methodologies and case studies are presented.
The practical classes focus on solving exercises and developing a requirements specification project.
Learning Results
This course aims to develop skills for software engineering requirements (RE). The main objectives are:
– Acquisition of theoretical and practical knowledge in the field of requirements engineering;
– Know and apply advanced requirements analysis techniques;
– Solve real world problems.
The main skills to be acquired are:
– Know to analyze a problem, identify its characteristics and design a software requirements specification (SRS);
– Recognize the advantages and limitations of using RE methodologies;
– Develop autonomously new strategies;
Program
1. Introduction and overview
2. Requirements Engineering Processes
3. Requirements Elicitation
4. UX analysis
5. Requirements negotiation
6. Documentation
7. Requirements Validation
8. Requirements Management
9. Traceability
10. Requirements Engineering in Agile UX
11. Defining requirements according to “points of view
12. Requirements for interactive systems
Curricular Unit Teachers
Internship(s)
NAO
Bibliography
Main:
Benyon, D. (2014). Designing interactive systems: A comprehensive guide to HCI, UX and interaction design, 1A-12-175 (ISEC) – 16890
Wiegers, K., & Beatty, J. (2013). Software requirements. Pearson Education. 1A-7-58 (ISEC) – 13424
Kotonya, G., & Sommerville, I. (1998). Requirements engineering: processes and techniques. John Wiley & Sons, Inc..1A-7-74 (ISEC) – 14675
Graham, I. (2008). Requirements modelling and specification for service oriented architecture. John Wiley & Sons.1A-7-84 (ISEC) – 14948
Complementary:
Lutowski, R. (2016). Software requirements: encapsulation, quality, and reuse. Auerbach Publications.
Wiegers, K., & Beatty, J. (2013). Software requirements. Pearson Education.
Cohn, M. (2004). User stories applied: For agile software development. Addison-Wesley Professional.
Leffingwell, D., & Widrig, D. (2000). Managing software requirements: a unified approach. Addison-Wesley Professional.
Sommerville, I. (2001). Quality Management. Sommerville, I., Software Engineering, 6th ed., Addison-Wesley, 535-556.
Hull, E., Jackson, K., & Dick, J. (2005). Requirements engineering in the solution domain (pp. 109-129). Springer London.
Fowler, M. (2004). UML distilled: a brief guide to the standard object modeling language. Addison-Wesley Professional.