Documente Academic
Documente Profesional
Documente Cultură
5.
not partitionable
more
T software development
I
M
perfectly partitionable
E
less
few many
PEOPLE
6. a.
1
T2
4
2 2
T1
T3 T5
start finish
7 4
T4 T6
2
b. start -> T4 -> T6 -> finish
c. T2: 4, T3: 1, T6: 0
8. Domain experts may not communicate such requirements because they are
so obvious (to the experts). Hence, they sometimes remain unspoken as
“implicit” requirements.
12. Such methods rely on contracts where the customer pays for the time and
resources required for system development rather than the development
of a system meeting a specific set of requirements. This can result in
problems if disputes arise over who is to blame and who should pay for
the extra time and resources needed to correct problems.
b. Define an axiom which sets out what is always true for each
inspection operation over each (primitive) constructor operation.
16. a. pre-condition: N ≥ 1
post-condition:
b. FOUND := false
J := 1
While (NOT FOUND and J <> N+1) do
If LIST[J]=KEY then
FOUND := true
Else
J := J+1
End_if_else
End_while
c. Suppose the values of LIST are [-3, 2, 5, 17] and the value of KEY
is 5. After execution of the program, the value of FOUND is true
and the value of J is 3; The values of LIST and KEY are [-3, 2, 5,
17] and 5.
17. Inner layers may provide basic facilities, such as file management,
that are required at all levels. Allowing direct access to these
facilities subverts the model. Performance can also be a problem
because of the multiple levels of command interpretation that may be
required.
b. Advantages:
Disadvantages:
c.
Thin-client model – the application logic and data management
are implemented on the server; clients only handle the user
interface.
Fat-client model – the server is only responsible for data
management; clients handle the application logic and the user
interface.
20. Objects that provide services have IDL skeletons that link their
interface to an implementation. Calling objects have IDL stubs for
every object being called. The calling object binds an IDL stub that
defines the interface of the called object. Calling this stub results
in calls to the ORB which then calls the required object through a
published IDL skeleton that links the interface to the service
implementation.