Chapter 19, Requirements Facets Video Solutions, Software Engineering 3: Domains, Requirements, and Software Design

Problem 1

An Incomplete Container Terminal Terminology. We refer to Example 19.3. There are two versions of this exercise: an informal version and a formal version.
$\bullet$ Informal version: Please define all sorts, that is, the abstract types, and please state signatures of all functions mentioned in Example 19.3. Then rephrase a selection of some 10 terms.
$\bullet$ Formal version: First, solve the above informal version exercise. Then, formalise the chosen selection of terms.

Check back soon!

Problem 2

Domain Instantiation: Local Regional Railway Nets. We refer to Example 19.15. Please read that example carefully. The problem is to formalise that example's description of a simple railway net. We ask for a solution which simply takes the railway net formalisations shown in Vol. 2, Chaps. 2 and 10, and imposes further, constraining axioms.

Check back soon!

00:35

Problem 3

Domain Requirements: Fitting. We refer to Example 19.18. Please provide formal models of the domain, the two original requirements, and the $2+1$ revised original + shared domain requirements outlined in Example 19.18 .

Srilakshmi E K

Numerade Educator

Problem 4

Domain Requirements. For the fixed topic, selected by you, you are to suggest some two to three distinct domain requirements. Outline (informally, and/or formally) for each of the distinct domain requirements how they are projected, and/or made more deterministic, and/or instantiated, and/or extended, and/or fitted (the latter with some other requirements that you have to postulate) with respect to your narrative domain description given earlier (as answers to Exercises 11.1-11.7.)

Check back soon!

Problem 5

Interface Requirements. For the fixed topic, selected by you, and for the domain requirements that you have established in Exercise 19.4, identify shared phenomena and shared concepts, and suggest at least four distinct interface requirements, one each from the possible set of six possibilities covered in Sects. 19.5.4-19.5.9.

Check back soon!

Problem 6

Machine Requirements. For the fixed topic, selected by you,, and for the domain requirements that you have established in Exercise 19.4, suggest at least one machine requirement from each of the five kinds outlined in Sects. 19.6.3-19.6.4 and 19.6.6-19.6.8

Check back soon!

Problem 7

Container Terminals: A Preliminary (Flat) Formal Domain Model. We refer to Example 19.1. Based on what is described in the referenced example, please propose a formal model of container terminals. You may wish to formulate the solution in flat RSL, i.e., without the use of the scheme, class and object constructs of RSL. See Exercise 19.9.

Check back soon!

Problem 8

Container Terminals: A Preliminary (Flat) Formal Requirements Model. We refer to Example 19.2. Based on what is described in the referenced example, please propose a formal model of indicated requirements for software for ship container loading plans. If you chose to formulate the solution to Exercise 19.7 in flat RSL, i.e., without the use of the scheme, class and object constructs of RSL, then you may choose to do likewise for the present exercise.

Check back soon!

Problem 9

Container Terminals: Modular Formal Domain Model. We refer to Exercise 19.7. If you already expressed the solution to that exercise using the scheme, class and object constructs of RSL, then that could be a solution to the present exercise. Otherwise, please rephrase your solution to Exercise 19.7 using these modular constructs of RSL.

Check back soon!

Problem 10

Container Terminals: Modular Formal Requirements Model. We refer to Exercise 19.8. If you already expressed the solution to that exercise using the scheme, class and object constructs of RSL, then that could be a solution to the present exercise. Otherwise, please rephrase your solution to Exercise 19.8, based on your solution to Exercise 19.9, by, preferably, using the schema calculus constructs of extension (with), hiding (hide), etc., of RSL.

Check back soon!

02:58

Problem 11

Rail Net and Unit Data Structure Initialisation. We refer to Example 19.22. Please read that example carefully. Suggest a context in which the initialisation takes place: Awareness of the geography, through some cartographic and/or geodetic map representation. Then complete the narrative and formalise what is indicated in Example 19.22.

Kelsey Dondelinger

Numerade Educator

02:58

Problem 12

Rail Net and Unit Data Structure Refreshment. We refer to Example 19.23. Please read that example carefully. Suggest a context in which the refreshment takes place: awareness of the geography, through some cartographic and/or geodetic map representation - as well as some already existing state. Then complete the narrative and formalise what is indicated in Example 19.23.

Kelsey Dondelinger

Numerade Educator

04:20

Problem 13

Banking Script Language. We refer to Example 19.9 - and all of the examples referenced initially in Example 19.9. Redefine, as suggested there, the banking script language to allow such transactions as: (i) merge two mortgage accounts, (ii) transfer money between accounts in two different banks, (iii) pay monthly and quarterly credit card bills, (iv) send and receive funds from stockbrokers, etc.

Jennifer Stoner

Numerade Educator

Problem 14

Computational Data and Control Interface. We refer to Example 19.24. You are to sketch, using RSL/CSP, a formalisation of that example in terms of two processes: the user and the referenced software package. By sketching we mean that basically only (i) the type of messages sent between these processes, and (ii) the RSL/CSP input/output clauses that outline the interaction, are defined. What leads the computation (based on the software package) to decide when and where to interact with the user is not to be specified, only that the interaction occurs.

Check back soon!

00:41

Problem 15

A 24-hour Crane Behaviour. We refer to Example 19.1. You are to come up with a rough sketch, a description and a prescription of what you can logically think of as a factual, respectively a desirable 24-hour behaviour of a ship/shore (i.e., quay) container crane.

Nick Johnson

Numerade Educator

01:35

Problem 16

A 24-hour Container Truck/Chassis Behaviour. We refer to Example 19.1. You are to come up with a rough sketch, a description and a prescription of what you can logically think of as a factual, respectively a desirable 24-hour behaviour of a container truck/chassis.

Supratim Pal

Numerade Educator