Overvie of CORE Methodology

Overview of CORE Methodology
Controlled Requirement Expression (CORE) was developed for the British Aerospace programs while the UK Ministry of Defence was carrying out a requirement analysis (Hull et al., 2010). The fundamental component of the CORE methodology is viewpoints as different users see systems in different ways. There are many different stakeholders involved in a system; using CORE methodology involves finding all the different viewpoints of those stakeholders that have an interest in the system whether it’s a person, role or organisation ext.… (Sommerville and Sawyer, 2000). By organising viewpoints hierarchy it assists experts to read the scope and supports the analysis process. CORE Methodology is extensively used for real time system requirements specification.

Stage 1: CORE Viewpoint Bubble Diagram
Bubble diagrams exhibit different viewpoints of a system including all function and non-function reflected from all stakeholders’ viewpoints. Once all viewpoints are identified this permits an expert to partition the viewpoint into clusters in the next stage.
CORE Viewpoint Bubble Diagram for the FASAM system below:

Stage 2: CORE Viewpoint Clusters
Stage 2 involves dividing viewpoints documented in the first stage into clusters. This allows experts to organize functions/non-functions based on viewpoints. Which makes it easier to read of the page and neater. Furthermore, it helps the expert create a CORE viewpoint hierarchy. Example Below:

Stage 2a: Bounding and Defining Viewpoints

Stage 3: CORE Viewpoint Hierarchy
Stage 3 involves creating an Architectural Model version of the whole system including sub systems. A Viewpoint Hierarchy shows a skeleton version of the system which can be ins...

... middle of paper ...

...
Tabular Collection Diagram shows the process of the system, so it helps identify risks or problems in a system early on. Tabular Collection Diagram put requirements to the test and enables you to see if more requirements are desirable. A brilliant method to discover problem’s in the earlier stages of development.
Node Notes

Action Diagram

Works Cited

Hull, E., Jackson, K. and Dick, J. (2010) Requirements Engineering. 3rd ed. London: University of Ulster.
Kotonya, G. and Sommerville, I. (1998) Requirements engineering: processes and techniques. London: J. Wiley.
SINTEF and Kresken, T. (2010) Technology Briefing Report. System Modelling. 10 31, pp.1-9.
Sommerville, I. and Sawyer, P. (2000) Requirements Engineering: A good practice guide. Chichester: Lancaster University.
Sommerville, I. (2007) Software Engineering 8. 8th ed. London: Addison-Wesley Publishers.