Dr Keith Phalp: Teaching Notes and Materials
| Home | Publications | Research & CV | Projects | Teaching |
| |
Dr Keith Phalp: Teaching Notes and Materials |
||||
|
My part of the unit concentrates upon the early requirements activities. Hence we revisit what we mean by requirements, consider the need to model the problem domain, and introduce process modelling as one way to support understanding of the client business process.
I envisage covering topics 1-6, with two sessions per week, though we may spend more practical time on process modelling.
Week |
Overview of Content and Link to Notes |
1 |
The Problem with requirements. This lecture gives an overview of the main themes of this part of the unit, revisits what we mean by requirements, and specification, adopts some definitions, and considers the implications of these definitions. Exercise: Types of Requirement. ADDITIONAL MATERIAL:
Analysis (the trouble with) & approaches
to analysis. This follows from our understanding of th requirements
phase, and examines issues with current approaches. That is, now that
we understand what requirements analysis should be, we can evaluate the
strength, or otherwise, of existing approaches. |
2 |
Process Models, Roles and Role Activity Diagrams (RADs) . An exercise for drawing RADs. A purist solution (Don't look). Further examples of Role Activity Diagrams. Some further alternative RADs, v1 & v2, and the process description. An optional addition: enactable role models. ADDITIONAL MATERIAL: A review of use cases and Use case Descriptions. |
3 |
Moving from Process Models to Use Cases. Practical approach. You can also read some further theoretical perspectives in the following slides. aligning Process models (domain) and specification (as use cases). A concise view: Business process models & Use Cases. A further view, Ali's slides. incorporating requirements (and process models) within an MDA framework. A more positive treatment on moving from process models to augmented use cases: Dependencies in Use Cases Use Case Rules and Guidelines. A presentation to SQM 2006 on emprical studies of guidelines. A paper on the basis for guidelines, and one on their assesment. A further presentation on the problems with guidelines and issues for empirical studies, which was given as part of the the Departmental Research Seminar Series, and which can be used to inform research methods. Business Processes and Requirements: Part Two of the CourseworkAssignment 2009/10A word about the agile game.
|
4 |
Alignment. (An overview, of the early ideas of: Process Oriented Requirements Engineering). Requirements Engineering for Business Need and IT Alignment. 1st REBNITA workshop. REBNITA home page, and REBNITA proceedings. Variations on the move from Process Model to Problem Frames . REFSQ03, position paper and presentation. Journal papers: Deriving requirements from process models, Requirements Engineering for E-business advantage, and Business Systems Context and Process (B-SCP). Shows development from position paper, and increasing focus on integration of strategy. Progression of problems and problem frames for alignment. How these ideas can be seen in current approaches. MDA and Stakeholders in the requirements process |
These resources are to support the guest lecture as part of the final year Management in Computing unit (and the Masters unit in Software Project Management). An overview of estimation and prediction in Computing, the major approaches to estimation and their strengths and weaknesses, along with some descriptions of recent research work undertaken within the group. Lecture: Estimation and Prediction in Computing
Some slides describing an earlier study (with previous Masters students) where the Delphi technique (to support prediction using collaborative expert judgement): Delphi Approach.
Topic |
Overview of Content and Link to Materials |
1 |
|
2 |
Analysis (the trouble with) & approaches to analysis. Exercise: Types of Requirement |
3 |
Problem Frames. An exercise on identifying problem frames. Some suggested answers.(Masters topic only) |
4 |
Process Models, Roles and Role Activity Diagrams (RADs) . An exercise for drawing RADs. A purist solution (Don't look). Further examples of Role Activity Diagrams. Some further alternative RADs, v1 & v2, and the process description. (An extension to these ideas, enactable role models). |
5 |
An introduction to use cases |
6 |
Use case Descriptions |
7 |
Use Case Rules and Guidelines. A presentation to SQM 2006 on emprical studies of guidelines. A paper on the basis for guidelines, and one on their assesment. |
8 |
|
9 |
Isssues in aligning Process models (domain) and specification (as use cases). Another view: Business process models & Use Cases. A more positive view of the same issues from Rebnita05. |
10 |
Comprehension in Use Cases. (Optional) |
11 |
MDA and Stakeholders in the requirements process |
12 |
Alignment. (An overview, of the early ideas of: Process Oriented Requirements Engineering). Requirements Engineering for Business Need and IT Alignment. 1st REBNITA workshop. REBNITA home page, and REBNITA proceedings. Variations on the move from Process Model to Problem Frames . REFSQ03, position paper and presentation. Journal papers: Deriving requirements from process models, Requirements Engineering for E-business advantage, and Business Systems Context and Process (B-SCP). Shows development from position paper, and increasing focus on integration of strategy. Progression of problems and problem frames for alignment. A web services example. Student presentations on selected alignment papers from REBNITA |
| 13 |
